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 editing a docker compute resource, if it has emtpy credentials (username/password), WebUI automatically - everytime - fills admin/****** there.
Please get rid of the automatic pre-filling of credentials when editing a docker compute resource. It tries to override what is really stored, confuses a user and attempts to store data a user does not want.
Version-Release number of selected component (if applicable):
Sat6.1.6
How reproducible:
100%
Steps to Reproduce:
1. Create a docker compute resource with empty credentials. Test connection it is OK.
2. Edit the docker compute resource.
3. Test Connection.
4. Save it.
Actual results:
2. shows admin/****** credentials, despite _emtpy_ were inserted.
3. Test fails with Docker::Error::AuthenticationError - despite it was working before.
4. The username is really saved (you can check this by running:
su - postgres -c "psql foreman -c \"select * from compute_resources;\""
before and after the save)
Expected results:
2. to show whatever I stored, not overriding anything
3. test connection to pass
4. not storing the username
Additional info:
Yet another scenario:
5. when editing the compute resource, remove "admin" from the username and click to Test connection.
6. check "admin" has been filled there again
That means, a user clicking to Test connection (that passes) and then to Submit, "admin" username is stored instead of empty one. Such confusing.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable 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.