During provisioning we create scripts for NetworkManager to run, but we don't restart NetworkManager.service after such scripts are put in place. For this reason those scripts are not executed when a network interface is configured via DHCP.
Host Environment
Host operating system and version: Ubuntu 16.04
Vagrant version: 2.0.1
Hypervisor version: Virtualbox 5.1.30
Output
Dec 01 14:48:50 localhost.localdomain nm-dispatcher[2278]: Received event: up, interface: enp0s8
Dec 01 14:48:50 localhost.localdomain root[2635]: NetworkManager Script up triggered
Dec 01 14:48:50 localhost.localdomain nm-dispatcher[2278]: <13>Dec 1 14:48:50 root: NetworkManager Script up triggered
Dec 01 14:48:50 localhost.localdomain nm-dispatcher[2278]: Removing default routes from enp0s8 interface
Dec 01 14:48:50 localhost.localdomain nm-dispatcher[2278]: Removing default via 10.0.2.2 dev enp0s3 proto static metric 100
Dec 01 14:48:50 localhost.localdomain nm-dispatcher[2278]: default via 10.10.0.1 dev enp0s8 proto static metric 101
Dec 01 14:48:50 prelude-manager-oss nm-dispatcher[2278]: req:13 'hostname': new request (6 scripts)
Dec 01 14:48:50 prelude-manager-oss nm-dispatcher[2278]: Removing default via 10.10.0.1 dev enp0s8 proto static metric 101
Dec 01 14:48:50 localhost.localdomain nm-dispatcher[2278]: req:14 'connectivity-change': new request (6 scripts)
Dec 01 14:48:50 localhost.localdomain nm-dispatcher[2278]: req:15 'hostname': new request (6 scripts)
Dec 01 14:48:50 localhost.localdomain nm-dispatcher[2278]: Configuring the default route for enp0s8 interface via 10.10.0.1 gateway
Dec 01 14:48:50 prelude-manager-oss nm-dispatcher[2278]: req:16 'connectivity-change': new request (6 scripts)
Dec 01 14:48:50 localhost.localdomain nm-dispatcher[2278]: req:17 'connectivity-change': new request (6 scripts)
Dec 01 14:48:50 localhost.localdomain nm-dispatcher[2278]: req:18 'hostname': new request (6 scripts)
Dec 01 14:48:50 localhost.localdomain nm-dispatcher[2278]: req:19 'hostname': new request (6 scripts)
Steps to Reproduce
vagrant up gateway
vagrant up kafka
vagrant ssh kafka
sudo journalctl -u NetworkManager-dispatcher
Expected behavior: see evidence of dispatcher.d scripts running
Prerequisites
Description
During provisioning we create scripts for NetworkManager to run, but we don't restart NetworkManager.service after such scripts are put in place. For this reason those scripts are not executed when a network interface is configured via DHCP.
Host Environment
Output
Steps to Reproduce
vagrant up gateway
vagrant up kafka
vagrant ssh kafka
sudo journalctl -u NetworkManager-dispatcher
Expected behavior: see evidence of
dispatcher.d
scripts runningActual behavior: scripts are not executed
Reproduces how often: always
Additional Information
N/A
References
N/A