[System Tests] Need to change regular expression in deploy_ha_neutron to get node with l3 agent

Bug #1388895 reported by Andrey Sledzinskiy
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Medium
Andrey Sledzinskiy

Bug Description

ERROR: Deploy cluster in HA mode, Neutron with GRE segmentation
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/usr/lib/python2.7/dist-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/usr/lib/python2.7/dist-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/6.0_fuelmain.system_test.centos.thread_5/fuelweb_test/helpers/decorators.py", line 53, in wrapper
    return func(*args, **kwagrs)
  File "/home/jenkins/workspace/6.0_fuelmain.system_test.centos.thread_5/fuelweb_test/tests/tests_strength/test_neutron.py", line 79, in deploy_ha_neutron
    'Started (node-\d+)', ret).group(1)
AttributeError: 'NoneType' object has no attribute 'group'

http://jenkins-product.srt.mirantis.net:8080/view/6.0_swarm/job/6.0_fuelmain.system_test.centos.thread_5/17/testReport/junit/%28root%29/deploy_ha_neutron/deploy_ha_neutron/

We need to change expression in test_strength/test_neutron.py(line 77):
 fqdn = re.search(
            'p_neutron-l3-agent\s+\(ocf::mirantis:neutron-agent-l3\):\s+'
            'Started (node-\d+)', ret).group(1)

Now output of crm status looks like:
Clone Set: clone_p_neutron-l3-agent [p_neutron-l3-agent]
     Started: [ node-1.test.domain.local node-2.test.domain.local node-3.test.domain.local ]

Tags: system-tests
Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :
Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → Andrey Sledzinskiy (asledzinskiy)
Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :

Seems that test isn't correct now and there is no point to check l3 agent migration. I will confirm it with fuel-library

Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :

After merging multiple-l3-agents l3-agent doesn't migrate now and it's present on every controller so test has no sence.
My proposition for now is to remove thread_5 group for this test and afterwards delete it at all and supersede it with neutron failover tests from ha improvements specification.

Changed in fuel:
importance: High → Medium
status: New → Triaged
Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

Do not agree. We should verify and test how cluster works in case if some l3 fails even if we have l3 running on all the controllers. We need to adapt current scenario

Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :

But what is the difference between this scenario and test on destroy controllers from test_failover.py?

Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

Just another test case :) When you have several nodes are running and only 1 l3 agent is up. For know we can skip test with descriptive message(with link to this issue) and discuss this later

Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :

Test on l3-agent rescheduling was proposed from Sergey Vasilenko instead of this one:
1. Find router for the network
neutron router-list
2. Find l3-agent that hosts this router
neutron l3-agent-list-hosting-router router_ID
3. Login to node with this l3-agent
4. Ban l3-agent on this node
pcs resource ban p_neutron-l3-agent NODE
5. Wait until resource is dead (check pcs status)
6. Wait router is re-scheduled to another l3-agent
neutron l3-agent-list-hosting-router router_ID
7. Ssh to instance and check network connectivity
8. Ssh to node with banned l3-agent and do
pcs resource clear p_neutron-l3-agent NODE

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-main (master)

Fix proposed to branch: master
Review: https://review.openstack.org/134880

Changed in fuel:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-main (master)

Reviewed: https://review.openstack.org/134880
Committed: https://git.openstack.org/cgit/stackforge/fuel-main/commit/?id=5eeee9514cbbdf9457366ae60c44d7cdfbba4825
Submitter: Jenkins
Branch: master

commit 5eeee9514cbbdf9457366ae60c44d7cdfbba4825
Author: asledzinskiy <email address hidden>
Date: Sat Nov 8 17:26:44 2014 +0200

    Change test on l3-rescheduling

    - Change logic of the test - check l3-agent rescheduling
    instead of l3-agent migration
    - Add methods to work with python neutron client

    Closes-Bug: #1388895

    Change-Id: Iddc266355beb442a152781b78ebfe40124a7442a

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :

{u'build_id': u'2014-11-26_13-35-04', u'ostf_sha': u'a35f516f1606b0d03d51ff63bfe3fbe23de4b622', u'build_number': u'10', u'auth_required': True, u'nailgun_sha': u'bf9ddb9f9d5dbb09c4b50201ce176635791d7d3e', u'production': u'docker', u'api': u'1.0', u'fuelmain_sha': u'465afb6479a0b3c677040fb978cc109dcf62f774', u'astute_sha': u'c15623d05ccdf7ac10873e7a90df954de8726280', u'feature_groups': [u'mirantis'], u'release': u'6.0', u'release_versions': {u'2014.2-6.0': {u'VERSION': {u'build_id': u'2014-11-26_13-35-04', u'ostf_sha': u'a35f516f1606b0d03d51ff63bfe3fbe23de4b622', u'build_number': u'10', u'api': u'1.0', u'nailgun_sha': u'bf9ddb9f9d5dbb09c4b50201ce176635791d7d3e', u'production': u'docker', u'fuelmain_sha': u'465afb6479a0b3c677040fb978cc109dcf62f774', u'astute_sha': u'c15623d05ccdf7ac10873e7a90df954de8726280', u'feature_groups': [u'mirantis'], u'release': u'6.0', u'fuellib_sha': u'25eb629f3c6a6ff41cf187e260fe4ff456cfc4e4'}}}, u'fuellib_sha': u'25eb629f3c6a6ff41cf187e260fe4ff456cfc4e4'}

Changed in fuel:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.