[upgrade] storage volumes don't get created on upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Critical
|
Ihor Kalnytskyi | ||
5.1.x |
Fix Released
|
Critical
|
Ihor Kalnytskyi | ||
6.0.x |
Fix Released
|
Critical
|
Ihor Kalnytskyi |
Bug Description
After Fuel (master node) upgrade from 5.0.1 to 5.1 'dockerctl revert ${container_name}' command doesn't work and its execution leads to container crash:
[root@fuel-
Stopping rsync...
fuel-core-5.1-rsync
Stopping rsync...
fuel-core-5.1-rsync
fuel-core-5.1-rsync
c15743763d9fcee
[debug] commands.go:1905 End of CmdRun(), Waiting for hijack to finish.
2014/10/17 11:20:18 Error: Cannot start container c15743763d9fcee
mount its volumes
[root@fuel-
Error: Cannot start container fuel-core-
2014/10/17 11:29:48 Error: failed to start one or more containers
...
[root@fuel-
3911e3e7c987 storage/
7c53d8ea7e25 storage/repo:latest /bin/sh -c '/bin/ech 26 hours ago Exited (0) 26 hours ago fuel-storage-
I guess it happens because we don't install new (5.1) storage containers during Fuel upgrade, so docker is unable to re-build other new containers.
Changed in fuel: | |
assignee: | nobody → Matthew Mosesohn (raytrac3r) |
Changed in fuel: | |
status: | New → Confirmed |
tags: | added: in progress |
The problem here is storage containers don't get made. They are all defined in the config.py for fuel_upgrade, but not a single one gets made and there are no references in fuel_upgrade.log for them. This should affect 5.1.1 and 6.0 as well when upgrading from 5.1.