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.
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.
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.
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.
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.