Bug 1310687 - Differentiate between no proxies found and all proxies found are not available
Summary: Differentiate between no proxies found and all proxies found are not available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Remote Execution
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: jcallaha
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-22 14:16 UTC by Adam Ruzicka
Modified: 2019-09-25 21:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 09:23:13 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1501 normal SHIPPED_LIVE Red Hat Satellite 6.2 Capsule and Server 2016-07-27 12:28:58 UTC
Foreman Issue Tracker 13263 None None None 2016-04-22 15:00:04 UTC

Description Adam Ruzicka 2016-02-22 14:16:16 UTC
The proxy load balancer removes proxies that are down, which results in the same error message as if there were no proxies at all.  We should either tell the user a different error message, or include that info in the existing one.

Comment 1 Adam Ruzicka 2016-02-22 14:16:27 UTC
Created from redmine issue http://projects.theforeman.org/issues/13263

Comment 3 Bryan Kearney 2016-02-24 17:07:49 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/13263 has been closed

Comment 5 jcallaha 2016-04-21 20:29:30 UTC
Verified in Satellite 6.2 Beta Snap 9. You are now told when a proxy is down as well as when a proxy is not configured.

Comment 7 errata-xmlrpc 2016-07-27 09:23:13 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, 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-2016:1501


Note You need to log in before you can comment on or make changes to this bug.