GeezerVison

listUnmanagedInstances ran a substring mount lookup for every disk. For an RBD disk the pool name 'cloudstack' matched an unrelated NFS mount line, so the disk was reported on that NFS datastore and the import failed with 'Storage pool ... not found'.

RBD disks now take the monitor host and the pool name from the libvirt source. Other disks, including Gluster network disks, keep the mount-based lookup.

Add unit tests for the RBD and Gluster cases.

Description

This PR...

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?

Unit tests (plugins/hypervisors/kvm): LibvirtGetUnmanagedInstancesCommandWrapperTest, 7 tests, all pass. The new cases check that an RBD disk takes the monitor host and pool name from the libvirt source without calling the mount lookup, and that a Gluster disk still uses the mount lookup.

Live test on a Trillian test environment (Ubuntu 26.04, two KVM hosts, Ceph RBD pools, management server and KVM agents built from this change):

1. Deployed a Tiny VM on an RBD pool.
2. Unmanaged the VM.
3. Ran listUnmanagedInstances on its KVM host. The RBD disk now reports datastore host = the Ceph monitor, datastore name and path = the RBD pool, type network, and image path <pool>/<image>.
4. Imported the VM with importUnmanagedInstance. The import succeeded, the VM ran on RBD, and libvirt still pointed at the same image.
5. Destroyed and expunged the imported VM.

Before this change the same disk was reported on the NFS mount that matched the pool name, and the import failed. The live run used an earlier build of the agent in which Gluster disks also took the RBD path. The RBD path is the same in both builds.

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

• Gluster network disks keep the mount-based lookup (unit test).
• File and block disks are not changed by this PR.
• Not covered: a live run with a Gluster disk, and a before/after comparison of a file-based disk on the test environment.