On Mon, Apr 19, 2010 at 9:12 AM, Brandon Perkins <[email protected]> wrote: > > Please open an ticket with support. Issues that impact more customers > usually get higher priority and will ultimately be fixed faster. Please > reference this bug so an Issue Tracker will be associated with this bug.
Opening a support ticket with Red Hat about anything related to Red Hat Network is a very painful process. After having opened the bugzilla ticket referenced and a follow up support ticket, I see it took this email on the mail list to get somebody at Red Hat to find the location of the leak. Maybe I am reading too much into the coincident time lines :) Interestingly enough, Red Hat's current support answer to the continually broken 'RHN Auto Update Errata' issues (cron :yum -y update") is now broken as well. Your updated cron entry is (yum clean all && yum -y update) , hehe... I know I have ranted on public lists in the past, but I continue to really wonder if anybody that works at Red Hat has systems on RHN hosted with "Auto Apply Errata" checked. I suppose I could open my 6th support ticket on the matter, but why not rant on a mail list, which provokes action less painfully! daryl _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
