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.
Description of problem:
When upgrading to Satellite 6.2.7, 'unify hosts' runs as part of the upgrade process.
Unfortunately, it does not seem to take into consideration whether or not the host being removed is 'Managed' by the Satellite via a Compute Resource.
This can cause the machine to be destroyed!
Version-Release number of selected component (if applicable): 6.2.7
How reproducible: ? (Have not yet attempted myself, will work on)
Steps to Reproduce:
1. Create system via compute resource, or register with shortname and set to managed.
2. Upgrade / manually invoke unify hosts script
3. Verify host destroyed afterward, check with Monitor -> Audit.
Actual results:
Unify hosts removed managed shortname host, destroyed system.
Expected results:
Unify hosts should handle or ignore managed hosts.
TESTPLAN
* Install Satellite 6.1
* Upgrade to Satellite 6.2
* Ensure you do *NOT* see this message in the satellite.log file in :
/var/log/foreman-installer/satellite.log
[ INFO 2017-01-26 10:41:08 main] Upgrade Step: unify_hosts (this may take a while) ...
if you don't see this message, the rake task was not run and this bug is VERIFIED
Performed upgrade from sat6.1.11 -> sat6.2.7 on rhel7 along w/ following two packages:
-bash-4.2# rpm -qa | grep katello-installer-base
katello-installer-base-3.0.0.71.1-1.el7sat.noarch
-bash-4.2# rpm -qa | grep foreman-installer-katello
foreman-installer-katello-3.0.0.71.1-1.el7sat.noarch
I don't see this "upgrade Step: unify_hosts (this may take a while)" while performing upgrade. Neither on console nor in /var/log/foreman-installer/satellite.log.
upgrade completed immediately after "Upgrade Step: remove_event_queue..."
==
Upgrade Step: remove_event_queue...
Upgrade completed!
==
Performed another upgrade from 6.2.6 -> 6.2.7 on rhel7 along w/
katello-installer-base-3.0.0.71.1-1.el7sat.noarch
foreman-installer-katello-3.0.0.71.1-1.el7sat.noarch
and I don't see the "upgrade Step: unify_hosts (this may take a while)"
Upgrade was completed after db:seed step.
---
out: Upgrade Step: db_seed...
[SAT_SERVER] out: Seeding /usr/share/foreman/db/seeds.d/03-auth_sources.rb
----
<truncate>
[SAT_SERVER] out: Upgrade completed!
----
Performed upgrade from sat6.1.11 -> sat6.2.7 on rhel6
Performed upgrade from 6.2.6 -> 6.2.7 on rhel6
along w/ following two packages:
katello-installer-base-3.0.0.71.1-1.el6sat.noarch
foreman-installer-katello-3.0.0.71.1-1.el6sat.noarch
there was no "upgrade Step: unify_hosts" step while upgrading
satellite.log output for both attached
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-2017:0251