Actions
Bug #21956
closedHost API update without compute attributes triggers vm update
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.
Updated by The Foreman Bot about 7 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/5077 added
Updated by Timo Goebel about 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset e653ec5e636ea93d09dfcb08a9de50bff1d9153f.
Updated by Tomer Brisker about 7 years ago
- Translation missing: en.field_release set to 296
Actions