fuel master upgrade from 6.0 to 6.1 failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
High
|
Ihor Kalnytskyi |
Bug Description
i used fuel-6.
Steps to reproduce:
1)Install fuel master 6.0
2)Download upgrade tar.lrz to 6.1
3)lrzuntar it
4) run upgrade.sh
Actual result:
It tries to call keystone, but keystone is unavailable. Part of the log:
2015-06-09 13:41:31 DEBUG 9642 (health_checker) Start integration_
2015-06-09 13:41:34 DEBUG 9642 (keystone_client) Cannot authenticate in keystone: HTTPConnectionP
2015-06-09 13:41:37 DEBUG 9642 (keystone_client) Cannot authenticate in keystone: HTTPConnectionP
2015-06-09 13:41:40 DEBUG 9642 (keystone_client) Cannot authenticate in keystone: HTTPConnectionP
2015-06-09 13:41:43 DEBUG 9642 (keystone_client) Cannot authenticate in keystone: HTTPConnectionP
2015-06-09 13:41:43 ERROR 9642 (keystone_client) Cannot retrieve an auth token - an unauthenticated request will be performed.
Traceback (most recent call last):
File "/var/upgrade/
token = utils.wait_
File "/var/upgrade/
'command with timeout {0}'.format(
TimeoutError: Failed to execute command with timeout 10
And at the end we get:
2015-06-09 13:56:10 ERROR 9642 (upgrade) *** UPGRADE FAILED
2015-06-09 13:56:10 ERROR 9642 (cli) Failed to run services ['integration_
Traceback (most recent call last):
File "/var/upgrade/
run_
File "/var/upgrade/
upgrade_
File "/var/upgrade/
upgrader.
File "/var/upgrade/
self.
File "/var/upgrade/
self.
UpgradeVerifica
=======
Couldn't start some of the services, try to run upgrade again.
Upgrade failed
Changed in fuel: | |
milestone: | none → 6.1 |
assignee: | nobody → Fuel Python Team (fuel-python) |
importance: | Undecided → High |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Igor Kalnitsky (ikalnitsky) |
1/ The upgrade wasn't run from fresh installed 6.0. It was a double upgrade: 5.1.1 -> 6.0 -> 6.1
2/ It's hard to say why upgrade procedure failed to retrieve keystone token. There may be a plenty of issues, I think it's something floating and second run (upgrade) should work fine.
3/ Unfortunately, rollback procedure failed too due to one of Docker issues with stale mounted resources. We can't fix it - it's up to Docker.
Move it to Incomplete for now. Let's try to reproduce it once again.