Created attachment 1401700 [details] email-with-traceback Description of problem: I was trying to verify that Spacewalk is able to export channel which contains info about errata severity to the dump using rhn-satellite-exporter. Dumps seem to be exported successfully. In the current situation, I don't see a reason to sync this dump back as there were some errors. I consider this as a blocker in the whole process of exporting and reimporting it back to the Spacewalk. Version-Release number of selected component (if applicable): spacewalk-admin-2.8.4-1.el6.noarch spacewalk-backend-2.8.47-1.el6.noarch spacewalk-schema-2.8.17-1.el6.noarch How reproducible: 100% Steps to Reproduce: 1.sync the channels using cdn-sync: cdn-sync -c rhel-x86_64-server-7 -c rhn-tools-rhel-x86_64-server-7 2.export these two channels using rhn-satellite-exporter: rhn-satellite-exporter --verbose --dir=/tmp/satexport/ -c rhel-x86_64-server-7 -c rhn-tools-rhel-x86_64-server-7 --email Actual results: Exporting these channels result in traceback. Expected results: Export should exit without traceback. Additional info: I'm attaching two attachments: output of: tree /tmp/satexport/ email sent by rhn-satellite-exporter.
Created attachment 1401707 [details] directory structure of the dump
177cede178a600957e254945b20b94f68c0a1a88
Moving ON_QA
Verified some weeks ago with spacewalk-backend-2.8.52-1. I was able to sync content via cdn-sync, export it via rhn-satellite-exporter and sync it back via satellite-sync.
Spacewalk 2.8 has been released. https://github.com/spacewalkproject/spacewalk/wiki/ReleaseNotes28