Description of problem: Unable to update RHEL host for RHV due to katello-agent and gofer dependency. ~~~ Error: Package: katello-agent-3.5.1-2.el7sat.noarch (rhel-7-server-rhv-4-mgmt-agent-rpms) Requires: gofer >= 2.12.5 Installed: gofer-2.12.3-1.el7.noarch (@rhel-7-server-rhv-4-mgmt-agent-rpms) gofer = 2.12.3-1.el7 Available: gofer-2.7.7-2.el7sat.noarch (rhel-7-server-rhv-4-mgmt-agent-rpms) gofer = 2.7.7-2.el7sat Available: gofer-2.7.7-3.el7sat.noarch (rhel-7-server-rhv-4-mgmt-agent-rpms) gofer = 2.7.7-3.el7sat Available: gofer-2.7.8-1.el7.noarch (rhel-7-server-rhv-4-mgmt-agent-rpms) gofer = 2.7.8-1.el7 ~~~ Version-Release number of selected component (if applicable): RHEL 7.6/7.7 with 'rhel-7-server-rhv-4-mgmt-agent-rpms' repo How reproducible: 100% Steps to Reproduce: 1. Try to update RHEL based RHV host Actual results: Fails to update via yum update and/or triggered from RHV-M Expected results: Should not fail Additional info: The issue is the version of 'gofer' availabe in the channel 'rhel-7-server-rhv-4-mgmt-agent-rpms' repo is older than required for katello-agent. A possible workaround is to exclude katello packages when updating and perform the update manually from each host: # yum update --exclude=katello*
Is there any update on this issue? I have simply excluded the package while updating.
This will be fixed by including the new gofer rpm in RHV channels, handled with bug #1768230
I was testing new katello-agent-3.5.1-2.el7sat.noarch and gofer-2.12.5-5.el7sat.noarch with their dependencies from sat tools 6.6 channel and integration of katello-agent with engine and hosts worked perfectly. Tested with Satellite 6.6 installed from CDN, also engine + hosts was installed from synced content from CDN provided in Satellite.
Tested build is included in erratum
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/RHEA-2019:3753