Red Hat Bugzilla – Bug 1316604
Update with content hosts no longer in candlepin breaks the migration
Last modified: 2016-07-27 07:03:14 EDT
If you have some hosts no longer in Candlepin and Katello didn't keep track of it, the migration that creates content host facets will fail. Instead, we should avoid creating these facets for hosts whose UUID 404s on Candlepin.
Created from redmine issue http://projects.theforeman.org/issues/13856
Upstream bug assigned to firstname.lastname@example.org
Upstream bug component is Candlepin
PR - https://github.com/Katello/katello/pull/5867
Moving to POST since upstream bug http://projects.theforeman.org/issues/13856 has been closed
Applied in changeset commit:katello|6d6ad9287802cfdd0a2dfdc2ae50db96366bb2dd.
Hey Walden, Could you please provide steps to verify this bz ?
(In reply to Sachin Ghai from comment #7)
> Hey Walden, Could you please provide steps to verify this bz ?
This is a bad bug report (especially for someone who spent many years as a QA Engineer) and I'd be happy to add some steps to reproduce. This is an issue we ran into in the wild so I'm not entirely sure how the user got into the state they were in.
Steps to Reproduce:
1. Find or create a host that only exists in the katello database and not in candlepin. You could maybe do this using SQL. Either creating a host row manually in the katello datebase or creating a host regularly and then removing it from the candlepin database.
2. Run the migration and not the above failure
I'm sorry these steps to reproduce aren't as precise as either you or I would like but we aren't really sure how the user got into this state.
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.