Package: grml-debootstrap
Version: 0.121

Hi,

If you use network bonding, the program crashes with:

+ for interface in /sys/class/net/*
+ udevadm info --query=all --path=/sys/class/net/bonding_masters
Unknown device "/sys/class/net/bonding_masters": No such device

Apparently this change in udevadm behavior was accommodated by:
https://github.com/grml/grml-debootstrap/commit/8172dda0de141297933721a25046cdce2bfced2f

> Skip udevadm execution on unsupported network interfaces like bonding_masters
> grml-debootstrap iterates over the present network devices by looking
> through /sys/class/net/, but file "bonding_masters" can't be queried:
> 
> | root@grml ~ # udevadm info --query=all --path=/sys/class/net/bonding_masters
> | Unknown device "/sys/class/net/bonding_masters": No such device
> 
> As a result, execution of grml-debootstrap fails when bonds are used.
> Instead, let's ensure that any network interface we want to operate on
> is actually based on (a symlink pointing to) a directory which we can
> query via udevadm.

Would it be possible to backport this fix, as the program became unusable
with bond setups?

TIA.

-- 
Josip Rodin

Reply via email to