upgrade fails if nova vm is launched
Bug #1596653 reported by
Steven Dake
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla |
Fix Released
|
Critical
|
Steven Dake | ||
Liberty |
Won't Fix
|
Critical
|
Steven Dake | ||
Mitaka |
Fix Released
|
Critical
|
Steven Dake |
Bug Description
deployed kolla stable/liberty (1.0.2 pending)
init-runonce
create a nova vm
kolla-ansible upgrade (after setting openstack_version: 2.0.2 - stable/mitaka pending)
receive following error from Docker engine:
Jun 27 14:26:05 minime-03 docker[1423]: time="2016-
Jun 27 14:26:05 minime-03 docker[1423]: time="2016-
Surely there must be a workaround.
Changed in kolla: | |
assignee: | nobody → Steven Dake (sdake) |
Changed in kolla: | |
milestone: | newton-2 → newton-3 |
Changed in kolla: | |
milestone: | newton-3 → newton-rc1 |
Changed in kolla: | |
milestone: | newton-rc1 → newton-rc2 |
Changed in kolla: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Note even after Kolla bombs out, the libvirt container is gone. I think this should be as simple as starting a new libvirt container and ignoring the error from docker engine. Its ok if it leaks the libvirt information I suspect.