Description of problem: Version-Release number of selected component (if applicable): >>rpm -qa |grep pulp-consumer pulp-consumer-client-2.4.0-0.29.beta.fc20.noarch How reproducible: always Steps to Reproduce: >> pulp-consumer --map Traceback (most recent call last): File "/usr/bin/pulp-consumer", line 9, in <module> load_entry_point('pulp-client-consumer==2.4.0', 'console_scripts', 'pulp-consumer')() File "/usr/lib/python2.7/site-packages/pulp/client/consumer/__init__.py", line 35, in main config_files, exception_handler_class=ConsumerExceptionHandler File "/usr/lib/python2.7/site-packages/pulp/client/launcher.py", line 85, in main server = _create_bindings(config, logger, username, password) File "/usr/lib/python2.7/site-packages/pulp/client/launcher.py", line 192, in _create_bindings validate_ssl_ca = config['server']['verify_ssl'].lower() != 'false' KeyError: 'verify_ssl' at the same time: >>pulp-consumer --help Usage: pulp-consumer [options] Options: -h, --help show this help message and exit -u USERNAME, --username=USERNAME credentials for the Pulp server; if specified will bypass the stored certificate -p PASSWORD, --password=PASSWORD credentials for the Pulp server; must be specified with --username --debug enables debug logging --config=CONFIG absolute path to the configuration file --map prints a map of the CLI sections and commands
This was fixed in the 2.4.1-0.1.alpha build.
after commenting the verify_ssl line in config file, there is no traceback
We are rebasing pulp-2.4.1, and so all of these bugs can no longer be considered VERIFIED. We will need to recheck them against the rebased build to make sure the cherry picking strategy did not introduce any regressions.
build: 2.5.0-0.6.beta