[System tests] Upgrade fuel after rollback failed with false negative result
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Vasily Gorin | ||
7.0.x |
Fix Committed
|
High
|
Vadim Rovachev |
Bug Description
Upgrade script fails with next message
Traceback (most recent call last):
File "/usr/lib/
testMethod()
File "/usr/lib/
self.
File "/home/
compatabili
File "/home/
func()
File "/home/
func(
File "/home/
result = func(*args, **kwargs)
File "/home/
exit_code=255)
File "/home/
result = func(*args, **kwargs)
File "/home/
" /var/log/
But there is no upgrade log in snapshot, and if we investigate system-tests.log we can see that we fail before upgrade execition according to we can not find upgrdae.sh
015-09-22 02:11:09,945 - DEBUG __init__.py:55 -- Calling: run_script with args: (<devops.
2015-09-22 02:11:09,945 - DEBUG helpers.py:330 -- Executing command: 'chmod 755 /var/upgrade.sh'
2015-09-22 02:11:10,013 - DEBUG checkers.py:276 -- Result of cmod is {'exit_code': 1, 'stderr': ["chmod: cannot access `/var/upgrade.sh': No such file or directory\n"], 'stdout': []}
2015-09-22 02:11:10,013 - DEBUG helpers.py:330 -- Executing command: 'UPGRADERS=
2015-09-22 02:11:10,078 - DEBUG checkers.py:288 -- Try to read status code from chain...
We should assert each command to avoid to false negative messages
File "/home/
raise ASSERTION_
AssertionError: Upgrade script fails with next message
Changed in fuel: | |
status: | New → Confirmed |
Changed in fuel: | |
assignee: | Fuel QA Team (fuel-qa) → Vasily Gorin (vgorin) |
tags: | added: area-qa |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
tags: | removed: non-release |
It might be the same problem that we faced before - https:/ /bugs.launchpad .net/fuel/ +bug/1448904 .
I propose to add logging of stderr from untar command as part of this bug and also add assert of upgrade.sh file after unpacking.