[Spacewalk-list] syncing epel to spacewalk 2.7
Gonçalo Miguel
gmiguel at neosbybold.com
Wed Jan 10 16:15:36 UTC 2018
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20180110/f888a584/attachment.htm>
More information about the Spacewalk-list
mailing list