br-int, br-ex and br-tup down. unable to access externa network.

Bug #1982698 reported by Vishwa Mithra Tatta Tatta
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
New
Undecided
Unassigned

Bug Description

What happend:
I am trying to deploy a working kolla ansible deployment. which is an all-in-one. Everything went fine, except that my public network (physnet1-flat-based) is unable to reach the internet. As I tried to diagnose the problem, the br-int, br-ex and br-tup are down in the main network namespace thereby rendering the networks useless in connecting to the underlying interfaces (which are again in the main rootspace). And also make the devices unavailable from the root network namespace.

What I expected to happen:
I expected the br-int, br-ex and br-tup to be turned on once the installation is successful and any public network I create through horizon/cli appear in the root network namespace so that the floating IPs are routable and have access to the external network.

Environment:

OS: ubuntu 20.04
Kernel: Linux ubuntu 5.4.0
Kolla-Ansible version - Stable/wallaby
docker image install-source (Using binary is causing it to stop at fluentd installation)

The VM on which this is deployed has 2 NICs, one bridged and the other behind NAT. The NIC which was bridged is given to external_network_interface while the NAT one is given to the network_interface.

Every port to every VM is however appearing as a network TAP in the main root space without an IP.

Please tell me how exactly is networking in kolla is supposed to work? I used both the init-runonce file and manual way to try. Thanks.

Revision history for this message
Vishwa Mithra Tatta Tatta (mnimi) wrote :
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.