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.

Bug 1734763

Summary: [RFE] Locking everything and not supporting system updates outside of sat upgrades.
Product: Red Hat Satellite Reporter: Jameer Pathan <jpathan>
Component: Satellite MaintainAssignee: Martin Bacovsky <mbacovsk>
Status: CLOSED ERRATA QA Contact: Jameer Pathan <jpathan>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: apatel, inecas, kgaikwad, mbacovsk, pcreech
Target Milestone: 6.7.0Keywords: FutureFeature
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-maintain-0.4.8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-14 12:58:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jameer Pathan 2019-07-31 11:32:02 UTC
Description of problem:
Locking everything and not supporting system updates outside of sat upgrades.

Version-Release number of selected component (if applicable):
- Satellite 6.6.0 snap 13

Actual results:
- Currently we only lock packages of satellite repo using FM.

Expected results:
- Locking everything and not supporting system updates outside of sat upgrades.

Additional info:

Comment 3 Martin Bacovsky 2019-08-28 20:16:15 UTC
Created redmine issue https://projects.theforeman.org/issues/27732 from this bug

Comment 4 Bryan Kearney 2019-09-05 16:04:45 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27732 has been resolved.

Comment 5 Jameer Pathan 2020-01-28 10:27:33 UTC
Verified

Verified with:
- Satellite 6.7.0 snap 10
- rubygem-foreman_maintain-0.5.1-1.el7sat.noarch

For Satellite >= 6.6, all packages are in locked state. Satellite user now have
to use foreman maintain packages install/update <package> command to
install packages. 

# foreman-maintain packages --help
Usage:
    foreman-maintain packages [OPTIONS] SUBCOMMAND [ARG] ...

Parameters:
    SUBCOMMAND                    subcommand
    [ARG] ...                     subcommand arguments

Subcommands:
    lock                          Prevent packages from automatic update
    unlock                        Enable packages for automatic update
    status                        Check if packages are protected against update
    install                       Install packages in an unlocked session
    update                        Update packages in an unlocked session
    is-locked                     Check if update of packages is allowed

Options:
    -h, --help                    print help

Comment 8 errata-xmlrpc 2020-04-14 12:58:36 UTC
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-2020:1442