cimtest).
Sure I have other domains defined already on the test system, one of them is running. It's strange that the only domain to not get a console rasd is the test domain.
On 09/10/2013 06:02 PM, John Ferlan wrote: that's actually to be expected, since the testsuite doesn't yet contain support for test domains with a console, I am currently testing a patch that will change this
I did find a bug in the 03*.py code - if there's an error from init_rasd_list, the code returns without undefining the domain. The fix would be:
rasds, status = init_rasd_list(virt, options.ip, test_dom) if status != PASS: logger.error("Unable to build rasd instance list") + vsxml.undefine(server) return status
But doing that still does not resolve the problem.
For whatever reason logger.info didn't spit out the messages, so I changed using to logger.error... I also added a printing of rasds and rasds_inst logger.info doesn't write to the console, only into suites/libvirt-cim/cimtest/$TESTGROUP/cimtest.log
-------------------------------------------------------------------- RASD - 03_rasd_errs.py: FAIL ERROR - RASD found KVM_InputResourceAllocationSettingData for if18lcl ERROR - RASD found KVM_InputResourceAllocationSettingData for if18lcl ERROR - RASD found KVM_InputResourceAllocationSettingData for VSSDC_dom ERROR - RASD found KVM_InputResourceAllocationSettingData for rh70-alpha3 ERROR - RASD found KVM_InputResourceAllocationSettingData for rh70-alpha3 ERROR - RASD found KVM_InputResourceAllocationSettingData for if18net ERROR - RASD found KVM_InputResourceAllocationSettingData for rh64 ERROR - RASD found KVM_InputResourceAllocationSettingData for rh64 ERROR - RASD found KVM_InputResourceAllocationSettingData for if18nopool ERROR - RASD found KVM_InputResourceAllocationSettingData for if18nopool ERROR - RASD found KVM_InputResourceAllocationSettingData for f18 ERROR - RASD found KVM_InputResourceAllocationSettingData for f18 ERROR - RASD found KVM_ProcResourceAllocationSettingData for if18lcl ERROR - RASD found KVM_ProcResourceAllocationSettingData for VSSDC_dom ERROR - RASD found KVM_ProcResourceAllocationSettingData for rhel65-f18 ERROR - RASD found KVM_ProcResourceAllocationSettingData for rh70-alpha3 ERROR - RASD found KVM_ProcResourceAllocationSettingData for if18net ERROR - RASD found KVM_ProcResourceAllocationSettingData for rh64 ERROR - RASD found KVM_ProcResourceAllocationSettingData for if18nopool ERROR - RASD found KVM_ProcResourceAllocationSettingData for f18 ERROR - RASD found KVM_ConsoleResourceAllocationSettingData for if18lcl ERROR - RASD found KVM_ConsoleResourceAllocationSettingData for rhel65-f18 ERROR - RASD found KVM_ConsoleResourceAllocationSettingData for rh70-alpha3 ERROR - RASD found KVM_ConsoleResourceAllocationSettingData for if18net ERROR - RASD found KVM_ConsoleResourceAllocationSettingData for rh64 ERROR - RASD found KVM_ConsoleResourceAllocationSettingData for if18nopool ERROR - RASD found KVM_ConsoleResourceAllocationSettingData for f18
nice finding, for the rest see below the domains above do have a serial or console definition and therefore show up in the first RASD enumeration ... as I have pointed out before, the VSSC_dom is plainly defined without a console by the testsuite, so it is perfectly correct for it not to show up above. Which means that the 03_xxx testcase is broken, as it should check whether the domain has the RASDs that are to be expected instead of a RASD of each type discovered on the system. Will try to fix this as well in the cimtest patch I'm working on -- Mit freundlichen Grüßen/Kind Regards Viktor Mihajlovski IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martina Köderitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294