...@planethoster.info]
Sent: Tuesday, April 24, 2018 9:10 PM
To: Sean McGinnis
Cc: openstack-operators
Subject: Re: [Openstack-operators] Strange behaviour change in cinder with a
Dell compellent backend
Thank you for your reply. This implies that the SAN keeps track of a volume’s
native ID. So
Thank you for your reply. This implies that the SAN keeps track of a volume’s
native ID. So, for example, if I had a VM that was trying to mount an
inexistant volume ID after migration, I could fix this by creating a new volume
with the proper ID and just migrate the data from the volume that
On Tue, Apr 24, 2018 at 09:58:26AM +0900, Jean-Philippe Méthot wrote:
> Hi,
>
> This is a very strange behaviour that has causing me issues with my SAN ever
> since we upgraded to Mitaka or Ocata I believe, several months ago.
> Essentially, I used to be able to change the ID of a disk in the
Hi,
This is a very strange behaviour that has causing me issues with my SAN ever
since we upgraded to Mitaka or Ocata I believe, several months ago.
Essentially, I used to be able to change the ID of a disk in the SAN to swap
the disk in Openstack. So, for example, I had disk 1. I could
