Hello,
I've found there is an Bugzilla reported on the same issue, probably
based on previous messages on the list. Please keep an eye on the BZ for
updates.
https://bugzilla.redhat.com/show_bug.cgi?id=1529253
Jiri
Dne 11.1.2018 v 11:11 Gonçalo Miguel napsal(a):
It's the same issue reported on message
https://www.redhat.com/archives/spacewalk-list/2017-December/msg00080.html.
I've checked what Michael said:
/
//"It looks like an issue in db schema. Can you verify that your schema//
//package is not modified (rpm -V spacewalk-schema) and your schema is//
//up-to-date (spacewalk-schema-upgrade).//
//
//Maybe even check if other spacewalk packages has not been changed//
//(rpm -V ...)."
/*Output*
Schema upgrade: [spacewalk-schema-2.7.28-1.el7] ->
[spacewalk-schema-2.7.28-1.el7]
Your database schema already matches the schema package version
[spacewalk-schema-2.7.28-1.el7].
Any help?
Gonçalo
On 10-01-2018 18:26, Wolfgang Stahl wrote:
Ah, sorry I haven’t read the whole mail. I had the same error on the
installation on CentOS 7.4.
So I’m not sure if it’s the same error…
Best Regards,
Wolfgang
Am 10.01.2018 um 18:22 schrieb Gonçalo Miguel
<[email protected] <mailto:[email protected]>>:
Hi Wolfgang
I'm not understanding the relation between the issues.
Syncing process only fails for EPEL repo and postgreSQL database was
successfully installed.
Gonçalo
On 10-01-2018 16:41, Wolfgang Stahl wrote:
Hi Goncalo,
had the same problem. These instructions
https://bugzilla.redhat.com/show_bug.cgi?id=1524221 were helpful
for me.
As mentioned there I have installed
spacewalk-admin-2.8.3-1.el7.centos.noarch and it works fine.
Wolfgang
Am 10.01.2018 um 17:15 schrieb Gonçalo Miguel
<[email protected] <mailto:[email protected]>>:
Hi all,
Same issue here syncing EPEL repo on spacewalk 2.7.
/Importing packages:
|##################################################| 100.0% //
//16:04:54 Linking packages to channel.//
//Traceback (most recent call last)://
// File "/usr/bin/spacewalk-repo-sync", line 257, in <module>//
// sys.exit(abs(main() or 0))//
// File "/usr/bin/spacewalk-repo-sync", line 240, in main//
// elapsed_time, channel_ret_code = sync.sync()//
// File
"/usr/lib/python2.7/site-packages/spacewalk/satellite_tools/reposync.py",
line 475, in sync//
// ret = self.import_packages(plugin, repo_id, url)//
// File
"/usr/lib/python2.7/site-packages/spacewalk/satellite_tools/reposync.py",
line 1038, in import_packages//
// importer.run()//
// File
"/usr/lib/python2.7/site-packages/spacewalk/server/importlib/importLib.py",
line 664, in run//
// self.fix()//
// File
"/usr/lib/python2.7/site-packages/spacewalk/server/importlib/packageImport.py",
line 76, in fix//
//self.backend.lookupChecksums(self.checksums)//
// File
"/usr/lib/python2.7/site-packages/spacewalk/server/importlib/backendOracle.py",
line 686, in lookupChecksums//
// raise e//
//spacewalk.server.rhnSQL.sql_base.SQLSchemaError: (99999,
'ERROR: LOCK TABLE can only be used in transaction blocks', '',
InternalError('LOCK TABLE can only be used in transaction
blocks\n',))//
//
/
Schema upgrade: [spacewalk-schema-2.7.28-1.el7] ->
[spacewalk-schema-2.7.28-1.el7]
Your database schema already matches the schema package version
[spacewalk-schema-2.7.28-1.el7].
Any idea?
Gonçalo
_______________________________________________
Spacewalk-list mailing list
[email protected] <mailto:[email protected]>
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
--
Jiří Dostál | Associate Software Engineer
Red Hat Satellite
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
