MAAS celery DHCP traceback

Bug #1274217 reported by Adam Collard
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Julian Edwards

Bug Description

⟫ dpkg-query -W maas
maas 1.4+bzr1820+dfsg-0ubuntu1

(with amttool template copied in place)

[2014-01-29 17:51:16,335: ERROR/MainProcess] Task provisioningserver.tasks.periodic_probe_dhcp[caefe698-3e98-4d79-9010-3b67d3f04e00] raised unexpected: IOError(99, 'Cannot assign requested address')
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/celery/app/trace.py", line 218, in trace_task
    R = retval = fun(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/celery/app/trace.py", line 398, in __protected_call__
    return self.run(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/provisioningserver/tasks.py", line 349, in periodic_probe_dhcp
    detect.periodic_probe_task()
  File "/usr/lib/python2.7/dist-packages/provisioningserver/dhcp/detect.py", line 338, in periodic_probe_task
    servers = probe_interface(interface, ip)
  File "/usr/lib/python2.7/dist-packages/provisioningserver/dhcp/detect.py", line 279, in probe_interface
    servers = probe_dhcp(interface)
  File "/usr/lib/python2.7/dist-packages/provisioningserver/dhcp/detect.py", line 213, in probe_dhcp
    transaction_id = request_dhcp(interface)
  File "/usr/lib/python2.7/dist-packages/provisioningserver/dhcp/detect.py", line 170, in request_dhcp
    bind_address = get_interface_IP(sock, interface)
  File "/usr/lib/python2.7/dist-packages/provisioningserver/dhcp/detect.py", line 148, in get_interface_IP
    info = fcntl.ioctl(sock, SIOCGIFADDR, ifreq)
IOError: [Errno 99] Cannot assign requested address

Got the above traceback using MAAS with 3 KVMs and 9 physical nodes. Doesn't appear to have any affect on actual operations (nodes come up/go down, can be deployed to).

Related branches

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Looks similar to bug 1274190. Won't dupe for now because the traceback is different but I suspect the same underlying cause.

Changed in maas:
status: New → Triaged
importance: Undecided → Critical
milestone: none → 14.04
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Ok this happens when the interface has no IP address. We should probably not do the detection for these interfaces as they are clearly not in use.

Changed in maas:
status: Triaged → In Progress
assignee: nobody → Julian Edwards (julian-edwards)
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
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.