Description of problem: When executing vdsm-client Host getVMFullList I get for a VM I have - "vmName": "nNone" and not the actual VM name Version-Release number of selected component (if applicable): 4.2.0-0.0.master.20171116212005.git61ffb5f.el7.centos vdsm-4.20.7-34.gitab15536.el7.centos.x86_64 vdsm-client-4.20.7-34.gitab15536.el7.centos.noarch How reproducible: 100% Steps to Reproduce: 1. Start VM on host 2. Run 'vdsm-client Host getVMFullLis' on host 3. Actual results: Expected results: Additional info:
Regression flag: We use vmName in our automation to identify the VM and it used to work fine
Raz, if there are vdsm-client commands you use for automation and are critical, let me know so we can add them to ovirt-system-tests.
(In reply to Yaniv Kaul from comment #2) > Raz, if there are vdsm-client commands you use for automation and are > critical, let me know so we can add them to ovirt-system-tests. Or better yet, add them yourself :-)
Sure, will do
Alternatively, how about migrating automation code to libvirt; e.g. virsh -r list would show currently-running names of VMs.
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
We actually need more information on the VM like IP, disk logical names, etc. which is not provided be virsh -r list. Of course, we can workaround this issue, otherwise, I would mark it as urgent, but I don't think this is the correct approach
(In reply to Raz Tamir from comment #7) > We actually need more information on the VM like IP, disk logical names, > etc. which is not provided be virsh -r list. > > Of course, we can workaround this issue, otherwise, I would mark it as > urgent, but I don't think this is the correct approach Vdsm does not report anymore this information for any VM created with the Domain XML - as per Engine >= 4.2 defaults (it does if VM is created with vm.conf, as Engine <= 4.1 does) Some informations are easy to provide, and we can evaluate to do that to give time to the automated tools to catch up. Please provide the fields you need. Fixing 'vmName' meanwhile.
(In reply to Francesco Romani from comment #8) > (In reply to Raz Tamir from comment #7) > > We actually need more information on the VM like IP, disk logical names, > > etc. which is not provided be virsh -r list. > > > > Of course, we can workaround this issue, otherwise, I would mark it as > > urgent, but I don't think this is the correct approach > > Vdsm does not report anymore this information for any VM created with the > Domain XML - as per Engine >= 4.2 defaults (it does if VM is created with > vm.conf, as Engine <= 4.1 does) > > Some informations are easy to provide, and we can evaluate to do that to > give time to the automated tools to catch up. > > Please provide the fields you need. Fixing 'vmName' meanwhile. I forgot to mention that the output of 'getAllVmStats' is unchanged, and always the same regardless the VM is created.
I tested few other fields we use in our automation and seems like this is the only issue
If we agree this is a regression, then this doesn't deserve any doc_text.
patch merged -> MODIFIED
Verified on ovirt-engine-ovirt-engine-4.2.0-0.5.master.el7.noarch: # vdsm-client Host getVMFullList ... } }, "clientIp": "", "statusTime": "4572590680", "vmName": "golden_env_mixed_virtio_1_0" }
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.