Error deleting a machine
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Triaged
|
Medium
|
Unassigned | ||
3.4 |
Won't Fix
|
Medium
|
Unassigned | ||
3.5 |
Won't Fix
|
Medium
|
Unassigned | ||
3.6 |
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,
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.
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
return target()
File "/usr/lib/
task()
File "/usr/lib/
task()
--- <exception caught here> ---
File "/usr/lib/
result = inContext.theWork()
File "/usr/lib/
inContext.
File "/usr/lib/
return self.currentCon
File "/usr/lib/
return func(*args,**kw)
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
result = func(*args, **kwargs)
File "/usr/lib/
return func_outside_
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
return func(*args, **kwds)
File "/usr/lib/
obj = self.get_
File "/usr/lib/
obj = super(NodeHandler, self).get_
File "/usr/lib/
raise HandlerDoesNotE
maasserver.
2018-06-10 16:42:07 maasserver.
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 |
Changed in maas: | |
milestone: | 3.4.0 → 3.4.x |
Changed in maas: | |
milestone: | 3.4.x → 3.5.x |
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.