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:
When assigning parameters at the top of the tree (for example, in <region>) we cannot see these in the children. We can add values to the children with the same name and this overwrites as expected. The values parent location are available as parameters in the YAML files. We should be able to view the parents parameters along with options to override these.
Version-Release number of selected component (if applicable):
How reproducible: 100%
Steps to Reproduce:
1. manage locations
2. create a new location
3. select a parent for the new location
4. review the location ( you see no parameters)
Actual results:
Child location is separate from the parent.
Expected results:
Child should inherit from the parent including parameters
Additional info:
To give some context, we use nested locations for example:
<region>
|---- <country>
| |---- <city>
We permission users to have access only to particular parts of this (for various legal and sphere of influence). For example, the region level we will define defaults, some of these may be overwritten at the country / city levels (time zones, root passwords for example) currently these are not visible.
Moving to POST since upstream bug http://projects.theforeman.org/issues/12931 has been closed
-------------
Ori Rabin
Applied in changeset commit:7422bc43ff93fe4603b6c5a4b71d8dc103e14d67.
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:1500