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: None

Section Number and Name: None

Describe the issue: 
In the Satellite 6.6 new package locking feature is going to be introduced. It needs to be covered in our documentation. The feature is there to protect Satellite server form unwanted updates of underlying packages that can cause various inconsistencies and failures of the server.

The feature has upstream documentation  https://github.com/theforeman/foreman_maintain/wiki/Version-locking-of-Foreman-packages

Based on feedback during testing the feature will be further tuned and the final version may change in its functionality.

Suggestions for improvement: 

Additional information:

Thank you for opening this ticket, Martin.
I'll look into it.