Host API update without compute attributes triggers vm update
When changing the content view of a host in Katello, Katello issues an update via api v2 to /api/v2/hosts/23789 with payload:
This fails because Foreman tries to schedule a compute orchestration.
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.