Sent to wrong list, my mistake. Looking at coding an API stub to replace the spacecmd in the script, thanks for the advice.
On 2015-04-07 7:34, Tomas Lestach wrote: > Well, if you would be a Spacewalk user, I'd advise you to apply the patch > manually. > > Another option is to use channel.software.listErrata API directly instead of > calling > "spacecmd softwarechannel_listerrata", as spacecmd is more or less a wrapper > around > the API calls. > > Regards, > -- > Tomas Lestach > Red Hat Satellite Engineering, Red Hat > > ----- Original Message ----- > >> From: "J Epperson" <[email protected]> To: >> [email protected] Sent: Monday, April 6, 2015 4:00:22 PM Subject: >> [Spacewalk-list] Any Satellite 5.6 workarounds for spacecmd >> softwarechannel_listerrata bug 1180233? We have scripts to do security >> errata cloning for quality control in the patching cycles. These just broke >> after updating to Satellite 5.6 because of bug 1180233 which results in an >> error being returned by "spacecmd softwarechannel_listerrata". The bugfix >> (RHBA-2015:0281-1) is released only for Satellite 5.7, which requires RHEL6 >> instead of the RHEL5 we are running. We have a case open, but expect that it >> will be difficult to get Red Hat to help since spacecmd is not officially >> supported (although the scripting was done by a Red Hat engineer on a >> consulting engagement). Has anyone else worked through this situation? Any >> advice/workarounds? Thanks, J. >> _______________________________________________ Spacewalk-list mailing list >> Spacewalk-list@redh! at.com https://www.redhat.com/mailman/listinfo/spacewalk-list [1] > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list [1] Links: ------ [1] https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
