Bug 1389794 - Status Cache not used when listing repos with a bad proxy
Summary: Status Cache not used when listing repos with a bad proxy
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-28 16:32 UTC by Shwetha Kallesh
Modified: 2016-10-31 14:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-31 14:33:02 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1176219 0 low CLOSED subscription-manager repos --list with bad proxy options is silently using cache 2021-02-22 00:41:40 UTC

Internal Links: 1176219

Description Shwetha Kallesh 2016-10-28 16:32:17 UTC
Description of problem:
Status Cache not used when listing repos with a bad proxy

Version-Release number of selected component (if applicable):
[root@ibm-x3650m4-01-vm-13 ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 2.0.19-1
subscription management rules: 5.20
subscription-manager: 1.18.3-1.el6
python-rhsm: 1.18.4-1.el6


How reproducible:


Steps to Reproduce:
[root@ibm-x3650m4-01-vm-13 ~]# subscription-manager repos --list
+----------------------------------------------------------+
    Available Repositories in /etc/yum.repos.d/redhat.repo
+----------------------------------------------------------+
Repo ID:   awesomeos
Repo Name: awesomeos
Repo URL:  https://cdn.redhat.com/path/to/$basearch/$releasever/awesomeos
Enabled:   0

Repo ID:   awesomeos-x86_64
Repo Name: awesomeos-x86_64
Repo URL:  https://cdn.redhat.com/path/to/awesomeos/x86_64
Enabled:   0

Repo ID:   awesomeos-modifier
Repo Name: awesomeos-modifier
Repo URL:  http://example.com/awesomeos-modifier
Enabled:   0

Repo ID:   admin-content-label
Repo Name: admin-content
Repo URL:  https://cdn.redhat.com/admin/foo/path
Enabled:   0

Repo ID:   awesomeos-ppc
Repo Name: awesomeos-ppc
Repo URL:  https://cdn.redhat.com/path/to/awesomeos/ppc
Enabled:   0

Repo ID:   awesomeos-ppc64
Repo Name: awesomeos-ppc64
Repo URL:  https://cdn.redhat.com/path/to/awesomeos/ppc64
Enabled:   0

Repo ID:   awesomeos-x86_64-only-content
Repo Name: awesomeos-x86_64-only-content
Repo URL:  https://cdn.redhat.com/path/to/awesomeos/all
Enabled:   0

Repo ID:   content-label-empty-gpg
Repo Name: content-emptygpg
Repo URL:  https://cdn.redhat.com/foo/path
Enabled:   0

Repo ID:   awesomeos-s390x
Repo Name: awesomeos-s390x
Repo URL:  https://cdn.redhat.com/path/to/awesomeos/s390x
Enabled:   0

Repo ID:   content-label-no-gpg
Repo Name: content-nogpg
Repo URL:  https://cdn.redhat.com/foo/path
Enabled:   0

Repo ID:   awesomeos-ia64
Repo Name: awesomeos-ia64
Repo URL:  https://cdn.redhat.com/path/to/awesomeos/ia64
Enabled:   0

Repo ID:   awesomeos-i686
Repo Name: awesomeos-i686
Repo URL:  https://cdn.redhat.com/path/to/awesomeos/i686
Enabled:   0

Repo ID:   awesomeos-x86_64-i386-content
Repo Name: awesomeos-x86_64-i386-content
Repo URL:  https://cdn.redhat.com/path/to/awesomeos/all
Enabled:   0

Repo ID:   never-enabled-content
Repo Name: never-enabled-content
Repo URL:  https://cdn.redhat.com/foo/path/never
Enabled:   0

Repo ID:   content-label
Repo Name: content
Repo URL:  https://cdn.redhat.com/foo/path
Enabled:   0

[root@ibm-x3650m4-01-vm-13 ~]# subscription-manager repos --list --proxy=auto-services.usersys.redhat.com:3128 --proxyuser=bad-username --proxypassword=bad-password
Proxy connection failed, please check your settings.

Actual results:
Network error

Expected results:
Cache should used to complete the command execution without error

Additional info:

Comment 3 Chris Snyder 2016-10-31 14:33:02 UTC
This is now the expected behavior as of bug 1176219, which is now ON_QA.


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