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 1618799

Summary: Satellite 6: Removing hypervisor from one host collection will remove hypervisor from all host collections
Product: Red Hat Satellite Reporter: Sunayana <suarora>
Component: Host CollectionsAssignee: Andrew Kofink <akofink>
Status: CLOSED ERRATA QA Contact: Lai <ltran>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.2CC: egolov, jeremy.collins, ltran, suarora
Target Milestone: 6.4.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-3.7.0.27-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 19:19:57 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:
Attachments:
Description Flags
Verify Host collection in Hypervisor none

Description Sunayana 2018-08-17 15:44:28 UTC
Description of problem:

If virt-who hypervisor is part of more than one host collection, if we try to remove it from one host collection, it will be removed from all host collections.

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

Satellite 6.x

Steps to Reproduce:

1. Go to Satellite WebUI --> Hosts --> Content Hosts --> Select any hypervisor --> Host Collections --> Add --> select more than one host collection from list --> Add Selected

2.  Go to Satellite WebUI --> Hosts --> Content Hosts --> Select any hypervisor --> Host Collections --> List/Remove --> Select any one repository to remove --> Remove Selected

Actual results: 
It will remove the virt-who hypervisor from all host collections.

Expected results:
It should remove virt-who hypervisor from host collection which is selected only.

Additional info:

This scenario will work fine when we will remove virt-who hypervisor from host collection as below:

Go to Satellite WebUI --> Host Collections --> Click on host collection from which you want to remove hypervisor --> Hosts --> Select hypervisor --> Remove Selected

This will remove virt-who hypervisor from one selected host collection only.

And it will work fine for content-hosts in both ways.

Comment 6 Andrew Kofink 2018-09-11 20:09:13 UTC
Created redmine issue https://projects.theforeman.org/issues/24905 from this bug

Comment 7 Satellite Program 2018-09-12 20:06:01 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24905 has been resolved.

Comment 10 Lai 2018-09-18 15:49:13 UTC
Created attachment 1484422 [details]
Verify Host collection in Hypervisor

1. Added hypervisor and added 3 host collections to hypervisor.
2. Removed one host collection and the other host collections still remain in the hypervisor.

See attachment for verification.

Verified on snap_6.4.0_22.0

Comment 11 Bryan Kearney 2018-10-16 19:19:57 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