Failed to start docker-registry.service: Unit not found.

Bug #1683901 reported by Mark Hamzy
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

[hamzy@hamzy-tp-w540 tripleo-quickstart]$ (export VIRTHOST=9.114.219.30; bash quickstart.sh --ansible-debug --release mitaka $VIRTHOST 2>&1 | tee errors3)
...
    "cmd": "set -o pipefail && /home/stack/undercloud-install.sh 2>&1 | awk '{ print strftime(\"%Y-%m-%d %H:%M:%S |\"), $0; fflush(); }' > /home/stack/undercloud_install.log",
    "delta": "0:12:43.902304",
    "end": "2017-04-18 15:29:07.266368",
    "failed": true,
...
[stack@undercloud ~]$ tail /home/stack/undercloud_install.log
...
2017-04-18 15:17:02 | ---> Package docker-distribution.x86_64 0:2.6.0-1.el7 will be obsoleting
2017-04-18 15:17:02 | ---> Package docker-registry.x86_64 0:0.9.1-7.el7 will be obsoleted
...
2017-04-18 15:17:04 | Installing:
2017-04-18 15:17:04 | docker-distribution x86_64 2.6.0-1.el7 extras 3.3 M
2017-04-18 15:17:04 | replacing docker-registry.x86_64 0.9.1-7.el7
...
2017-04-18 15:18:50 | Erasing : docker-registry-0.9.1-7.el7.x86_64 120/157
...
2017-04-18 15:19:48 | Verifying : docker-registry-0.9.1-7.el7.x86_64 155/157
...
Error: Could not start Service[docker-registry]: Execution of '/bin/systemctl start docker-registry' returned 5: Failed to start docker-registry.service: Unit not found.
Error: /Stage[main]/Main/Service[docker-registry]/ensure: change from stopped to running failed: Could not start Service[docker-registry]: Execution of '/bin/systemctl start docker-registry' returned 5: Failed to start docker-registry.service: Unit not found.
...

[stack@undercloud ~]$ sudo rpm -qa | grep docker
python-docker-py-1.10.6-1.el7.noarch
python-docker-pycreds-1.10.6-1.el7.noarch
docker-distribution-2.6.0-1.el7.x86_64
[stack@undercloud ~]$ sudo yum install -y docker-registery
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
 * base: cosmos.illinois.edu
 * extras: centos.mirrors.tds.net
 * updates: centos.mirrors.tds.net
350 packages excluded due to repository priority protections
No package docker-registery available.
Error: Nothing to do
[stack@undercloud ~]$ cat /etc/yum.repos.d/delorean.repo
[delorean]
name=delorean-python-django-horizon-ce80bb6fec3cb0262728e7ae8b9d695cf832e5bf
baseurl=https://trunk.rdoproject.org/centos7-mitaka/ce/80/ce80bb6fec3cb0262728e7ae8b9d695cf832e5bf_f8fd3d22
enabled=1
gpgcheck=0
priority=1

Tags: quickstart
tags: added: quickstart
Changed in tripleo:
status: New → Triaged
importance: Undecided → Medium
milestone: none → pike-2
Revision history for this message
David Hill (david-hill-ubisoft) wrote :

I got this with RHEL 7.3 too.

Changed in tripleo:
milestone: pike-2 → pike-3
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Revision history for this message
Emilien Macchi (emilienm) wrote : Cleanup EOL bug report

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

Changed in tripleo:
importance: Medium → Undecided
status: Triaged → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.