| Summary: | another typo in "Proxy connnection failed, please check your settings." | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | John Sefler <jsefler> |
| Component: | subscription-manager | Assignee: | Kevin Howell <khowell> |
| Status: | CLOSED ERRATA | QA Contact: | John Sefler <jsefler> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 7.3 | CC: | khowell, redakkan, skallesh |
| Target Milestone: | rc | Keywords: | EasyFix, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| 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: | |
|
Description
John Sefler
2016-09-02 15:52:42 UTC
There is no typo now , so moving bug to verified state
[root@dhcp70-149 ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 2.1.0-1
subscription management rules: 5.23
subscription-manager: 1.19.5-1.el7
python-rhsm: 1.19.3-1.el7
[root@dhcp70-149 ~]# rpm -ql subscription-manager-gui | egrep managergui.py$
/usr/lib/python2.7/site-packages/subscription_manager/gui/managergui.py
[root@dhcp70-149 ~]# grep "Proxy conn" /usr/lib/python2.7/site-packages/subscription_manager/gui/managergui.py
print_error(_("Proxy connection failed, please check your settings."))
error_dialog = messageWindow.ContinueDialog(_("Proxy connection failed, please check your settings."),
[root@dhcp70-149 ~]# msgunfmt --no-wrap /usr/share/locale/it/LC_MESSAGES/rhsm.mo | egrep "Proxy .*, please check your settings"
msgid "Proxy connection failed, please check your settings."
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 |