+++ This bug was initially created as a clone of Bug #1428606 +++
Adding clone for OSP10
Description of problem:
During undercloud deployment, the docker registry is being configured by default even though default installations do not need it.
Version-Release number of selected component (if applicable):
OSP 11
How reproducible:
Always
Steps to Reproduce:
1. deploy undercloud
2.check for docker registry
3.
Actual results:
docker registry running (or failed to start)
Expected results:
docker not running or trying to run.
Additional info:
This is compounded by the fact that the docker registry service no longer exists in RHEL 7.3 Extras docker packages. It causes undercloud installs and updates/upgrades to fail
--- Additional comment from wes hayutin on 2017-03-02 18:22:36 EST ---
WORKAROUND: In the undercloud.conf file
set the following:
hieradata_override = foo.yaml
in foo.yaml
# turn off docker registry
enable_docker_registry: false
Mike:
The new package name is docker-distribution. Puppet-tripleo should now be updated to use this package on older branches (see the previous comment).
I don't think we want to change the defaults for this release as it would affect the tech preview instructions to enable the containerized compute role right?
Is this still a high priority?
This was filed in conjunction with bug 1428608. I viewed it as an either/or situation. I still think that we shouldn't enable the docker registry if we're not deploying containers (which is the default for OSP 10), but I'll leave it to your team to decide whether to fix this or not.