[2.0rc2] MAAS is not automatically monitoring timeouts for commissioning.

Bug #1598149 reported by Andres Rodriguez on 2016-07-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Critical
Andres Rodriguez
2.0
Critical
Andres Rodriguez
Trunk
Critical
Andres Rodriguez

Bug Description

A machine got stuck in releasing state and there was no way for me to be able to move it to another state. After investigation, the status_expires field on the node table was empty, meaning the monitoring service was not working, which would have marked the machine as 'Failed Releasing' automatically.

As such, the issue is not only present in releasing, but also on other sections, such as commissioning and deploying.

Related branches

summary: - [2.0b8] When a machine is stuck in 'Releasing' I cannot abort it
+ [2.0b8] Machine was stuck in releasing
description: updated
summary: - [2.0b8] Machine was stuck in releasing
+ [2.0b8] MAAS is automatically monitoring timeouts.
summary: - [2.0b8] MAAS is automatically monitoring timeouts.
+ [2.0b8] MAAS is automatically monitoring timeouts causing machines to
+ not get move to failed status automatically.
summary: - [2.0b8] MAAS is automatically monitoring timeouts causing machines to
- not get move to failed status automatically.
+ [2.0b8] MAAS is not automatically monitoring timeouts causing failed
+ commissioning machines to not timeout.
summary: - [2.0b8] MAAS is not automatically monitoring timeouts causing failed
- commissioning machines to not timeout.
+ [2.0b8] MAAS is not automatically monitoring timeouts for commissioning.
summary: - [2.0b8] MAAS is not automatically monitoring timeouts for commissioning.
+ [2.0rc2] MAAS is not automatically monitoring timeouts for
+ commissioning.
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers