Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
DescriptionAshfaqur Rahaman
2023-05-24 01:07:12 UTC
Description of problem:
Satellite generated virt-who config updates the global virt-who configuration which does recognize no_proxy.
even with no_proxy=* in /etc/virt-who.conf, virt-who does not ignore the default proxy configured in /etc/rhsm/rhsm.conf
Version-Release number of selected component (if applicable):
satellite 6.10.7
virt-who-0.28.10-1.el7_9.noarch
I have tested in 6.10, later versions should have similar impact as well.
How reproducible:
100%
Steps to Reproduce:
1. Configure a proxy in /etc/rhsm/rhsm.conf which is default proxy.
2. Create virt-who configuration in satellite GUI with "Ignore Proxy" = *
3. Deploy virt-who configuration and it will set "no_proxy=*" in /etc/virt-who.conf
3. Check /var/log/rhsm.log
Actual results:
- /etc/virt-who.conf updated with "no_proxy=*"
- virt-who failed to send the guest-host mapping , it still tried to connect via proxy and ignored the "no_proxy" option:
~~~
2023-05-23 19:33:41,391 [virtwho.rhsm_log WARNING] MainProcess(24321):MainThread @config.py:init_config:1556 - [global]: Ignoring unknown configuration option "no_proxy"
~~~
Expected results:
- Satellite virt-who configuration should update "/etc/virt-who.d/virt-who-config-X.conf" with "rhsm_no_proxy=*" instead updating the global configuration.
Additional info:
Workaround :
- Add "rhsm_no_proxy=*" in /etc/virt-who.d/virt-who-config-X.conf , where X is the latest generated configuration.
- restart virt-who