Bug 2169854 - [RFE] Handling of multiple proxies for different virt-who configurations where virt-who is deployed on a single machine
Summary: [RFE] Handling of multiple proxies for different virt-who configurations wher...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Virt-who Configure Plugin
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: yanpliu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-14 19:55 UTC by Jayant Bhatia
Modified: 2023-08-08 15:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19438 0 None None None 2023-08-08 15:44:19 UTC

Description Jayant Bhatia 2023-02-14 19:55:09 UTC
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.

Comment 2 Rehana 2023-04-06 10:17:03 UTC
*** Bug 2181960 has been marked as a duplicate of this bug. ***

Comment 3 Nikos 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


Note You need to log in before you can comment on or make changes to this bug.