You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version-Release number of selected component (if applicable):
OCP version: 4.15.0-rc.8
MTV image build: registry-proxy.engineering.redhat.com/rh-osbs/iib:699104
Description of problem:
Create migration plan with esxi endpoint on OCP web UI, but the migration plan will be failed with error 'The plan is not ready - StorageMapNotReady' and status of storage map is 'Source storage not found.'
The root cause of failed storage mapping is storage name will be changed to storage id after creating migration plan, for example:source storage name 'esx7.0-matrix' was detected and correct during creating migration plan on OCP web UI, but storage name 'esx7.0-matrix' will be changed to id '10.73.194.35:/vol/s3tzheng393301/s3images/esx7.0' in storage mapping after creating migration plan
yaacov
changed the title
The storagemap has problem if it was created during migration plan creation using the ESXi endpoint on the OCP Web UI
🐞 The storagemap has problem if it was created during migration plan creation using the ESXi endpoint on the OCP Web UI
Apr 1, 2024
Version-Release number of selected component (if applicable):
OCP version: 4.15.0-rc.8
MTV image build: registry-proxy.engineering.redhat.com/rh-osbs/iib:699104
Description of problem:
Create migration plan with esxi endpoint on OCP web UI, but the migration plan will be failed with error 'The plan is not ready - StorageMapNotReady' and status of storage map is 'Source storage not found.'
The root cause of failed storage mapping is storage name will be changed to storage id after creating migration plan, for example:source storage name 'esx7.0-matrix' was detected and correct during creating migration plan on OCP web UI, but storage name 'esx7.0-matrix' will be changed to id '10.73.194.35:/vol/s3tzheng393301/s3images/esx7.0' in storage mapping after creating migration plan
Ref: https://issues.redhat.com/browse/MTV-1018
The text was updated successfully, but these errors were encountered: