Bug 1371632
Summary: | Connection test passed even fields are blank in proxy dialog | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jan Stavel <jstavel> |
Component: | subscription-manager | Assignee: | Kevin Howell <khowell> |
Status: | CLOSED ERRATA | QA Contact: | Jan Stavel <jstavel> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | csnyder, jsefler, khowell, redakkan, skallesh, weiliu |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 19:20:42 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
Jan Stavel
2016-08-30 16:48:54 UTC
@candlepin_devs: The fix for this would be to disallow testing connections in the case above. *** Bug 1379251 has been marked as a duplicate of this bug. *** verify this issue when the RHEL7.4 composes start rolling out Verifying version: [root@dhcp-128-6 ~]# subscription-manager version server type: Red Hat Subscription Management subscription management server: 0.9.51.21-1 subscription management rules: 5.15.1 subscription-manager: 1.19.4-1.el7 python-rhsm: 1.19.2-1.el7 Verification: 1.Install build RHEL-7.4-20170330.1,and open Subscription Manager GUI. 2.Click on the menu "System -> Configure Proxy" 3.Check "I would like to connect via an HTTP proxy" and leave the proxy url empty 4.Try to click button "Test Connection" # The "Test Connection" is disabled when the proxy field is blank,so can not use this button to test connection when the proxy is blank. So this issue is verified and move the status to "verified". 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/RHBA-2017:2083 |