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.

Bug 2084115

Summary: Stop/disable the virt-who service needs to present in the Documentation after removal of virt-who configuration
Product: Red Hat Satellite Reporter: Sonam <sshewale>
Component: DocumentationAssignee: Marie Hornickova <mdolezel>
Documentation sub component: default QA Contact:
Status: CLOSED WONTFIX Docs Contact:
Severity: unspecified    
Priority: unspecified CC: mdolezel, peter.vreman
Version: 6.10.4   
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-01 21:00:04 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 Sonam 2022-05-11 12:46:16 UTC
Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/configuring_virtual_machine_subscriptions_in_red_hat_satellite/troubleshooting-virt-who#removing-an-existing-virt-who-configuration_vm-subs-satellite

Section Number and Name:  

A.2. Removing an Existing virt-who Configuration


Describe the issue: 

1. According to section "A.2. Remove an existing virt-who Configuration", the customer has removed the Virt-who Configuration from WEBUI as well as Satellite CLI.

2. However customer wants to completely remove the virt-who configuration so there should be a step to Stop and disable of virt-who service.

~~~
# systemctl stop virt-who
# systemctl disable virt-who
~~~

Suggestions for improvement: Customer is saying in the documentation that there should be stop/disable the virt-who service should be included for complete removal of Virt-who configuration

Additional information: Applicable on satellite 6.10 also.

Comment 1 Brad Buckingham 2023-07-21 21:06:39 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 2 Brad Buckingham 2023-09-01 21:00:04 UTC
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.