Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1187317 - Deleting hosts from the "All Hosts" listing leaves them as Content Hosts.
Deleting hosts from the "All Hosts" listing leaves them as Content Hosts.
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Content Management (Show other bugs)
6.0.7
Unspecified Unspecified
unspecified Severity low (vote)
: Beta
: Unused
Assigned To: satellite6-bugs
sthirugn@redhat.com
http://projects.theforeman.org/issues...
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-01-29 13:36 EST by Joe Giordano
Modified: 2016-07-27 05:13 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-27 05:13:07 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1501 normal SHIPPED_LIVE Red Hat Satellite 6.2 Capsule and Server 2016-07-27 08:28:58 EDT

  None (edit)
Description Joe Giordano 2015-01-29 13:36:05 EST
Description of problem:
Creating a new host and then deleting the hosts leaves their entry in the content host section and the user has to do an unregister to fully remove the entry. 

Version-Release number of selected component (if applicable):
6.0.7

How reproducible:
Always

Steps to Reproduce:
1. Create a new host.
2. Validate it was provisioned and registered successfully 
3.Click hosts > Content Hosts and validate the entry exists.
4. Go back to Hosts > All Hosts
5. Poweroff (if it is virtual) and delete the host.
6. Go back to Hosts > Content Hosts and validate the existance of the host. 

Actual results:
Host is still listed in the content host listing even after deleting.

Expected results:
Either the host is automatically removed or the user is asked whether they would like to automatically remove the host fromt he Content Hosts/ 

Additional info:
Comment 1 RHEL Product and Program Management 2015-01-29 13:54:49 EST
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Joe Giordano 2015-01-29 14:23:50 EST
This seems to happen specifically when using RHEV/Ovirt images to provision, then powering them off and deleting them.
Comment 4 Tom McKay 2015-02-13 16:08:56 EST
Created redmine issue http://projects.theforeman.org/issues/9384 from this bug
Comment 5 Joe Giordano 2015-02-23 09:35:14 EST
As an additional thought, this issue has the potential to consume subscriptions if users delete from the all hosts and leave the content hosts. Users may have issues provisioning and troubleshooting that as opposed to looking if they are maxed out on subs.
Comment 6 Bryan Kearney 2015-08-25 14:33:14 EDT
Upstream bug component is Content Management
Comment 8 Komal 2015-09-10 04:34:07 EDT
Hello,

After upgrade to satellite 6.1 customer is no longer facing the issue and seems to be fixed. 

Regards,
Komal
Comment 9 Brad Buckingham 2016-03-07 10:51:19 EST
Satellite 6.2 includes a feature referred to as 'host unification'.  With that feature, this behavior should no longer occur. 

Moving bug to ON_QA for verification.
Comment 11 sthirugn@redhat.com 2016-04-04 14:11:51 EDT
Verified in Satellite 6.2-beta-snap-6.1

I did the exact same steps as mentioned in the bug description.  After deleting the host, the host is gone form both 'All Hosts' page and 'Content Hosts' page.
Comment 13 errata-xmlrpc 2016-07-27 05:13:07 EDT
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-2016:1501

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