1231642 – Allow editing taxonomy on Provision Host form

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 1231642 - Allow editing taxonomy on Provision Host form

Summary: Allow editing taxonomy on Provision Host form

Keywords:
Status:	CLOSED WONTFIX
Alias:	None
Product:	Red Hat Satellite
Classification:	Red Hat
Component:	Discovery Plugin
Sub Component:
Version:	6.1.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	high
Target Milestone:	Unspecified
Assignee:	Lukas Zapletal
QA Contact:	Sachin Ghai
Docs Contact:
URL:	http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:	1193977
TreeView+	depends on / blocked

Reported:	2015-06-15 07:07 UTC by Sachin Ghai
Modified:	2021-06-10 10:55 UTC (History)
CC List:	4 users (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2018-09-04 18:04:40 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)
Please see the org/location when hostgroup is not associated with discovered host while provisioning (38.74 KB, image/png) 2015-06-15 07:08 UTC, Sachin Ghai	no flags	Details
org/location changed on associating HostGroup with discovered host while provisioning (30.41 KB, image/png) 2015-06-15 07:09 UTC, Sachin Ghai	no flags	Details
View All

Links
System	ID	Priority	Status	Summary	Last Updated
Foreman Issue Tracker	8148	None	None	None	2016-04-26 17:11:34 UTC
Red Hat Bugzilla	1257607	unspecified	CLOSED	Discovered hosts UI does not allow setting Organization/Location when provisioning	2021-02-22 00:41:40 UTC
Red Hat Knowledge Base (Solution)	2094621	None	None	None	2015-12-17 15:07:14 UTC

Internal Links: 1257607

Description Sachin Ghai 2015-06-15 07:07:13 UTC

Description of problem:
I was trying to provision a discovered host manually and associated a hostgroup. As soon as I associated the hostgroup  with discovered host, the selected org/location was changed to first available org in the list. Please see the scareenshot

Version-Release number of selected component (if applicable):
sat6.1 GA snap8

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
Assigning a hostgroup to a discovered host during provision changes selected organization and location

Expected results:
org/location should n't be changed.

Additional info:
its a customer reported issue.

Comment 1 Sachin Ghai 2015-06-15 07:08:33 UTC

Created attachment 1038797 [details]
Please see the org/location when hostgroup is not associated with discovered host while provisioning

Comment 2 Sachin Ghai 2015-06-15 07:09:42 UTC

Created attachment 1038798 [details]
org/location changed on associating HostGroup with discovered host while provisioning

Comment 5 Bryan Kearney 2015-06-19 15:53:57 UTC

Connecting redmine issue http://projects.theforeman.org/issues/8148 from this bug

Comment 6 Lukas Zapletal 2016-03-03 09:46:40 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 8 Lukas Zapletal 2016-05-13 07:10:47 UTC

We are not fixing this one for GA, it's a design issue of discovered new host form.

Comment 11 Lukas Zapletal 2017-05-24 08:54:30 UTC

First, no matter in what taxonomy discovered host is created, it always must fall into taxonomy of a hostgroup. If these are different, hostgroup must win.

Second, taxonomy is disabled when provisioning host, this is technical limitation we workaround in Satellite 6.3 with new Quick Provision form until we solve it.

Comment 12 Lukas Zapletal 2017-05-24 09:08:51 UTC

To be more clear, hostgroup enforces taxonomy, this is a feature not bug, but the fact the field is disabled is the bug we need to solve.

Comment 14 Bryan Kearney 2018-09-04 18:04:40 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

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