Description of problem:
While upgrading the Satellite server from 6.1 to 6.2 (Beta), it removes all the Hypervisor profiles from the Satellite server.
Version-Release number of selected component (if applicable):
- Satellite 6.2 Beta
Steps to Reproduce:
1. Install a Satellite 6.1 Server.
2. Install and configure virt-who (make sure that hypervisor profiles are available).
3. Upgrade the Satellite server to 6.2.
Upgrade process removes the Hypervisor profiles from the Satellite server.
Satellite server should keep the profiles.
- As the hypervisor profiles are removed the derived SKU is also removed.
- It causes the client to use the Temporary subscription.
- And customer has to attach the subscriptions to the Hypervisor profiles again.
While running the pre_upgrade check it returns the warning,
# foreman-rake katello:preupgrade_content_host_check
Calculating Host changes on upgrade. This may take a few minutes.
Content hosts to be preserved: 2
Content hosts to be deleted: 1
Details on Content Hosts planned for deletion saved to /tmp/pre-upgrade-1468612101.csv
You may want to manually resolve some of the conflicts and duplicate Content Hosts.
Upon upgrade those found for deletion will be removed permanently.
# cat /tmp/pre-upgrade-1468612101.csv
uuid, name, hostname, last_checkin, causes for deletion
a4b49ec8-bb33-45d6-aa03-4620e77b9fc1,dca47d81-53d8-11cb-bbeb-b4c1c02ffba4,,2016-07-11T19:57:49.450+0000,Missing hostname information.
Connecting redmine issue http://projects.theforeman.org/issues/15726 from this bug
Upstream bug component is Upgrades
Moving to ASSIGNED, since there is an upstream PR
Verified with upgrade from at6.1.9 -> sat6.2 GA snap21
I can see hypervisor profiles post-upgrade. Please see the attached screenshot.
Created attachment 1182447 [details]
hypervisor profiles post upgrade are visible under content-hosts page
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.