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: 
All guides must be searched for the occurrences of "yum install" run on Satellite Server.
For example, https://access.redhat.com/documentation/en-us/red_hat_satellite/6.5/html-single/provisioning_guide/index#Provisioning_Bare_Metal_Hosts-Configuring_Red_Hat_Satellites_Discovery_Service

Section number and name:
For example, 6.4. Configuring Red Hat Satellite’s Discovery Service:
~~~~
 Enter the following commands on the Capsule Server:

# yum install foreman-discovery-image rubygem-smart_proxy_discovery
~~~~
But there more instances of yum install with other packages.

Describe the issue: 
BZ#1739389 introduces a bug around installing additional Satellite packages caused by the new package locking feature

Suggestions for improvement: 
To all places where we ask users to install additional packages on Satellite Server, add the workaround from BZ#1739389 comment#3

Hi Sergei,
How is different than BZ#1739389?
(Just trying to determine the scope here)

Also, there is no comment #3 in 1739389 yet. Are you sure you linked the correct BZ#?

Thank you

Kind regards,
Vlada

> Suggestions for improvement: 
> To all places where we ask users to install additional packages on Satellite
> Server, add the workaround from BZ#1739389 comment#3

I think you meant BZ#1738199 comment#3

Hi Vlada,

(In reply to Vlada Grosu from comment #1)
> Hi Sergei,
> How is different than BZ#1739389?
> (Just trying to determine the scope here)
BZ#1739389 is about adding a new section about the package locking feature. I believe that we do not need a new section because no actions from the user are required here. Therefore, no user story available. 
> 
> Also, there is no comment #3 in 1739389 yet. Are you sure you linked the
> correct BZ#?
sorry, it's BZ#1738199 comment #3.
> 
Thank you

These changes are ready to be published with 6.6-beta documentation.