[Spacewalk-list] CentOS 7 yum transaction aborted status incorrectly reported by Spacewalk 2.4

[Kobus Bensch]

I have seen something similar, but on Centos6. The way I worked around it was to increase the script timeout for the scheduled actions. I think the default is 600, I changed this to 1800.

----- Original Message -----
From: "Robert Paschedag" <robert.paschedag at web.de>
To: "Coffman, Anthony J" <Tony.Coffman at snapon.com>
Cc: spacewalk-list at redhat.com
Sent: Monday, 18 July, 2016 16:34:28
Subject: Re: [Spacewalk-list] CentOS 7 yum transaction aborted status incorrectly reported by Spacewalk 2.4

Because rpm returned exit code 0 (no error), everything is OK. Also, as stated, the package is already installed. Nothing to argue with.

Regards
Robert
Am 18.07.2016 4:30 nachm. schrieb "Coffman, Anthony J" <Tony.Coffman at snapon.com>:
>
> I patched around 20 CentOS 7 systems yesterday.
>
>  
>
> Spacewalk reported all of the scheduled actions completed.
>
>  
>
> 5 of them experienced a yum aborted condition resulting in duplicate packages and a little mess to cleanup.  For those 5 systems, Spacewalk recorded the transaction as “Completed” (green) but in the action details recorded “Requested packages already installed (code 0)”.  So I think there may be a condition when yum aborts that isn’t correctly trapped and reported by Spacewalk 2.4
>
>  
>
> yum history shows the transaction aborted but I don’t yet know why.  I’ve been all over the systems logs but I haven’t found the reason for the transaction aborted yet.
>
>  
>
> I haven’t found a common denominator between these 5 as all 20 systems are very similar setups.
>
>  
>
> Has anybody else seen something similar on 7.x?
>
>  
>
> Regards,
>
> --Tony
>
>  
>
>  

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