[Spacewalk-list] Is Bug 1529253 - LOCK TABLE can only be used in transaction blocks FIXED in 2.8?

[Francis Mondia]

Hi Robert,

Thanks for responding. TBH, I don't know why its failing for EPEL only. The guys in the bugtracker have confirmed this and presented their own ideas about it too.

At this point, all I want to know if this has been fixed in the new version so I can get a new install going and get rid of the emails I receive regarding this.

Kind regards,
Francis

-----Original Message-----
From: Robert Paschedag [mailto:robert.paschedag at web.de] 
Sent: Tuesday, 8 May 2018 5:32 PM
To: spacewalk-list at redhat.com; Francis Mondia <Francis.Mondia at endace.com>; spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Is Bug 1529253 - LOCK TABLE can only be used in transaction blocks FIXED in 2.8?

Am 8. Mai 2018 02:22:18 MESZ schrieb Francis Mondia <Francis.Mondia at endace.com>:
>Hi,
>
>We're having the issue described in this bugtracker
>https://bugzilla.redhat.com/show_bug.cgi?id=1529253
><https://bugzilla.redhat.com/show_bug.cgi?id=1529253>
>
>Has this been fixed in version 2.8?
>
>Seems that the only way to resolve it is to nuke and re-install, but be 
>mindful to set the database encoding is set properly. With this the 
>only option, upgrading to a new install with the latest stable version 
>seems the logical way to go IF ITS BEEN FIXED.
>

Well... Maybe I'm not that tired as I thought. Why does this error not trigger always? The "lock" should be executed on every repo to check the checksums.

So why is only the EPEL repo failing? This should have nothing to do with the encoding, I think.

Robert
>
>Kind regards,
>
>
>
>--
>Francis Mondia
>Engineering Systems Administrator


--
sent from my mobile device