Bug 1549625
Summary: | webui updates failing when a proxy is required | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> |
Component: | Appliance | Assignee: | Brandon Dunne <bdunne> |
Status: | CLOSED ERRATA | QA Contact: | luke couzens <lcouzens> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.9.0 | CC: | abellott, bdunne, cpelland, jprause, lcouzens, obarenbo, simaishi |
Target Milestone: | GA | Keywords: | ZStream |
Target Release: | 5.9.2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | webui:upgrade | ||
Fixed In Version: | 5.9.2.0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1540550 | Environment: | |
Last Closed: | 2018-05-07 20:42:43 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | CFME Core | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1540550 | ||
Bug Blocks: |
Comment 2
CFME Bot
2018-03-07 18:31:53 UTC
I don't believe this is working correctly. I added the rhsm settings and proxy info to the ui but check/updating the appliance still fails. Checking the file from the PR /etc/yum.conf I see no proxy info has been added. If I manually add the settings to this file it works as expected. Pushing back to on dev. Hi Luke, Do you have an appliance to test this on? I don't have a proxy anywhere to test locally. I see that the code is in 5.9.2.0, so I would expect it to work. Did you select the server and click register first? The proxy information is written to the config file during the registration process. Hi Brandon, I didn't realize registration was required to add the proxy info to yum.conf I just tested this again on 5.9.2.3 and it indeed seems to work correctly if you hit register first. Thanks for this info, Moving bug to verified. Verified in 5.9.2.3 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, 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-2018:1328 |