[Spacewalk-list] Errata problems

uri van creveld uri.van.creveld at gmail.com
Wed Mar 7 09:34:41 UTC 2012


Hi, i'm running spacewalk 1.5 on rhel 5 server/clients and got some
problems. Here is what i did:
1. I created a rhel5 base channel, and uploaded all rhel 5.7 rpms and
errata. Things looked ok.
2. I upgraded some systems via applying all the errata. It went fine.
Kernel was updated to 2.6.18-274
3. Now that rhel 5.8 is out, i uploaded all its rpms to the channel, as
well as the errata.
I now face some problems
1. Rhel 5.8 comes with kernel 2.6.18-308. However, there is no specific
errata connected with its rpms. This causes the gui to ignore the fact that
the 2.6.18-274 kernel does have errata related to it. What now happens is
that the gui shows servers that were not upgraded to rhel 5.7 and run an
old kernel - as no longer needing to apply kernel errata.
their 'errata' section no longer show kernel errata. It can still be
updated via the 'packages' section - but if that's the case - why do i need
spacewalk? I can do yum update and get it over with.
2. It seems spacewalk only shows the latest errata for every package. So
lets say httpd got a critical security errata and then a minor bugfix (and
that is actually the case in rhel5.8)  - only the latest errata is shown as
pending installation. This means i cannot rely on spacewalk to tell me if
the update is really critical or not, if it needs boot etc. Again, if this
is the case - why not use yum update in stead?
Thanksx
Uri
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20120307/a3d34d4d/attachment.htm>


More information about the Spacewalk-list mailing list