I cloned the bug 1320557 into Satellite 6.2. Even though the code was moved to a different file and it has changed a bit as 6.2 no longer uses elasticsearch, the root of the problem persists. It is still possible that an event form Candlepin comes when the host is already unregistered. app/lib/actions/candlepin/import_pool_handler.rb: def reindex_consumer(message) if message.content['newEntity'] uuid = JSON.parse(message.content['newEntity'])['consumer']['uuid'] subscription_facet = ::Katello::Host::SubscriptionFacet.find_by_uuid(uuid) if subscription_facet.nil? @logger.debug "skip re-indexing of non-existent registered host #{uuid}" else @logger.debug "re-indexing content host #{subscription_facet.host.name}" subscription_facet.update_subscription_status end end end
This is shipping in 6.1.9 and must be fixed in 6.2, marking regression+blocker to ensure it gets fixed.
Please see related bugs https://bugzilla.redhat.com/show_bug.cgi?id=1338578 https://bugzilla.redhat.com/show_bug.cgi?id=1209866 https://bugzilla.redhat.com/show_bug.cgi?id=1244309 https://bugzilla.redhat.com/show_bug.cgi?id=1276241 https://bugzilla.redhat.com/show_bug.cgi?id=1325879 https://bugzilla.redhat.com/show_bug.cgi?id=1212674
Moving 6.2 bugs out to sat-backlog.
Since the elasticsearch was removed in satellite 6.2, this issue was resolved in 6.2 as well
I'm re-opening this. Elasticsearch is gone but the problem actually lied in the code that was triggering ES re-index. Please see my first comment for details: https://bugzilla.redhat.com/show_bug.cgi?id=1325879#c1
Created redmine issue http://projects.theforeman.org/issues/16170 from this bug
Upstream bug component is Content Management
Moving to POST since upstream bug http://projects.theforeman.org/issues/16170 has been closed
Feature worked on Satellite 6.3 snap 18. I've registered a Content Host using AK and it has shown green icon on UI. Just after that I've unsubscribed it and icon changed to red one. Thus I'm moving this BZ to verified.
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/RHSA-2018:0336