| Summary: | "empty transaction" when running errata install of package not cached in client | ||
|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Petter Hassberg <phassber> |
| Component: | Provisioning | Assignee: | Tomas Lestach <tlestach> |
| Status: | CLOSED DEFERRED | QA Contact: | Red Hat Satellite QA List <satqe-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 541 | CC: | cperry, slukasik |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-05-29 20:11:36 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 462714 | ||
Description of problem: A new package is pushed to satellite channel, and an errata is created containing this new package. When applying this errata to a system which have an older version of that package installed and local cache on system does not contain the newer version from errata, then scheduled errata install fails with "(6,), 'Error while executing packages action: empty transaction', {}" If re-schedueling the errata installation after running #yum clean all on target system, errata package installation works fine afterwards. Version-Release number of selected component (if applicable): 5.4.1 Rhel 6.1 client running rhn-setup-1.0.0-61.el6.noarch rhn-check-1.0.0-61.el6.noarch rhnsd-4.9.3-2.el6.x86_64 rhn-client-tools-1.0.0-61.el6.noarch yum-rhn-plugin-0.9.1-26.el6_1.1.noarch yum-utils-1.1.30-6.el6.noarch rhnlib-2.5.22-10.el6.noarch yum-metadata-parser-1.1.2-16.el6.x86_64 yum-3.2.29-17.el6.noarch How reproducible: 100% Steps to Reproduce: 1. Push package to a channel 2. Create errata with that rpm package in it 3. apply errata to a system which is a.) subscribing to that channel, and b.) has a previous version of package installed -- so it appears on the errata "affected systems view" in Satellite UI 4. rhn_check or wait for osad to pick up on the client system If package installs first time, repeat with a newer version of package. Actual results: Error while executing packages action: empty transaction [[6]] Expected results: Errata installation to update affected package. Additional info: