No more dynamic IP addresses may cause cluster crash

Bug #1507435 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Won't Fix
Critical
Unassigned

Bug Description

==> /var/log/maas/regiond.log <== [110/9229]
2015-10-19 11:48:08 [-] Unhandled failure dispatching AMP command. This
  is probably a bug. Please ensure that this error is handled within
  appli cation code or declared in the signature of the UpdateLeases
  command. [trusty-maas9:pid=5891:cmd=UpdateLeases:ask=3fe7]
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 783, in __bootstrap
    self.__bootstrap_inner()
  File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File ".../provisioningserver/utils/twisted.py", line 791, in _worker
    return super(ThreadPool, self)._worker()
--- <exception caught here> ---
  File ".../twisted/python/threadpool.py", line 191, in _worker
    result = context.call(ctx, function, *args, **kwargs)
  File ".../twisted/python/context.py", line 118, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File ".../twisted/python/context.py", line 81, in callWithContext
    return func(*args,**kw)
  File ".../provisioningserver/utils/twisted.py", line 200, in wrapper
    return func(*args, **kwargs)
  File ".../maasserver/utils/orm.py", line 480, in
  call_within_transaction
    return func_outside_txn(*args, **kwargs)
  File ".../maasserver/utils/orm.py", line 307, in retrier
    return func(*args, **kwargs)
  File ".../django/db/transaction.py", line 339, in inner
    return func(*args, **kwargs)
  File ".../maasserver/rpc/leases.py", line 51, in update_leases
    StaticIPAddress.objects.update_leases(nodegroup, leases)
  File ".../maasserver/models/staticipaddress.py", line 473, in
  update_leases
    subnet=ipaddress.subnet)
  File ".../django/db/models/manager.py", line 154, in get_or_create
    return self.get_queryset().get_or_create(**kwargs)
  File ".../django/db/models/query.py", line 373, in get_or_create
    return self.get(**lookup), False
  File ".../django/db/models/query.py", line 310, in get
    (self.model._meta.object_name, num))
maasserver.models.staticipaddress.MultipleObjectsReturned: get()
returned more than one StaticIPAddress -- it returned 7!

==> /var/log/maas/clusterd.log <==
2015-10-19 11:48:08+0800 [ClusterClient,client] Unhandled Error
Traceback (most recent call last):
Failure: twisted.protocols.amp.UnhandledCommand: ('UNHANDLED', 'Unknown
  Error [trusty-maas9:pid=5891:cmd=UpdateLeases:ask=3fe7]')

Changed in maas:
milestone: none → 1.9.0
Revision history for this message
Blake Rouse (blake-rouse) wrote :

Looking at this stacktrace I believe the title of this bug is completely incorrect. By looking at the trace it looks like something in the lease parsing is broken, whether or not you have no free addresses.

Revision history for this message
Andres Rodriguez (andreserl) wrote : Re: [Bug 1507435] Re: no more ip addresses may cause cluster crush

Actually, no, I only see this stacktrace when all the DHCP address on the
dynamic range have been allocated, and other machines can't commission
because they don't receive IP addresses.

On Mon, Oct 19, 2015 at 9:16 AM, Blake Rouse <email address hidden>
wrote:

> Looking at this stacktrace I believe the title of this bug is completely
> incorrect. By looking at the trace it looks like something in the lease
> parsing is broken, whether or not you have no free addresses.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1507435
>
> Title:
> no more ip addresses may cause cluster crush
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1507435/+subscriptions
>

--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

Gavin Panella (allenap)
summary: - no more ip addresses may cause cluster crush
+ No more dynamic IP addresses may cause cluster crash
Changed in maas:
importance: Undecided → Critical
status: New → Confirmed
Gavin Panella (allenap)
Changed in maas:
status: Confirmed → Triaged
description: updated
Christian Reis (kiko)
Changed in maas:
milestone: 1.9.0 → 1.9.1
Changed in maas:
milestone: 1.9.1 → 1.9.2
Changed in maas:
milestone: 1.9.2 → 1.9.3
Changed in maas:
milestone: 1.9.3 → 1.9.4
Changed in maas:
milestone: 1.9.4 → 1.9.5
Revision history for this message
Andres Rodriguez (andreserl) wrote :

We believe that this is not longer an issue in the latest releases of MAAS. If you believe this is still an issue, please re-open this bug report and target it accordingly.

Changed in maas:
status: Triaged → Won't Fix
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.