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:
Navigate to Satellite WebUI -> Infrastructure -> HTTP Proxies -> New HTTP Proxy and create 2 proxy (say 'test_proxy_1' and 'test_proxy_2' where both of these are 2 different proxies ).
Navigate to Satellite WebUI -> Infrastructure -> Virt-who Configurations -> Create Config. Select 'Hypervisor Type' as 'VMware vSphere / vCenter (esx)' and fill all the respective mandatory fields accordingly.
Create 2 Virt-who Configurations here (say 'virt-who_config_1' and 'virt-who_config_2'). Requirement here is 'virt-who_config_1' should use the 'test_proxy_1' and 'virt-who_config_2' should use the 'test_proxy_2'
Expected results: The proxy entry should not be added in /etc/virt-who.conf file, but it should be only added to /etc/virt-who.d/virt-who-config-x.conf file. Because there could be a scenario where user would like to use proxy only for one config and not for all config or where a user would like to use different proxies for different virt-who configuration. Proxy added in /etc/virt-who.conf file will make it effective for all present virt-who configs.
Version-Release number of selected component (if applicable): satellite-6.13.0-4.el8sat.noarch
Additional info: Currently the workaround is, if a user want to run different virt-who endpoints with different proxies, user need to have different instances of virt-who.
*** Bug 2181960 has been marked as a duplicate of this bug. ***
Comment 3Nikos Moumoulidis
2023-07-20 15:14:07 UTC
This isn't related to Candlepin. It would have to be fixed first in virt-who itself (see 2181960) and after that, the Virt-Who configure plugin.
Thus moving component
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.