Breaking out part of the RFE from https://bugzilla.redhat.com/show_bug.cgi?id=1184568 Specifically, that there should be a version lock so that a customer can not upgrade the satellite exception through approved tools like foreman maintain.
I am guessing that we do not need to implement all of 1512600, 1459358, and 1316246. Linking them all together so we decide which to do and then close out the others.
Created redmine issue https://projects.theforeman.org/issues/26216 from this bug
Upstream bug assigned to mbacovsk
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26409 has been resolved.
Created attachment 1595049 [details] version_locking_issue_1
RE comment#16 and comment#17: There are still some packages not handled by installer which are not installed by default and the locking mechanism is preventing to install these packages, e.g. foreman-dicovery-image Filed BZ1738199 to resolve the situation around these packages.
Requested release notes, Docs BZ was linked. https://bugzilla.redhat.com/show_bug.cgi?id=1739389
Updated Docs request
Verified Verified with: - rubygem-foreman_maintain-0.4.5-1.el7sat.noarch Version locking via yum working with foreman-maintain considering: - Feature is locking all packages from Satellite repo, not just installed packages. - This means lock is applied on installed package updates along with new packages from Satellite repo. - In case user try to run katello-remove on existing satellite install then version lock still remains there and not allowing users to install packages even though repos are enabled. a bz[1] is filed to address it and workaround is there. - Redundant options for all subcommands under package commands but its not a blocker. Bug is filed[2] Note: currently lock is working for packages coming from Satellite repo not for everything e.g. lock for RHEL repo/custom repo is not in place for now and requires additional changes, so another RFE is filed for it[3]. And, it is not supported for capsule. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1728253 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1734766 [3] https://bugzilla.redhat.com/show_bug.cgi?id=1728253
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:3181