Unhandled UDP error during manual enlistment of xgene-2

Bug #1508087 reported by Newell Jensen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Critical
Unassigned
python-tx-tftp (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Manual enlistment of xgene-2 SOC fails with:

2015-10-20 10:35:35-0400 [RemoteOriginReadSession (UDP)] Unhandled Error
 Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/twisted/python/log.py", line 73, in callWithContext
     return context.call({ILogContext: newCtx}, func, *args, **kw)
   File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 118, in callWithContext
     return self.currentContext().callWithContext(ctx, func, *args, **kw)
   File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 81, in callWithContext
     return func(*args,**kw)
   File "/usr/lib/python2.7/dist-packages/twisted/internet/posixbase.py", line 614, in _doReadOrWrite
     why = selectable.doRead()
 --- <exception caught here> ---
   File "/usr/lib/python2.7/dist-packages/twisted/internet/udp.py", line 234, in doRead
     self.protocol.datagramReceived(data, addr)
   File "/usr/lib/python2.7/dist-packages/tftp/bootstrap.py", line 177, in datagramReceived
     return self._datagramReceived(datagram)
   File "/usr/lib/python2.7/dist-packages/tftp/bootstrap.py", line 394, in _datagramReceived
     return self.tftp_ACK(datagram)
   File "/usr/lib/python2.7/dist-packages/tftp/bootstrap.py", line 407, in tftp_ACK
     self.timeout_watchdog.cancel()
   File "/usr/lib/python2.7/dist-packages/tftp/util.py", line 115, in cancel
     raise Cancelled("This SequentialCall has already been cancelled")
 tftp.util.Cancelled: This SequentialCall has already been cancelled

This is using MAAS trunk as 1.9 is needed for arm64 (UEFI):

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=================================-====================================-============-===============================================================================
ii maas 1.9.0~alpha5+bzr4381-0ubuntu1 all MAAS server all-in-one metapackage
ii maas-cli 1.9.0~alpha5+bzr4381-0ubuntu1 all MAAS command line API tool
ii maas-cluster-controller 1.9.0~alpha5+bzr4381-0ubuntu1 all MAAS server cluster controller
ii maas-common 1.9.0~alpha5+bzr4381-0ubuntu1 all MAAS server common files
ii maas-dhcp 1.9.0~alpha5+bzr4381-0ubuntu1 all MAAS DHCP server
ii maas-dns 1.9.0~alpha5+bzr4381-0ubuntu1 all MAAS DNS server
ii maas-proxy 1.9.0~alpha5+bzr4381-0ubuntu1 all MAAS Caching Proxy
ii maas-region-controller 1.9.0~alpha5+bzr4381-0ubuntu1 all MAAS server complete region controller
ii maas-region-controller-min 1.9.0~alpha5+bzr4381-0ubuntu1 all MAAS Server minimum region controller
ii python-django-maas 1.9.0~alpha5+bzr4381-0ubuntu1 all MAAS server Django web framework
ii python-maas-client 1.9.0~alpha5+bzr4381-0ubuntu1 all MAAS python API client
ii python-maas-provisioningserver 1.9.0~alpha5+bzr4381-0ubuntu1 all MAAS server provisioning libraries

Gavin Panella (allenap)
Changed in maas:
status: New → Triaged
importance: Undecided → Critical
Revision history for this message
Ming Lei (tom-leiming) wrote :

This one should be same with LP1508738, and can anyone to try to use the customerised grub to see if it
can fix the issue?

       http://kernel.ubuntu.com/~ming/bugs/1508893/bootnetaa64.efi

Revision history for this message
Newell Jensen (newell-jensen) wrote :

Ming,

I tried using the above bootnetaa64.efi but the firmware won't allow me to PXE boot:

TianoCore 2.0.0 UEFI 2.4.0 Sep 1 2015 12:48:07
CPU: APM ARM 64-bit Strega Rev A2 2400MHz PCP 2400MHz
     32 KB ICACHE, 32 KB DCACHE
     SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 66MHz
Board: X-Gene Merlin Board
Slimpro FW:
 Ver: 3.4 (build 2015/07/22)
 PMD: 980 mV
 SOC: 950 mV
The default boot selection will start in 3 seconds
[1] ubuntu
[2] PXE on MAC :3C
[3] nfs boot via TFTP
[4] Shell
[5] Boot Manager
[6] Reboot
[7] Shutdown
Start: 2
..PXE-E23: Client received TFTP error from server.
[1] ubuntu
[2] PXE on MAC :3C
[3] nfs boot via TFTP
[4] Shell
[5] Boot Manager
[6] Reboot
[7] Shutdown
Start: 2
..PXE-E23: Client received TFTP error from server.
[1] ubuntu
[2] PXE on MAC :3C
[3] nfs boot via TFTP
[4] Shell
[5] Boot Manager
[6] Reboot
[7] Shutdown
Start:

Revision history for this message
Newell Jensen (newell-jensen) wrote :

It should be noted that the above issue with PXE booting was only seen after upgrading the APM firmware. Before we were able to get further in the PXE booting process with MAAS. I am going to investigate using the above grub with a seperate DHCP and TFTP server.

Revision history for this message
Newell Jensen (newell-jensen) wrote :

After testing the updated grub, I was able to manually enlist the xgene-2 SOC without the above stacktrace error.

Revision history for this message
Andres Rodriguez (andreserl) wrote :

I believe that in the latest versions of MAAS, this has now been fixed. If you believe this issue still exists, please re-open this bug report or file a new one.

no longer affects: python-tx-tftp
Changed in python-tx-tftp (Ubuntu):
status: New → Invalid
Changed in maas:
status: Triaged → Invalid
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.