Public bug reported:
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.
** Affects: maas
Importance: Critical
Status: New
** Affects: maas/2.0
Importance: Critical
Status: New
** Affects: maas/trunk
Importance: Critical
Status: New
** Changed in: maas (Ubuntu)
Importance: Undecided => Critical
** Also affects: maas
Importance: Undecided
Status: New
** No longer affects: maas (Ubuntu)
** Also affects: maas/1.9
Importance: Undecided
Status: New
** Also affects: maas/2.0
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605252
Title:
[2.0] Error messaging about monitor expiry have been dropped
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1605252/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
