Bug 1379483 - Dissapeared tap devices and mac addresses never learned in mac address table
Summary: Dissapeared tap devices and mac addresses never learned in mac address table
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Eoghan Glynn
QA Contact: Prasanth Anbalagan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-26 23:36 UTC by Shinobu KINJO
Modified: 2020-12-21 19:35 UTC (History)
21 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-05 21:36:52 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Comment 2 Miguel Angel Ajo 2016-09-27 12:22:01 UTC 
It seems like NetworkManager is fiddling with the tap device, while it should not be doing that.

Is NetworkManager up to date?

 
$ grep tap7afc5502-58 compute-l0* -R

compute-l01_message.tar.gz/messages:Sep 14 18:11:00 compute-l01 NetworkManager[1412]: <info>  (tap7afc5502-58): new Tun device (carrier: OFF, driver: 'tun', ifindex: 222)
compute-l01_message.tar.gz/messages:Sep 14 18:11:00 compute-l01 NetworkManager[1412]: <info>  (qbr7afc5502-58): bridge port tap7afc5502-58 was attached
compute-l01_message.tar.gz/messages:Sep 14 18:11:00 compute-l01 NetworkManager[1412]: <info>  (tap7afc5502-58): enslaved to qbr7afc5502-58
compute-l01_message.tar.gz/messages:Sep 14 18:11:00 compute-l01 kernel: device tap7afc5502-58 entered promiscuous mode
compute-l01_message.tar.gz/messages:Sep 14 18:11:00 compute-l01 kernel: qbr7afc5502-58: port 2(tap7afc5502-58) entered forwarding state
compute-l01_message.tar.gz/messages:Sep 14 18:11:00 compute-l01 kernel: qbr7afc5502-58: port 2(tap7afc5502-58) entered forwarding state
compute-l01_message.tar.gz/messages:Sep 14 18:11:00 compute-l01 NetworkManager[1412]: <info>  (tap7afc5502-58): link connected
compute-l01_message.tar.gz/messages:Sep 14 18:11:00 compute-l01 NetworkManager[1412]: <info>  keyfile: add connection in-memory (e80e58b3-c993-4ced-a316-f47ff9bde30b,"tap7afc5502-58")
compute-l01_message.tar.gz/messages:Sep 14 18:11:00 compute-l01 NetworkManager[1412]: <info>  (tap7afc5502-58): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]
compute-l01_message.tar.gz/messages:Sep 14 18:11:00 compute-l01 NetworkManager[1412]: <info>  (tap7afc5502-58): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41]
compute-l01_message.tar.gz/messages:Sep 14 18:11:00 compute-l01 NetworkManager[1412]: <info>  (tap7afc5502-58): Activation: starting connection 'tap7afc5502-58' (e80e58b3-c993-4ced-a316-f47ff9bde30b)
compute-l01_message.tar.gz/messages:Sep 14 18:11:00 compute-l01 NetworkManager[1412]: <info>  (tap7afc5502-58): device state change: disconnected -> prepare (reason 'none') [30 40 0]
compute-l01_message.tar.gz/messages:Sep 14 18:11:00 compute-l01 NetworkManager[1412]: <info>  (tap7afc5502-58): device state change: prepare -> config (reason 'none') [40 50 0]
compute-l01_message.tar.gz/messages:Sep 14 18:11:00 compute-l01 NetworkManager[1412]: <info>  (tap7afc5502-58): device state change: config -> ip-config (reason 'none') [50 70 0]
compute-l01_message.tar.gz/messages:Sep 14 18:11:00 compute-l01 NetworkManager[1412]: <info>  (tap7afc5502-58): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
compute-l01_message.tar.gz/messages:Sep 14 18:11:00 compute-l01 NetworkManager[1412]: <info>  (tap7afc5502-58): device state change: secondaries -> activated (reason 'none') [90 100 0]
compute-l01_message.tar.gz/messages:Sep 14 18:11:00 compute-l01 NetworkManager[1412]: <info>  (tap7afc5502-58): Activation: successful, device activated.
compute-l01_message.tar.gz/messages:Sep 14 18:11:00 compute-l01 nm-dispatcher: Dispatching action 'up' for tap7afc5502-58
compute-l01_message.tar.gz/messages:Sep 14 18:11:04 compute-l01 ntpd[1316]: Listen normally on 182 tap7afc5502-58 fe80::fc16:3eff:fe69:269f UDP 123
Comment 5 Thomas Haller 2016-09-27 14:25:24 UTC 
(In reply to Miguel Angel Ajo from comment #2)
> It seems like NetworkManager is fiddling with the tap device, while it
> should not be doing that.

from the logfile it is not clear that NetworkManager actually touches the device. It certainly should not interfere, but the logging messages alone don't indicate that NetworkManager interferes.

If the problem is reproducible, please enable debug-logging of NetworkManager and provide the full logfile.

You do that, by configuring

  [logging]
  level=TRACE

in /etc/NetworkManager/NetworkManager.conf, followed by `systemctl restart NetworkManager`.
Note You need to log in before you can comment on or make changes to this bug.