confusing nova output in test logs

Bug #2073431 reported by Brian Murray
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Auto Package Testing
New
Low
Unassigned

Bug Description

https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/s390x/r/resource-agents/20240717_210739_8dce9@/log.gz

In the above test log I see the following:

1341s nova [E] Timed out waiting for ssh. Aborting! Console log:
1341s ------- nova console-log c2265cdb-5760-4f8b-b0b5-2ffd319cdd63 (adt-noble-s390x-resource-agents-20240717-200318-juju-7f2275-prod-proposed-migration-environment-3-f67e3788-79c4-451e-880c-c536aeaf65b0) ------

Then some minimal console output and a call to nova show:

1341s ------- nova show c2265cdb-5760-4f8b-b0b5-2ffd319cdd63 (adt-noble-s390x-resource-agents-20240717-200318-juju-7f2275-prod-proposed-migration-environment-3-f67e3788-79c4-451e-880c-c536aeaf65b0) ------

However, after that we see nova console-log and nova show being called with a different UUID.

2117s ------- nova console-log c31cc55e-2d45-4b0c-b985-a88b7f10191a (adt-noble-s390x-resource-agents-20240717-200318-juju-7f2275-prod-proposed-migration-environment-3-f67e3788-79c4-451e-880c-c536aeaf65b0) ------
2117s ERROR (CommandError): No server with a name or ID of 'c31cc55e-2d45-4b0c-b985-a88b7f10191a' exists.
2117s ---------------------------------------------------
2117s ------- nova show c31cc55e-2d45-4b0c-b985-a88b7f10191a (adt-noble-s390x-resource-agents-20240717-200318-juju-7f2275-prod-proposed-migration-environment-3-f67e3788-79c4-451e-880c-c536aeaf65b0) ------
2117s ERROR (CommandError): No server with a name or ID of 'c31cc55e-2d45-4b0c-b985-a88b7f10191a' exists.

Given the 700+ second delay between the messages perhaps there was an attempt to create another instances and it failed? Regardless this led to some confusion when Ural and I were looking at the logs for other reasons.

Revision history for this message
Brian Murray (brian-murray) wrote :
Changed in auto-package-testing:
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.