Revision history [back]

click to hide/show revision 1
initial version

Fail scheduling network (Grizzly, Quantum, gre)

Hi everyone,

I am getting this warning (which seems more like an error) when trying to launch instances:

/var/log/quantum/server.log:2013-06-24 09:34:03  WARNING [quantum.db.agentschedulers_db] Fail scheduling network {'status': u'ACTIVE', 'subnets': [u'19f681a4-99b0-4e45-85eb-6d08aa77cedb'], 'name': u'demo-net', 'provider:physical_network': None, 'admin_state_up': True, 'tenant_id': u'c9ec52b4506b4d789180af84b78da5b1', 'provider:network_type': u'gre', 'router:external': False, 'shared': False, 'id': u'7a753d4b-b4dc-423a-98c2-79a1cbeb3d15', 'provider:segmentation_id': 2L}

The instance launches (on a different node) and seems to work correctly. I have gone over my quantum configuration on both nodes and all the IP's and hostnames seem to have been set correctly (I can post configs if handy).

Here is my setup: I have three "all-in-one nodes" (test1,test2,test3) that each run all of the services (except l3-agent... that only runs on one node at a time). The APIs, novnc-proxy, and mysql (actually Percona/Galera Cluster) are load balanced with haproxy. All services have their APIs bound to the internal IP. haproxy is bound to a VIP that can move around with pacemaker.

In the example above a request comes into haproxy on test2. quantum-server spits out the warning above on test2, test1 launches the instance and seems to work fine (without any warnings or errors). Oddly, test3 never seems to even try to launch any instances. Here is a list of my nova services and quantum agents:

root@test1:~# quantum agent-list
+--------------------------------------+--------------------+-------+-------+----------------+
| id                                   | agent_type         | host  | alive | admin_state_up |
+--------------------------------------+--------------------+-------+-------+----------------+
| 0dfc68a8-7321-4d6c-a266-a4ffef5f9a33 | DHCP agent         | test3 | :-)   | True           |
| 2ca7d965-c292-48a3-805c-11afebf18e20 | DHCP agent         | test1 | :-)   | True           |
| 2f2c3259-4f63-4e7e-9552-fbc2ed69281e | L3 agent           | test2 | :-)   | True           |
| 5a76fbee-47d0-4dc1-af50-24dfb6113400 | Open vSwitch agent | test1 | :-)   | True           |
| 7c6c4058-c9c2-4774-8924-ab6ba54266b3 | DHCP agent         | test2 | :-)   | True           |
| 7d01c7b2-1102-4249-85a0-7afcd9421884 | Open vSwitch agent | test2 | :-)   | True           |
| bde82424-b5ff-41b7-9d7e-35bf805cfae8 | Open vSwitch agent | test3 | :-)   | True           |
| dcb122ab-8c17-4f60-9b3a-41abfdf036c3 | L3 agent           | test1 | xxx   | True           |
+--------------------------------------+--------------------+-------+-------+----------------+


root@test1:~# nova-manage service list                                                                                                                                                        
Binary           Host                                 Zone             Status     State Updated_At
nova-cert        test1                                internal         enabled    :-)   2013-06-24 14:26:11
nova-conductor   test1                                internal         enabled    :-)   2013-06-24 14:26:12
nova-consoleauth test1                                internal         enabled    :-)   2013-06-24 14:26:07
nova-scheduler   test1                                internal         enabled    :-)   2013-06-24 14:26:11
nova-compute     test1                                nova             enabled    :-)   2013-06-24 14:26:08
nova-cert        test2                                internal         enabled    :-)   2013-06-24 14:26:06
nova-conductor   test2                                internal         enabled    :-)   2013-06-24 14:26:11
nova-consoleauth test2                                internal         enabled    :-)   2013-06-24 14:26:12
nova-scheduler   test2                                internal         enabled    :-)   2013-06-24 14:26:12
nova-compute     test2                                nova             enabled    :-)   2013-06-24 14:26:07
nova-cert        test3                                internal         enabled    :-)   2013-06-24 14:26:11
nova-consoleauth test3                                internal         enabled    :-)   2013-06-24 14:26:14
nova-scheduler   test3                                internal         enabled    :-)   2013-06-24 14:26:11
nova-conductor   test3                                internal         enabled    :-)   2013-06-24 14:26:12
nova-compute     test3                                nova             enabled    :-)   2013-06-24 14:26:08

Any ideas what might be happening? Again, I can post additional logs, configs, etc. Whatever might help me get past this problem.

Thanks, Sam

click to hide/show revision 2
Added more information

Fail scheduling network (Grizzly, Quantum, gre)

Hi everyone,

I am getting this warning (which seems more like an error) when trying to launch instances:

/var/log/quantum/server.log:2013-06-24 09:34:03  WARNING [quantum.db.agentschedulers_db] Fail scheduling network {'status': u'ACTIVE', 'subnets': [u'19f681a4-99b0-4e45-85eb-6d08aa77cedb'], 'name': u'demo-net', 'provider:physical_network': None, 'admin_state_up': True, 'tenant_id': u'c9ec52b4506b4d789180af84b78da5b1', 'provider:network_type': u'gre', 'router:external': False, 'shared': False, 'id': u'7a753d4b-b4dc-423a-98c2-79a1cbeb3d15', 'provider:segmentation_id': 2L}

The instance launches (on a different node) and seems to work correctly. I have gone over my quantum configuration on both nodes and all the IP's and hostnames seem to have been set correctly (I can post configs if handy).

Here is my setup: I have three "all-in-one nodes" (test1,test2,test3) that each run all of the services (except l3-agent... that only runs on one node at a time). The APIs, novnc-proxy, and mysql (actually Percona/Galera Cluster) are load balanced with haproxy. All services have their APIs bound to the internal IP. haproxy is bound to a VIP that can move around with pacemaker.

In the example above a request comes into haproxy on test2. quantum-server spits out the warning above on test2, test1 launches the instance and seems to work fine (without any warnings or errors). Oddly, test3 never seems to even try to launch any instances. Here is a list of my nova services and quantum agents:

root@test1:~# quantum agent-list
+--------------------------------------+--------------------+-------+-------+----------------+
| id                                   | agent_type         | host  | alive | admin_state_up |
+--------------------------------------+--------------------+-------+-------+----------------+
| 0dfc68a8-7321-4d6c-a266-a4ffef5f9a33 | DHCP agent         | test3 | :-)   | True           |
| 2ca7d965-c292-48a3-805c-11afebf18e20 | DHCP agent         | test1 | :-)   | True           |
| 2f2c3259-4f63-4e7e-9552-fbc2ed69281e | L3 agent           | test2 | :-)   | True           |
| 5a76fbee-47d0-4dc1-af50-24dfb6113400 | Open vSwitch agent | test1 | :-)   | True           |
| 7c6c4058-c9c2-4774-8924-ab6ba54266b3 | DHCP agent         | test2 | :-)   | True           |
| 7d01c7b2-1102-4249-85a0-7afcd9421884 | Open vSwitch agent | test2 | :-)   | True           |
| bde82424-b5ff-41b7-9d7e-35bf805cfae8 | Open vSwitch agent | test3 | :-)   | True           |
| dcb122ab-8c17-4f60-9b3a-41abfdf036c3 | L3 agent           | test1 | xxx   | True           |
+--------------------------------------+--------------------+-------+-------+----------------+


root@test1:~# nova-manage service list                                                                                                                                                        
Binary           Host                                 Zone             Status     State Updated_At
nova-cert        test1                                internal         enabled    :-)   2013-06-24 14:26:11
nova-conductor   test1                                internal         enabled    :-)   2013-06-24 14:26:12
nova-consoleauth test1                                internal         enabled    :-)   2013-06-24 14:26:07
nova-scheduler   test1                                internal         enabled    :-)   2013-06-24 14:26:11
nova-compute     test1                                nova             enabled    :-)   2013-06-24 14:26:08
nova-cert        test2                                internal         enabled    :-)   2013-06-24 14:26:06
nova-conductor   test2                                internal         enabled    :-)   2013-06-24 14:26:11
nova-consoleauth test2                                internal         enabled    :-)   2013-06-24 14:26:12
nova-scheduler   test2                                internal         enabled    :-)   2013-06-24 14:26:12
nova-compute     test2                                nova             enabled    :-)   2013-06-24 14:26:07
nova-cert        test3                                internal         enabled    :-)   2013-06-24 14:26:11
nova-consoleauth test3                                internal         enabled    :-)   2013-06-24 14:26:14
nova-scheduler   test3                                internal         enabled    :-)   2013-06-24 14:26:11
nova-conductor   test3                                internal         enabled    :-)   2013-06-24 14:26:12
nova-compute     test3                                nova             enabled    :-)   2013-06-24 14:26:08

Any ideas what might be happening? Again, I can post additional logs, configs, etc. Whatever might help me get past this problem.

Thanks, Sam

----------------- edit -----------------

So I stopped all the services, dropped the databases, recreated them, made sure all my services were logging (openswitch didn't seem to be logging the first time), wiped out all rabbitmq queues and exchanges, rebooted all nodes... I still get the problem.

I noticed the first VM launches on test1 and does not emit the "Fail scheduling network" warning. All subsequent launches do.

I also noticed that when I launched the first vm openvswitch spit out (and continues to spit out) a lot of warnings (well formatted: http://pastie.org/pastes/8083390/text)

Anyone have any ideas of what to try? I am dead in the water.

Jun 26 14:35:58|00070|bridge|INFO|created port tap0f95314d-88 on bridge br-int
Jun 26 14:35:58|00071|netdev_linux|WARN|/sys/class/net/tap0f95314d-88/carrier: open failed: No such file or directory
Jun 26 14:35:58|00072|bridge|WARN|bridge br-tun: using default bridge Ethernet address ce:3c:35:27:c4:44
Jun 26 14:35:58|00073|bridge|WARN|bridge br-int: using default bridge Ethernet address 2e:9c:3e:0b:0b:45
Jun 26 14:35:59|00074|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:35:59|00075|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:35:59|00076|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:35:59|00077|netdev_linux|WARN|ethtool command ETHTOOL_GSET on network device tap0f95314d-88 failed: No such device
Jun 26 14:35:59|00078|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on tap0f95314d-88 device failed: No such device
Jun 26 14:35:59|00079|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:35:59|00080|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:35:59|00081|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:35:59|00082|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:35:59|00083|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:00|00084|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:00|00085|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:00|00086|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:00|00087|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:00|00088|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:00|00089|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:01|00090|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:01|00091|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:01|00092|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:01|00093|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:01|00094|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:01|00095|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:02|00096|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:02|00097|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:02|00098|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:02|00099|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:02|00100|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:02|00101|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:02|00102|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:02|00103|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:02|00104|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:02|00105|bridge|WARN|bridge br-tun: using default bridge Ethernet address ce:3c:35:27:c4:44
Jun 26 14:36:02|00106|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on tap0f95314d-88 device failed: No such device
Jun 26 14:36:02|00107|bridge|WARN|bridge br-int: using default bridge Ethernet address 2e:9c:3e:0b:0b:45
Jun 26 14:36:02|00108|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:36:02|00109|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:36:02|00110|netdev_linux|WARN|tap0f95314d-88: linux-sys get stats failed 19
Jun 26 14:36:02|00111|netdev_linux|WARN|ethtool command ETHTOOL_GDRVINFO on network device tap0f95314d-88 failed: No such device
Jun 26 14:36:02|00112|netdev_linux|WARN|ethtool command ETHTOOL_GSET on network device tap0f95314d-88 failed: No such device
Jun 26 14:36:06|00113|bridge|INFO|created port qvoe8ad2c1f-04 on bridge br-int
Jun 26 14:36:06|00114|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:36:06|00115|netdev_linux|WARN|tap0f95314d-88: linux-sys get stats failed 19
Jun 26 14:36:06|00116|netdev_linux|WARN|ethtool command ETHTOOL_GDRVINFO on network device tap0f95314d-88 failed: No such device
Jun 26 14:36:06|00117|netdev_linux|WARN|ethtool command ETHTOOL_GSET on network device tap0f95314d-88 failed: No such device
Jun 26 14:36:06|00118|bridge|WARN|bridge br-tun: using default bridge Ethernet address ce:3c:35:27:c4:44
Jun 26 14:36:06|00119|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on tap0f95314d-88 device failed: No such device
Jun 26 14:36:06|00120|bridge|WARN|bridge br-int: using default bridge Ethernet address 2e:9c:3e:0b:0b:45
Jun 26 14:36:06|00121|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:36:07|00122|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:36:07|00123|netdev_linux|WARN|tap0f95314d-88: linux-sys get stats failed 19
Jun 26 14:36:07|00124|netdev_linux|WARN|ethtool command ETHTOOL_GDRVINFO on network device tap0f95314d-88 failed: No such device
Jun 26 14:36:07|00125|netdev_linux|WARN|ethtool command ETHTOOL_GSET on network device tap0f95314d-88 failed: No such device
Jun 26 14:36:09|00126|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:36:09|00127|netdev_linux|WARN|tap0f95314d-88: linux-sys get stats failed 19
Jun 26 14:36:09|00128|netdev_linux|WARN|ethtool command ETHTOOL_GDRVINFO on network device tap0f95314d-88 failed: No such device
Jun 26 14:36:09|00129|netdev_linux|WARN|ethtool command ETHTOOL_GSET on network device tap0f95314d-88 failed: No such device
Jun 26 14:36:09|00130|bridge|WARN|bridge br-tun: using default bridge Ethernet address ce:3c:35:27:c4:44
Jun 26 14:36:09|00131|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on tap0f95314d-88 device failed: No such device
Jun 26 14:36:09|00132|bridge|WARN|bridge br-int: using default bridge Ethernet address 2e:9c:3e:0b:0b:45
Jun 26 14:36:09|00133|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:36:12|00134|netdev|WARN|Dropped 134 log messages in last 11 seconds (most recently, 1 seconds ago) due to excessive rate
Jun 26 14:36:12|00135|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:12|00136|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:36:12|00137|netdev_linux|WARN|tap0f95314d-88: linux-sys get stats failed 19
Jun 26 14:36:12|00138|netdev_linux|WARN|ethtool command ETHTOOL_GDRVINFO on network device tap0f95314d-88 failed: No such device
Jun 26 14:36:12|00139|netdev_linux|WARN|ethtool command ETHTOOL_GSET on network device tap0f95314d-88 failed: No such device
Jun 26 14:36:17|00140|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:36:17|00141|netdev_linux|WARN|tap0f95314d-88: linux-sys get stats failed 19
Jun 26 14:36:17|00142|netdev_linux|WARN|ethtool command ETHTOOL_GDRVINFO on network device tap0f95314d-88 failed: No such device
Jun 26 14:36:17|00143|netdev_linux|WARN|ethtool command ETHTOOL_GSET on network device tap0f95314d-88 failed: No such device
Jun 26 14:36:22|00144|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:36:24|00145|netdev|WARN|Dropped 121 log messages in last 12 seconds (most recently, 1 seconds ago) due to excessive rate
Jun 26 14:36:24|00146|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:32|00147|netdev_linux|WARN|Dropped 7 log messages in last 10 seconds (most recently, 5 seconds ago) due to excessive rate
Jun 26 14:36:32|00148|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:36:36|00149|netdev|WARN|Dropped 67 log messages in last 12 seconds (most recently, 1 seconds ago) due to excessive rate
Jun 26 14:36:36|00150|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:42|00151|netdev_linux|WARN|Dropped 7 log messages in last 10 seconds (most recently, 5 seconds ago) due to excessive rate
Jun 26 14:36:42|00152|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:36:48|00153|netdev|WARN|Dropped 69 log messages in last 12 seconds (most recently, 1 seconds ago) due to excessive rate
Jun 26 14:36:48|00154|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:36:57|00155|netdev_linux|WARN|Dropped 11 log messages in last 15 seconds (most recently, 5 seconds ago) due to excessive rate
Jun 26 14:36:57|00156|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:37:00|00157|netdev|WARN|Dropped 75 log messages in last 12 seconds (most recently, 1 seconds ago) due to excessive rate
Jun 26 14:37:00|00158|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:37:07|00159|netdev_linux|WARN|Dropped 7 log messages in last 10 seconds (most recently, 5 seconds ago) due to excessive rate
Jun 26 14:37:07|00160|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:37:12|00161|netdev|WARN|Dropped 83 log messages in last 12 seconds (most recently, 1 seconds ago) due to excessive rate
Jun 26 14:37:12|00162|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:37:22|00163|netdev_linux|WARN|Dropped 11 log messages in last 15 seconds (most recently, 5 seconds ago) due to excessive rate
Jun 26 14:37:22|00164|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:37:24|00165|netdev|WARN|Dropped 109 log messages in last 12 seconds (most recently, 1 seconds ago) due to excessive rate
Jun 26 14:37:24|00166|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:37:32|00167|netdev_linux|WARN|Dropped 7 log messages in last 10 seconds (most recently, 5 seconds ago) due to excessive rate
Jun 26 14:37:32|00168|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:37:36|00169|netdev|WARN|Dropped 77 log messages in last 12 seconds (most recently, 1 seconds ago) due to excessive rate
Jun 26 14:37:36|00170|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:37:42|00171|netdev_linux|WARN|Dropped 7 log messages in last 10 seconds (most recently, 5 seconds ago) due to excessive rate
Jun 26 14:37:42|00172|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:37:48|00173|netdev|WARN|Dropped 81 log messages in last 12 seconds (most recently, 1 seconds ago) due to excessive rate
Jun 26 14:37:48|00174|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:37:57|00175|netdev_linux|WARN|Dropped 11 log messages in last 15 seconds (most recently, 5 seconds ago) due to excessive rate
Jun 26 14:37:57|00176|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:38:00|00177|netdev|WARN|Dropped 69 log messages in last 12 seconds (most recently, 1 seconds ago) due to excessive rate
Jun 26 14:38:00|00178|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:38:07|00179|netdev_linux|WARN|Dropped 7 log messages in last 10 seconds (most recently, 5 seconds ago) due to excessive rate
Jun 26 14:38:07|00180|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:38:12|00181|netdev|WARN|Dropped 67 log messages in last 12 seconds (most recently, 1 seconds ago) due to excessive rate
Jun 26 14:38:12|00182|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:38:22|00183|netdev_linux|WARN|Dropped 11 log messages in last 15 seconds (most recently, 5 seconds ago) due to excessive rate
Jun 26 14:38:22|00184|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:38:24|00185|netdev|WARN|Dropped 87 log messages in last 12 seconds (most recently, 1 seconds ago) due to excessive rate
Jun 26 14:38:24|00186|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:38:32|00187|netdev_linux|WARN|Dropped 7 log messages in last 10 seconds (most recently, 5 seconds ago) due to excessive rate
Jun 26 14:38:32|00188|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device
Jun 26 14:38:36|00189|netdev|WARN|Dropped 71 log messages in last 12 seconds (most recently, 1 seconds ago) due to excessive rate
Jun 26 14:38:36|00190|netdev|WARN|failed to get flags for network device tap0f95314d-88: No such device
Jun 26 14:38:42|00191|netdev_linux|WARN|Dropped 7 log messages in last 10 seconds (most recently, 5 seconds ago) due to excessive rate
Jun 26 14:38:42|00192|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap0f95314d-88 device failed: No such device