I found:
However that doesn’t mention what would happen to the default profile that is used by all containers I’ve moved over? would this break them?
Is there an easier way to set which pool should be considered “default” going forward instead?
Not really. Profile changes apply to all affected instances straight away (or block the change if it cannot be applied).
I would create a new profile for the old instances with a root disk pool set to the old pool and then apply it to the old instances. Then change the default profile’s root disk pool.
is it concerning that I already moved all my containers to the second pool, but the default profile still lists them in the used_by section? should I modify those too?
Its because the default profile is still applied to them for networking device but the root disk device is overridden in the new profile.
1 Like
It worked, thank you so much!
1 Like