Skip to:
In the older Resource Graph selectors, you would see " (graph data not updated) "-type wording for stale rrd/jrbs.
This doesn't happen with the newer style selector.
For the given collection interface directories, see attached screenshot:
drwxrwxr-x 2 root root 4096 Aug 19 23:57 Ethernet1_1drwxrwxr-x 2 root root 4096 Aug 26 19:00 Ethernet1_1-547fee0c4a68drwxrwxr-x 2 root root 4096 Aug 19 23:57 Ethernet1_10drwxrwxr-x 2 root root 4096 Aug 26 19:00 Ethernet1_10-547fee0c4a71drwxrwxr-x 2 root root 4096 Aug 19 23:57 Ethernet1_11drwxrwxr-x 2 root root 4096 Aug 26 19:00 Ethernet1_11-547fee0c4a72drwxrwxr-x 2 root root 4096 Aug 19 23:57 Ethernet1_12drwxrwxr-x 2 root root 4096 Aug 26 19:00 Ethernet1_12-547fee0c4a73drwxrwxr-x 2 root root 4096 Aug 19 23:57 Ethernet1_13drwxrwxr-x 2 root root 4096 Aug 26 19:00 Ethernet1_13-547fee0c4a74drwxrwxr-x 2 root root 4096 Aug 19 23:57 Ethernet1_14drwxrwxr-x 2 root root 4096 Aug 26 19:00 Ethernet1_14-547fee0c4a75drwxrwxr-x 2 root root 4096 Aug 19 23:57 Ethernet1_15drwxrwxr-x 2 root root 4096 Aug 26 19:00 Ethernet1_15-547fee0c4a76drwxrwxr-x 2 root root 4096 Aug 19 23:57 Ethernet1_16drwxrwxr-x 2 root root 4096 Aug 26 19:00 Ethernet1_16-547fee0c4a77
I was able to get the indicator to show on a provisioned node. What exactly are you doing to reproduce?
Whoops, hang on. I see the convention above on a Capsd based node, but not on a Provisiond node
The above example is from one of the provisioned nodes.
I see this convention on a different node in 1.9.91, so this can be resolved.
Nothing about the labels for the reports should have changed between the old component and the new one. Do you see the footer:
If that footer isn't printed then the graphs are still in the database somehow.
In the older Resource Graph selectors, you would see " (graph data not updated) "-type wording for stale rrd/jrbs.
This doesn't happen with the newer style selector.
For the given collection interface directories, see attached screenshot:
drwxrwxr-x 2 root root 4096 Aug 19 23:57 Ethernet1_1
drwxrwxr-x 2 root root 4096 Aug 26 19:00 Ethernet1_1-547fee0c4a68
drwxrwxr-x 2 root root 4096 Aug 19 23:57 Ethernet1_10
drwxrwxr-x 2 root root 4096 Aug 26 19:00 Ethernet1_10-547fee0c4a71
drwxrwxr-x 2 root root 4096 Aug 19 23:57 Ethernet1_11
drwxrwxr-x 2 root root 4096 Aug 26 19:00 Ethernet1_11-547fee0c4a72
drwxrwxr-x 2 root root 4096 Aug 19 23:57 Ethernet1_12
drwxrwxr-x 2 root root 4096 Aug 26 19:00 Ethernet1_12-547fee0c4a73
drwxrwxr-x 2 root root 4096 Aug 19 23:57 Ethernet1_13
drwxrwxr-x 2 root root 4096 Aug 26 19:00 Ethernet1_13-547fee0c4a74
drwxrwxr-x 2 root root 4096 Aug 19 23:57 Ethernet1_14
drwxrwxr-x 2 root root 4096 Aug 26 19:00 Ethernet1_14-547fee0c4a75
drwxrwxr-x 2 root root 4096 Aug 19 23:57 Ethernet1_15
drwxrwxr-x 2 root root 4096 Aug 26 19:00 Ethernet1_15-547fee0c4a76
drwxrwxr-x 2 root root 4096 Aug 19 23:57 Ethernet1_16
drwxrwxr-x 2 root root 4096 Aug 26 19:00 Ethernet1_16-547fee0c4a77