Admin user cannot create new repository

Support
1

Problem:
Another admin user cannot create a new repository. (Works fine on my user, users are configured the same)

Expected outcome:
Repository should be created.

Foreman and Proxy versions:
Foreman 1.22
Katello 3.12

Foreman and Proxy plugin versions:

Other relevant data:
[e.g. logs from Foreman and/or the Proxy, modified templates, commands issued, etc]
(for logs, surround with three back-ticks to get proper formatting, e.g.)

Aug 12 09:54:02 foreman pulp: kombu.transport.qpid:INFO: Connected to qpid with SASL mechanism ANONYMOUS
Aug 12 09:54:02 foreman pulp: pulp.server.controllers.repository:ERROR: (10540-34080) Exception adding importer to repo [6f6f20e7-73b0-40bf-9a1d-e326171de3be]; the repo will be deleted
Aug 12 09:54:02 foreman pulp: pulp.server.controllers.repository:ERROR: (10540-34080) Traceback (most recent call last):
Aug 12 09:54:02 foreman pulp: pulp.server.controllers.repository:ERROR: (10540-34080)   File "/usr/lib/python2.7/site-packages/pulp/server/controllers/repository.py", line 419, in create_repo
Aug 12 09:54:02 foreman pulp: pulp.server.controllers.repository:ERROR: (10540-34080)     importer_controller.set_importer(repo_id, importer_type_id, importer_repo_plugin_config)
Aug 12 09:54:02 foreman pulp: pulp.server.controllers.repository:ERROR: (10540-34080)   File "/usr/lib/python2.7/site-packages/celery/local.py", line 191, in __call__
Aug 12 09:54:02 foreman pulp: pulp.server.controllers.repository:ERROR: (10540-34080)     return self._get_current_object()(*a, **kw)
Aug 12 09:54:02 foreman pulp: pulp.server.controllers.repository:ERROR: (10540-34080)   File "/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py", line 529, in __call__
Aug 12 09:54:02 foreman pulp: pulp.server.controllers.repository:ERROR: (10540-34080)     return super(Task, self).__call__(*args, **kwargs)
Aug 12 09:54:02 foreman pulp: pulp.server.controllers.repository:ERROR: (10540-34080)   File "/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py", line 107, in __call__
Aug 12 09:54:02 foreman pulp: pulp.server.controllers.repository:ERROR: (10540-34080)     return super(PulpTask, self).__call__(*args, **kwargs)
Aug 12 09:54:02 foreman pulp: pulp.server.controllers.repository:ERROR: (10540-34080)   File "/usr/lib/python2.7/site-packages/celery/app/task.py", line 379, in __call__
Aug 12 09:54:02 foreman pulp: pulp.server.controllers.repository:ERROR: (10540-34080)     return self.run(*args, **kwargs)
Aug 12 09:54:02 foreman pulp: pulp.server.controllers.repository:ERROR: (10540-34080)   File "/usr/lib/python2.7/site-packages/pulp/server/controllers/importer.py", line 99, in set_importer
Aug 12 09:54:02 foreman pulp: pulp.server.controllers.repository:ERROR: (10540-34080)     validate_importer_config(repo, importer_type_id, clean_config)
Aug 12 09:54:02 foreman pulp: pulp.server.controllers.repository:ERROR: (10540-34080)   File "/usr/lib/python2.7/site-packages/pulp/server/controllers/importer.py", line 177, in validate_importer_config
Aug 12 09:54:02 foreman pulp: pulp.server.controllers.repository:ERROR: (10540-34080)     raise exceptions.PulpDataException(message)
Aug 12 09:54:02 foreman pulp: pulp.server.controllers.repository:ERROR: (10540-34080) PulpDataException: Configuration errors:
Aug 12 09:54:02 foreman pulp: pulp.server.controllers.repository:ERROR: (10540-34080) The configuration parameter <basic_auth_password> requires the <basic_auth_username> parameter to also be set.
Aug 12 09:54:02 foreman pulp: pulp.server.webservices.middleware.exception:INFO: (10540-34080) Configuration errors:
Aug 12 09:54:02 foreman pulp: pulp.server.webservices.middleware.exception:INFO: (10540-34080) The configuration parameter <basic_auth_password> requires the <basic_auth_username> parameter to also be set.
<basic_auth_username>
2

Are you specifying a username/password when you create a repository? Would it be possible for you to also paste the stack trace you get from /var/log/foreman/production.log

3

Found the problem from your comment, Thanks.

Chrome was inserting a password into the password field, user removed it ( leaving field blank ) and saving fails. Testing in incognito worked since autocomplete/insert is disabled.

This is then, however, still a bug albeit a different one: Deleting autocomplete-filled password field does not seem to work properly.

4

This issue was recent addressed in Bug #27279: Saving Custom repos can cause "Upstream password requires upstream username be set" - Katello - Foreman
Should be fixed in the next release.

5

Addressed in release 3.14 rather

6

Marked my own answer as the solution since it has the explanation of what is going on, even though your answer got me there.
At least now there are more known ways that this bug seems to rear its head :wink:

Thank you for your help in this matter :slight_smile:

7

This was a solution for me as well.
RedHat Satellite 6 product. July 2021.

To state more plainly - I needed to use a non-Chrome browser to login to the Satellite GUI to create the new repository because Chrome auto-inserted a password into the password field. I saw this and cleared the password it inserted, but Chrome silently re-added the password when submitting the form (when I clicked the ‘save’ button). I used the opera browser (on MacOS) which worked, I guess other will too. The error I saw was a red popup box saying ‘400 Error’. There was an error in SatSvr:/var/log/foreman/production.log
The error said “http_status”: 400 and “The configuration parameter <basic_auth_password> requires the <basic_auth_username> parameter to also be set.”

8

we’re gonna be investigating this again as part of Bug #33164: attempting to delete a user name and password for "Upstream Authorization" fails - Katello - Foreman

this is a really annoying issue and chrome doesn’t make it easy :frowning: