Bug #26253: Compute profile settings do not get transported during upgrade from Satellite 6.3 to 6.4 - Foreman

Actions

Copy link

Bug #26253

closed

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.

Status:

Closed

Priority:

High

Assignee:

Shira Maximov

Category:

DB migrations

Target version:

Difficulty:

Triaged:

Bugzilla link:

1650624

Pull request:

https://github.com/theforeman/foreman/pull/6542, https://github.com/theforeman/foreman/pull/6610

Fixed in Releases:

1.22.0

Found in Releases:

Red Hat JIRA:

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