User Tools

Site Tools


tempest_brahmaputra_page

This is an old revision of the document!


Functest Brahmaputra - Tempest status

All tests executed on Stable/Brahmaputra except Apex on Master

Test case success rate for available scenarios

Scenario Apex Compass Fuel Joid
os-nosdn-nofeature-ha 209/210 (100%) 188/210 (90%) (-8%) no POD available
os-odl_l2-nofeature-ha 71/73 (97%) 199/210 (94%) (+3%) 177/210 (84%) (+20%) 73/210 (35%) (+21%)*
os-odl_l3-nofeature-ha 54/71 (76%) 153/192 (80%) (+8%)
os-onos-nofeature-ha 36/84 (42%) (-58%) 199/210 (95%) (-) 96/210 (46%) (-50%) 120/210 (57%)

* same scenario executed on Orange POD 2 ⇒ 190/210 = 90%

Failure analysis for available scenarios

Scenario Apex Compass Fuel Joid
os-nosdn-nofeature-ha 1 test case failed because of " u'192.168.10.158' != u"Please login as 'cirros' user, not as root\n\n": Failed while verifying metadata on server. Result of command "curl http://169.254.169.254/latest/meta-data/public-ipv4" is NOT "192.168.10.158"." error.
os-odl_l2-nofeature-ha Two test cases fail with "create_port_postcommit failed" and "create_subnet_postcommit failed" errors. This is OpenDaylight related problem.
os-odl_l3-nofeature-ha
os-onos-nofeature-ha 10 test cases failed because of "Connection to the 192.168.10.N via SSH timed out." error so there is probably some problem with external network connectivity. One test case failed because of " u'192.168.10.155' != u"Please login as 'cirros' user, not as root\n\n": Failed while verifying metadata on server. Result of command "curl http://169.254.169.254/latest/meta-data/public-ipv4" is NOT "192.168.10.155"." error. One test case failed because of "Timed out waiting for 172.30.10.182 to become reachable" error and 6 others with "Connection to the 172.30.10.N via SSH timed out." error. There seems to be some problem with external network connectivity.

Following table describes most common tempest case failures and probable reasons for them:

Error message Explanation/status
'Floating ip pool not found' The reason for this problem is that default_floating_pool parameter in /etc/nova/nova.conf file doesn't match the name of existing external network. Note that default value of this parameter is 'public'. The problem can be easily reproducing by giving 'nova floating-ip-create' command without any parameters.
'create_network_postcommit failed' / 'create_subnet_postcommit failed' This is quite common problem in setups with OpenDaylight SDN controller. The problem seems not to be permanent and can be probably caused by known ODL ML2 driver problems (see e.g. https://bugs.launchpad.net/networking-odl/+bug/1493551)
'Server <UUID> failed to reach VERIFY_RESIZE status' The reason for this error is that nova service is not able to copy server data between compute nodes using ssh/scp. SSH keys should be generated and distributed between nodes (see http://bderzhavets.blogspot.fi/2015/09/resize-nova-instances-on-rdo-liberty.html for more details.)
tempest_brahmaputra_page.1454489675.txt.gz · Last modified: 2016/02/03 08:54 by Morgan Richomme