Docker service can't be started after upgrade fuel node
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
Critical
|
MOS Maintenance |
Bug Description
Steps to reproduce:
1. Install latest Fuel 8.0 with MU
2. Deploy any cluster
3. Try to upgrade the Fuel master node to proposed MU using following instruction: https:/
Observed behaviour:
After restart master node docker service can't be started:
[root@nailgun ~]# sudo systemctl status docker.service -l
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/
Active: failed (Result: exit-code) since Tue 2017-07-11 11:06:26 UTC; 8min ago
Docs: http://
Process: 2216 ExecStart=
Main PID: 2216 (code=exited, status=1/FAILURE)
Jul 11 11:06:26 nailgun.
Jul 11 11:06:26 nailgun.
Jul 11 11:06:26 nailgun.
Jul 11 11:06:26 nailgun.
Jul 11 11:06:26 nailgun.
Jul 11 11:06:26 nailgun.
Jul 11 11:06:26 nailgun.
Jul 11 11:06:26 nailgun.
Jul 11 11:06:26 nailgun.
Jul 11 11:06:26 nailgun.
Changed in fuel: | |
importance: | Undecided → Critical |
assignee: | nobody → MOS Maintenance (mos-maintenance) |
milestone: | none → 8.0-updates |
Changed in fuel: | |
assignee: | MOS Maintenance (mos-maintenance) → Alexey Stupnikov (astupnikov) |
Changed in fuel: | |
status: | New → Confirmed |
I was able to reproduce this issue by simply restarting docker
containers, docker services and rebooting master node twice.
From my point of view this issue is caused by a combination of
suboptimal docker's PV size and a docker bug. I have tested the
workaround from bug #1604941 and it worked just great.
https:/ /bugs.launchpad .net/fuel/ +bug/1604941/ comments/ 8
Assigning back to mos-maintenance team as there is no reliable
solution to backport for this bug.