Description of problem: Attempting to update Upstream URL of a custom repo via WebUI fails with error: An error occurred saving the Repository: Validation failed: Upstream password requires upstream username be set. Doing the same via hammer, no validation fails. Also when one updates any other setting of the repo (e.g. just edit "Verify SSL" and save without a change), then updating the URL do pass. Version-Release number of selected component (if applicable): Sat 7.0 snap 9 How reproducible: 100% Steps to Reproduce: 1. Create a custom product and a custom repo with whatever Upstream URL. 2. In WebUI, edit the Upstream URL and click to Save. 3. Edit Verify SSL, optionally (un)check the option or leave unchanged, and save. 4. Edit the Upstream URL again. 5. Do the same change via hammer. Actual results: 2. fails with the above Validation failed error 4. succeeds 5. succeeds Expected results: 2. to succeed as well Additional info:
After "oh, I cant reproduce either", I realized this is tricky :) My observation: whenever I am creating a new yum repo in WebUI, I get upstream username and password pre-filled. To admin / (admin's WebUI password). That is filled by my *Firefox* that stores credentials to the Satellite WebUI and recognizes the fields as login username/password fields. So, when I allow Firefox to store my WebUI credentials, it pre-fills them to any new repo being created. The original bug report is a result of such confusion (I guess I removed the username but not password and tried to save it). So the real bugreport should be "change some meta-information about the input fields for upstream username and upstream password, such that FF does not pre-fill with auto-saved credentials". Which makes the bug of less priority but still valid, I guess.
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34818 has been resolved.
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 (Moderate: Satellite 6.11 Release), 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-2022:5498