Failed loading storage pool: No such object

yes, once the clustered storage pool and volumes created, though it would have fixed the problem.

Not sure on next steps, verify the pool and volumes can be accessed on each node?

So… I ran in to this exact problem today. What worked for me was to create a new storage pool in lxc called “default” as type dir, and then set it as the root volume pool in my profile. After that, no more storage pool errors.

1 Like

What profile did you set it in? What profile does the charmed-kubernetes bundle use?

The solution is (as always) hidden deep in the juju documentation
“LXD
Unsupported: [cpu-power, tags, virt-type, container, allocate-public-ip]
Valid values: arch=[host arch]
Note: root-disk-source is the LXD storage pool for the root disk. The default LXD storage pool is used if root-disk-source is not specified”
Juju | Constraint.

Similar issue is also described here

1 Like