After Ocata to Pike undercloud upgrade docker-distribution service is not started

[Marius Cornea]

After Ocata to Pike undercloud upgrade docker-distribution service is not started hence the docker registry on undercloud is not available:

Steps to reproduce:
Deploy Ocata undercloud and overcloud
Upgrade repos to Pike

Upgrade undercloud:

openstack undercloud upgrade
openstack overcloud container image upload --verbose --config-file /usr/share/tripleo-common/container-images/overcloud_containers.yaml

(undercloud) [stack@undercloud-0 ~]$ systemctl status docker-distribution
● docker-distribution.service - v2 Registry server for Docker
   Loaded: loaded (/usr/lib/systemd/system/docker-distribution.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Thu 2017-06-08 12:00:18 UTC; 1h 14min ago
 Main PID: 615 (code=killed, signal=PIPE)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

(undercloud) [stack@undercloud-0 ~]$ sudo ss -lpn | grep 8787
(undercloud) [stack@undercloud-0 ~]$ sudo systemctl start docker-distribution
(undercloud) [stack@undercloud-0 ~]$ sudo ss -lpn | grep 8787
tcp LISTEN 0 128 192.168.0.1:8787 *:* users:(("registry",pid=26198,fd=4))
(undercloud) [stack@undercloud-0 ~]$

[Steve Baker (steve-stevebaker)]

I've set the importance to low because the undercloud registry is for development only. Production deployments should never use the undercloud docker-distribution registry as the local registry, so I don't see this as a huge issue for upgrades testing.

[Steve Baker (steve-stevebaker)]

Bringing this back up to High, since we're supporting the undercloud registry in production

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE