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 1236377 - Disassociate Hosts - possible error
Summary: Disassociate Hosts - possible error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: orabin
QA Contact: Stephen Benjamin
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-28 11:27 UTC by Tzach Shefi
Modified: 2019-09-26 17:38 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:05:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 5707 0 Normal Closed disassociate is highlighted for physical host 2020-10-27 23:57:42 UTC

Description Tzach Shefi 2015-06-28 11:27:17 UTC 
Description of problem: Opted to remove my physical hosts due to a failed deployment, wasn't sure if I should chose "Delete" or "Disassociate".
Any way hitting "Disassociate Hosts" I think I hit a bug on the bottom of the popup page it says-> "Disassociate the selected hosts from their VMs"

Which VM's are we talking about? 
I'm running on physical servers. 

Version-Release number of selected component (if applicable):
ISO with the Media ID 1434638612.868458 

BTW which competent should I search for running  #rpm -qa | grep... ? 
katello maybe as I didn't see anything related to RHCI. 

How reproducible:
Unsure first time I see this.

Steps to Reproduce:
1. Run a deployment on physical hosts, in my case got stuck, a case of another bug. 
2. On hosts menu, select "All hosts"
3. Select Action   ->  "Disassociate Hosts"
4. Notice VM remark on screen. 

Actual results:
See a remark about VM's, which is odd as im not using any VMs.

Expected results:
Come to think of it I'm not sure what should happen, as I clicked submit and nothing happens. Maybe this option is just for VM's? 

So I'll use delete hosts and see what happens.
Comment 1 John Matthews 2015-08-12 18:59:30 UTC 
Please re-test, this sounds like a possible Sat 6.1 issue, not RHCI specific.
Comment 2 Thom Carlin 2015-08-25 11:51:19 UTC 
2A. Select a host (checkbox)
3 [augmented].  Upper-right side "Select Action" -> "Disassociate Hosts"
4. Window pops up with: "Disassociate Hosts - The following hosts are about to be changed".  Click Submit

Actual:
"Updated hosts: Disassociated from VM"

Occurs in tech preview rc-2.

You can re-run command.  Possibly tied to POST /hosts/update_multiple_disassociate?host_ids%5B%5D=<host id>

Foreman associate/deassociate of compute resources?
Comment 3 John Matthews 2015-08-25 12:16:20 UTC 
Thom, 

This sounds like a Sat6 issue and not RHCI specific, do you agree?  If so, please reassign to a Sat6 component.
Comment 5 orabin 2016-03-06 15:06:42 UTC 
Created redmine issue http://projects.theforeman.org/issues/14062 from this bug
Comment 6 orabin 2016-03-07 09:01:54 UTC 
The problem here is that you shouldn't see physical hosts when disassociating so the disassociate button should be disabled when editing a host and the multiple actions should show that some of the selected hosts can't actually be disassociated.
I updated the redmine issue because there was already a bug open about the button showing up for all hosts.
Comment 7 Bryan Kearney 2016-03-07 11:07:54 UTC 
Upstream bug component is WebUI
Comment 9 Bryan Kearney 2016-04-06 18:08:05 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/5707 has been closed
-------------
Ori Rabin
Applied in changeset commit:5a9ad12fac51ae40732de587db9f1d965b8d64a1.
Comment 10 orabin 2016-04-06 20:25:11 UTC 
This bug had another fix related that was applied in: 19df8e105bcb53f1e04fdf08fd2217350e1b90f5
Comment 11 Stephen Benjamin 2016-07-15 14:20:51 UTC 
Verified in Satellite 6.2 Snap 20.1.

Physical hosts do not have a "Disassociate" button, and using the bulk action tool, physical hosts are excluded with a message at the bottom of the modal window "The list is excluding 4 physical hosts. "
Comment 12 Bryan Kearney 2016-07-27 11:05:34 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/RHBA-2016:1501
Note You need to log in before you can comment on or make changes to this bug.