Bug 104908
| Summary: | RHN errata updates: failure to remove successful updates from errata list. | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Network | Reporter: | Need Real Name <jebates> |
| Component: | RHN/Web Site | Assignee: | Adrian Likins <alikins> |
| Status: | CLOSED WONTFIX | QA Contact: | Red Hat Satellite QA List <satqe-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | RHN Stable | CC: | rhn-bugs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-10-16 18:34:22 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
October 4. Updated all critical errata. (25 listed) Result 16 were successful. 9 failed of the 16 that were successful, 15 of them had previously succeeded only one was a success that had previously failed. A check of the new errata list still lists 25 errata. This bug has been closed due to inactivity. Please open a new bug with specific details if this problem is still occurring or if an enhancement is needed. |
Description of problem: I schedule errata "critical" updates. They run, some successfully. BUT some of the successful ones do not get removed from the errata list.(About 15 of them) Repeat above. Same result Version-Release number of selected component (if applicable): How reproducible: Happens every time. Steps to Reproduce: Schedule critical errata updates 1. 2. 3. Actual results: out of about 20 updates, approximately 15 succeed, 5 fail. New errata list contains many (not always all) of the "successful" ones as well as the failures Expected results: Successful ones should be removed from the errata list. Additional info: Fault has existed for a long time. I detected it only recently. It can be checked (with a lot of work) by looking at the archived actions which have both successes and failures recorded, and comparing that with the current errata list.