Re: [Spacewalk-list] Duplicate packages in selection and spacewalk

[Andreas Dijkman]

Yes, that worked! I’ve added the saltstack channel again but didn’t include it 
in the kickstart key or kickstart profile. That worked.

Now I only have to create a saltstack-state that adds that channel and starts 
the salt-stack-stuff. Thanks for the workaround!

Kind regards,

Andreas Dijkman


> On 19 May 2016, at 14:23, Kalchik, Jeffery  wrote:
> 
> Good morning. 
>  
> The hash clash isn’t unknown, I have it albeit under different channels.
>  
> Given your situation, as a fall back, you could run spacewalk-channel during 
> a chrooted post install script, to add your SaltStack channel and install 
> packages there.  Not optimal, but a possibility.  I do this for things that I 
> really can’t determine until run time, like installing the HP Proliant 
> Support Pack.
>  
> Jeff Kalchik
> Systems Engineering
> Land O’Lakes
>  
> From: spacewalk-list-boun...@redhat.com 
> [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Andreas Dijkman
> Sent: Wednesday, May 18, 2016 10:23 AM
> To: spacewalk-list 
> Subject: [Spacewalk-list] Duplicate packages in selection and spacewalk
>  
> Hi,
>  
> We have a SW2.4-installation, successfully setup with PXE-boot, kickstart, 
> the works.
>  
> I recently started using SaltStack as configuration management, so I’ve added 
> the SaltStack-repository to my SpaceWalk-system 
> (https://repo.saltstack.com/yum/rhel6/ 
> <https://repo.saltstack.com/yum/rhel6/>). Everything works fine until I try 
> to kickstart a system using PXE or ISO. Somehow the SpaceWalk-system is 
> confused about duplicate packages that are the same in versions but not in 
> hash. In my case it first breaks on the package pciutils. I think Spacewalk 
> decides to serve the wrong package during installation so anaconda is 
> complaining it can’t find the correct package. SaltStack isn’t playing nice 
> because in their repo they are supplying the same packages as used in CentOS. 
> But the packages from Oracle Linux and CentOS are different from each other.
>  
> After I removed the SaltStack-channels and packages from SpaceWalk, the 
> Kickstart worked fine again…
>  
> Is there a way to prioritise packages during kickstart with spacewalk or give 
> a spacewalk-channel priority above other channels? I really want to keep the 
> SaltStack-channel in our SpaceWalk-server, but if it breaks updates, I have 
> to figure something else out.
> 
> Kind regards,
> 
> Andreas Dijkman
> This message may contain confidential material from Land O'Lakes, Inc. (or 
> its subsidiary) for the sole use of the intended recipient(s) and may not be 
> reviewed, disclosed, copied, distributed or used by anyone other than the 
> intended recipient(s). If you are not the intended recipient, please contact 
> the sender by reply email and delete all copies of this message. 
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com <mailto:Spacewalk-list@redhat.com>
> https://www.redhat.com/mailman/listinfo/spacewalk-list 
> <https://www.redhat.com/mailman/listinfo/spacewalk-list>


smime.p7s
Description: S/MIME cryptographic signature
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Duplicate packages in selection and spacewalk

[Kalchik, Jeffery]

Good morning.

The hash clash isn’t unknown, I have it albeit under different channels.

Given your situation, as a fall back, you could run spacewalk-channel during a 
chrooted post install script, to add your SaltStack channel and install 
packages there.  Not optimal, but a possibility.  I do this for things that I 
really can’t determine until run time, like installing the HP Proliant Support 
Pack.

Jeff Kalchik
Systems Engineering
Land O’Lakes

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Andreas Dijkman
Sent: Wednesday, May 18, 2016 10:23 AM
To: spacewalk-list 
Subject: [Spacewalk-list] Duplicate packages in selection and spacewalk

Hi,

We have a SW2.4-installation, successfully setup with PXE-boot, kickstart, the 
works.

I recently started using SaltStack as configuration management, so I’ve added 
the SaltStack-repository to my SpaceWalk-system 
(https://repo.saltstack.com/yum/rhel6/). Everything works fine until I try to 
kickstart a system using PXE or ISO. Somehow the SpaceWalk-system is confused 
about duplicate packages that are the same in versions but not in hash. In my 
case it first breaks on the package pciutils. I think Spacewalk decides to 
serve the wrong package during installation so anaconda is complaining it can’t 
find the correct package. SaltStack isn’t playing nice because in their repo 
they are supplying the same packages as used in CentOS. But the packages from 
Oracle Linux and CentOS are different from each other.

After I removed the SaltStack-channels and packages from SpaceWalk, the 
Kickstart worked fine again…

Is there a way to prioritise packages during kickstart with spacewalk or give a 
spacewalk-channel priority above other channels? I really want to keep the 
SaltStack-channel in our SpaceWalk-server, but if it breaks updates, I have to 
figure something else out.

Kind regards,

Andreas Dijkman
This message may contain confidential material from Land O'Lakes, Inc. (or its 
subsidiary) for the sole use of the intended recipient(s) and may not be 
reviewed, disclosed, copied, distributed or used by anyone other than the 
intended recipient(s). If you are not the intended recipient, please contact 
the sender by reply email and delete all copies of this message.
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] Duplicate packages in selection and spacewalk

[Andreas Dijkman]

Hi,

We have a SW2.4-installation, successfully setup with PXE-boot, kickstart, the 
works.

I recently started using SaltStack as configuration management, so I’ve added 
the SaltStack-repository to my SpaceWalk-system 
(https://repo.saltstack.com/yum/rhel6/ 
). Everything works fine until I try to 
kickstart a system using PXE or ISO. Somehow the SpaceWalk-system is confused 
about duplicate packages that are the same in versions but not in hash. In my 
case it first breaks on the package pciutils. I think Spacewalk decides to 
serve the wrong package during installation so anaconda is complaining it can’t 
find the correct package. SaltStack isn’t playing nice because in their repo 
they are supplying the same packages as used in CentOS. But the packages from 
Oracle Linux and CentOS are different from each other.

After I removed the SaltStack-channels and packages from SpaceWalk, the 
Kickstart worked fine again…

Is there a way to prioritise packages during kickstart with spacewalk or give a 
spacewalk-channel priority above other channels? I really want to keep the 
SaltStack-channel in our SpaceWalk-server, but if it breaks updates, I have to 
figure something else out.

Kind regards,

Andreas Dijkman


smime.p7s
Description: S/MIME cryptographic signature
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list