[Spacewalk-list] Some CentOS/EL6 Packages show up for EL7, and some EL7 for EL6

[prmarino1 at gmail.com]

Try restarting taskomatic it sounds like the reposync bunch may have gotten frozen
If that helps then you may need to increase the ram limit for taskomatic

  Original Message  
From: Ricky Boone
Sent: Thursday, January 14, 2016 15:13
To: spacewalk-list at redhat.com
Reply To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Some CentOS/EL6 Packages show up for EL7, and some EL7 for EL6

Here's another example of it happening. I'm still not sure what's
causing it. This time it is with the ldb update from a few days ago.

Additionally, I will say that I am using the errata-import.pl script
from the "CEFS: CentOS Errata for Spacewalk" site
(http://cefs.steve-meier.de/). It is currently at version 20150630,
which isn't the most recent one, but it didn't look like there were
any updates that jumped out as relevant to this, and I didn't think
that it would be modifying which packages were linked to different
repositories. I can update it to the latest version, and if
necessary, temporarily disable the cron job to try to rule it out if
it is suspected to be the problem.

Here are some screenshots if anyone is interested.

libldb i686 and x86_64 EL7 packages, linked to EL6:
http://i.imgur.com/vmwaLqb.png
http://i.imgur.com/3Wtkmw2.png

Affected system details page (happens to be the Spacewalk server this time):
http://i.imgur.com/wz4yZ8l.png

Affected system package updates: http://i.imgur.com/Ihp83hx.png

Errata details: http://i.imgur.com/xrlVLl7.png

Errata packages: http://i.imgur.com/CTFB6zV.png

Packages in centos6-x86_64-updates matching "el7":
http://i.imgur.com/R2cd8RB.png

Packages in centos6-i686-updates matching "el7":
http://i.imgur.com/cF4IxnB.png

Packages in centos7-x86_64-updates matching "el6":
http://i.imgur.com/waob4vy.png


On Thu, Dec 31, 2015 at 5:38 PM, Ricky Boone <ricky.boone at gmail.com> wrote:
> Adding further to the mystery...
>
> When I look at the logs under /var/log/rhn/reposync, I don't see any
> mention of el7 in centos6-x86_64-updates.log, or el6 in
> centos7-x86_64-updates.log. Strange...
>
> I've removed the el7 packages from CentOS 6 Updates, and visa versa,
> but yum update still marks the offending packages as available (even
> after yum clean all). I'm sure I'm missing a step, but I'll dig
> around some more.
>
> On Thu, Dec 31, 2015 at 4:55 PM, Ricky Boone <ricky.boone at gmail.com> wrote:
>> My apologies for starting a new thread... there appears to be an
>> existing thread going on here, but I just subbed to this list, so I
>> can't reply to it yet.
>>
>> https://www.redhat.com/archives/spacewalk-list/2015-December/msg00024.html
>>
>> I think I see similar behavior with my system. The issue was prompted
>> by a coworker that noticed some odd yum errors when he was trying to
>> update one of his systems. When I looked into it, the update was
>> trying to install EL7 packages on his EL6 system.
>>
>> The Spacewalk server is running version 2.3, on CentOS 6.7, but has
>> been upgraded from Spacewalk 2.2. All of the repositories were
>> created by spacewalk-common-channels while on 2.2. All of the
>> repositories are one-to-one with their respective channel (CentOS 7
>> Updates x86_64, etc.), with no repositories being linked to other
>> channels.
>>
>> When I search for el6 under Packages in the "CentOS 7 Updates
>> (x86_64)" channel, there are currently 142 matches, ranging from
>> autocorr-af-4.2.8.2-11.el6_7.1:1.noarch to
>> openssl-static-1.0.1e-42.el6_7.1.x86_64. Alternatively, when I search
>> for el7 in "CentOS 6 Updates (x86_64)", there are 134 matches. I have
>> not checked all channels yet.
>>
>> My suspicion is that there was something going on with the
>> mirrorlist.centos.org site, sending requests for one release to the
>> other, or that one of the mirrors had the wrong release listed for the
>> wrong URL, etc. I can't prove this, but that's all I can think of at
>> the moment. When I manually browse some of the sites returned, they
>> look okay.
>>
>> I'm going to try removing the offending packages and manually running
>> a sync... and do a couple spot checks to be sure that none of them
>> somehow ended up on the wrong platforms.
>>
>> Any thoughts would be appreciated.

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