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: NEW --- 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: 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.