Hide Forgot
Description of problem: "Auto Errata Update" do not work for newly published package. Version-Release number of selected component (if applicable): Satellite 5.4.1 nightly spacewalk-java-1.2.39-68.el6sat.noarch spacewalk-backend-1.2.13-48.el6sat.noarch How reproducible: always (tested on RHEL5 and 6 variant) with one RHEL4 client Steps to Reproduce: 1. Prepare RHEL4 client and install old version of some package and register it to Satellite and then move it to your custom channel # rpm -q zsh zsh-4.2.0-3.EL.3.x86_64 2. Your custom channel contains zsh-4.2.0-3.EL.3.x86_64, zsh-4.2.0-4.EL.4.5.x86_64 and others 3. Enable Auto Errata Update Details -> Properties -> [CHECK] Automatic application of relevant errata 4. Create errata with zsh-4.2.0-4.EL.4.5.x86_64 and publish it to the channel 5. Ensure WebUI shows applicable errata 6. Run `rhn_chek -vv` to get new errata installed Actual results: Errata do not get installed (no event were created) Note: I have ensured all errata related taskomatic tasks finished before I have run rhn_check: Errata was pushed before 11:50 WebUI shows: Errata Cache: 2011-05-12 11:50:00 EDT FINISHED Errata Notification Mail: 2011-05-12 11:50:00 EDT FINISHED Errata Notification Queue: 2011-05-12 11:50:00 EDT FINISHED Command line from client: # date Thu May 12 11:53:33 EDT 2011 # rhn_check -vv D: do_call packages.checkNeedUpdate ('rhnsd=1',) D: local action status: (0, 'rpm database not modified since last update (or package list recently updated)', {}) Expected results: Errata event should be created and errata installed by rhn_check Additional info: This might be an duplicate of bug 694829. I have to check with RHEL4 client.
Using info from bug 694829, I have switched "Auto Errata Update" to No and then again to Yes and that triggered event creation and `rhn_check -vv` nicely upgraded the package.
I have tested with RHEL6 client and it behaves same way (including the workaround from comment #1). But, I have asked tlestach and he believes "Auto Errata Update" do not handle erratas in custom channels, so this might be just a NOTABUG. Sorry for a spam in that case.