Thank you Mike for the detailed explanation, I misread the "private image id" as the cluster id.
If I understand correctly, this bug happens when a user creates an image with a location set to another image location.
Can't glance prevents setting a single location to multiple image ?
Thank you Mike for the detailed explanation, I misread the "private image id" as the cluster id.
If I understand correctly, this bug happens when a user creates an image with a location set to another image location.
Can't glance prevents setting a single location to multiple image ?