Description of problem: yum versionlock prevents additional satellite packages being installed. The most important exhibit of the bahavior is foreman-discovery-image package. The issue is that the new locking mechanism assumes that all packages are either installed by default or handled by installer. That is not true, the most important example is foreman-discovery-image Version-Release number of selected component (if applicable): 6.6.0 How reproducible: deterministic Steps to Reproduce: 1. # yum install foreman-discovery-image Loaded plugins: product-id, search-disabled-repos, subscription-manager, versionlock Excluding 420 updates due to versionlock (use "yum versionlock status" to show them) No package foreman-discovery-image available. Error: Nothing to do Actual results: installing of additional satellite rpms is prevented Expected results: user can install additional satellite rpms somehow
You can use the following steps as a workaround to unblock your installation. Proper fix will follow soon. $ foreman-maintain packages unlock $ yum install foreman-discovery-image $ foreman-maintain packages lock
In BZ#1739416, I am adding the workaround Martin shared in comment#3 to our docs everywhere `yum install` is issued. This is the list of packages that we tell users to run `yum install` with to either install or to ensure that the package is installed, in our documentation: ipa-client foreman-proxy ipa-admintools rh-mongodb34 rh-mongodb34-syspaths postgresql-server rhel-system-roles ipa-client tfm-rubygem-foreman* gssproxy nfs-utils sssd adcli realmd ipa-python-compat krb5-workstation tfm-rubygem-foreman_templates python-pulp-manifest nfs-utils bind-utils foreman-discovery-image rubygem-smart_proxy_discovery tfm-rubygem-net-ssh-krb foreman-telemetry pcp-mmvstatsd pcp-webapi pcp-webapp-grafana pcp-webapp-vector pcp-pmda-apache pcp-pmda-postgresql pcp-system-tools pcp-webjs livecd-tools libvirt-client rubygem-smart_proxy_discovery satellite-clone rubygem-foreman_maintain virt-who
Created redmine issue https://projects.theforeman.org/issues/27686 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/27686 has been resolved.
*** Bug 1753605 has been marked as a duplicate of this bug. ***
VERIFIED. @Satellite 6.6.0 Snap22 rubygem-foreman_maintain-0.4.9-1.el7sat.noarch User has now two options how to install additional rpms on Satellite machine: 1) Supported way includes running installer with --upgrade flag and takes longer (~3min) # foreman-maintain packages install -y foreman-discovery-image 2) Unsupported? way skips running installer so is much faster (~20sec) # foreman-maintain packages unlock # yum -y install foreman-discovery-image # foreman-maintain packages lock With new locking mechanism everything is locked (not only Sat but also OS) To upgrade all packages there is command: # foreman-maintain packages update \\* Implicit default all packages is not possible: # foreman-maintain packages update ERROR: parameter 'PACKAGES ...': no value provided Yet worse explicit all packages (*) has to be escaped twice \\* (one would expect only once \* like with yum) Going to file a BZ for this as it's not obvious and documented
Filed https://bugzilla.redhat.com/show_bug.cgi?id=1759588 - foreman-maintain packages update fails to update all packages
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/RHSA-2019:3172