Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐞 The storagemap has problem if it was created during migration plan creation using the ESXi endpoint on the OCP Web UI #1049

Closed
mxie91 opened this issue Apr 1, 2024 · 3 comments
Assignees
Labels
bug Categorizes issue or PR as related to a bug.
Milestone

Comments

@mxie91
Copy link

mxie91 commented 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

@yaacov yaacov added the bug Categorizes issue or PR as related to a bug. label Apr 1, 2024
@yaacov yaacov added this to the 2.6.0 milestone Apr 1, 2024
@yaacov 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
@yaacov yaacov self-assigned this Apr 1, 2024
@yaacov
Copy link
Member

yaacov commented Apr 3, 2024

the datastore inventory is:

/api/proxy/plugin/forklift-console-plugin/forklift-inventory/providers/vsphere/4fd52a45-23db-4492-bb74-384407281e48//datastores

  {
    "id": "10.73.194.35:/vol/s3tzheng393301/s3images",
    "parent": {
      "kind": "Folder",
      "id": "ha-folder-datastore"
    },
    "path": "/ha-datacenter/datastore/esx6.7-6.5-matrix",
    "revision": 59,
    "name": "esx6.7-6.5-matrix",
    "selfLink": "providers/vsphere/4fd52a45-23db-4492-bb74-384407281e48/datastores/10.73.194.35:/vol/s3tzheng393301/s3images"
  },
  {
    "id": "10.73.194.35:/vol/virtv2v/function",
    "parent": {
      "kind": "Folder",
      "id": "ha-folder-datastore"
    },
    "path": "/ha-datacenter/datastore/esx6.7-6.5-function",
    "revision": 88,
    "name": "esx6.7-6.5-function",
    "selfLink": "providers/vsphere/4fd52a45-23db-4492-bb74-384407281e48/datastores/10.73.194.35:/vol/virtv2v/function"
  },
  {

@ahadas @bennyz is this expected ? how do i get the real ids ?

@yaacov
Copy link
Member

yaacov commented Apr 3, 2024

@ahadas, hi, will be fixed on the backend side ?

@yaacov
Copy link
Member

yaacov commented Apr 3, 2024

closing, will be fixed on backend side

@yaacov yaacov closed this as completed Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants