Comment 2 for bug 1863729

The solution should be simple, just check the cluster_name field and see if it's in a cluster, and if it is ignore the host field and just use the cluster_name, but when I added the cluster functionality for A/A y forgot to add the field to the volume information.

A solution would be to check if Cinder is running microversion 3.7 or higher, and if it is, after we create the volume we ask Cinder for the service information on that volume's host and see if it is in a cluster.

If it is in a cluster we have to compare the cluster for the service running the host value from before and the one from after the retype instead of the host field itself.