Bug #26253


Compute profile settings do not get transported during upgrade from Satellite 6.3 to 6.4

Added by Shira Maximov about 5 years ago. Updated about 5 years ago.

DB migrations
Target version:
Fixed in Releases:
Found in Releases:


Cloned from

Description of problem:

After upgrading Satellite from satellite 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

Actions #1

Updated by The Foreman Bot about 5 years ago

  • Status changed from New to Ready For Testing
  • Pull request added
Actions #2

Updated by Tomer Brisker about 5 years ago

  • Category changed from Unattended installations to DB migrations
  • Assignee set to Shira Maximov
  • Fixed in Releases 1.22.0 added
Actions #3

Updated by Shira Maximov about 5 years ago

  • Status changed from Ready For Testing to Closed
Actions #4

Updated by The Foreman Bot about 5 years ago

  • Pull request added

Also available in: Atom PDF