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/red-hat-satellite/6.2/single/virtual-instances-guide/#software_requirements

Section Number and Name: 4.2. SOFTWARE REQUIREMENTS

Describe the issue: This section states that the virt-who daemon may be installed on the Satellite Server, an external Capsule Server, or a dedicated instance of RHEL, which is correct. However, chapter 2, item 3 states that you can choose between either the Satellite Server, or a dedicated instance of RHEL.

Suggestions for improvement:

1. Correct chapter 2, item 3, to match the requirements stated in "4.2. SOFTWARE REQUIREMENTS".
2. Correct the grammar of the opening sentence in "4.2. SOFTWARE REQUIREMENTS".

Setting release flags.

Matt replied with the following via email, which I take to be subject matter expert review, so I will progress and raise a merge request.

"Thank you, Russell. I send the updated PDF over to my customer and the changes look good to both of us.  They also said thank you for the attention on updating the docs.

Matt Ruzicka"

Attention: Brandi

As noted in comment 3, the reporter and customer have reviewed the changes I made for this BZ ticket, so I have raised a merge request. Note that while making these quite minor changes, I also made some markup corrections.


git diff view:

https://gitlab.cee.redhat.com/satellite-6-documentation/virtual-instances-guide/commit/1e4bde88bb47a03ce9f2d120242d075e9e9e37f7

Merge request:

https://gitlab.cee.redhat.com/satellite-6-documentation/virtual-instances-guide/merge_requests/7

Setting release flags.

Russell,

I accepted the Merge Request and am moving this bug to Verified.

Thanks,
Brandi

Since the changes for this BZ ticket have been reviewed and approved, I have republished the Virtual Instances Guide to the Customer Portal [1].


[1] https://access.redhat.com/documentation/en/red-hat-satellite/6.2/single/virtual-instances-guide/