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.
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.
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 ***