On 13/10/14 13:26, Veiko Kukk wrote:
I'm trying to upgrade from pulp-1.1.11-1.el6.noarch to
pulp-server-2.3.1-1.el6.noarch. Both systems are Centos 6.5.
Repo creation, population etc works fine, but I ran into problems with
securing selectively some of the repos.
Old syntax goes like this and runs/works fine:
# pulp-admin -u admin -p password repo update --id reponame
--consumer_ca=/etc/pulp/capulp.crt --consumer_cert=/etc/pulp/client.crt
--consumer_key=/etc/pulp/client.key
Successfully updated repository [ reponame ]
Looks very similar to this bug
https://bugzilla.redhat.com/show_bug.cgi?id=1119126
When executing:
# pulp-admin -u admin -p password rpm repo update --repo-id reponame
--host-ca=/etc/pki/pulp/ca.crt --auth-ca=/etc/pki/pulp/capulp.crt
--auth-cert=/etc/pki/pulp/client.crt
The server indicated one or more values were incorrect. The server
provided the
following error message:
Configuration key 'https_ca' is not supported
More information can be found in the client log file ~/.pulp/admin.log.
And from the log:
2014-10-13 13:24:36,961 - ERROR - Exception occurred:
href: /pulp/api/v2/repositories/reponame/
method: PUT
status: 400
error: Configuration key 'https_ca' is not supported
traceback: None
data: {u'args': [u"Configuration key 'https_ca' is not
supported"]}
Veiko
_______________________________________________
Pulp-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/pulp-list
