Difference between revisions of "PowerKVM"
(→Libvirt failures) |
|||
Line 1: | Line 1: | ||
This is the page of the team working with PowerKVM and OpenStack | This is the page of the team working with PowerKVM and OpenStack | ||
+ | |||
+ | = Current Status = | ||
+ | * Reporting disabled | ||
= Actual projects being tested = | = Actual projects being tested = |
Revision as of 20:47, 14 August 2014
This is the page of the team working with PowerKVM and OpenStack
Contents
Current Status
- Reporting disabled
Actual projects being tested
Production
Production means we are testing and reporting back to community. Right now we have the following projects being tested:
- Nova
Development
Development means we are testing internally only, after the project became mature will be added in production and will report back to community
- Tempest
- Devstack
Skip list
We are using a regular expression to skip the list of tests that we know have issues with PowerKVM, or the functionality isn't complete implemented yet.
// TODO add the list of skipped tests here
Debugging PowerKVM Failures
There's a few issues when you're running tempest on PowerKVM that you might can ignore
No results were uploaded
This means that the job fails in stack.sh step, the way we are uploading the results doesn't upload until tempest run. We are aware of this, and we are trying other alternatives.
Libvirt failures
We are aware that sometimes the libvirt driver doesn't work properly, and get stucked, so, if you see this in the console.log please disregard the failures. We are working in a solution and we'll update this wiki as soon as we have it.
sudo virsh list --all ++ sed 's/.*\(instance-[0-9a-fA-F]*\).*/\1/g' ++ grep instance- error: failed to connect to the hypervisor error: no valid connection error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory