-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
6.10.7
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