error when setting up WiFi interface on Raspberry Pi 5 / Bookworm 7.0.4-2 (Sandworm)

This may be another eth0/end0 related problem but I'm getting errors when trying to set up a WiFi interface on a 'fresh' OMV7 installation on a RPi5 running Bookworm. Everything else is working very well and I'm now up to version 7.0.4-2 (Sandworm).

Have I done something stupid or is this a bug?

The full notification text shows the following in the one failed step:

----------

ID: configure_netplan_ethernet_eth0

Function: file.managed

Name: /etc/netplan/20-openmediavault-eth0.yaml

Result: False

Comment: Unable to manage file: Jinja error: [Errno 2] No such file or directory: '/sys/class/net/eth0/addr_assign_type'

Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/salt/utils/templates.py", line 477, in render_jinja_tmpl

output = template.render(**decoded_context)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 1301, in render

self.environment.handle_exception()

File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 936, in handle_exception

raise rewrite_traceback_stack(source=source)

File "<template>", line 6, in top-level template code

File "/usr/lib/python3/dist-packages/jinja2/sandbox.py", line 396, in call

return __context.call(__obj, *args, **kwargs)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/lib/python3/dist-packages/salt/loader/lazy.py", line 149, in __call__

return self.loader.run(run_func, *args, **kwargs)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/lib/python3/dist-packages/salt/loader/lazy.py", line 1234, in run

return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/lib/python3/dist-packages/salt/loader/lazy.py", line 1249, in _run_as

return _func_or_method(*args, **kwargs)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/lib/python3/dist-packages/salt/modules/file.py", line 3973, in read

with salt.utils.files.fopen(path, access_mode) as file_obj:

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/lib/python3/dist-packages/salt/utils/files.py", line 393, in fopen

f_handle = open(*args, **kwargs) # pylint: disable=resource-leakage

^^^^^^^^^^^^^^^^^^^^^

FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/net/eth0/addr_assign_type'

; line 6

---

{%- set dns_config = salt['omv_conf.get']('conf.system.network.dns') -%}

network:

ethernets:

{{ interface.devicename }}:

match:

{%- if salt['file.read']('/sys/class/net/' + interface.devicename + '/addr_assign_type') | int == 0 %} <======================

macaddress: {{ salt['grains.get']('hwaddr_interfaces:' + interface.devicename) }}

{%- else %}

name: {{ interface.devicename }}

{%- endif %}

{%- if interface.altmacaddress | length > 0 %}

[...]

---

Started: 10:00:26.447463

Duration: 129.332 ms

Changes:

----------

I'm not sure why it is trying to do something with eth0 for wifi when wlan0 does exist - but the missing file errors are because /sys/class/net/ has only 'redirects' to end0, lo and wlan0

oh? Obviously my misunderstanding. The Pi is using a hard-wired ethernet interface as its main connection - which I want to persist. But I also wanted to set up a WiFi connection in addition, effectively as a back-up since the Pi will use the eth0 (end0) connection if it is 'live' but if it goes down for some reason (damaged connector, intermediate switch failure, or whatever) then the Pi would automatically start using any established wifi link.

Can that not be done with the omv setup? Why does the wifi set up routine try to update eth0 instead of wlan0?

Oh - sorry my further misunderstanding - because when I looked more carefully I had both an existing end0 and an eth0 interface - so I simply deleted the eth0 - just as you suggested! and the wifi came up - thanks!!