Description of problem:
When it hasn't configure rhsm_proxy_port in /etc/virt-who.d/XXX, virt-who won't check rhsm_proxy_hostname.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure virt-who with a wrong proxy in /etc/virt-who.d/xxx
[root@hp-z220-05 virt-who.d]# cat /etc/virt-who.d/hyperv
rhsm_proxy_hostname=aaaa ===> It's wrong
2. Restart virt-who and check virt-who's log
[root@hp-z220-05 virt-who.d]# service virt-who restart && tail -f /var/log/rhsm/rhsm.log
Virt-who can send mapping info to satellite server successfully, it hasn't check rhsm_proxy_hostname.
As it's a wrong rhsm_proxy_hostname, virt-who shouldn't send mapping info to satellite server, it should show error info to remind " Name or service not known"
If configure rhsm_proxy_hostname and rhsm_proxy_host in /etc/virt-who.d/xxx, it can show error info as the following:
"gaierror: [Errno -2] Name or service not known"
This is a result of the implementation of the UEPConnection in python-rhsm used by virt-who to communicate with Satellite (as well as hosted).
I do not believe this is a bug.
As such I am closing this.
If there is disagreement, please reopen the bug with details as to why this is actually a bug.
I think it still is a bug since it should has a default "rhsm_proxy_port" if "rhsm_proxy_port" hasn't be set.
Actually, we can compare a similar pair of configure "rhsm_hostname and rhsm_port".
1. If it hasn't set "rhsm_port", configure wrong "rhsm_hostname", it will show error info "Name or service not known" since it should has a default "rhsm_port=443", it's the correct behavior.
2. If it hasn't set "rhsm_port", configure correct "rhsm_hostname", it will send mapping info to server,it's the correct behavior.
So I expect the "rhsm_proxy_port and rhsm_proxy_hostname" should have the same behavior as "rhsm_hostname and rhsm_port".
Therefore, I reopen it. Thanks.