Description of problem: Spacewalk-clone-by-date can not proceed if configuration file is used and option blacklist or removelist are not present. Version-Release number of selected component (if applicable): spacewalk-utils-2.3.2-5 How reproducible: Always Steps to Reproduce: 1. Have the following configuration file test.conf: { "username":"admin", "password":"redhat", "to_date": "2011-10-01", "errata": ["RHBA-2014:1646", "RHSA-2014:1635"], "channels":[ { "rhel-x86_64-server-6":"clone-rhel-x86_64-server-6" } ] } 2. spacewalk-clone-by-date -c test.conf Actual results: blacklist is not formatted correctly Additional info: In case options blacklist and removelist are present and even empty, the spacewalk-clone-by-date tool works as expected. { "username":"admin", "password":"redhat", "to_date": "2011-10-01", "errata": ["RHBA-2014:1646", "RHSA-2014:1635"], "blacklist":{}, "removelist":{}, "channels":[ { "rhel-x86_64-server-6":"clone-rhel-x86_64-server-6" } ] }
Committing to Spacewalk master: 6f0fe3165c5e84f21f074836e18fcb6405dfce7a
VERIFIED on spacewalk-utils-2.3.2-8.el6sat Reproducer in comment 0.
With the release of Red Hat Satellite 5.7 on January 12th 2015 this bug is being moved to a Closed Current Release state. The Satellite 5.7 GA Errata: - https://rhn.redhat.com/errata/RHSA-2015-0033.html Satellite 5.7 Release Notes: - https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.7/html-single/Release_Notes/index.html Satellite Customer Portal Blog announcement for release: - https://access.redhat.com/blogs/1169563/posts/1315743 Cliff NOTE: This bug has not been re-verified (moved to RELEASE_PENDING) prior to release. We assume that the bug has indeed been fixed and not regressed since we initially verified it. Please re-open in the future if needed.