Bug 2063218

Summary: [RFE] Implement a mechanism to ensure that all virt-who configurations that belong to the same organization use the same 'rhsm_username'
Product: Red Hat Satellite Reporter: momran
Component: Virt-who Configure PluginAssignee: Lucy Fu <lufu>
Status: CLOSED ERRATA QA Contact: yanpliu <yanpliu>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.9.6CC: chrobert, jrichards2, lufu, mhulan, msunil, thadzhie, yanpliu, zhunting
Target Milestone: 6.15.0Keywords: FutureFeature, Triaged, UserExperience
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-04-23 17:11:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description momran 2022-03-11 14:24:32 UTC
Description of problem:

Implement a mechanism that is activated when creating a new virt-who configuration. This mechanism should be able to check if there is an existing virt-who configuration (which has been created earlier) that belongs to the same organization the new virt-who configuration is being created for, and if one is found, use the same 'rhsm_username' from the existing configuration in setting up the new configuration.


Justification:

Ensure that for all virt-who configurations that belong to the same organization, a single report is generated by virt-who and sent to Red Hat Satellite.

Comment 13 errata-xmlrpc 2024-04-23 17:11:01 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.15.0 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2024:2010