Error when setting up autopkgtest armhf system in Canonistack

Bug #1912368 reported by Brian Murray
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
autopkgtest (Ubuntu)
New
Undecided
Unassigned

Bug Description

I was running the following command '/usr/bin/autopkgtest -dd gzip --setup-commands setup-testbed --apt-upgrade -- ssh -s nova -- --flavor m1.small --image ubuntu/ubuntu-hirsute-daily-armhf-server-20201124-disk1.img --keyname brian_canonistack-bos01' with autopkgtest version 5.13.1 and encountered this error:

autopkgtest: DBG: got reply from testbed: ok
autopkgtest: DBG: testbed open, scratch=None
autopkgtest: DBG: sending command to testbed: open
Creating nova instance autopkgtest-nova-eTpEx1 from image ubuntu/ubuntu-hirsute-daily-armhf-server-20201124-disk1.img (UUID d0206a61-4a4d-4b9f-bfe6-348c8f45eb4f)...
Timed out waiting for ssh. Aborting! Console log:
------- nova console-log e937e68f-2703-408a-8cdb-0eabd6873f17 (autopkgtest-nova-eTpEx1) ------
[2J[01;01H[=3h[2J[01;01H[2J[01;01H[=3h[2J[01;01H[2J[01;01H[=3h[2J[01;01H[0m[35m[40m[2J[01;01H[01;01H[0m[37m[40mUEFI Interactive Shell v2.2
EDK II
UEFI v2.70 (EDK II, 0x00010000)
[1m[33m[40mMapping table[0m[37m[40m
[1m[33m[40m FS0:[0m[37m[40m [1m[37m[40mAlias(s):[0m[37m[40mHD0p:;BLK2:
          PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/HD(15,GPT,96AA4AA6-B04A-41BC-B52E-594E423DED0D,0x800,0x31801)
[1m[33m[40m BLK4:[0m[37m[40m [1m[37m[40mAlias(s):[0m[37m[40m
          VenHw(F9B94AE2-8BA6-409B-9D56-B9B417F53CB3)
[1m[33m[40m BLK3:[0m[37m[40m [1m[37m[40mAlias(s):[0m[37m[40m
          VenHw(8047DB4B-7E9C-4C0C-8EBC-DFBBAACACE8F)
[1m[33m[40m BLK0:[0m[37m[40m [1m[37m[40mAlias(s):[0m[37m[40m
          PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)
[1m[33m[40m BLK1:[0m[37m[40m [1m[37m[40mAlias(s):[0m[37m[40m
          PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/HD(1,GPT,5A887B10-5EB1-4880-AFB0-B091D80966A2,0x32800,0x4337DF)
[17;01HPress [1m[37m[40mESC[0m[37m[40m in 5 seconds to skip [1m[33m[40mstartup.nsh[0m[37m[40m or any other key to continue.[17;01HPress [1m[37m[40mESC[0m[37m[40m in 4 seconds to skip [1m[33m[40mstartup.nsh[0m[37m[40m or any other key to continue.[17;01HPress [1m[37m[40mESC[0m[37m[40m in 3 seconds to skip [1m[33m[40mstartup.nsh[0m[37m[40m or any other key to continue.[17;01HPress [1m[37m[40mESC[0m[37m[40m in 2 seconds to skip [1m[33m[40mstartup.nsh[0m[37m[40m or any other key to continue.[17;01HPress [1m[37m[40mESC[0m[37m[40m in 1 seconds to skip [1m[33m[40mstartup.nsh[0m[37m[40m or any other key to continue.
[18;01H[1m[33m[40mShell> [0m[37m[40m

This always happens when trying to setup an armhf image. The full log is attached.

Revision history for this message
Brian Murray (brian-murray) wrote :
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.