unity replication fails on UnityVSA
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Undecided
|
Ryan Liang |
Bug Description
When using UnityVSA for unity replication, it fails with below errors:
======
2020-05-26 02:13:04.893 7 ERROR cinder.
Error scheduling 1b08a2fe-
', ' File /usr/lib/
result = task.execute(
', ' File /usr/lib/
context, volume, **volume_spec) │
', ' File /usr/lib/
exception=ex) │
', ' File /usr/lib/
self.
', ' File /usr/lib/
six.
', ' File /usr/lib/
raise value │
', ' File /usr/lib/
ret = self.driver.
', ' File /usr/lib/
return self.adapter.
', ' File /usr/lib/
model_update = self.setup_
', ' File /usr/lib/
\'Cannot find it.\') % remote_
', 'cinder.
']
...
2020-05-26 02:13:05.805 7 ERROR cinder.
Error scheduling 1b08a2fe-
', ' File /usr/lib/
result = task.execute(
', ' File /usr/lib/
context, volume, **volume_spec) │
', ' File /usr/lib/
exception=ex) │
', ' File /usr/lib/
self.
', ' File /usr/lib/
six.
', ' File /usr/lib/
raise value │
', ' File /usr/lib/
ret = self.driver.
', ' File /usr/lib/
return self.adapter.
', ' File /usr/lib/
is_
', ' File /usr/lib/
is_
', ' File /usr/local/
is_
', ' File /usr/local/
resp.
', ' File /usr/local/
raise ex_clz(self.error) │
', 'storops.
'] │
===
Unity driver uses secondary IP to get the remote serial number then uses this serial number to filter the remoteSystem on primary Unity.
The problem here is the name and serial number of UnityVSA are not the same while these two variables are the same on physical machines.