br-int: could not open network device

Bug #2060549 reported by macchese
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
charm-ovn-dedicated-chassis
Invalid
Undecided
Unassigned

Bug Description

Problem: after deploying a ovn-dedicated-chassis, cannot bind any vif to any openstack network

charm: ovn-dedicated-chassis
channel: 23.09/stable
Rev: 132
ubuntu: 22.04

1. deployed 3 ovn-central units
Unit Workload Agent Machine Public address Ports Message
ovn-central/10* active idle 7/lxd/35 192.168.70.127 6641-6642/tcp Unit is ready (leader: ovnnb_db, ovnsb_db northd: active)
ovn-central/11 active idle 8/lxd/35 192.168.70.128 6641-6642/tcp Unit is ready
ovn-central/12 active idle 3/lxd/37 192.168.70.129 6641-6642/tcp Unit is ready

2. deployed an ovn-dedicated-chassis (alias: ovn-chassis-gw)
App Version Status Scale Charm Channel Rev Exposed Message
ovn-chassis-gw 23.09.0 active 1 ovn-dedicated-chassis 23.09/stable 132 no Unit is ready

Unit Workload Agent Machine Public address Ports Message
ovn-chassis-gw/5* active idle 8 192.168.6.110 Unit is ready

Machine State Address Inst id Base AZ Message
8 started 192.168.6.110 op1 ubuntu@22.04 default Deployed

Integration provider Requirer Interface Type Message
ovn-central:ovsdb ovn-chassis-gw:ovsdb ovsdb regular
vault:certificates ovn-chassis-gw:certificates tls-certificates regular

3. on the chassis-gw node:
root@op1:/var/log/openvswitch# ovs-vsctl show
02e22c0c-e807-4bea-b9b8-216de8f3fa83
    Manager "ptcp:6640:127.0.0.1"
    Bridge br-provider
        fail_mode: standalone
        datapath_type: system
        Port br-provider
            Interface br-provider
                type: internal
        Port patch-provnet-0f6dc796-6023-45ab-af78-ab19fc8bde81-to-br-int
            Interface patch-provnet-0f6dc796-6023-45ab-af78-ab19fc8bde81-to-br-int
                type: patch
                options: {peer=patch-br-int-to-provnet-0f6dc796-6023-45ab-af78-ab19fc8bde81}
        Port bond0
            Interface bond0
                type: system
    Bridge br-int
        fail_mode: secure
        datapath_type: system
        Port patch-br-int-to-provnet-0f6dc796-6023-45ab-af78-ab19fc8bde81
            Interface patch-br-int-to-provnet-0f6dc796-6023-45ab-af78-ab19fc8bde81
                type: patch
                options: {peer=patch-provnet-0f6dc796-6023-45ab-af78-ab19fc8bde81-to-br-int}
        Port tapfa291087-30
            Interface tapfa291087-30
                error: "could not open network device tapfa291087-30 (No such device)"
        Port br-int
            Interface br-int
                type: internal
        Port tap47621598-0b
            Interface tap47621598-0b
                error: "could not open network device tap47621598-0b (No such device)"
    ovs_version: "3.2.1"

of course if I deploy a nova-compute unit on this node, no interface manages to bind to any network I could set-up

Revision history for this message
macchese (max-liccardo) wrote :

from ovs-vswitchd.log on the chassis-gw node:

dpif|WARN|system@ovs-system: failed to query port patch-br-int-to-provnet-0f6dc796-6023-45ab-af78-ab19fc8bde81: Invalid argument

macchese (max-liccardo)
description: updated
description: updated
Revision history for this message
macchese (max-liccardo) wrote :

I resolved removing the interfaces with status :error and switching to nova-compute + ovn-chassis

Changed in charm-ovn-dedicated-chassis:
status: New → 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.