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 1654915 - list available subscriptions with noproxy failed when set invalid proxy_hostname on rhel8-aarch64
Summary: list available subscriptions with noproxy failed when set invalid proxy_hostn...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: subscription-manager
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: candlepin-bugs
QA Contact: Red Hat subscription-manager QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-30 02:55 UTC by yanpliu
Modified: 2018-11-30 07:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 07:29:46 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description yanpliu 2018-11-30 02:55:05 UTC
Description of problem:
list available subscriptions with invalid proxy failed on rhel8-aarch64 

Version-Release number of selected component (if applicable):

subscription-manager-cockpit-1.23.8-1.el8.noarch
dnf-plugin-subscription-manager-1.23.8-1.el8.aarch64
subscription-manager-1.23.8-1.el8.aarch64
subscription-manager-rhsm-certificates-1.23.8-1.el8.aarch64
python3-subscription-manager-rhsm-1.23.8-1.el8.aarch64


How reproducible:


Steps to Reproduce:
1.Register RHEL-8.0-20181120.0-BaseOS-aarch64 against satellite6.4:
# subscription-manager register --username=admin --password=admin
Registering to: ent-01-vm-02.lab.eng.nay.redhat.com:443/rhsm
The system has been registered with ID: f82cc963-03b0-4ebc-adf2-da7419b5de11
The registered system name is: kernelci-03.khw.lab.eng.bos.redhat.com

2.Set invalid proxy_hostname and proxy_port
#  subscription-manager config --server.proxy_hostname=haha.example.com --server.proxy_port=666
3. List available subscriptions with noproxy 
#  subscription-manager list --avai --matches="Red Hat Enterprise Linux Server" --noproxy=*.redhat.com
No available subscription pools were found matching the expression "Red Hat Enterprise Linux Server".


Actual results:
Step3 no No available subscription pools were found 

Expected results:
Step3 should list available subscription pools


Additional info:

Comment 1 yanpliu 2018-11-30 07:29:46 UTC
#  subscription-manager list --avai --all --matches="Red Hat Enterprise Linux Server" --noproxy=*.redhat.com
# subscription-manager list --avai --matches="Red Hat Enterprise Linux High Touch Beta" --noproxy=*.redhat.com

Can list the available subscriptions, so it is not a bug, I will close this bug.


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