Error deleting a machine

Bug #1776084 reported by Mark Shuttleworth
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Triaged
Medium
Unassigned

Bug Description

Am struggling to delete machines in the gmaas. One of my rack controllers is busted, but that shouldn't affect this operation. I see this in the regiond.log:

2018-06-10 16:40:38 RegionServer,2,::ffff:192.168.9.7: [info] RegionServer connection lost (HOST:IPv6Address(TCP, '::ffff:192.168.9.10', 5251) PEER:IPv6Address(TCP, '::ffff:192.168.9.7', 37158))
2018-06-10 16:40:38 maasserver.ipc: [info] Worker pid:3060 lost RPC connection to ('8tsb7m', '192.168.9.10', 5251).
2018-06-10 16:40:38 maasserver.ipc: [info] Worker pid:3060 lost RPC connection to ('4y3h7n', '192.168.9.10', 5251).
2018-06-10 16:40:38 maasserver.ipc: [info] Worker pid:3060 lost RPC connection to ('fbgtn8', '192.168.9.10', 5251).
2018-06-10 16:40:54 maasserver: [error] Error while calling DescribePowerTypes: Unable to get RPC connection for rack controller 'lapsi' (4nqs36).
2018-06-10 16:40:58 maasserver: [error] Error while calling DescribePowerTypes: Unable to get RPC connection for rack controller 'lapsi' (4nqs36).

2018-06-10 16:42:03 maasserver.websockets.protocol: [critical] Error on request (37) machine.action: hkttxq
 Traceback (most recent call last):
   File "/usr/lib/python3.6/threading.py", line 864, in run
     self._target(*self._args, **self._kwargs)
   File "/usr/lib/python3/dist-packages/provisioningserver/utils/twisted.py", line 850, in worker
     return target()
   File "/usr/lib/python3/dist-packages/twisted/_threads/_threadworker.py", line 46, in work
     task()
   File "/usr/lib/python3/dist-packages/twisted/_threads/_team.py", line 190, in doWork
     task()
 --- <exception caught here> ---
   File "/usr/lib/python3/dist-packages/twisted/python/threadpool.py", line 250, in inContext
     result = inContext.theWork()
   File "/usr/lib/python3/dist-packages/twisted/python/threadpool.py", line 266, in <lambda>
     inContext.theWork = lambda: context.call(ctx, func, *args, **kw)
   File "/usr/lib/python3/dist-packages/twisted/python/context.py", line 122, in callWithContext
     return self.currentContext().callWithContext(ctx, func, *args, **kw)
   File "/usr/lib/python3/dist-packages/twisted/python/context.py", line 85, in callWithContext
     return func(*args,**kw)
   File "/usr/lib/python3/dist-packages/provisioningserver/utils/twisted.py", line 883, in callInContext
     return func(*args, **kwargs)
   File "/usr/lib/python3/dist-packages/provisioningserver/utils/twisted.py", line 232, in wrapper
     result = func(*args, **kwargs)
   File "/usr/lib/python3/dist-packages/maasserver/utils/orm.py", line 756, in call_within_transaction
     return func_outside_txn(*args, **kwargs)
   File "/usr/lib/python3/dist-packages/maasserver/utils/orm.py", line 563, in retrier
     return func(*args, **kwargs)
   File "/usr/lib/python3.6/contextlib.py", line 52, in inner
     return func(*args, **kwds)
   File "/usr/lib/python3/dist-packages/maasserver/websockets/handlers/machine.py", line 732, in action
     obj = self.get_object(params)
   File "/usr/lib/python3/dist-packages/maasserver/websockets/handlers/node.py", line 692, in get_object
     obj = super(NodeHandler, self).get_object(params)
   File "/usr/lib/python3/dist-packages/maasserver/websockets/base.py", line 289, in get_object
     raise HandlerDoesNotExistError(pk)
 maasserver.websockets.base.HandlerDoesNotExistError: hkttxq

2018-06-10 16:42:07 maasserver.region_controller: [info] Reloaded DNS configuration; removed node amused-guinea

Changed in maas:
status: New → Triaged
importance: Undecided → High
status: Triaged → Confirmed
milestone: none → 2.7.0alpha1
Changed in maas:
milestone: 2.7.0b1 → 2.7.0b2
Changed in maas:
milestone: 2.7.0b2 → none
Revision history for this message
Björn Tillenius (bjornt) wrote :

This looks like the machine already had been deleted. Maybe the UI was stale and didn't indicate this.

Either way, MAAS should handle this, and shouldn't error out if you try to delete a node that doesn't exist anymore.

Changed in maas:
status: Confirmed → Triaged
importance: High → Medium
Revision history for this message
Jerzy Husakowski (jhusakowski) wrote :

To be re-tested if this is indeed an issue with a stale UI: view a machine in the UI, delete it and check the UI & the logs.

Changed in maas:
milestone: none → 3.4.0
Alberto Donato (ack)
Changed in maas:
milestone: 3.4.0 → 3.4.x
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.