Tests on destroying one controller and verification l3 agent behaviour and pings between VMs fail for MOS 8.0

Bug #1578605 reported by Alexander Gromov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Fix Committed
High
Alexander Gromov

Bug Description

Repository: https://github.com/Mirantis/mos-integration-tests

Tests "Shut down non-primary controller and check l3-agent work" and "Shut down primary controller and check l3-agent" fail for MOS 8.0 with the following message:
TimeoutExpired: Timeout of 180 seconds expired waiting for SSH command: ping -c1 8.8.8.8 && ping -c1 192.168.4.4 && ping -c1 10.109.27.133 && ping -c1 192.168.3.4 completed with 0 exit code

Testrail links:
https://mirantis.testrail.com/index.php?/tests/view/5269880
https://mirantis.testrail.com/index.php?/tests/view/5269878

Sometimes the following error can be found:
Failed: There are routers on l3_agent(ea1db255-eca7-4628-83b0-89116071d941): router04(11d36eaa-44e4-4da3-aba1-5c09ff440dbf) router01(7e9d508b-6c34-4cb9-97fa-496b5758e0ab)

Environment: 3 controllers + 2 computes-cinder VxLAN + L2POP

Milestone: Mirantis OpenStack 8.0-updates

Tags: area-qa
Changed in mos:
status: New → Confirmed
assignee: nobody → Alexander Gromov (agromov)
Revision history for this message
Alexander Gromov (agromov) wrote :

There was a problem with implementation of ssh connection.
Review link: https://review.gerrithub.io/#/c/275328/

Changed in mos:
status: Confirmed → In Progress
status: In Progress → Fix Committed
Revision history for this message
Alexander Gromov (agromov) wrote :

The problem exists after commit.

Changed in mos:
status: Fix Committed → Confirmed
tags: added: area-qa
Changed in mos:
milestone: none → 8.0-updates
importance: Undecided → High
Revision history for this message
Alexander Gromov (agromov) wrote :

There is also a problem with check_no_routers_on_l3_agent function.

description: updated
Revision history for this message
Alexander Gromov (agromov) wrote :
Changed in mos:
status: Confirmed → In Progress
status: In Progress → Fix Committed
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.