upgrade.sh scripts should wait until all upgraded containers are started
Bug #1453400 reported by
Dennis Dmitriev
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Matthew Mosesohn |
Bug Description
Reproduced on CI test 'deploy_
Scenario:
1) Install Fuel v6.0 admin node;
2) Unpack fuel-6.
3) Start upgrade: '/var/upgrade.sh --no-rollback --password admin'
Upgrade script can fail after start the upgraded containers with the following error (http://
2015-05-09 04:04:34 ERROR 28299 (upgrade) OpenStackUpgrader: failed to upgrade: "502 Server Error: Bad Gateway"
Manual reproducing of the bug can be successful from time to time.
Changed in fuel: | |
importance: | Undecided → High |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Matthew Mosesohn (raytrac3r) |
To post a comment you must log in.
Root cause here is blinking of services in start.sh of containers. We should either extend our timeout or remove blinking.