Bug 104630
| Summary: | Auto errata updates not working | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Network | Reporter: | Howard Holm <howard-redhat> |
| Component: | RHN/Web Site | Assignee: | Chip Turner <cturner> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fanny Augustin <fmoquete> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | RHN Stable | CC: | howard-redhat, rhn-bugs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-02-21 18:58: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: | |
| Embargoed: | |||
More information please, what version(s) of RH Linux are you running, what recent critical errata have not auto-applied. Also, please provide the results of: rpm -q up2date grep -e SkipList= /etc/sysconfig/rhn/up2date I'm running Red Hat 9 with all errata applied # rpm -q up2date up2date-3.1.23.2-1 # grep -e SkipList= /etc/sysconfig/rhn/up2date pkgSkipList=; fileSkipList=; removeSkipList=kernel*; The recent openssh and sendmail errata required manual updates, as did gtk-html when it came out last week. Removing security status given this issue isn't really a security flaw. *** This bug has been marked as a duplicate of 98907 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 Description of problem: I have two hosts with a basic entitlement. Both hosts have "Auto Errata Updates" set to "yes" which is verified on the details page for each host. Neither host will auto update. Critical updates have repeatedly become available, with notification to me by e-mail. As much as 12-24 hours after notification I can log in to Red Hat network, see critical updates available, see that the hosts both hosts have been checking in on schedule, and that no automatic updates have been done or are scheduled. Manually running up2date correctly notes that updates exist and updates the systems. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Wait for critical update to be released 2. 3. Additional info: It is dangerously misleading for security to believe your hosts are automatically receiving updates when they must be performed manually.