[2.0RC1] MAAS displays every power query on the summarized view of node event log

Bug #1594991 reported by Lee Trager
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Unassigned
2.0
Fix Released
Undecided
Unassigned

Bug Description

MAAS power queries a machine every 5 minutes to track the status of it along the lifecycle of the machine. MAAS stores those messages in the node event log. However, this messages are being stored as INFO and not DEBUG. Provided that it creates a long list of power query's every 5 second, these should be made DEBUG.

Tags: oil

Related branches

Lee Trager (ltrager)
summary: - MAAS logs every power query as a machine event
+ [2.0RC2] MAAS logs every power query as a machine event
summary: - [2.0RC2] MAAS logs every power query as a machine event
+ [2.0RC2] MAAS logs every power query as a NodeEvent
Lee Trager (ltrager)
summary: - [2.0RC2] MAAS logs every power query as a NodeEvent
+ [2.0RC1] MAAS logs every power query as a NodeEvent
Revision history for this message
Andres Rodriguez (andreserl) wrote : Re: [2.0RC1] MAAS logs every power query as a NodeEvent

Actually, this is good to have because it provides and indication that stuff is happening on a node event if it is idled.

Changed in maas:
status: Triaged → Won't Fix
Revision history for this message
Gavin Panella (allenap) wrote :

What we could do is compress the display in the UI to "Power off between $start_time and $end_time (checked every 5 minutes)" or something like that.

Revision history for this message
Jason Hobbs (jason-hobbs) wrote :

We can't use the event log at all, because on the node detail page the events are all "Queried node's BMC - Power state queried: on", and when we go to the detailed page, it's so slow the page basically freezes up because there are so many events.

tags: added: oil
summary: - [2.0RC1] MAAS logs every power query as a NodeEvent
+ [2.0RC1] MAAS displays every power query on the summarized view of node
+ event log
Revision history for this message
Jason Hobbs (jason-hobbs) wrote :

16:22 < jhobbs> We can't use the event log at all, because on the node detail page the events are all "Queried node's BMC - Power state queried: on", and when we go to the detailed page, it's so slow the page basically freezes up because there are so many events.
16:23 < jhobbs> might as well not even bother displaying the events on the detail page because they're all just "Queried node's BMC - Power state queried"
16:23 < roaksoax> actually, then the fix would be to fix the detailed view"
16:23 < jhobbs> nah it would be to stop showing the power query logs
16:23 < jhobbs> it didn't used to do that and it was a lot more useful then
16:23 < jhobbs> power querying isn't a node event
16:24 < roaksoax> jhobbs: it is a node event, it is happening every so often
16:24 < roaksoax> it is adding more observability to what MAAS is doing
16:24 < jhobbs> it's ruining the node event log
16:24 < jhobbs> and making it harder to observe actual events we care about
16:25 < jhobbs> we don't care about what MAAS is doing, we care about what the node is doing
16:25 < jhobbs> it's actually making it way less observable
16:26 < roaksoax> jhobbs: not at all. The node event log table is to log all events that are happening on a machine
16:26 < roaksoax> jhobbs: the fact that you don't see i the overview but you see all in the detailed view
16:27 < roaksoax> is just a UI thing
16:27 < roaksoax> jhobbs: the backend will store that anyway

Changed in maas:
status: Won't Fix → Triaged
description: updated
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.