Bug #26253
Compute profile settings do not get transported during upgrade from Satellite 6.3 to 6.4
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1650624
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
Associated revisions
History
#1
Updated by The Foreman Bot 9 months ago
Updated by - Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/6542 added
#2
Updated by Tomer Brisker 9 months ago
Updated by - Assignee set to Shira Maximov
- Category changed from Unattended installations to DB migrations
- Fixed in Releases 1.22.0 added
#3
Updated by Shira Maximov 9 months ago
Updated by - Status changed from Ready For Testing to Closed
Applied in changeset d20591b3bd011d8320c43055b504525aefb8483d.
#4
Updated by The Foreman Bot 9 months ago
- Pull request https://github.com/theforeman/foreman/pull/6610 added
Fixes #26253 - fix the format of serialized attributes
In a past migration hash-with-ivars objects were incorrectly converted to hash leading to extraneous elements in the hash.