Bug 1907864
| Summary: | Repository enable failed on http-proxy configured setup. | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Devendra Singh <desingh> |
| Component: | Repositories | Assignee: | Marek Hulan <mhulan> |
| Status: | CLOSED ERRATA | QA Contact: | Tasos Papaioannou <tpapaioa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.9.0 | CC: | bmbouter, gpayelka, ipanova, mhulan, rchan, ssainkar |
| Target Milestone: | 6.9.0 | Keywords: | Regression, Triaged |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | foreman-2.3.1.8-1 | Doc Type: | Known Issue |
| Doc Text: |
Enabling repository on a Satellite installation with http-proxy configured fails with a 404 error.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-04-21 13:24:23 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Devendra Singh
2020-12-15 11:55:36 UTC
So what happens is, if HttpProxy object has username set to emtpy string, pulp 2 thinks it is asked to use username and password, but the password is not passed (the value in Foreman DB is nil). The empty string stored for the user name comes from WebUI form, if user leaves the field blank. After resetting this to nil in DB, it works fine again. This can be seen as a regression from 6.8 but technically it is not. The change in 6.9 is that password field of http proxy form is disabled by default, once needs to click on the pencil icon to enable it. If it remains disabled, the value for passowrd is nil, if it is enabled, it's empty string. If both username and password is empty string, pulp is happy and all works. So we need to make sure either both username and password is empty string (submitted enabled empty text fields) or none of them is empty string (can be acheived through API). After a discussion with Ina, the fix should land in Pulp 2. The workaround to unblock QE: when you create a HTTP proxy in UI, click the pencil and save the form only when the password field is enabled. Or use API and don't specify any username and password. The Pulp upstream bug status is at NEW. Updating the external tracker on this bug. The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug. @Marek, turned out that even if the fix is not complex, we would need to touch the code for multiple plugin types in multiple plances, which I would try to really avoid. Can you please ensure on your side that values for user/pass coming from UI are nil? I am removing pulp component, please update the component accordingly, I was not sure which one to select. Created redmine issue https://projects.theforeman.org/issues/31637 from this bug Thanks, I've sent a fix to Foreman core for this. Devendra, let me know if you'd like to participate in testing, the patch can be easily applied but one file needs to be omitted on the production system. I'm happy to assist. Upstream bug assigned to mhulan Upstream bug assigned to mhulan (In reply to Marek Hulan from comment #10) > Devendra, let me know if you'd like to participate in testing, the patch can > be easily applied but one file needs to be omitted on the production system. > I'm happy to assist. yes, I would like to participate in the testing. Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31637 has been resolved. No worries, it was already merged meanwhile but thanks for the interest! I believe this will get into the next snap. *** Bug 1919577 has been marked as a duplicate of this bug. *** Verified on 6.9.0 snap 14.0. 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.9 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-2021:1313 |