© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
Looks like this is the problem: https:/
That's been around since Newton. I also assume that if people are using ceph/rbd then their computes are on shared storage.
Why would the two computes here not be on the same shared storage pool? If they aren't, but other computes are on shared storage, then you should probably use host aggregates to define the groups of hosts which are in the same shared storage pools so that the scheduler won't pick a destination host for the resize which the source compute can't reach.