[OSTF] OSTF test 'Check network connectivity from instance via floating IP' failed on env with multiple node groups.

Bug #1593262 reported by Olesia Tsvigun
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel Contrail plugin
Invalid
High
Olesia Tsvigun

Bug Description

Fuel ISO#570
contrail-4.0-4.0.0-1-437.noarch.rpm

Steps to reproduce
            1. Revert snapshot with ready master node
            2. Install contrail plugin
            3. Bootstrap slaves from default nodegroup
            4. Create cluster with Neutron GRE and custom nodegroups
            5. Activate plugin and configure plugins setings
            6. Remove 2nd custom nodegroup which is added automatically
            7. Bootstrap slave nodes from custom nodegroup
            8. Download network configuration
            9. Update network.json with customized ip ranges
            10. Put new json on master node and update network data
            11. Verify that new IP ranges are applied for network config
            12. Add following nodes to default nodegroup:
                * 3 controller+ceph
            13. Add following nodes to custom nodegroup:
                * 1 compute
                * 1 contrail-config+contrail-control+contrail-db
            14. Deploy cluster
            15.Run OSTF

Actual result
OSTF test 'Check network connectivity from instance via floating IP' failed on env with multiple node groups with error:

Time limit exceeded while waiting for VM connectivity checking to finish. Please refer to OpenStack logs for more details.

Tags: contrail
tags: added: contrail
Changed in fuel-plugin-contrail:
importance: Undecided → High
milestone: none → 4.0.0
assignee: nobody → Partner Centric Engineering (fuel-partner-engineering)
Illia Polliul (ipolliul)
Changed in fuel-plugin-contrail:
status: New → In Progress
Revision history for this message
Illia Polliul (ipolliul) wrote :

Problem was in missing configuration on vSRX router for this nodes layout.

Here are missing commands:
set protocols bgp group Contrail_Controller allow 10.109.5.0/24
set routing-options static route 10.109.5.0/24 next-hop 10.109.4.1
delete routing-options static route 10.109.4.0/24 next-table public.inet.0
set routing-options dynamic-tunnels dynamic_overlay_tunnels destination-networks 10.109.5.0/24

Also, there should be no nat between private networks in both node groups. GRE tunnels will not work over nat.

Changed in fuel-plugin-contrail:
status: In Progress → Invalid
Changed in fuel-plugin-contrail:
status: Invalid → Confirmed
milestone: 4.0.0 → 4.0.1
Revision history for this message
Olesia Tsvigun (otsvigun) wrote :

Reproduced at :
Fuel ISO#570
contrail-4.0-4.0.0-1-152.noarch.rpm

Steps to reproduce
1. Revert snapshot with ready master node
2. Install contrail plugin
3. Bootstrap slaves from default nodegroup
4. Create cluster with Neutron GRE and custom nodegroups
5. Activate plugin and configure plugins setings
6. Remove 2nd custom nodegroup which is added automatically
7. Bootstrap slave nodes from custom nodegroup
8. Download network configuration
9. Update network.json with customized ip ranges
10. Put new json on master node and update network data
11. Verify that new IP ranges are applied for network config
12. Add following nodes to default nodegroup:
* 3 controller+ceph
13. Add following nodes to custom nodegroup:
* 1 compute
* 1 contrail-config+contrail-control+contrail-db+
  contrail-analytics
14. Deploy cluster
15. Run network verification
16. Verify that excluded ip is not used for nodes or VIP
17. Run health checks (OSTF)

Actual Result
OSTF test 'Check network connectivity from instance via floating IP' failed on env with multiple node groups with error:

Time limit exceeded while waiting for VM connectivity checking to finish. Please refer to OpenStack logs for more details.

Revision history for this message
Olesia Tsvigun (otsvigun) wrote :
Changed in fuel-plugin-contrail:
assignee: Partner Centric Engineering (fuel-partner-engineering) → Olesia Tsvigun (otsvigun)
Changed in fuel-plugin-contrail:
status: Confirmed → In Progress
Revision history for this message
Olesia Tsvigun (otsvigun) wrote :

Cause of failure was VSRX configuration issue.

Changed in fuel-plugin-contrail:
status: In Progress → Invalid
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.