This is just normal behavior of the `nova` script whenever a cloud hit
an issue. Improvements to this logging have already been deployed. Cloud
issues are dealt with usually by talking to IS. Closing this.
** Changed in: auto-package-testing
Status: New => Invalid
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2073431
Title:
confusing nova output in test logs
Status in Auto Package Testing:
Invalid
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2073431/+subscriptions
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
