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.
Description of problem: When a proxy is configured using the virt-who config plugin the proxy is incorrectly
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Create virt-who config using plugin and specify proxy
Actual results:
The resulting script will set an 'http_proxy' environment variable in /etc/sysconfig/virt-who
Expected results: The configuration file should be populated with these fields:
rhsm_proxy_hostname
rhsm_proxy_port
rhsm_proxy_user
rhsm_proxy_password or more likely rhsm_encrypted_proxy_password
The environment variable NO_PROXY is also used to ignore hosts.
Additional info: We will also probably need to add fields to the UI, or do something like parsing of the 'proxy' URL scheme.
Ignore my comment about the proxy:// URL scheme, there is no standard way to parse this. So we will have to either add fields or do something else here.
Perry, this is not a bug. http_proxy global parameter can be used if you need to proxy the communication, if you need to do it selectively, use Ignore Proxy option. If you want to change the rhsm_hostname you should just change the satellite url but that's not a proxy. How would the proxy know where is the Satellite that it should proxy the communication to?
Anyway this is consistent with the lab script. Please see inline help of fields if it's still confusing or ask Suresh, who was involved in the testing from the beginning.
If you think there should be proxy configurable per hypervisor, please raise RFE for virt-who project.