Bug 1559189

Summary: [Docs][Virtual Instances Guide] Clarify when user should change the default virt-who interval
Product: Red Hat Satellite Reporter: Julie <juwu>
Component: DocumentationAssignee: satellite-doc-list
Status: CLOSED DUPLICATE QA Contact: satellite-doc-list
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: adahms
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: 2018-11-07 12:23:02 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 Julie 2018-03-21 23:47:13 UTC 
Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html-single/virtual_instances_guide/#creating-virt-who-configuration-with-hammer (Section 3.1 item 3)
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html-single/virtual_instances_guide/#virtual_machine_subscription_process-1 (Section 4.2 step4)

Describe the issue: 

It is not clear whether users should change the virt-who interval from the default value and when users should change it.

Section 3.1 says recommended value is 2 hours.

Section 4.2 says says default value is 1 hour, and user should not change it unless requested by Red Hat Support.

According to the healthcheck report for a customer, it says default is 60 seconds, and recommended should be 900 seconds.  -> (possibly meant minutes instead of seconds)

According to the healthcheck report for a customer, the value should be adjusted after the bulk activities of provisionings and system registrations are done. 

Suggestions for improvement: 
* Confirm what is the recommended value.
* Add in info on when to adjust the value, for example after the initial provisionings and system registrations are done. 

Additional information: 
This issue was identified when researching for the My customer pilot project.
Comment 1 Andrew Dahms 2018-11-07 12:23:02 UTC 
BZ#1602034 has since been raised, and contains information and recommendations about this feature.

Closing as a duplicate and using the bug noted above to complete this work.

*** This bug has been marked as a duplicate of bug 1602034 ***