Closed derrickmehaffy closed 2 years ago
Let me know if this is a duplicate, I tried searching other issues here and on the lxc repo / forum and didn't see anything that really described this.
Also not entirely sure if this is intended or not (I'm a bit new to lxc/lxd) or if this is even the right repo :sweat_smile: to report this issue on. If you need any other information let me know!
@markylaing want to take a stab at this one?
I think it's right that the UsedBy on a storage pool should reflect volumes on all cluster members.
The URLs will need to include the target=NAME
field though so we don't end up with duplicates, unless we're dealing with a remote storage pool that is, in which case volume should only be listed once.
@markylaing want to take a stab at this one?
I think it's right that the UsedBy on a storage pool should reflect volumes on all cluster members. The URLs will need to include the
target=NAME
field though so we don't end up with duplicates, unless we're dealing with a remote storage pool that is, in which case volume should only be listed once.
Just to reinforce this, some other examples of this, the profiles show the proper count across the cluster:
(Also thanks for answering so quickly :star_struck: )
Holy cow that was fast, thanks @markylaing & @stgraber \o/
Required information
Issue description
I have a 3 node LXD Cluster setup:
And I currently have 14 containers spread ~evenly between all 3 nodes of the cluster:
Each node has a storage pool configured called
local-m2
(this is the only storage on each node so all profiles, containers, and images are on this storage pool).When I run
lxc storage list
the count provided this command underused by
is wrong and it appears to only be taking the count from one node of the cluster. It doesn't appear that I can pass the--target
into this command either, I have to use thelxc storage info --target <node-name> local-m2
in order to get the actual list of containers in each node's storage pool.Expected behavior
I believe it's intended that a simple
lxc storage list
should take the used by information from all members of the cluster as the storage pool is configured at the cluster level.Information to attach
dmesg
)lxc info NAME --show-log
)lxc config show NAME --expanded
)lxc monitor
while reproducing the issue)