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

VM previously imported as OVA missing after detach/import of Data Storage Domain #674

Closed
ahadas opened this issue Sep 23, 2022 · 0 comments · Fixed by #745
Closed

VM previously imported as OVA missing after detach/import of Data Storage Domain #674

ahadas opened this issue Sep 23, 2022 · 0 comments · Fixed by #745
Assignees
Labels

Comments

@ahadas
Copy link
Member

ahadas commented Sep 23, 2022

VM previously imported as OVA, is not visible in the "VM Import" Tab of Data Storage Domain after the Storage Domain has been put in maintenance/detached/removed, then imported/activated. Hence VM configuration is lost and can't be imported, although its disks are visibles with no alias/name in "Disk Import" Tab.

Other VM created (not OVA imported) on the same Data Storage Domain has no issue.

Version-Release number of selected component (if applicable): ovirt 4.4

How reproducible: 100%

Steps to Reproduce:

  1. import VM1 from OVA file to a Data Storage domain
  2. create VM2 on the same Data Storage domain
  3. Maintenance/Detach/Remove Data Storage Domain from Data Center
  4. Import/activate Data Storage Domain in the same Data Center
  5. VM1 won't appear in the Storage Domain "VM Import" Tab => VM1 configuration is lost. Its disks are visibles with no alias/name in "Disk Import" Tab.
  6. VM2 is visible the Storage Domain "VM Import" Tab => VM2 import successful

Actual results: VM lost after Storage Domain Detach/Import

Expected results: VM should be visible to import

See more details on the original bz: https://bugzilla.redhat.com/2028242

@ahadas ahadas added the storage label Sep 23, 2022
@ahadas ahadas linked a pull request Nov 9, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants