Bug 1428826

Summary: undercloud fails to deploy due to docker-registry service not found
Product: Red Hat OpenStack Reporter: Jon Schlueter <jschluet>
Component: instack-undercloudAssignee: James Slagle <jslagle>
Status: CLOSED ERRATA QA Contact: Arik Chernetsky <achernet>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 10.0 (Newton)CC: achernet, apevec, fpercoco, jjoyce, jstransk, mburns, mcornea, rhel-osp-director-maint, sasha, vcojot
Target Milestone: asyncKeywords: Automation, AutomationBlocker, ZStream
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-tripleo-5.5.0-4.el7ost instack-undercloud-5.2.0-2.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1428608 Environment:
Last Closed: 2017-03-06 19:38:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1428608    
Bug Blocks:    

Description Jon Schlueter 2017-03-03 12:45:05 UTC
+++ This bug was initially created as a clone of Bug #1428608 +++

Description of problem:
During undercloud deployment, docker-registry is started in puppet.  A recent docker release removed docker-registry, so the service fails to start which causes undercloud deployment to fail

Version-Release number of selected component (if applicable):
Ocata RDO
OSP 11
OSP 10

How reproducible:
Always

Steps to Reproduce:
1.deploy undercloud with default options
2.
3.

Actual results:
undercloud fails

Expected results:
undercloud install succeeds

Additional info:

Related bug 1428606 has been filed to disable docker registry by default.


Workaround:

In the undercloud.conf file
set the following:

hieradata_override = foo.yaml

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

--- Additional comment from Mike Burns on 2017-03-02 18:26 EST ---



--- Additional comment from Mike Burns on 2017-03-02 18:43:10 EST ---

RHEL bug that dropped docker-registry:  https://bugzilla.redhat.com/show_bug.cgi?id=1388923

--- Additional comment from Alan Pevec on 2017-03-02 20:17:35 EST ---

(In reply to Mike Burns from comment #2)
> RHEL bug that dropped docker-registry: 
> https://bugzilla.redhat.com/show_bug.cgi?id=1388923

That bug says docker-registry is unmaintained since long time and docker-distribution should be used.
So bug is in tripleo that it uses docker-registry at all.
On the RPM level, docker-distribution has correct Obsoletes/Provides:
 http://pkgs.devel.redhat.com/cgit/rpms/docker-distribution/tree/docker-distribution.spec?h=extras-rhel-7.3#n54
but they missed to add compat docker-registry.service symlink :(

--- Additional comment from Alan Pevec on 2017-03-02 20:23:15 EST ---

> So bug is in tripleo that it uses docker-registry at all.

ok, that's already fixed https://github.com/openstack/puppet-tripleo/commit/a21f1a193a7076a335d82f47cab04340da9c93ff

Why is it failing then in Ocata ?!

--- Additional comment from Mike Burns on 2017-03-02 20:44:12 EST ---

(In reply to Alan Pevec from comment #4)
> > So bug is in tripleo that it uses docker-registry at all.
> 
> ok, that's already fixed
> https://github.com/openstack/puppet-tripleo/commit/
> a21f1a193a7076a335d82f47cab04340da9c93ff
> 
> Why is it failing then in Ocata ?!

The other half of the change was only in master:

https://review.openstack.org/#/c/440842/

--- Additional comment from Jiri Stransky on 2017-03-03 07:31:35 EST ---

Linking another patch that has to be backported alongside, to prevent introducing this bug:

https://bugs.launchpad.net/tripleo/+bug/1666459

Comment 2 Jason Joyce 2017-03-06 13:00:29 UTC
CI testing passed where it was previously failing.  Marking Verified

Comment 4 errata-xmlrpc 2017-03-06 19:38:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0451.html