Bug 1428606 - docker-registry trying to start regardless of whether containers are enabled
Summary: docker-registry trying to start regardless of whether containers are enabled
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: instack-undercloud
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Dan Prince
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks: 1428848 1428853 1428871
TreeView+ depends on / blocked
 
Reported: 2017-03-02 23:20 UTC by Mike Burns
Modified: 2020-04-15 15:25 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1428848 1428853 1428871 (view as bug list)
Environment:
Last Closed: 2017-08-04 14:06:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2955121 0 None None None 2017-03-06 09:51:40 UTC

Description Mike Burns 2017-03-02 23:20:21 UTC
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

Comment 1 wes hayutin 2017-03-02 23:22:36 UTC
WORKAROUND: In the undercloud.conf file
set the following:

hieradata_override = foo.yaml

in foo.yaml
# turn off docker registry
enable_docker_registry: false

Comment 3 Chris Paquin 2017-05-12 17:46:39 UTC
Seeing OSP 10 when attempting to update undercloud. Should I open a new bug.

Comment 4 Dan Prince 2017-06-26 21:05:48 UTC
Looks to me that we've already backported fixes here to upstream stable/ocata and stable/newton that contain the new docker-distribution package:

http://git.openstack.org/cgit/openstack/puppet-tripleo/tree/manifests/profile/base/docker_registry.pp?h=stable/newton

Is it perhaps just something we need to cherry-pick downstream or just rebase and rebuild?

----

Also, Wes's workaround looks valid to me.

Comment 5 Dan Prince 2017-07-07 15:21:09 UTC
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?

Comment 6 Mike Burns 2017-07-24 12:08:43 UTC
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 11), but I'll leave it to your team to decide whether to fix this or not.

Comment 7 Dan Prince 2017-08-04 14:06:58 UTC
Closing for now as to keep things simple.


Note You need to log in before you can comment on or make changes to this bug.