[Spacewalk-list] error populating transaction

Fri Apr 1 17:16:21 UTC 2016

Solved. Lesson learned, do not set your default umask to 077. The directory the rpm was in was not world readable therefore apache could not see it.

From: <spacewalk-list-bounces at redhat.com<mailto:spacewalk-list-bounces at redhat.com>> on behalf of Noah Rømer <baronmog at gmail.com<mailto:baronmog at gmail.com>>
Reply-To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Date: Friday, April 1, 2016 at 12:12 PM
To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Subject: Re: [Spacewalk-list] error populating transaction

Do you have multiple channels or repositories that it might come from? If you have the file in one channel, it won't be accessible through other channels, until you sync them as well.

On Fri, Apr 1, 2016 at 6:14 AM, Camp, Neil (NIH/NCI) [C] <neil.camp at nih.gov<mailto:neil.camp at nih.gov>> wrote:
I apologize for the extra e-mails. I am not sure what is going on at all. I really believed that the error message yesterday was for version libXent-1.2.2-3.el7.x86_64.rpm but I misread it and fat fingered it. The error log in packaging.log shows libXext-1.3.3-3.el7.x86_64.rpm so I tried to download the rpm through spacewalk and it showed as being unavailable. I then did a find looking for the rpm on the file system and it found
./582/libXext/1.3.3-3.el7/x86_64/58284e32f1f3343c56722653e7870e8062c1570cd965802bc284da6480d9d366/libXext-1.3.3-3.el7.x86_64.rpm

If it is on the file system but showing as unavailable in Spacewalk where could the disconnect be coming from?

From: <spacewalk-list-bounces at redhat.com<mailto:spacewalk-list-bounces at redhat.com>> on behalf of Neil Camp <neil.camp at nih.gov<mailto:neil.camp at nih.gov>>
Reply-To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Date: Friday, April 1, 2016 at 8:24 AM

To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Subject: Re: [Spacewalk-list] error populating transaction

I did find the disconnect but I am not sure where the package information came from. After closer inspection the package the installer is complaining about (libXent-1.2.2-3.el7.x86_64.rpm) is not in any channel nor is it in my install media. I did not look at the versions close enough. Currently (libXext-1.3.3-3.el7.x86_64.rpm) is the latest version in my parent channel. Where would this package information/repo be generated to give the incorrect version compared to what is in the channel?

From: <spacewalk-list-bounces at redhat.com<mailto:spacewalk-list-bounces at redhat.com>> on behalf of Lachlan Musicman <datakid at gmail.com<mailto:datakid at gmail.com>>
Reply-To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Date: Thursday, March 31, 2016 at 5:34 PM
To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Subject: Re: [Spacewalk-list] error populating transaction

I also had this problem, but with a different solution.

The files weren't actually there - they had been moved/disappeared when I discovered a configuration snafu when setting up. When we set up we had added packages to the parent Channel, but then decided to keep the parent channel clear, and only populate child channels. When we cleared the packages out of the parent channel (they still existed in the child channel!), the download would fail and then the install would fail.

A re-configuration and confirming that the packages were still in the child channel was sufficient.

Doesn't sound like this is your issue - but check to make sure the kickstart is subscribed to the channel the package is in.

Cheers
L.

------
The most dangerous phrase in the language is, "We've always done it this way."

- Grace Hopper

On 1 April 2016 at 07:10, Noah Rømer <baronmog at gmail.com<mailto:baronmog at gmail.com>> wrote:
Do you have a spacewalk proxy/squid cache between the kickstarting system and the spacewalk server? I had a similar problem and removing the spacewalk proxy from the equation made it go away.

On Thu, Mar 31, 2016 at 12:45 PM, Camp, Neil (NIH/NCI) [C] <neil.camp at nih.gov<mailto:neil.camp at nih.gov>> wrote:
Hello,

I have been digging around the internet and the archives and have not found a solution. I have a kickstart for a CentOS 7 desktop and the packaging.log shows
INFO Packaging:   populate transaction set
ERR packaging:  error populating transaction after 10 retries: failure Packages/libXent-1.2.2-3.el7.x86_64.rpm from anaconda:  [Errno 256] No more mirrors to try.

No packages have been installed. The package in question is in the main channel. Did I miss-configure my kickstart or is there some sort of disconnect with my parent channel? The kickstart was generated through spacewalk and was not created by hand.

Thank you.

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

--
Squirrels are the lunatic teenagers of the animal kingdom.

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

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

--
Squirrels are the lunatic teenagers of the animal kingdom.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20160401/f59ce298/attachment.htm>