with netctl results in systemd timing gamble if it works or not
Task Info (Flyspray) | |
---|---|
Opened By | Oliver Dzombic (layer7gmbh) |
Task ID | 66451 |
Type | Bug Report |
Project | Community Packages |
Category | Packages |
Version | None |
OS | All |
Opened | 2020-04-28 16:08:29 UTC |
Status | Assigned |
Assignee | Sergej Pupykin (sergej) |
Assignee | Jouke Witteveen (jouke) |
Details
Description:
using netctl in combination with openvswitch -- following the archwiki howtos.
Lucky show ( even the stop of the services are not clean, at least the start is ):
-- Reboot -- Apr 28 17:24:01 systemd[1]: Starting ovsbr... Apr 28 17:24:01 network[756]: Starting network profile 'ovsbr'... Apr 28 17:24:02 ovs-vsctl[807]: ovs|00001|vsctl|INFO|Called as ovs-vsctl --may-exist add-port ovsbr enp3s0 Apr 28 17:24:04 systemd[1]: Started ovsbr. Apr 28 17:24:04 network[756]: Started network profile 'ovsbr'
Apr 28 17:53:35 systemd[1]: Stopping ovsbr... Apr 28 17:53:35 network[39544]: Stopping network profile 'ovsbr'... Apr 28 17:53:35 ovs-vsctl[39591]: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-br ovsbr Apr 28 17:53:35 ovs-vsctl[39591]: ovs|00002|db_ctl_base|ERR|unix:/run/openvswitch/db.sock: database connection failed (No such file or directory) Apr 28 17:53:35 network[39591]: ovs-vsctl: unix:/run/openvswitch/db.sock: database connection failed (No such file or directory) Apr 28 17:53:35 network[39544]: Failed to bring the network down for profile 'ovsbr' Apr 28 17:53:35 systemd[1]: netctl@ovsbr.service: Control process exited, code=exited, status=1/FAILURE Apr 28 17:53:35 systemd[1]: netctl@ovsbr.service: Failed with result 'exit-code'. Apr 28 17:53:35 systemd[1]: Stopped ovsbr.
Now machine comes up after the reboot, with a not so lucky shot:
-- Reboot -- Apr 28 17:56:17 systemd[1]: Starting ovsbr... Apr 28 17:56:17 network[720]: Starting network profile 'ovsbr'... Apr 28 17:56:18 ovs-vsctl[734]: ovs|00001|vsctl|INFO|Called as ovs-vsctl --may-exist add-port ovsbr enp3s0 Apr 28 17:56:18 network[720]: /usr/lib/netctl/interface: line 46: /sys/class/net/ovsbr/flags: No such file or directory Apr 28 17:56:23 network[841]: Error: Nexthop has invalid gateway. Apr 28 17:56:23 network[720]: Could not set gateway '192.168.178.1' on interface 'ovsbr' Apr 28 17:56:23 network[720]: Failed to bring the network up for profile 'ovsbr' Apr 28 17:56:23 systemd[1]: netctl@ovsbr.service: Main process exited, code=exited, status=1/FAILURE Apr 28 17:56:23 systemd[1]: netctl@ovsbr.service: Failed with result 'exit-code'. Apr 28 17:56:23 systemd[1]: Failed to start ovsbr.
The netctl config:
Description="ovsbr" Interface=ovsbr Connection=openvswitch BindsToInterfaces=(enp3s0) IP=static Address=('192.168.178.10/24') Gateway='192.168.178.1' DNS=('1.1.1.1 1.0.0.1') WaitOnline=yes
netctl version 1.21 ovs-vsctl (Open vSwitch) 2.13.0 DB Schema 8.2.0
To me, as it seems sometimes openvswitch manages to start up fast enough before netctl take action. And sometime not.
Netctl manages to configure the IP Address, but it does not manage to configure the gateway.