KeyError when monitor expires

Bug #1381615 reported by Gavin Panella
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Gavin Panella

Bug Description

2014-10-15 23:54:48+0800 [-] Unhandled Error
        Traceback (most recent call last):
          File "/usr/lib/python2.7/dist-packages/twisted/application/app.py", line 392, in startReactor
            self.config, oldstdout, oldstderr, self.profiler, reactor)
          File "/usr/lib/python2.7/dist-packages/twisted/application/app.py", line 313, in runReactorWithLogging
            reactor.run()
          File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1192, in run
            self.mainLoop()
          File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1201, in mainLoop
            self.runUntilCurrent()
        --- <exception caught here> ---
          File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 824, in runUntilCurrent
            call.func(*call.args, **call.kw)
          File "/usr/lib/python2.7/dist-packages/provisioningserver/rpc/monitors.py", line 62, in monitor_expired
            _, context = running_monitors.pop(monitor_id)
        exceptions.KeyError: u'node-1e4e3914-53ad-11e4-967b-00163e11c886'

Related branches

Changed in maas:
milestone: none → next
Gavin Panella (allenap)
Changed in maas:
status: Triaged → In Progress
assignee: nobody → Gavin Panella (allenap)
Gavin Panella (allenap)
Changed in maas:
status: In Progress → Fix Committed
Revision history for this message
Raphaël Badin (rvb) wrote :

Could you please explain how I can reproduce this? MAAS starts a monitor when a node transitions to 'Deploying' and cancels the monitor when the node transitions out of the 'Deploying' state; this means we should never encounter this. I'd like to fix the root cause of the problem instead of simply papering over the crash.

Changed in maas:
milestone: next → 1.7.0
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.