[Spacewalk-list] yum not updating needed packages, which are shown on spacewalk

[Will Cladek]

I have a CentOS 5 x86_64 server subscribed to a spacewalk (0.5) channel containing the base and update repo packages for CentOS 5.3 x86_64. There are 20 packages that need updating, as confirmed by the system information on the spacewalk server. I'll pick on wireshark here. Spacewalk shows that I have wireshark-1.0.3-4.el5_2 installed, which is true, and need to update to wireshark-1.0.6-2.el5_3. However, when I do a "yum check-update" or "yum update" on the system itself, it shows no updates being available. Furthermore, yum doesn't even seem to be aware that the newer version of wireshark exists:

# yum list wireshark
Loaded plugins: fastestmirror, rhnplugin
Loading mirror speeds from cached hostfile
centos-5-x86_64 | 871 B 00:00
Installed Packages
wireshark.x86_64 1.0.3-4.el5_2 installed

Why won't yum show these updates?

[Will Cladek]

In fact, upon further investigation, it seems to be the case that ALL packages from the CentOS 5.3 x86_64 update repo aren't being recognized by yum (when doing a "yum list"), even though they are in the channel as verified on the spacewalk server. I just put both the base and update repos in the same channel, rather than making update a child channel as mentioned in another thread, but this wasn't a problem with spacewalk 0.2 and CentOS 5.2. Spacwalk shows kernel-2.6.18-128.1.1.el5.x86_64 being in the x86_64 channel, but not yum:

# yum list kernel
Loaded plugins: fastestmirror, rhnplugin
Loading mirror speeds from cached hostfile
centos-5-x86_64 | 871 B 00:00
Installed Packages
kernel.x86_64 2.6.18-92.1.18.el5 installed
kernel.x86_64 2.6.18-92.1.22.el5 installed
kernel.x86_64 2.6.18-128.el5 installed

In contrast, I have an i386 CentOS 5 system subscribed to an i386 channel containing both base and update packages from 5.3. Updating with yum works fine, and doing a yum list shows the packages from the update repo. In this case, Spacewalk shows kernel-2.6.18-128.1.6.el5.i686 being in the i386 channel, and so does yum:

# yum list kernel
Loaded plugins: fastestmirror, rhnplugin
Loading mirror speeds from cached hostfile
centos-5-i386 | 871 B 00:00
Installed Packages
kernel.i686 2.6.18-92.1.18.el5 installed
kernel.i686 2.6.18-92.1.22.el5 installed
kernel.i686 2.6.18-128.1.6.el5 installed

Is this somehow an issue specific to x86_64?

Post by Will Cladek
I have a CentOS 5 x86_64 server subscribed to a spacewalk (0.5) channel
containing the base and update repo packages for CentOS 5.3 x86_64.
There are 20 packages that need updating, as confirmed by the system
information on the spacewalk server. I'll pick on wireshark here.
Spacewalk shows that I have wireshark-1.0.3-4.el5_2 installed, which is
true, and need to update to wireshark-1.0.6-2.el5_3. However, when I do
a "yum check-update" or "yum update" on the system itself, it shows no
updates being available. Furthermore, yum doesn't even seem to be aware
# yum list wireshark
Loaded plugins: fastestmirror, rhnplugin
Loading mirror speeds from cached hostfile
centos-5-x86_64
| 871 B 00:00 Installed Packages
wireshark.x86_64
1.0.3-4.el5_2
installed
Why won't yum show these updates?

[Pradeep Kilambi]

Post by Will Cladek
In fact, upon further investigation, it seems to be the case that ALL
packages from the CentOS 5.3 x86_64 update repo aren't being
recognized by yum (when doing a "yum list"), even though they are in
the channel as verified on the spacewalk server. I just put both the
base and update repos in the same channel, rather than making update a
child channel as mentioned in another thread, but this wasn't a
problem with spacewalk 0.2 and CentOS 5.2. Spacwalk shows
kernel-2.6.18-128.1.1.el5.x86_64 being in the x86_64 channel, but not
# yum list kernel
Loaded plugins: fastestmirror, rhnplugin
Loading mirror speeds from cached hostfile
centos-5-x86_64
| 871 B 00:00 Installed Packages
kernel.x86_64
2.6.18-92.1.18.el5
installed
kernel.x86_64
2.6.18-92.1.22.el5
installed
kernel.x86_64
2.6.18-128.el5
installed
In contrast, I have an i386 CentOS 5 system subscribed to an i386
channel containing both base and update packages from 5.3. Updating
with yum works fine, and doing a yum list shows the packages from the
update repo. In this case, Spacewalk shows
kernel-2.6.18-128.1.6.el5.i686 being in the i386 channel, and so does
# yum list kernel
Loaded plugins: fastestmirror, rhnplugin
Loading mirror speeds from cached hostfile
centos-5-i386
| 871 B 00:00 Installed Packages
kernel.i686
2.6.18-92.1.18.el5
installed
kernel.i686
2.6.18-92.1.22.el5
installed
kernel.i686
2.6.18-128.1.6.el5
installed
Is this somehow an issue specific to x86_64?

Post by Will Cladek
I have a CentOS 5 x86_64 server subscribed to a spacewalk (0.5)
channel containing the base and update repo packages for CentOS 5.3
x86_64. There are 20 packages that need updating, as confirmed by
the system information on the spacewalk server. I'll pick on
wireshark here. Spacewalk shows that I have wireshark-1.0.3-4.el5_2
installed, which is true, and need to update to
wireshark-1.0.6-2.el5_3. However, when I do a "yum check-update" or
"yum update" on the system itself, it shows no updates being
available. Furthermore, yum doesn't even seem to be aware that the
# yum list wireshark
Loaded plugins: fastestmirror, rhnplugin
Loading mirror speeds from cached hostfile
centos-5-x86_64
| 871 B 00:00 Installed Packages
wireshark.x86_64
1.0.3-4.el5_2
installed
Why won't yum show these updates?

I fixed this issue and built new updates on Wednesday. I dont think
they synced the repo yet with these new packages.

Zeus, when you get a chance, can you pull the updated spacewalk-backend
and spacewalk-java packages into the 0.5 repo? I already built em into
koji. I still see older ones in the repo.

Thanks,
~ Prad

Post by Will Cladek
_______________________________________________
Spacewalk-list mailing list
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Jesus M. Rodriguez]

Pradeep,

I'll get these packages out on Monday.

jesus

Post by Will Cladek
In fact, upon further investigation, it seems to be the case that ALL
packages from the CentOS 5.3 x86_64 update repo aren't being recognized by
yum (when doing a "yum list"), even though they are in the channel as
verified on the spacewalk server.  I just put both the base and update repos
in the same channel, rather than making update a child channel as mentioned
in another thread, but this wasn't a problem with spacewalk 0.2 and CentOS
5.2.  Spacwalk shows kernel-2.6.18-128.1.1.el5.x86_64 being in the x86_64
# yum list kernel
Loaded plugins: fastestmirror, rhnplugin
Loading mirror speeds from cached hostfile
centos-5-x86_64
                 |  871 B     00:00     Installed Packages
kernel.x86_64
                                                    2.6.18-92.1.18.el5
                              installed
kernel.x86_64
                                                    2.6.18-92.1.22.el5
                              installed
kernel.x86_64
                                                    2.6.18-128.el5
                              installed
In contrast, I have an i386 CentOS 5 system subscribed to an i386 channel
containing both base and update packages from 5.3.  Updating with yum works
fine, and doing a yum list shows the packages from the update repo.  In this
case, Spacewalk shows kernel-2.6.18-128.1.6.el5.i686 being in the i386
# yum list kernel
Loaded plugins: fastestmirror, rhnplugin
Loading mirror speeds from cached hostfile
centos-5-i386
                  |  871 B     00:00     Installed Packages
kernel.i686
                                                   2.6.18-92.1.18.el5
                                installed
kernel.i686
                                                   2.6.18-92.1.22.el5
                                installed
kernel.i686
                                                   2.6.18-128.1.6.el5
                                installed
Is this somehow an issue specific to x86_64?

Post by Will Cladek
I have a CentOS 5 x86_64 server subscribed to a spacewalk (0.5) channel
containing the base and update repo packages for CentOS 5.3 x86_64.  There
are 20 packages that need updating, as confirmed by the system information
on the spacewalk server.  I'll pick on wireshark here.  Spacewalk shows that
I have wireshark-1.0.3-4.el5_2 installed, which is true, and need to update
to wireshark-1.0.6-2.el5_3.  However, when I do a "yum check-update" or "yum
update" on the system itself, it shows no updates being available.
 Furthermore, yum doesn't even seem to be aware that the newer version of
# yum list wireshark
Loaded plugins: fastestmirror, rhnplugin
Loading mirror speeds from cached hostfile
centos-5-x86_64
                 |  871 B     00:00     Installed Packages
wireshark.x86_64
                                                         1.0.3-4.el5_2
                               installed
Why won't yum show these updates?

I fixed this issue and built new updates on Wednesday. I  dont think they
synced the repo yet with these new packages.
Zeus, when you get a chance, can you pull the updated spacewalk-backend and
spacewalk-java packages into the 0.5 repo? I already built em into koji. I
still see older ones in the repo.
Thanks,
~ Prad

Post by Will Cladek
_______________________________________________
Spacewalk-list mailing list
https://www.redhat.com/mailman/listinfo/spacewalk-list

_______________________________________________
Spacewalk-list mailing list
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Will Cladek]

I found the other thread where a similar problem was noted, and it was caused by the repo data not being updated when new packages were pushed. I realized that my i386 packages had been there much longer than the x86_64 packages, so once I removed the repodata and forced it to rebuild, the new packages were found. Is this auto-rebuild issue what's being fixed in the new packages?

-Will

Post by Jesus M. Rodriguez
Pradeep,
I'll get these packages out on Monday.
jesus

Post by Will Cladek
In fact, upon further investigation, it seems to be the case that ALL
packages from the CentOS 5.3 x86_64 update repo aren't being recognized by
yum (when doing a "yum list"), even though they are in the channel as
verified on the spacewalk server. I just put both the base and update repos
in the same channel, rather than making update a child channel as mentioned
in another thread, but this wasn't a problem with spacewalk 0.2 and CentOS
5.2. Spacwalk shows kernel-2.6.18-128.1.1.el5.x86_64 being in the x86_64
# yum list kernel
Loaded plugins: fastestmirror, rhnplugin
Loading mirror speeds from cached hostfile
centos-5-x86_64
| 871 B 00:00 Installed Packages
kernel.x86_64
2.6.18-92.1.18.el5
installed
kernel.x86_64
2.6.18-92.1.22.el5
installed
kernel.x86_64
2.6.18-128.el5
installed
In contrast, I have an i386 CentOS 5 system subscribed to an i386 channel
containing both base and update packages from 5.3. Updating with yum works
fine, and doing a yum list shows the packages from the update repo. In this
case, Spacewalk shows kernel-2.6.18-128.1.6.el5.i686 being in the i386
# yum list kernel
Loaded plugins: fastestmirror, rhnplugin
Loading mirror speeds from cached hostfile
centos-5-i386
| 871 B 00:00 Installed Packages
kernel.i686
2.6.18-92.1.18.el5
installed
kernel.i686
2.6.18-92.1.22.el5
installed
kernel.i686
2.6.18-128.1.6.el5
installed
Is this somehow an issue specific to x86_64?

Post by Will Cladek
I have a CentOS 5 x86_64 server subscribed to a spacewalk (0.5) channel
containing the base and update repo packages for CentOS 5.3 x86_64. There
are 20 packages that need updating, as confirmed by the system information
on the spacewalk server. I'll pick on wireshark here. Spacewalk shows that
I have wireshark-1.0.3-4.el5_2 installed, which is true, and need to update
to wireshark-1.0.6-2.el5_3. However, when I do a "yum check-update" or "yum
update" on the system itself, it shows no updates being available.
Furthermore, yum doesn't even seem to be aware that the newer version of
# yum list wireshark
Loaded plugins: fastestmirror, rhnplugin
Loading mirror speeds from cached hostfile
centos-5-x86_64
| 871 B 00:00 Installed Packages
wireshark.x86_64
1.0.3-4.el5_2
installed
Why won't yum show these updates?

I fixed this issue and built new updates on Wednesday. I dont think they
synced the repo yet with these new packages.
Zeus, when you get a chance, can you pull the updated spacewalk-backend and
spacewalk-java packages into the 0.5 repo? I already built em into koji. I
still see older ones in the repo.
Thanks,
~ Prad

Post by Will Cladek
_______________________________________________
Spacewalk-list mailing list
https://www.redhat.com/mailman/listinfo/spacewalk-list

_______________________________________________
Spacewalk-list mailing list
https://www.redhat.com/mailman/listinfo/spacewalk-list

_______________________________________________
Spacewalk-list mailing list
https://www.redhat.com/mailman/listinfo/spacewalk-list

[mark]

Post by Will Cladek
In fact, upon further investigation, it seems to be the case that ALL
packages from the CentOS 5.3 x86_64 update repo aren't being recognized
by yum (when doing a "yum list"), even though they are in the channel as
verified on the spacewalk server. I just put both the base and update
repos in the same channel, rather than making update a child channel as
mentioned in another thread, but this wasn't a problem with spacewalk
0.2 and CentOS 5.2. Spacwalk shows kernel-2.6.18-128.1.1.el5.x86_64

<snip>
Right. I just used the sync_repo.sh script I posted a while back, and it didn't
work. Or, I thought it worked, and I think it got the right i386 release. But I
kept failing when I tried to do the upgrade, after unsubscribing my test system
from the 5.2 channel, and subscribing it to the 5.3. Then, last night, the
other admin I work with realized that I did *not* have an x86_64 repository,but
rather that it was full of the i386 version. He wound up remaking the cache,
and then seems to have gotten the correct release.

This is uncomfortable. I don't understand why this occurs in a released version
of software. I would have expected testing for something like a full subrelease
upgrade.

mark "way too much manual 'oh, yeah, got to do that, too'"

[Jesus M. Rodriguez]

On Fri, Apr 10, 2009 at 7:46 PM, mark <***@rcn.com> wrote:
[snip]

Mark,

Post by mark
This is uncomfortable. I don't understand why this occurs in a released version
of software. I would have expected testing for something like a full subrelease
upgrade.

You really need to stop complaining, because the folks on this mailing list have
done nothing but be gracious and help you with your problems.

Spacewalk is a released project, but it goes through minimal QA. In fact,
we rely on the community as much as we can to help QA the project.
Out of curiosity, how many bugs have you filed against Spacewalk? I
couldn't find
any from 'mark' or 'm.roth'.

If Spacewalk is not of high enough quality for you, feel free to buy
Red Hat Network
Satellite which comes with support and gets thoroughly tested.

jesus