Skip to content

[Vmware to KVM Migration] Fix issue with vCenter Standalone hosts for VM listing #11091

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

Open
wants to merge 1 commit into
base: 4.19
Choose a base branch
from

Conversation

nvazquez
Copy link
Contributor

@nvazquez nvazquez commented Jun 26, 2025

Description

This PR fixes the listing of VMware VMs for Migration to KVM on vCenter datacenters that have standalone hosts (don't belong to any cluster)

Example setup with standalone hosts:
Image

Listing retrieved successfully, setting cluster field empty on the listing table:
Screenshot 2025-06-25 at 23 59 32

Fixes: #11090

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)
  • build/CI
  • test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

Bug Severity

  • BLOCKER
  • Critical
  • Major
  • Minor
  • Trivial

Screenshots (if appropriate):

How Has This Been Tested?

Set standalone hosts on the datacenter, having VMs on them
List VMs for Migration on CloudStack pointing to the vCenter

How did you try to break this feature and the system with this change?

@nvazquez
Copy link
Contributor Author

@blueorangutan package

@blueorangutan
Copy link

@nvazquez a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Copy link

codecov bot commented Jun 26, 2025

Codecov Report

Attention: Patch coverage is 0% with 12 lines in your changes missing coverage. Please review.

Project coverage is 15.17%. Comparing base (cbd2b5a) to head (eb7447e).

Files with missing lines Patch % Lines
...in/java/com/cloud/hypervisor/vmware/mo/BaseMO.java 0.00% 12 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##               4.19   #11091      +/-   ##
============================================
- Coverage     15.17%   15.17%   -0.01%     
+ Complexity    11363    11356       -7     
============================================
  Files          5416     5416              
  Lines        475911   475921      +10     
  Branches      58096    58096              
============================================
- Hits          72241    72223      -18     
- Misses       395584   395615      +31     
+ Partials       8086     8083       -3     
Flag Coverage Δ
uitests 4.28% <ø> (ø)
unittests 15.90% <0.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@blueorangutan
Copy link

Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 13921

@DaanHoogland
Copy link
Contributor

@blueorangutan test ol8 vmware-80u3

@blueorangutan
Copy link

@DaanHoogland a [SL] Trillian-Jenkins test job (ol8 mgmt + vmware-80u3) has been kicked to run smoke tests

Comment on lines +273 to +274
String msg = String.format("Standalone host %s found, setting empty cluster field", hostName);
s_logger.debug(msg);
Copy link
Contributor

@DaanHoogland DaanHoogland Jun 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
String msg = String.format("Standalone host %s found, setting empty cluster field", hostName);
s_logger.debug(msg);
String msg = String.format(Host %s not found, assuming standalone host, setting cluster name as empty", hostName);
s_logger.info(msg);

Copy link
Member

@weizhouapache weizhouapache left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

code lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Vmware to KVM Migration] Standalone hosts are not supported for listing VMs on vCenter
4 participants