-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CiaB 7.0.1: bootstrap fails on traefik #261
Comments
Is something wrong with the network (netplan) config? |
And |
And this somehow needs to be persisted, so the system survives a reboot. |
I wonder if this is a netplan bug. The settings in 01-osism.yaml look correct to me and according to the docs, I would have expected netplan to bring up these vlan ifaces. |
I could not find a way how to tell netplan to bring up the vlan links, so I injected a custom systemd unit into the boot process. This is certainly not the intended way to do things. dragon@manager:~$ cat /etc/rc.network
#!/bin/bash
if test "$1" = "start" -o "$1" = "restart"; then
ip link add link eno1np0 name vlan100 type vlan id 100
ip link add link eno1np0 name vlan101 type vlan id 101
netplan apply
fi
dragon@manager:~$ cat /etc/systemd/system/rc-network.service
# SPDX-License-Identifier: LGPL-2.1-or-later
# Injected to work around missing vlan links in netplan
# (c) Kurt Garloff <[email protected]>, 4/2024
[Unit]
Description=/etc/rc.network setup
Documentation=man:systemd-rc-local-generator(8)
ConditionFileIsExecutable=/etc/rc.network
After=network-pre.target
[Service]
Type=forking
ExecStart=/etc/rc.network start
TimeoutSec=0
RemainAfterExit=yes
GuessMainPID=no
[Install]
WantedBy=multi-user.target |
Please paste |
Looks correct to me ... # This file describes the network interfaces available on your system
# For more information, see netplan(5).
---
network:
version: 2
renderer: networkd
bonds:
{}
bridges:
{}
ethernets:
eno1np0:
dhcp4: true
tunnels:
{}
vlans:
vlan100:
addresses:
- 192.168.16.10/24
id: 100
link: eno1np0
vlan101:
id: 101
link: eno1np0
vrfs:
{} |
This was probably fixed with osism/ansible-collection-commons#637. |
The text was updated successfully, but these errors were encountered: