| Summary: | "Upgrade Satellite Clients Using the Bulk Repository Set UI" is not working as expected. | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Raviraj Lavande <rlavande> |
| Component: | katello-agent | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED WONTFIX | QA Contact: | Radovan Drazny <rdrazny> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.4 | CC: | ahumbe, alexander.lackner, asamad, ben.argyle, chrism, greartes, hasuzuki, hyu, janarula, jbuckley, kagarwal, ktordeur, mcorr, mvanderw, ramsingh, rdrazny, satellite6-bugs, saydas, sraut, swadeley, vlblink, wpinheir |
| Target Milestone: | Unspecified | Keywords: | PrioBumpGSS, Triaged |
| Target Release: | Unused | Flags: | ben.argyle:
needinfo?
(satellite6-bugs) |
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-05-01 13:30:59 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: | |
|
Description
Raviraj Lavande
2018-11-14 13:32:20 UTC
Please let us know when will the fix for this bug will be released ? I also can reproduce the same on Satellite 6.5 as well. 1. Create an RHEL 7.5 host and install katello-agent\gofer\python-gofer\katello-host-tools etc packages from "rhel-7-server-satellite-tools-6.4-rpms" repository. 2. Now, enable "rhel-7-server-rpms" and "rhel-7-server-satellite-tools-6.5-rpms" on this host. 3. Apply all the packages from Satellite server via katello-agent [ which will include updates for base OS packages as well as katello-agent\gofer\python-gofer\katello-host-tools etc packages ]. 4. Check-in satellite GUI the task will be displayed completed but result of the same action in the host is as below, --> "yum history info" about the last transaction says "** Aborted **" and it failed at "1 warning: %postun(gofer-2.12.3-1.el7.noarch) scriptlet failed, signal 15". --> "yum history" also complains about "** Found 43 pre-existing rpmdb problem(s), 'yum check' output follows:" which means the transaction was not completed. --> There will be duplicate packages present on the host. --> Latest kernel installed will only have a vmlinuz file created but not the initramfs file which will create problem during reboot. To fix this situation, 1. yum-complete-transaction 2. yum reinstall <latest-kernel-package> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A) This doesn't happen if we simply execute "yum update" or use the feature "Package updates via Remote Execution". B) Above behavior also does not happen if we don't enable "rhel-7-server-satellite-tools-6.5-rpms" on this host and perform the patching via katello-agent. The error "1 warning: %postun(gofer-2.12.3-1.el7.noarch) scriptlet failed, signal 15" and fact mentioned in points A and B, led me to believe that, --> Everything goes smooth till package installation or upgradation. --> When cleanup gets started, yum attempts to remove the old gofer package and as a postuninstall script, it attempts to restart the goferd service. I believe that is the point where the transaction gets aborted as with to restart of goferd service, the communication with satellite\capsule server(qdrouterd) gets disturbed. Let me know if the above analysis makes any sense. Just an FYI, as part of BZ#1767134, I have added docs to provide a workaround for BZ#1653040. Thanks, Melanie Satellite 6.4 is now End of Life. These bus will not be fixed on the 6.4 stream. Users of Satellite should upgrade to the latest version of Satellite to get access to the most current set of bugfixes and feature improvements. I'm still seeing this issue in Satellite 6.6, and expect to see it when I migrate to 6.7. Looking at https://bugzilla.redhat.com/show_bug.cgi?id=1653040 I really don't see the workaround in https://bugzilla.redhat.com/show_bug.cgi?id=1767134 as all that helpful if I have more than a handful of hosts. I can push out something via Ansible, but this seems like something that Satellite should be able to fix/deal with as part of its own upgrading, rather that relying on outside intervention? |