Description of problem: After upgrading Satellite from satellite 6.3.to 6.4. Compute Profile still lists the old resources assignments that were configured in Satellite 6.3 but VMs that are newly built using that compute profile has only 1 CPU and 2048GB. Also, compute profile overview page shows proper VM Attributes(resources assignments) but after clicking on the compute resource it shows CPU = 1 and memory = 2048GB. Please see the screenshots for more details. Version-Release number of selected component (if applicable): Satellite 6.4 Steps to Reproduce: 1. On satellite 6.3 create the compute profiles with some random resources assignments 2. Upgrade the satellite to 6.4. 3. Try to provision VM using old compute profiles. Actual results: VM is created with 1 CPU and 2048GB Memory. Expected results: It should create the VM according to the resources assignments of compute profile which was created in satellite 6.3
Created attachment 1506466 [details] screenshot1
Created attachment 1506467 [details] screenshot2
Created redmine issue https://projects.theforeman.org/issues/26253 from this bug
Connecting redmine issue http://projects.theforeman.org/issues/26253 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26253 has been resolved.
There was an error in the vars name, We now need that https://github.com/theforeman/foreman/commit/30eec9de62ecf426da5b7abe9d1b6d36de42f20f to be cherry picked, in order to work for all cases.
VERIFIED on upgrade from sat6.4.3 to 6.5.0-21 - pre-upgrade I set the `small` profile to use 3GB of RAM and 2 CPUs. - upgrade went smooth - post-upgrade i checked that the profile is still present - tried to provision a centos host using the `small` profile, the machine got the resources assigned accordingly.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:1222