Actions
Issue #5416
closed
Docker remote seems to ignore ssl_client_* options on sync
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 58
Quarter:
Description
When creating a docker remote with a ssl_client_certificate and ssl_client_key, the sync seems to ignore them. Here's the remote i created:
{
"count":1,
"next":null,
"previous":null,
"results":[
{
"_href":"/pulp/api/v3/remotes/docker/docker/c32d31d2-f984-4baf-b5e1-d23b83ead9f8/",
"_created":"2019-09-06T19:21:13.772540Z",
"_type":"docker.docker",
"name":"1-docker_sync_test-docker-2e6664ad-e565-4d26-88f6-c2d9104c37e5",
"url":"https://devel.localhost.example.com",
"ssl_ca_certificate":"2d85b0335c442e9c2b3ec6e6a3eebf168a76731d773587b53567554367cb3236",
"ssl_client_certificate":"3d621f0c311fc3c595698049cbcd32d6f0ae5cb29a936eb4c9daa583593cb5c2",
"ssl_client_key":"3920d22ec4ff2d804a7ae0838ad2b1b1959f906ce2244690a144d00e462ff13f",
"ssl_validation":true,
"proxy_url":null,
"_last_updated":"2019-09-06T19:32:11.946413Z",
"download_concurrency":20,
"policy":"immediate",
"upstream_name":"default_organization-docker-docker_sync_test-docker_pulp3-capsule_test",
"whitelist_tags":null
}
]
}
but when i sync, it doesn't appear to use the configured certs
Related issues
Actions
.