GNOME Bugzilla – Bug 592077
Procedure: periodically check RHN account
Last modified: 2010-10-04 13:28:04 UTC
The automatic application of updates via RHN doesn't always work properly. One possible reason for this is that local packages we have installed (RPMForge or GNOME custom) conflict with updates in some fashion. The simplest way to catch when this is happening is to make sure some human goes to our RHN account on a regular basis, logs in and makes sure that everything looks clean. We need to establish a procedure for this. If doing this monthly is good enough (I think it is, though ideally it would happen more frequently), then a simple procedure would to be to make the "monthly TODO check-off" part of the sysadmin team meeting. We'd probably have a designated volunteer to do it before the meeting, but this is fast enough so it could be done right then if it wasn't done before. To get access to our RHN account, a new user account needs to be created by one of the people that has access to our account already. (Current list: me, gleblanc, rossg, jrb, menthos, ovitters) Note that RHN accounts are scoped to the organization, so even if you have an existing RHN account, a new account <username>-gnome will need to be created.
I have setup a Google Calendar reminder to login and verify server status at RHN for every two weeks. I have also documented the SOP: http://live.gnome.org/Sysadmin/SOP/RHN