Hide Forgot
post-rhn 500: Systems that check in get auto errata updates scheduled, but if the system doesn't check in after the errata is released, the errata update doesn't get scheduled (even though if you run up2date -l the system shows it needs the update.) (where 'check in' == rhn_check or up2date -p, somehow up2date -l doesn't seem to trigger the update getting scheduled)
Thanks for posting the bug. It appears that at some point, the errata is sort of scheduled for the machine since they show up as "Pending Events". But the association that the errata applies to the machine is not made on the web GUI. I think that is another bz entry.
re comment 1, the seamonkey errata for the sid in question is not pending as of 1.5 days after the errata was released this bug may be related to: bug 226897 (closed, rhn500), bug 232235, bug 232061
thanks. That is correct. As an aside, IMHO, the requirement that a system check into RHN in order for the Web GUI to be updated seems to cause a good amount of confusion. If the web GUI was updated when the errata is released, perhaps it would be less confusing. For example. 1. Errata is released. 2. I go to RHN GUI and see it applies to 40 of my systems, 10 have picked it up already, 30 have it scheduled. 3. I go along my happy way. Current, step #2 is not possible with RHN. I would only see the number of machines that are currently checking in and have seen the errata. step #3 is not possible either, since I am bitter in my old age! :) hopefully my comment is on-topic for this bug. thanks!
Good evening. Strangely enough, the wireshark errata now shows up in the "relevent errata" for this system in question. seamonkey should be there, but isn't. Will be curious to see what the next errata does :)
Just to confirm, the wireshark errata that went out a day ago is not yet scheduled for the system 'amelia' (sid in comment #5), right?
wireshark is scheduled seamonkey is not thanks!
This is very strange. I've been going thru all the queries used in the errata processing and scheduling code. I can't find any queries which even reference the rhnServerInfo table, which is where we keep track of when servers check in. I'm going to take a look at how we determine which servers get autoupdates and see if there's any issues there. I was in that code for the last release (RHN500) and so I think its pretty solid, but I'll take another look.
*** This bug has been marked as a duplicate of 237590 ***
Thanks for closing this bug in favour of a bug we can not see :(
Hi Daryl, sorry about that, that was not our intention. I've opened up bug 237590 and added you and John to it. Thanks for speaking up!