Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionDeepannagaraj Nagarathinam
2016-07-15 22:38:58 UTC
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
How reproducible:
- Always
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.
Actual results:
Upgrade process removes the Hypervisor profiles from the Satellite server.
Expected results:
Satellite server should keep the profiles.
Additional info:
- 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.
Summary:
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.
~~~~~~
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/RHBA-2016:1501