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.

Bug 1622666

Summary: clean_backend_objects does not verify managed host status prior to action
Product: Red Hat Satellite Reporter: Craig Donnelly <cdonnell>
Component: Hosts - ContentAssignee: Justin Sherrill <jsherril>
Status: CLOSED ERRATA QA Contact: Roman Plevka <rplevka>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.2.15CC: aagrawal, egolov, ikanner, inecas, jhutar, jsherril, mmello, rplevka
Target Milestone: 6.4.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-3.7.0.24-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1624028 (view as bug list) Environment:
Last Closed: 2018-10-16 19:20:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Craig Donnelly 2018-08-27 17:23:02 UTC
Description of problem:
The clean_backend_objects rake task does not check to see if a host is managed prior to suggesting a removal of that host, and taking that action - which can result in the deletion of a system if the host is managed and the corresponding setting is enabled in Administer -> Settings -> Content (unregister_delete_host).

Version-Release number of selected component (if applicable): 6.2, 6.3+


How reproducible: 50%? Triggering a host deletion seems to depend on certain circumstances of how the host data is lacking, and clean_backend_objects taking action against that host.


Steps to Reproduce:
1. Have fully registered host that is attached to Compute Resource and set to Managed
2. Remove some piece of host that would be checked by CBO
3. Run CBO

Actual results:
Host is deleted from Satellite and VM is destroyed.

Expected results:
CBO should not remove host that is in a Managed state that would result in it being destroyed, ever.

Additional info:

Comment 1 Craig Donnelly 2018-08-27 17:24:03 UTC
Also ensure 'unregister_delete_host' = true when attempting to reproduce.

Should be able to take a host and destroy its 'subscription_facet' to cause a trigger on CBO and get destroyed during the run.

Comment 4 Satellite Program 2018-09-05 18:10:23 UTC
Upstream bug assigned to jsherril

Comment 5 Satellite Program 2018-09-05 18:10:26 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24812 has been resolved.

Comment 10 Bryan Kearney 2018-10-16 19:20:55 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:2927