[Spacewalk-list] channel weirdness

[Guy Matz]

That didn't exactly work.  The checksums in the repomd.xml file were not
right . . .  After manually updating repomd.xml I now get:
matz at nyc-lv01 ~ $ sudo yum repolist
Loaded plugins: fastestmirror, langpacks, priorities, rhnplugin, versionlock
This system is receiving updates from RHN Classic or Red Hat Satellite.
Determining fastest mirrors
schro                                                    | 2.9 kB     00:00
schro/7/x86_64/primary_db                                  |  97 kB   00:00
prod-centos7-x86_64                                      | 1.0 kB     00:00
prod-centos7-x86_64/group                                | 893 kB     00:00
prod-centos7-x86_64/primary                              |  12 MB     00:01
Error: Error reading from file
/var/cache/yum/x86_64/7/prod-centos7-x86_64/primary.xml.gz: CRC check
failed 0x584621a9 != 0xfd19ef97L

Any advice?

On Wed, Jul 14, 2021 at 10:02 AM Guy Matz <guymatz at gmail.com> wrote:

> Ah!!  So it looks like my metadata files got created, but with a ".new"
> extension!!
>
> matz at pdx-lv01:/var/cache/rhn/repodata/prod-centos7-x86_64$ ls -lrt
> total 608196
> -rw-r--r-- 1 root root      1039 May  3 08:48 repomd.xml
> -rw-r--r-- 1 root root  11414104 May  3 08:48 primary.xml.gz
> -rw-r--r-- 1 root root 248871638 May  3 08:48 other.xml.gz
> -rw-r--r-- 1 root root  27746744 May  3 08:48 filelists.xml.gz
> -rw-r--r-- 1 root root  12895419 Jun 25 13:48 primary.xml.gz.new
> -rw-r--r-- 1 root root  32289039 Jun 25 13:48 filelists.xml.gz.new
> -rw-r--r-- 1 root root 289556494 Jun 25 13:48 other.xml.gz.new
>
> What's up with that?! Can I just mv the .new files in place?
>
>
> On Mon, Jul 12, 2021 at 1:10 PM Brian Long <briandlong at gmail.com> wrote:
>
>> There are a couple of things to check.  When you promote a channel
>> using spacewalk-manage-channel-lifecycle, it takes a while for spacewalk to
>> generate the new yum metadata (could be 5-15 minutes depending on your
>> server and other activities).  You can run "ls -ltr /var/cache/rhn/repodata
>> | tail" to see if the channel you promoted has updated the metadata.  Also,
>> yum-based systems typically cache the repodata locally for six hours.
>> Unless you run "yum clean metadata" and "yum check-update" manually, it
>> could be up to six hours before your hosts see the updated repodata from
>> Spacewalk.  This can be lowered in /etc/yum.conf on each client, but it
>> will add more load to your spacewalk server.
>>
>> /Brian/
>>
>> On Fri, Jul 9, 2021 at 6:48 PM Guy Matz <guymatz at gmail.com> wrote:
>>
>>> Hello!  I have archived my prod channel and promoted from test to prod,
>>> however my clients don't see the new updates in the prod channel!  I see
>>> the updates on the spacewalk server, but not on the clients!  What's up
>>> with that?!
>>> _______________________________________________
>>> Spacewalk-list mailing list
>>> Spacewalk-list at redhat.com
>>> https://listman.redhat.com/mailman/listinfo/spacewalk-list
>>
>> _______________________________________________
>> Spacewalk-list mailing list
>> Spacewalk-list at redhat.com
>> https://listman.redhat.com/mailman/listinfo/spacewalk-list
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20210714/d5fea071/attachment.htm>