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 we click on "edit host" from all hosts. edit page showing the default settings with respect to the selected hostgroup. Any change in the parameters does not reflect on WebUI. However, hammer shows updated details.
Version-Release number of selected component (if applicable):
- Satellite 6.3
How reproducible:
- Always
Steps to Reproduce:
1. provision a host with hostgroup
2. change the LE/CV or content-source fromWebUI and save it
3. click on edit host again and LE/CV changed to the default one in the hostgroup
Actual results:
- edit page showing values from hostgroup after changing
Expected results:
- changes should be visible on WebUI
Additional info:
- hammer host info shows correct values
- only reproducible in 6.3
- reproducer details added
This appears to be a bug in the host form. Changing the values from the hostgroup defaults in the form and saving saves the new values, but when opening the form again the hostgroup defaults are repopulated in these fields. @walden - any idea on why this happens?
(In reply to Tomer Brisker from comment #2)
> This appears to be a bug in the host form. Changing the values from the
> hostgroup defaults in the form and saving saves the new values, but when
> opening the form again the hostgroup defaults are repopulated in these
> fields. @walden - any idea on why this happens?
No I don't, I'm sorry. I don't know much about foreman's forms unfortunately.
Comment 12Daniel Lobato Garcia
2018-05-25 11:36:41 UTC
Comment 13Daniel Lobato Garcia
2018-05-28 09:25:40 UTC
I can successfully reproduce the error on the latest nightly version of Katello + Foreman. Working on a fix for this now.
Comment 14Daniel Lobato Garcia
2018-05-28 10:05:06 UTC
Alright, after some investigation I found this issue is quite interesting:
1 - We have a host with a Host Group. Then we decide to override the Lifecycle Environment and Content View. Fine, just go to the edit form and change them.
2 - Submit the form - everything should be OK. (in fact it is at this point)
3 - We reopen the edit form to make sure the changes were applied but surprise: Lifecycle Environment and Content View are set back to the Host Group ones. Or.. is that true? No! It's just an UI bug.
After you submit the form, the data is saved properly on your database. For example:
Host A is inheriting LE with name 'test-le' and CV with name 'test-cv'.
We edit the form with LE with name 'production-le' and CV with name 'production-cv'. Submit.
We check using the API, /api/v2/hosts/A - and the data is fine!
However if we open the form, we will see LE 'test-lv' and CV 'test-cv'. This is NOT what's on the database, and it's misleading. Especially if you press the submit button again by mistake, you'll actually change the values for good, when you actually wanted 'production-le' and 'production-cv'.
I will fix this ASAP, however keep in mind and please inform customers that their changes are being applied properly. The problem is just that the UI is not displaying it right. You may verify this using the API if you wish.
Comment 16Daniel Lobato Garcia
2018-05-28 12:24:52 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:2927