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.
Bug 2064793 - Remotes should have username and password cleared out if a user sets them to be blank
Summary: Remotes should have username and password cleared out if a user sets them to ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.11.0
Assignee: Ian Ballou
QA Contact: Cole Higgins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-16 14:51 UTC by Ian Ballou
Modified: 2022-07-05 14:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-05 14:34:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 34619 0 Normal Closed Remotes should have username and password cleared out if a user sets them to be blank 2022-03-21 20:21:03 UTC
Red Hat Product Errata RHSA-2022:5498 0 None None None 2022-07-05 14:34:38 UTC

Description Ian Ballou 2022-03-16 14:51:53 UTC 
Currently, we do not update the username or password in Pulp if they are blank: https://github.com/Katello/katello/blob/master/app/services/katello/pulp3/repository.rb#L417

This seems to be related to the following community thread and maybe have worked around the related Pulp bug: https://community.theforeman.org/t/pulprpmclient-apierror-http-500-during-sync-repository/27480/14
Comment 1 Ian Ballou 2022-03-16 14:51:56 UTC 
Created from redmine issue https://projects.theforeman.org/issues/34619
Comment 2 Ian Ballou 2022-03-16 14:51:58 UTC 
Upstream bug assigned to iballou
Comment 4 Bryan Kearney 2022-03-21 20:05:19 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34619 has been resolved.
Comment 7 Ian Ballou 2022-06-08 18:23:12 UTC 
Testing steps:


1) Update a repo's username and password
2) Check the username and password in from the DB:

```
vagrant@centos8-katello-devel ~/katello $ sudo -i -u postgres
postgres@centos8-katello-devel ~ $ psql
psql (12.9)
Type "help" for help.

postgres=# \c pulpcore 
You are now connected to database "pulpcore" as user "postgres".
pulpcore=#  select pulp_id, name, url, username, password, length(username) from core_remote;
...
```

Note: the username and password will appear as gibberish.

3) Clear out the username and password on the repo
4) Sync the repo
5) The username and password should now be empty in postgres
Comment 11 errata-xmlrpc 2022-07-05 14:34:27 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 (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
Note You need to log in before you can comment on or make changes to this bug.