Red Hat Bugzilla – Bug 1267135
[RFE] virt-who should support "--proxy" when run it with command-line
Last modified: 2016-11-30 19:35:16 EST
Description of problem:
When virt-who run at command-line, it can't support connect hyperv/rhevm/vcenter through proxy, it should add --proxy option in command line.
Version-Release number of selected component (if applicable):
virt-who can't connect rhevm directly.
Steps to Reproduce:
1. Register system to SAM
2. Run virt-who at command line and monitor rhevm through proxy
[root@hp-z220-06 virt-who.d]# virt-who --rhevm --rhevm-owner=ACME_Corporation --rhevm-env=Library --rhevm-server=https://10.66.79.83:443 --rhevm-username=admin@internal --rhevm-password=redhat --proxy -o -d
Usage: virt-who [-d] [-i INTERVAL] [-o] [--sam|--satellite5|--satellite6] [--libvirt|--vdsm|--esx|--rhevm|--hyperv]
virtwho.py: error: no such option: --proxy
3. [root@hp-z220-06 virt-who.d]# virt-who --help | grep proxy
Virt-who can't support proxy when it run at command line. it also hasn't included any proxy's information in virt-who's help info.
Virt-who should support proxy when it run at command line. it also should include --proxy option in virt-who's help info.
You can use the environment variable even on command line:
HTTPS_PROXY=https://some.proxy:1234 virt-who --rhevm ...
This is standard way to define proxy for many linux command line applications. Most of them doesn't have extra --proxy parameter.
I don't think adding the --proxy option is not worth the efford. Setting the environment variable seems to be sufficient. Do you agree to close this bug?
(In reply to Radek Novacek from comment #2)
> I don't think adding the --proxy option is not worth the efford. Setting the
> environment variable seems to be sufficient. Do you agree to close this bug?
Yes, It is acceptable that "HTTPS_PROXY/HTTP_PROXY" replace of "proxy". Therefore, close it. Thanks.