Old container started during the fuel update
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Alexander Kislitsky |
Bug Description
Upgrading Fuel from 5.0 to 5.1.
Set of containers are not started due to rabbitmq container is not started.
In the 'supervisorctl' console we have BACKOFF error for rabbitmq container, but in 'docker ps' output we have rabbitmq container of 5.0 version. This bug can be with any container.
By the logs we can restore workflow:
1. all containers are stopped by supervisord api call
2. all containers are stopped by docker api call (due to supervisord bugs)
3. supervisord starts one of stopped containers
4. upgrading workflow
5. new container can't be started with error: Error: Cannot start container fuel-core-
For fix this bug we should switch configs of containers to new version after db is dumped, cobbler configs are saved and before stopping services by supervisord api call.
Fix proposed to branch: master /review. openstack. org/112892
Review: https:/