test_runner can fail while acquiring the console log when the test bed instance can't be created
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu CI Engine |
Fix Released
|
High
|
Vincent Ladeuil | ||
Ubuntu CI Services |
Fix Released
|
High
|
Vincent Ladeuil |
Bug Description
adt-run: @@@@@@@
adt-run: @@@@@@@
adt-run: @@@@@@@
adt-run: @@@@@@@@@@ read control ...
adt-run: @@@@@@@@@@ run_tests ...
* SKIP no tests in this package
adt-run: @@@@@@@
INFO:test_
INFO:test_
INFO:urllib3.
INFO:ci_
INFO:urllib3.
INFO:urllib3.
INFO:urllib3.
INFO:urllib3.
INFO:test_
ERROR:test_
Traceback (most recent call last):
File "./test_
console = test_bed.
File "/srv/tr_
return self.instance.
AttributeError: 'NoneType' object has no attribute 'get_console_
ERROR:test_
We're trying to acquire the console after the test run, this can succeed if the testbed deletion is slow.
Related branches
- Andy Doan (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 132 lines (+43/-20)2 files modifiedtest_runner/tstrun/run_worker.py (+40/-18)
test_runner/tstrun/testbed.py (+3/-2)
summary: |
- test_runner can fail while acquiring the console log *after* the test - succeeded + test_runner can fail while acquiring the console log when the test bed + instance can't be created |
Changed in ubuntu-ci-services-itself: | |
importance: | Critical → High |
Changed in ubuntu-ci-services-itself: | |
status: | In Progress → Fix Committed |
Changed in ubuntu-ci-services-itself: | |
status: | Fix Committed → Fix Released |
Changed in uci-engine: | |
assignee: | nobody → Vincent Ladeuil (vila) |
importance: | Undecided → High |
milestone: | none → phase-0 |
status: | New → Fix Released |
I misread the log, only the last part is relevant, the part about the test succeeding is for a previous ticket.
Upon investigation it appeared that the image_id received was a list (instead of a scalar), due to some wip by Chris.
This led to a failed call to nova.servers. create( ) but the corresponding exception was masked by the attempt to upload the console (which didn't exist anyway in this case since there was no instance).
I'm re-targetting this bug at providing a more robust code and better error reporting in light of the above scenario (the error misled Chris instead of telling him what the problem was).