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 1257607 - Discovered hosts UI does not allow setting Organization/Location when provisioning
Summary: Discovered hosts UI does not allow setting Organization/Location when provisi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Discovery Plugin
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: orabin
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks: 1338516
TreeView+ depends on / blocked
 
Reported: 2015-08-27 12:42 UTC by Barak Korren
Modified: 2019-11-14 06:54 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:51:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Unable to change org/loc via mass action (127.86 KB, image/png)
2015-08-31 10:59 UTC, Barak Korren 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 4426 0 None None None 2016-04-22 15:39:59 UTC
Red Hat Bugzilla 1231642 0 unspecified CLOSED Allow editing taxonomy on Provision Host form 2021-06-10 10:55:12 UTC

Internal Links: 1231642

Description Barak Korren 2015-08-27 12:42:45 UTC 
Description of problem:
The discovered hosts UI includes "Assign Location" and "Assign Organization" actions but there is no way to preform those actions from the API. 

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

How reproducible:
Easy

Steps to Reproduce:
1. Setup Satellite with multiple organizations and locations 
2. Setup the discovery plugin
3. Let some hosts be discovered
4. Try to assign organizations and locations from the API

Actual results:
There is no API for assigning organizations and locations

Expected results:
There should be API for this...
Comment 1 Bryan Kearney 2015-08-28 17:36:44 UTC 
Created redmine issue http://projects.theforeman.org/issues/11605 from this bug
Comment 2 Lukas Zapletal 2015-08-31 10:01:45 UTC 
WORKAROUND: It is possible to change org/loc of existing discovered hosts using mass assignement action. Select one or more hosts, click on Select action and use Assign org/loc button to do this.
Comment 3 Barak Korren 2015-08-31 10:59:27 UTC 
Created attachment 1068596 [details]
Unable to change org/loc via mass action

There is a problem with this - the mass action window shows the list of hosts again instead of allowing to select the org/loc. (See attached screenshot)
Comment 4 Lukas Zapletal 2015-08-31 14:31:16 UTC 
Thanks, reported and fixed as in https://bugzilla.redhat.com/show_bug.cgi?id=1258521

The patch is small, you can apply it onto your instance if you dont want to wait for z-stream update.

Or you can use "foreman-rake console" if API won't work.
Comment 6 Lukas Zapletal 2016-03-03 09:46:37 UTC 
Unfortunately, this is a technical limitation of reusing Edit Host form in Discovery. This can't be easily fixed, my initial attempt stalled and we need to implement proper solution - brand new provisioning form for discovered hosts.
Comment 7 Bryan Kearney 2016-06-15 16:08:08 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/4426 has been closed
Comment 12 orabin 2017-08-10 06:30:58 UTC 
Version Tested: Satellite-6.3 Snap 10

The selection of organization and location works with the wizard.
Choosing hostgroup, organization and location then clicking quick or create will work as expected.
However, I found a bug with one case:
1) Click provision on a discovered host
2) Choose organization and location that are not the default and leave the hostgroup empty
3) Click create host
4) fill in hostgroup and submit

Expected result: Success save or validation erro

Actual result: Host not found

Moved bug back to assigned but it's also possible to open a new bug and mark this one as verified.
Adding need more information so assignee will decide how to proceed.
Comment 13 Lukas Zapletal 2017-08-29 10:15:12 UTC 
Ok I prefer separate bug for this, created upstream issue for that:

http://projects.theforeman.org/issues/20784
Comment 14 Bryan Kearney 2018-02-21 16:44:32 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
Comment 15 Satellite Program 2018-02-21 16:51:07 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.