Deepti B Kalakeri wrote:
Kaitlin Rupert wrote:
>> +
>> + # Since we cannot create a Xen/XenFV guest with invalid networkpool
>> info,
>> + # we first create a guest with valid networkpool info and then + #
>> then destroy the networkpool info as a work around to, verify if the
>> + # provider returns an exception for Xen/XenFV guest when its
>> networkpool + # does not exist anymore on the machine.
>> + status, vsxml = setup_env(server, virt, int_name, in_list)
>> + if status != PASS:
>> + logger.error("Failed to setup the domain")
>> + vsxml.undefine(server)
>
> In the Xen/XenFV case, you'll need to cleanup the network pool.
cleaning of the networkpool for Xen and XenFV is taken care in the
setup_env() fn, before it leaves the function when it fails to define a
domain.
Yep, I missed that. It's been applied now =)
--
Kaitlin Rupert
IBM Linux Technology Center
kaitlin(a)linux.vnet.ibm.com