> Stainforth, Matthew (SD/DS) wrote: > > Just wondering if anyone else has been bitten by this bug: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=566746 > > > > I ran into it while running RHEL 5.5 upgrade tests via RHN push. > Systems with less than 8GB of memory go OOM due to rhn_check leakage. > > > > Apparently the only ETA is "some time before the next minor > revision". It's a show stopper for our 5.5 upgrade plans for now. > > > > Just curious if anyone else has run into the same problem. > > > > 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. > > Thanks, > Brandon
I opened the ticket (2010608) with support on April 8, which is where I got the "sometime before next minor release" ETA. I was surprised that the bug was opened two months ago (well before RHEL 5.5 release) and it still has a low priority rating and medium severity. The low priority and loose ETA seemed paradoxical to me considering the fact that 5.5 was released and this bug cripples the use of RHN for more than a handful of patches. That is why I reached out to the list to see who else besides us might be hurting from it. I'm hoping it gets some traction soon since our RHEL 5.5 upgrade for unfortunately shelved until then. Thanks, Matt... _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
