Project

General

Profile

Bug #21956

Host API update without compute attributes triggers vm update

Added by Timo Goebel almost 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
API
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

When changing the content view of a host in Katello, Katello issues an update via api v2 to /api/v2/hosts/23789 with payload:

{"id":23789,"host":{"subscription_facet_attributes":{"id":87,"autoheal":true,"service_level":"","release_version":"7.4"}}}

This fails because Foreman tries to schedule a compute orchestration.

Logs show:
Scheduling compute instance update because cluster changed it's value from 'Unchanged Value' (String) to 'Undesired Value from Compute Profile' (String)

The API controller sets the compute attributes for the host object with the data from the compute profile. This leads to the unwanted compute orchestration.

Associated revisions

Revision e653ec5e (diff)
Added by Timo Goebel almost 3 years ago

fixes #21956 - apply compute profile only when needed

History

#1 Updated by The Foreman Bot almost 3 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/5077 added

#2 Updated by Timo Goebel almost 3 years ago

  • % Done changed from 0 to 100
  • Status changed from Ready For Testing to Closed

#3 Updated by Tomer Brisker almost 3 years ago

  • Legacy Backlogs Release (now unused) set to 296

Also available in: Atom PDF