RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1425904 - [RFE][RHEL6] Include Reason in cases of failed proxy
Summary: [RFE][RHEL6] Include Reason in cases of failed proxy
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: redhat-support-tool
Version: 6.8
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Vikas Rathee
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks: 1457436 1685295
TreeView+ depends on / blocked
 
Reported: 2017-02-22 17:45 UTC by Deepu K S
Modified: 2019-03-04 22:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1457436 (view as bug list)
Environment:
Last Closed: 2017-06-13 18:47:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Deepu K S 2017-02-22 17:45:42 UTC 
Description of problem:
[RFE][RHEL6] Include Reason in cases of failed proxy connection.

In case of a failed proxy connection, we simply get
ERROR: Problem connecting to the support services API.  Is the service accessible from this host?

But with this it is not able to figure out the cause of this failure.

Version-Release number of selected component (if applicable):
redhat-support-tool-0.9.8-4.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Add a proxy_url in redhat-support-tool.conf (failure condition)

2. # redhat-support-tool addattachment -c 01786133 glibc-2.12-1.192.el6.x86_64.rpm

3.Gives an "ERROR: Problem connecting to the support services API.  Is the service accessible from this host?"

Actual results:
$ redhat-support-tool addattachment -c 01786128 sosreport-uswaspl21k-20170205135147-01c9.tar.xz
Uploading sosreport-uswaspl21k-20170205135147-01c9.tar.xz to the case ...      failed.
ERROR: Problem connecting to the support services API.  Is the service accessible from this host?

$ env|grep -i HTT
http_proxy=
https_proxy=

$ unset http_proxy
$ unset https_proxy
$ redhat-support-tool addattachment -c 01786128 sosreport-uswaspl21k-20170205135147-01c9.tar.xz
Uploading sosreport-uswaspl21k-20170205135147-01c9.tar.xz to the case ...      failed.
ERROR: Problem connecting to the support services API.  Is the service accessible from this host?

Expected results:
Should give an ERROR message as in below case where the user password was wrong.
ERROR: Unable to connect to support services API.  Reason: Unauthorized

The goal would be a warning message of why direct / proxy connection has been refused.

Examples:
- port not reachable?
- proxy auth refused?
- upstream connection failed?

Additional info:
Comment 3 Chris Williams 2017-06-13 18:47:27 UTC 
Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017.  During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
 
The official life cycle policy can be reviewed here:
 
http://redhat.com/rhel/lifecycle
 
This issue does not appear to meet the inclusion criteria for the Production Phase 3 and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification.  Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
 
https://access.redhat.com
Note You need to log in before you can comment on or make changes to this bug.