[2.0] Log messaging about timeout monitor has been dropped

Bug #1605252 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Andres Rodriguez
2.0
Fix Released
Critical
Andres Rodriguez

Bug Description

In 1.8, I notice that some events are:

Jul 21 16:22:35 maas maas.node: [INFO] slave2: Status transition from COMMISSIONING to FAILED_COMMISSIONING
Jul 21 16:22:35 maas maas.node: [ERROR] slave2: Marking node failed: Node operation 'Commissioning' timed out after 0:20:00.

In 2.0, however, you see messages such:

Jul 21 16:22:35 maas maas.node: [ERROR] slave2: Marking node failed: None,

Looking at the code, this was handled in handle_monitor_expired function src/maasserver/models/node.py: def handle_monitor_expired(self, context):

Bu this has changed in 2.0 and nothing does the same thing.

Related branches

Changed in maas (Ubuntu):
importance: Undecided → Critical
no longer affects: maas (Ubuntu)
no longer affects: maas/1.9
summary: - [2.0] Error messaging about monitor expiry have been dropped
+ [2.0] Log messaging about timeout monitor has been dropped
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.