Bug 1446718 - clean_backend_objects doesn't handle nil subscription_facet uuids properly
Summary: clean_backend_objects doesn't handle nil subscription_facet uuids properly
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Infrastructure
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Jitendra Yejare
Depends On:
TreeView+ depends on / blocked
Reported: 2017-04-28 16:26 UTC by Satellite Program
Modified: 2019-04-01 20:27 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1434609
Last Closed: 2018-02-21 16:54:37 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 18972 0 None None None 2017-04-28 16:26:46 UTC

Comment 3 Jitendra Yejare 2017-12-20 08:57:06 UTC
Verified !

@ Satellite 6.3 snap 29


As per steps in the original bug(https://bugzilla.redhat.com/show_bug.cgi?id=1434609#c6) of this bug.

In the foreman-rake console run the following commands
1. sub = Host.find(ID).subscription_facet
2. sub.uuid = nil
=> nil
3. sub.save
=> true

then run the rake command,

# foreman-rake katello:clean_backend_objects COMMIT=true
=> Host 69 dockhost1 is partially missing subscription information.  Un-registering
1 orphaned consumer id(s) found in candlepin.
0 orphaned consumer id(s) found in pulp


Visiting ContentHost page in Satellite says,
This Host is not currently registered with subscription-manager. Click here for registration information.

Hence changing the state to verified !

Comment 4 Satellite Program 2018-02-21 16:54:37 UTC
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

Note You need to log in before you can comment on or make changes to this bug.