Ask Your Question
0

error: "could not add network device eno2 to ofproto (Device or resource busy)"

asked 2019-03-17 17:22:24 -0500

d@kj gravatar image

updated 2019-04-01 08:38:25 -0500

I've opened this https://ask.openstack.org/en/question/119783/no-route-to-instance-ssh-and-ping-no-route-to-host/ (post) to resolve the problem of the Ping and Ssh connection to my instance. During same checks I've seen this issue:

error: "could not add network device eno2 to ofproto (Device or resource busy)"

Maybe that is the cause of my first issue, but I don't understand how I can fix it and having a working lab.

Run the following command:

ubuntu@os-compute01:~$ sudo ovs-vsctl show
6f8542aa-45d7-409d-8787-8983f3c643eb
    Manager "ptcp:6640:127.0.0.1"
        is_connected: true
    Bridge br-ex
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port "eno2"
            Interface "eno2"
                error: "could not add network device eno2 to ofproto (Device or resource busy)"
        Port br-ex
            Interface br-ex
                type: internal
        Port phy-br-ex
            Interface phy-br-ex
                type: patch
                options: {peer=int-br-ex}
    Bridge br-tun
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port br-tun
            Interface br-tun
                type: internal
        Port "gre-0a145118"
            Interface "gre-0a145118"
                type: gre
                options: {df_default="true", in_key=flow, local_ip="10.20.81.21", out_key=flow, remote_ip="10.20.81.24"}
    Bridge br-int
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port br-int
            Interface br-int
                type: internal
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "tapb0b04b07-8f"
            tag: 2
            Interface "tapb0b04b07-8f"
        Port int-br-ex
            Interface int-br-ex
                type: patch
                options: {peer=phy-br-ex}
        Port "tap2354468c-88"
            tag: 4
            Interface "tap2354468c-88"
        Port "tap6d2b2fe0-47"
            tag: 4
            Interface "tap6d2b2fe0-47"
    ovs_version: "2.10.0"

juju status

$:juju status

Model      Controller             Cloud/Region  Version  SLA          Timestamp
openstack  maas-cloud-controller  maas-cloud    2.5.1    unsupported  22:10:17Z

App                    Version       Status  Scale  Charm                  Store       Rev  OS      Notes
ceph-mon               13.2.4+dfsg1  active      3  ceph-mon               jujucharms   31  ubuntu  
ceph-osd               13.2.4+dfsg1  active      3  ceph-osd               jujucharms  273  ubuntu  
ceph-radosgw           13.2.4+dfsg1  active      1  ceph-radosgw           jujucharms  262  ubuntu  
cinder                 13.0.2        active      1  cinder                 jujucharms  276  ubuntu  
cinder-ceph            13.0.2        active      1  cinder-ceph            jujucharms  238  ubuntu  
glance                 17.0.0        active      1  glance                 jujucharms  271  ubuntu  
keystone               14.0.1        active      1  keystone               jujucharms  288  ubuntu  
mysql                  5.7.20-29.24  active      1  percona-cluster        jujucharms  272  ubuntu  
neutron-api            13.0.2        active      1  neutron-api            jujucharms  266  ubuntu  
neutron-gateway        13.0.2        active      1  neutron-gateway        jujucharms  256  ubuntu  
neutron-openvswitch    13.0.2        active      3  neutron-openvswitch    jujucharms  255  ubuntu  
nova-cloud-controller  18.0.3        active      1  nova-cloud-controller  jujucharms  316  ubuntu  
nova-compute           18.0.3        active      3  nova-compute           jujucharms  290  ubuntu  
ntp                    3.2           active      4  ntp                    jujucharms   31  ubuntu  
openstack-dashboard    14.0.1        active      1  openstack-dashboard    jujucharms  271  ubuntu  
rabbitmq-server        3.6.10        active      1  rabbitmq-server        jujucharms   82  ubuntu  

Unit                      Workload  Agent  Machine  Public address  Ports                       Message
ceph-mon/0                active    idle   1/lxd/0  10.20.81.4                                  Unit is ready and clustered
ceph-mon/1                active    idle   2/lxd/0  10.20.81.8                                  Unit is ready and clustered
ceph-mon/2*               active    idle   3/lxd/0  10.20.81.5                                  Unit is ready and clustered
ceph-osd/0                active    idle   1        10 ...
(more)
edit retag flag offensive close merge delete

Comments

Is there any interface already attached to eno2 ?

Mohit gravatar imageMohit ( 2019-03-18 09:34:40 -0500 )edit

As showed above it seems to be a bridge interface, in the lab isn't present any device with the same IP addr. I'll try again to deploy that and I'll see if that is still present.

d@kj gravatar imaged@kj ( 2019-03-18 10:32:50 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2019-03-19 11:12:21 -0500

d@kj gravatar image

updated 2019-04-01 08:40:02 -0500

Update 22/03/19:

is it possible that the error on the eno2 is done of that?:

https://pasteboard.co/I6BRWHM.png (image)

both the interface, on compute node (BMC and Interface), use the same network... Any suggestions please. I am still unable to solve the problem. Thanks.

Update 26/03/19:

On Juju gui I've that:

neutron-gateway:
    bridge-mappings:         physnet1:br-ex
    data-port:               br-ex:eno2
neutron-api:
    flat-network-providers:  physnet1

Before to run the deploy via juju of Openstack I've changed data-port from br-ex:eno2 to br-ex:eno3

neutron-gateway:
    bridge-mappings:         physnet1:br-ex
    data-port:               br-ex:eno3
edit flag offensive delete link more

Comments

1

from error , it appears that there is some other resource using up eno2 , can you try to use any other ethernet interface apart from eno2 .... on juju config param ext-port

Mohit gravatar imageMohit ( 2019-03-23 10:12:27 -0500 )edit

@Mohit: I've upgraded the post with the results about that.

d@kj gravatar imaged@kj ( 2019-03-29 08:35:21 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2019-03-17 17:22:24 -0500

Seen: 87 times

Last updated: Apr 01