10:11 p.m.
Distro: Fedora 9 Beta
Kernel: 2.6.25-0.121.rc5.git4.fc9
Libvirt: 0.4.1-7.fc9
CIMOM: 2.7.0-6.fc9
PyWBEM: 0.6-1
libcmpiutil: 0.3-1.fc9
libvirt-cim: 0.3-4.fc9
cimtest: changeset-127
========PASS(83)=SKIP(17)=XFAIL(7)=FAIL(16)=================
AllocationCapabilities - 01_enum.py: PASS
AllocationCapabilities - 02_alloccap_gi_errs.py: PASS
ComputerSystem - 01_enum.py: PASS
ComputerSystem - 02_nosystems.py: PASS
ComputerSystem - 03_defineVS.py: PASS
ComputerSystem - 04_defineStartVS.py: PASS
ComputerSystem - 05_activate_defined_start.py: XFAIL Bug: 85769
ComputerSystem - 06_paused_active_suspend.py: XFAIL Bug: 85769
ComputerSystem - 22_define_suspend.py: PASS
ComputerSystem - 23_suspend_suspend.py: SKIP
ComputerSystem - 27_define_suspend_errs.py: SKIP
ComputerSystem - 32_start_reboot.py: SKIP
ComputerSystem - 33_suspend_reboot.py: SKIP
ComputerSystem - 35_start_reset.py: SKIP
ComputerSystem - 40_RSC_start.py: XFAIL Bug: 91410
ComputerSystem - 41_cs_to_settingdefinestate.py: SKIP
ComputerSystem - 42_cs_gi_errs.py: PASS
ComputerSystemIndication - 01_created_indication.py: FAIL
ElementAllocatedFromPool - 01_forward.py: SKIP
ElementAllocatedFromPool - 02_reverse.py: SKIP
ElementAllocatedFromPool - 03_reverse_errs.py: FAIL
ElementAllocatedFromPool - 04_forward_errs.py: XFAIL Bug: 88651
ElementCapabilities - 01_forward.py: PASS
ElementCapabilities - 02_reverse.py: PASS
ElementCapabilities - 03_forward_errs.py: PASS
ElementCapabilities - 04_reverse_errs.py: PASS
ElementCapabilities - 05_hostsystem_cap.py: PASS
ElementConforms - 01_forward.py: PASS
ElementConforms - 02_reverse.py: FAIL
ElementConforms - 03_ectp_fwd_errs.py: XFAIL Bug: 92642
ElementConforms - 04_ectp_rev_errs.py: FAIL
ElementSettingData - 01_forward.py: PASS
ElementSettingData - 03_esd_assoc_with_rasd_errs.py: FAIL
EnabledLogicalElementCapabilities - 01_enum.py: PASS
EnabledLogicalElementCapabilities - 02_elecap_gi_errs.py: PASS
HostSystem - 01_enum.py: PASS
HostSystem - 02_hostsystem_to_rasd.py: PASS
HostSystem - 03_hs_to_settdefcap.py: PASS
HostSystem - 04_hs_to_EAPF.py: SKIP
HostSystem - 05_hs_gi_errs.py: PASS
HostSystem - 06_hs_to_vsms.py: PASS
HostedDependency - 01_forward.py: PASS
HostedDependency - 02_reverse.py: PASS
HostedDependency - 03_enabledstate.py: PASS
HostedDependency - 04_reverse_errs.py: PASS
HostedResourcePool - 01_forward.py: PASS
HostedResourcePool - 02_reverse.py: PASS
HostedResourcePool - 03_forward_errs.py: PASS
HostedResourcePool - 04_reverse_errs.py: PASS
HostedService - 01_forward.py: PASS
HostedService - 02_reverse.py: PASS
HostedService - 03_forward_errs.py: PASS
HostedService - 04_reverse_errs.py: PASS
LogicalDisk - 01_disk.py: PASS
LogicalDisk - 02_nodevs.py: PASS
LogicalDisk - 03_ld_gi_errs.py: PASS
Memory - 01_memory.py: PASS
Memory - 02_defgetmem.py: PASS
Memory - 03_mem_gi_errs.py: PASS
NetworkPort - 01_netport.py: PASS
NetworkPort - 02_np_gi_errors.py: PASS
NetworkPort - 03_user_netport.py: FAIL
Processor - 01_processor.py: PASS
Processor - 02_definesys_get_procs.py: PASS
Processor - 03_proc_gi_errs.py: PASS
Profile - 01_enum.py: PASS
Profile - 02_profile_to_elec.py: SKIP
Profile - 03_rprofile_gi_errs.py: SKIP
RASD - 01_verify_rasd_fields.py: PASS
RASD - 02_enum.py: PASS
RASD - 03_rasd_errs.py: PASS
ReferencedProfile - 01_verify_refprof.py: FAIL
ReferencedProfile - 02_refprofile_errs.py: FAIL
ResourceAllocationFromPool - 01_forward.py: PASS
ResourceAllocationFromPool - 02_reverse.py: PASS
ResourceAllocationFromPool - 03_forward_errs.py: FAIL
ResourceAllocationFromPool - 04_reverse_errs.py: PASS
ResourceAllocationFromPool - 05_RAPF_err.py: PASS
ResourcePool - 01_enum.py: PASS
ResourcePool - 02_rp_gi_errors.py: PASS
ResourcePoolConfigurationCapabilities - 01_enum.py: PASS
ResourcePoolConfigurationCapabilities - 02_rpcc_gi_errs.py: PASS
ResourcePoolConfigurationService - 01_enum.py: PASS
ResourcePoolConfigurationService - 02_rcps_gi_errors.py: PASS
ResourcePoolConfigurationService - 03_CreateResourcePool.py: FAIL
ResourcePoolConfigurationService - 04_CreateChildResourcePool.py: FAIL
ResourcePoolConfigurationService - 05_AddResourcesToResourcePool.py:
XFAIL Bug: 92173
ResourcePoolConfigurationService -
06_RemoveResourcesFromResourcePool.py: FAIL
ResourcePoolConfigurationService - 07_DeleteResourcePool.py: FAIL
SettingsDefine - 01_forward.py: PASS
SettingsDefine - 02_reverse.py: FAIL
SettingsDefine - 03_sds_fwd_errs.py: PASS
SettingsDefine - 04_sds_rev_errs.py: PASS
SettingsDefineCapabilities - 01_forward.py: SKIP
SettingsDefineCapabilities - 03_forward_errs.py: PASS
SettingsDefineCapabilities - 04_forward_vsmsdata.py: PASS
SettingsDefineCapabilities - 05_reverse_vsmcap.py: PASS
SystemDevice - 01_forward.py: PASS
SystemDevice - 02_reverse.py: PASS
SystemDevice - 03_fwderrs.py: PASS
VSSD - 01_enum.py: PASS
VSSD - 02_bootldr.py: SKIP
VSSD - 03_vssd_gi_errs.py: PASS
VSSD - 04_vssd_to_rasd.py: PASS
VirtualSystemManagementCapabilities - 01_enum.py: PASS
VirtualSystemManagementCapabilities - 02_vsmcap_gi_errs.py: PASS
VirtualSystemManagementService - 01_definesystem_name.py: PASS
VirtualSystemManagementService - 02_destroysystem.py: PASS
VirtualSystemManagementService - 03_definesystem_ess.py: PASS
VirtualSystemManagementService - 04_definesystem_ers.py: PASS
VirtualSystemManagementService - 05_destroysystem_neg.py: PASS
VirtualSystemManagementService - 06_addresource.py: FAIL
VirtualSystemManagementService - 07_addresource_neg.py: PASS
VirtualSystemManagementService - 08_modifyresource.py: XFAIL Bug: 90853
VirtualSystemMigrationCapabilities - 01_enum.py: PASS
VirtualSystemMigrationCapabilities - 02_vsmc_gi_errs.py: PASS
VirtualSystemMigrationService - 01_migratable_host.py: SKIP
VirtualSystemMigrationService - 02_host_migrate_type.py: SKIP
VirtualSystemMigrationService - 05_migratable_host_errs.py: SKIP
VirtualSystemMigrationSettingData - 01_enum.py: PASS
VirtualSystemMigrationSettingData - 02_vsmsd_gi_errs.py: PASS
VirtualSystemSettingDataComponent - 01_forward.py: SKIP
VirtualSystemSettingDataComponent - 02_reverse.py: PASS
VirtualSystemSettingDataComponent - 03_vssdc_fwd_errs.py: FAIL
VirtualSystemSettingDataComponent - 04_vssdc_rev_errs.py: PASS
VirtualSystemSnapshotService - 01_enum.py: PASS
VirtualSystemSnapshotService - 02_vs_sservice_gi_errs.py: PASS
VirtualSystemSnapshotServiceCapabilities - 01_enum.py: PASS
VirtualSystemSnapshotServiceCapabilities - 02_vs_sservicecap_gi_errs.py:
PASS
--
- Zhengang
12:33 a.m.
ComputerSystemIndication - 01_created_indication.py: FAIL
Pegasus crashed after running this test case.
Log says 'BadStatusLine :'
ElementAllocatedFromPool - 03_reverse_errs.py: FAIL
exp:
ERR_NOT_FOUND(6) - No such instance
ret: ERR_FAILED(1) - Invalid InstanceID or unsupported pool type
ElementConforms - 02_reverse.py: FAIL
Binary rpm provider
returns CIM_ERR_INVALID_PARAMETER:
KVM_ElementConformsToProfile on the following query:
wbemain -ac KVM_ElementConformsToProfile
'http://u:p@host:5988/root/virt:KVM_ComputerSystem.CreationClassName="KVM_ComputerSystem",Name="domgst"'
Same wbemcli command gets the correct results on another system using
latest libvirt-cim tree (changeset 533).
ElementConforms - 04_ectp_rev_errs.py: FAIL
All negative checks
result in the CIM_ERR_INVALID_PARAMETER. Should be
the same reason as ElementConforms.02
ElementSettingData - 03_esd_assoc_with_rasd_errs.py: FAIL
This
one passed in individual run. The previous ElementConforms.04
undefine fix doesn't help here. Might be some other unknown missing
undefine.
NetworkPort - 03_user_netport.py: FAIL
'user' network
type.
[Known Issue]
ReferencedProfile - 01_verify_refprof.py: FAIL
Binary rpm
provider gives 2 results on the following query:
wbemein http://u:p@host:5988/root/interop:KVM_RegisteredProfile
"CIM:DSP1042-SystemVirtualization-1.0.0"
"CIM:DSP1057-VirtualSystem-1.0.0a"
Same wbemcli command gets 5 results on changeset-533 tree on another system.
"CIM:DSP1042-SystemVirtualization-1.0.0"
"CIM:DSP1057-VirtualSystem-1.0.0a"
"CIM:DSP1059-GenericDeviceResourceVirtualization-1.0.0"
"CIM:DSP1045-MemoryResourceVirtualization-1.0.0"
"CIM:DSP1081-VirtualSystemMigration-1.0"
This leads to ReferencedProfile's 'ain' query gets only 2 results.
ReferencedProfile - 02_refprofile_errs.py: FAIL
Same as
ReferencedProfile.01
ResourceAllocationFromPool - 03_forward_errs.py: FAIL
Daisy
sent a fix for this. Should be passed with her fix.
ResourcePoolConfigurationService - 03_CreateResourcePool.py: FAIL
ResourcePoolConfigurationService - 04_CreateChildResourcePool.py: FAIL
ResourcePoolConfigurationService - 06_RemoveResourcesFromResourcePool.py: FAIL
ResourcePoolConfigurationService - 07_DeleteResourcePool.py: FAIL
CIM_ERR_NOT_SUPPORTED for 03, 04, 06, 07
SettingsDefine - 02_reverse.py: FAIL
ProcRASD.InstanceID is
'domname/0' in binary rpm provider. Test case
expects 'domname/proc' now.
VirtualSystemManagementService - 06_addresource.py: FAIL
Different network xml returned from system_to_xml() in provider and
'virsh dumpxml'. Error message complains about missing <source> in the a
bridged network device.
VirtualSystemSettingDataComponent - 03_vssdc_fwd_errs.py: FAIL
Daisy sent a fix this morning. Should be passed upon patch applied.
--
- Zhengang
8:56 a.m.
Zhengang Li wrote:
> ComputerSystemIndication - 01_created_indication.py: FAIL
Pegasus crashed after running this test case.
Log says 'BadStatusLine :'
Any more information on why the provider is crashing here? I'm able to
run with KVM on current sources. Maybe this test is hitting a provider
but that's been fixed?
--
Kaitlin Rupert
IBM Linux Technology Center
kaitlin(a)linux.vnet.ibm.com
1:17 a.m.
Kaitlin Rupert wrote:
Zhengang Li wrote:
>> ComputerSystemIndication - 01_created_indication.py: FAIL
> Pegasus crashed after running this test case.
> Log says 'BadStatusLine :'
>
Any more information on why the provider is crashing here? I'm able
to run with KVM on current sources. Maybe this test is hitting a
provider but that's been fixed?
This test cases has never passed for me.
It always fails with timeout.
Any idea why this could be ?
9:50 a.m.
Deepti B Kalakeri wrote:
Kaitlin Rupert wrote:
> Zhengang Li wrote:
>>> ComputerSystemIndication - 01_created_indication.py: FAIL
>> Pegasus crashed after running this test case.
>> Log says 'BadStatusLine :'
>>
>
> Any more information on why the provider is crashing here? I'm able
> to run with KVM on current sources. Maybe this test is hitting a
> provider but that's been fixed?
>
This test cases has never passed for me.
It always fails with timeout.
Any idea why this could be ?
You'll need to have:
repositoryIsDefaultInstanceProvider=true
enableIndicationService=true
Set for the CIMOM (if you're using Pegasus).
Also, does the test return an error or does the test suite time out and
move to the next test?
--
Kaitlin Rupert
IBM Linux Technology Center
kaitlin(a)linux.vnet.ibm.com
12:46 a.m.
Kaitlin Rupert wrote:
Deepti B Kalakeri wrote:
>
>
> Kaitlin Rupert wrote:
>> Zhengang Li wrote:
>>>> ComputerSystemIndication - 01_created_indication.py: FAIL
>>> Pegasus crashed after running this test case.
>>> Log says 'BadStatusLine :'
>>>
>>
>> Any more information on why the provider is crashing here? I'm able
>> to run with KVM on current sources. Maybe this test is hitting a
>> provider but that's been fixed?
>>
> This test cases has never passed for me.
> It always fails with timeout.
> Any idea why this could be ?
>
You'll need to have:
repositoryIsDefaultInstanceProvider=true
enableIndicationService=true
Set for the CIMOM (if you're using Pegasus).
Also, does the test return an error or does the test suite time out
and move to the next test?
The test time's out and moves ahead to the next
test.
I tried setting the above options, but no luck.
Here is the list of options that are set on my test machine.
enableAssociationTraversal=true
maxProviderProcesses=0
enableAuditLog=false
sslClientVerificationMode=disabled
forceProviderProcesses=false
enableSubscriptionsForNonprivilegedUsers=false
socketWriteTimeout=20
messageDir=msg
shutdownTimeout=30
authorizedUserGroups=
enableRemotePrivilegedUserAccess=true
enableHttpsConnection=true
enableIndicationService=true
enableNamespaceAuthorization=true
sslTrustStoreUserName=
enableHttpConnection=true
Though I set the repositoryIsDefaultInstanceProvider=true and restart
the cimserver, I dont find it listed using cimconfig -l -p does not
list the repositoryIsDefaultInstanceProvider=true property.
4:07 p.m.
Deepti B Kalakeri wrote:
Kaitlin Rupert wrote:
> Deepti B Kalakeri wrote:
>>
>>
>> Kaitlin Rupert wrote:
>>> Zhengang Li wrote:
>>>>> ComputerSystemIndication - 01_created_indication.py: FAIL
>>>> Pegasus crashed after running this test case.
>>>> Log says 'BadStatusLine :'
>>>>
>>>
>>> Any more information on why the provider is crashing here? I'm able
>>> to run with KVM on current sources. Maybe this test is hitting a
>>> provider but that's been fixed?
>>>
>> This test cases has never passed for me.
>> It always fails with timeout.
>> Any idea why this could be ?
>>
>
> You'll need to have:
>
> repositoryIsDefaultInstanceProvider=true
> enableIndicationService=true
>
> Set for the CIMOM (if you're using Pegasus).
>
> Also, does the test return an error or does the test suite time out
> and move to the next test?
The test time's out and moves ahead to the next test.
I tried setting the above options, but no luck.
Here is the list of options that are set on my test machine.
Hmm.. I'm not sure why this would happen. Have you able to run the
indication tester (libcmpiutil/tools/indication_tester.py)?
--
Kaitlin Rupert
IBM Linux Technology Center
kaitlin(a)linux.vnet.ibm.com
7:10 a.m.
Zhengang Li wrote:
> ComputerSystemIndication - 01_created_indication.py: FAIL
Pegasus crashed after running this test case.
Log says 'BadStatusLine :'
> ElementAllocatedFromPool - 03_reverse_errs.py: FAIL
exp: ERR_NOT_FOUND(6) - No such instance
ret: ERR_FAILED(1) - Invalid InstanceID or unsupported pool type
> ElementConforms - 02_reverse.py: FAIL
Binary rpm provider returns CIM_ERR_INVALID_PARAMETER:
KVM_ElementConformsToProfile on the following query:
wbemain -ac KVM_ElementConformsToProfile
'http://u:p@host:5988/root/virt:KVM_ComputerSystem.CreationClassName="KVM_ComputerSystem",Name="domgst"'
Same wbemcli command gets the correct results on another system using
latest libvirt-cim tree (changeset 533).
I dont see the
KVM_ElementConformsToProfile.CIM_ElementConformsToProfile
registered in the root#virt namespace on F9 machine with rpm
libvirt-cim, while the same is present in both the root#interop and
root#virt namespace on F9 machine with latest libvirt-cim sources.
I tried copying the provider manually to the root#virt namespace and
restarted the cimserver, but I did not get any results even after that.
I dont know if this is proper way of registering the mof files in the
namespace.
Although, the above wbemcli gives me expected o/p on the
F9 with rpm when the query includes the root/interop namespace,
While on the F9 with latest source I get o/p for query with root/virt
namespace.
Could you please tell me the namespace and ECTP provider registration
details.
> ElementConforms - 04_ectp_rev_errs.py: FAIL
All negative checks result in the CIM_ERR_INVALID_PARAMETER. Should be
the same reason as ElementConforms.02
This returned XFAIL on F9 with rpm binary. It
passes with the latest
libvirt-cim sources.
> ElementSettingData - 03_esd_assoc_with_rasd_errs.py: FAIL
This one passed in individual run. The previous ElementConforms.04
undefine fix doesn't help here. Might be some other unknown missing
undefine.
> NetworkPort - 03_user_netport.py: FAIL
'user' network type.
[Known Issue]
> ReferencedProfile - 01_verify_refprof.py: FAIL
Binary rpm provider gives 2 results on the following query:
wbemein http://u:p@host:5988/root/interop:KVM_RegisteredProfile
"CIM:DSP1042-SystemVirtualization-1.0.0"
"CIM:DSP1057-VirtualSystem-1.0.0a"
Same wbemcli command gets 5 results on changeset-533 tree on another
system.
"CIM:DSP1042-SystemVirtualization-1.0.0"
"CIM:DSP1057-VirtualSystem-1.0.0a"
"CIM:DSP1059-GenericDeviceResourceVirtualization-1.0.0"
"CIM:DSP1045-MemoryResourceVirtualization-1.0.0"
"CIM:DSP1081-VirtualSystemMigration-1.0"
Yes this is correct.
This leads to ReferencedProfile's 'ain' query gets only 2
results.
I did not see the ReferncedProfile query return any results.
since the ReferencedProfile is not present on the on an rpm libvirt-cim
based F9 machine and hence the ain query fails without any results.
> ReferencedProfile - 02_refprofile_errs.py: FAIL
Same as ReferencedProfile.01
I think the ReferncedProfile was added with the changeset 500 and the
rpm contains the changes till 393, hence I think the ReferencedProfile
did not get registered on the machine.
Should we skip the above test cases for rpm based F9 ?
> ResourceAllocationFromPool - 03_forward_errs.py: FAIL
Daisy sent a fix for this. Should be passed with her fix.
> ResourcePoolConfigurationService - 03_CreateResourcePool.py: FAIL
> ResourcePoolConfigurationService - 04_CreateChildResourcePool.py: FAIL
> ResourcePoolConfigurationService -
> 06_RemoveResourcesFromResourcePool.py: FAIL
> ResourcePoolConfigurationService - 07_DeleteResourcePool.py: FAIL
CIM_ERR_NOT_SUPPORTED for 03, 04, 06, 07
Fix submitted.
> SettingsDefine - 02_reverse.py: FAIL
ProcRASD.InstanceID is 'domname/0' in binary rpm provider. Test case
expects 'domname/proc' now.
> VirtualSystemManagementService - 06_addresource.py: FAIL
Different network xml returned from system_to_xml() in provider and
'virsh dumpxml'. Error message complains about missing <source> in the
a bridged network device.
> VirtualSystemSettingDataComponent - 03_vssdc_fwd_errs.py: FAIL
Daisy sent a fix this morning. Should be passed upon patch applied.
10:04 a.m.
wbemain -ac KVM_ElementConformsToProfile
'http://u:p@host:5988/root/virt:KVM_ComputerSystem.CreationClassName="KVM_ComputerSystem",Name="domgst"'
I dont see the
KVM_ElementConformsToProfile.CIM_ElementConformsToProfile
registered in the root#virt namespace on F9 machine with rpm
libvirt-cim, while the same is present in both the root#interop and
root#virt namespace on F9 machine with latest libvirt-cim sources.
This might be a bug in the rpm install - I'll take a look.
I tried copying the provider manually to the root#virt namespace and
restarted the cimserver, but I did not get any results even after that.
I dont know if this is proper way of registering the mof files in the
namespace.
To register a mof file, you can do the following:
sudo cimmofl -uc -aEV -R$PEGASUS_REPO -n /root/virt <mof file>
Where PEGASUS_REPO is the location of your Pegasus repository (probably
PEGASUS_REPO=/var/lib/Pegasus).
However, the rpm should be doing this for you.
Although, the above wbemcli gives me expected o/p on the
F9 with rpm when the query includes the root/interop namespace,
While on the F9 with latest source I get o/p for query with root/virt
namespace.
ECTP is a cross-namespace provider. For our implementation, that means
the ECTP mof is registered to both root/interop and root/virt. The
provider is also registered to both name spaces.
You said said the following query works for you with the F9 rpm:
wbemain -ac KVM_ElementConformsToProfile
'http://localhost:5988/root/interop:KVM_ComputerSystem.CreationClassName="KVM_ComputerSystem",Name="domgst"'
That's a bug which been fixed in recent sources. You should see the
following:
*
* wbemain: Cim: (6) CIM_ERR_NOT_FOUND: CIM_ERR_NOT_FOUND:
KVM_ComputerSystem.CreationClassName="KVM_ComputerSystem",Name="domgst"
*
This query is asking for the associators for this reference in the
interop namespace. However, that instance doesn't exist in the interop
namespace - it should only exist in the virt namespace. To verify, you
can try the following query - it should also fail:
wbemcli gi
'http://localhost:5988/root/interop:KVM_ComputerSystem.CreationClassName="KVM_ComputerSystem",Name="domgst"'
Could you please tell me the namespace and ECTP provider
registration
details.
Take a look at the ECTP registration file
(schema/ElementConformsToProfile.registration) and compare this with the
registration file for ComputerSystem (schema/ComputerSystem.registration).
>
>> ElementSettingData - 03_esd_assoc_with_rasd_errs.py: FAIL
> This one passed in individual run. The previous ElementConforms.04
> undefine fix doesn't help here. Might be some other unknown missing
> undefine.
Is the test failing because it cannot create the guest, or is it due to
some other issue?
>
>> NetworkPort - 03_user_netport.py: FAIL
> 'user' network type.
> [Known Issue]
>
>> ReferencedProfile - 01_verify_refprof.py: FAIL
> Binary rpm provider gives 2 results on the following query:
> wbemein http://u:p@host:5988/root/interop:KVM_RegisteredProfile
> "CIM:DSP1042-SystemVirtualization-1.0.0"
> "CIM:DSP1057-VirtualSystem-1.0.0a"
> Same wbemcli command gets 5 results on changeset-533 tree on another
> system.
> "CIM:DSP1042-SystemVirtualization-1.0.0"
> "CIM:DSP1057-VirtualSystem-1.0.0a"
> "CIM:DSP1059-GenericDeviceResourceVirtualization-1.0.0"
> "CIM:DSP1045-MemoryResourceVirtualization-1.0.0"
> "CIM:DSP1081-VirtualSystemMigration-1.0"
Yes this is correct.
> This leads to ReferencedProfile's 'ain' query gets only 2 results.
>
I did not see the ReferncedProfile query return any results.
since the ReferencedProfile is not present on the on an rpm libvirt-cim
based F9 machine and hence the ain query fails without any results.
>> ReferencedProfile - 02_refprofile_errs.py: FAIL
> Same as ReferencedProfile.01
>
I think the ReferncedProfile was added with the changeset 500 and the
rpm contains the changes till 393, hence I think the ReferencedProfile
did not get registered on the machine.
Close - it's changeset 501.
Should we skip the above test cases for rpm based F9 ?
Yes - that's a good idea. You can check the changeset version, and skip
if it's lower than changeset 501.
Thanks!
--
Kaitlin Rupert
IBM Linux Technology Center
kaitlin(a)linux.vnet.ibm.com
3:57 a.m.
Kaitlin Rupert wrote:
>>
>>> ElementSettingData - 03_esd_assoc_with_rasd_errs.py: FAIL
>> This one passed in individual run. The previous ElementConforms.04
>> undefine fix doesn't help here. Might be some other unknown missing
>> undefine.
Is the test failing because it cannot create the guest, or is it due
to some other issue?
I dont have the details as to why the above test case failed, need to
ask Zhen Gang regarding this. But this tc passed on elm3b193 for me
which is a rpm libvirt-cim based f9 machine .
6073
days inactive
6079
days old
9 comments
3 participants
participants (3)
-
Deepti B Kalakeri -
Kaitlin Rupert -
Zhengang Li