commit 51d723a9ff0d7af47d1974a8e77fe7187e57357b
Author: Alex Schultz <email address hidden>
Date: Fri Jun 21 14:07:34 2019 -0600
Handle registries with incorrect certs correctly
We actually end up allowing registries with incorrect certificates in
the upload code so they get treated the same as inscure registries.
This change updates the return code of the is_insecure_registry to match
how we handle these registries in the image uploader. Additionally, this
means that when the container image prepare code runs, we will correctly
include these registries that have ssl enabled but incorrect
certificates will correctly be included in the
DockerInsecureRegistryAddress setting.
Reviewed: https:/ /review. opendev. org/666913 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=51d723a9ff0 d7af47d1974a8e7 7fe7187e57357b
Committed: https:/
Submitter: Zuul
Branch: master
commit 51d723a9ff0d7af 47d1974a8e77fe7 187e57357b
Author: Alex Schultz <email address hidden>
Date: Fri Jun 21 14:07:34 2019 -0600
Handle registries with incorrect certs correctly
We actually end up allowing registries with incorrect certificates in registry to match ureRegistryAddr ess setting.
the upload code so they get treated the same as inscure registries.
This change updates the return code of the is_insecure_
how we handle these registries in the image uploader. Additionally, this
means that when the container image prepare code runs, we will correctly
include these registries that have ssl enabled but incorrect
certificates will correctly be included in the
DockerInsec
Change-Id: I7fba881645ec2e a167c064be07ed6 d4281b7ed3d
Closes-Bug: #1833751