[6.8.0 RC6 - Starting "ALL" VM's causes VM's to disappear from Dashboard and VM tab]

I used to run on 6.7.0, upgraded to the 6.8.0 RC6 build today, and am experiencing this problem now too.
Same thing, only have 1 VM, when started they disappear (virsh list shows it running).

When I create another VM, it re-appears in the list as "running".

[Multiple Docker Update - output oddity]

This used to happen to me until I updated to 67.0 or so, now it just shows an empty window until all docker containers have updated, before outputting all the text at once.

Haven't tried updating to 6.8.0 yet, but since I recognized this issue, I figured I might as well add my 2 cents.

[[6.5.3] - HDD temperatures not correctly updated]

"*" is a placeholder value, not a live value. and those SMART values aren't live values because the drive doesn't spin up when I access them.

[[6.5.3] - HDD temperatures not correctly updated]

Changed Status to Closed

[[6.5.3] - HDD temperatures not correctly updated]

Whatever, I think you guys are just completely misunderstanding me.

Honestly, what's the point of having a dashboard if it doesn't show known values.

 

I'm going to stop trying to explain this now. It's pretty frustrating.

[[6.5.3] - HDD temperatures not correctly updated]

5 minutes ago, bonienl said:

There are very valid reasons why it is designed this way

1. Reading disk attributes (including temperature) can negatively impact the normal reading/writing of the disk. The temperature reading is done at a much lower interval with its own timer setting as reading the other disk statistics to keep impact on normal operation as low as possible.
2. Reading disk attributes may spin up a disk, that's why attributes are never read once a disk is spun down. The moment a disk becomes 'active' the aforementioned timer is started to read temperature with minimal interference.

Yes, but if I click on the disk it isn't showing the live values from S.M.A.R.T. is it?

So if those values are stored / cached somewhere, then surely they can just be displayed in the dashboard semi-live without impacting the disk itself, this would fix the entire issue.

[[6.5.3] - HDD temperatures not correctly updated]

In all honesty I don't get why you'd program the dashboard to work like that instead of just using the data it has, live.

 

Additionally I don't get why the Spin up button would trigger a refresh, but the automatic spinning up of the drives wouldn't, but that relates back to the dashboard not using live values in that case.

 

If it's not a bug I'll leave it, but I find it a very weird design choice.

 

Maybe worth noting I'm not in the actual "dashboard" tab, but the "main" tab.

[[6.5.3] - HDD temperatures not correctly updated]

But then why is it that I could read the temperature in the SMART values just fine but they weren't displayed in the dashboard until I pressed the "Spin up" button?

 

I feel like there's still a trigger bug related to this.