Hyper-V Inventory Doesn't Add Storage for VMs with VHDs on Network Drive #5383
Comments
Add changes to implement running SSA on HyperV virtual disks which are network mounted on the server. 1) in the MiqScvmmVm.init_disk_info determine whether a disk is network mounted. 2) in the Vhdx and Vhd disk modules pass the network attribute when instantiating a MiqHyperVDisk, and pass the attribute along when getting a parent disk (in the case of checkpoints/snapshots). 3) Add the winrm-elevated accessor to MiqWinRM, and make sure MiqHyperVDisk uses the correct accessor to run remote commands depending upon whether the virtual disk is remote-mounted or not. 4) Allow scanning of Microsoft VMs without storage in the DB (See Issue ManageIQ#5383)
Add changes to implement running SSA on HyperV virtual disks which are network mounted on the server. 1) in the MiqScvmmVm.init_disk_info determine whether a disk is network mounted. 2) in the Vhdx and Vhd disk modules pass the network attribute when instantiating a MiqHyperVDisk, and pass the attribute along when getting a parent disk (in the case of checkpoints/snapshots). 3) Add the winrm-elevated accessor to MiqWinRM, and make sure MiqHyperVDisk uses the correct accessor to run remote commands depending upon whether the virtual disk is remote-mounted or not. 4) Allow scanning of Microsoft VMs without storage in the DB (See Issue ManageIQ#5383)
|
Hi @jerryk55 - I see a lot of commits / PRs made against this issue. Should this still be open? |
|
@bronaghs I think so. The commits were a work-around to allow SSA to work in this situation, but the storage_id is still NULL in the database for these VMs. Assuming we want the storage to be populated correctly for these VMs, the issue would be still open. Your mileage may vary. |
|
Ok, Thanks @jerryk55 |
|
This issue has been automatically marked as stale because it has not been updated for at least 6 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! |
|
@jerryk55 if this issue is no longer relevant then please close. |
|
@miq-bot close_issue |
VMs with VHDs residing on network-mounted drives, starting with \ - have a NULL Storage_ID in the database. An attempt to run smart state analysis on one of these vms fails with the message "Is not located on a storage". The drive letter can be obtained via the PowerShell command "Net Use". Querying the VM settings shows the "" address rather than the drive letter. The inventory script should probably do the right thing. In addition the code for obtaining the actual VHD file in Smart State Analysis needs to do the right thing.
@blomquisg this is probably an issue for your team (at least partially).
The text was updated successfully, but these errors were encountered: