Debian Bug report logs - #815819
sysconfig-hardware udev rule ignores INTERFACE_NAME property

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Raphael Philipe Mendes da Silva <raphasil@linux.vnet.ibm.com>

To: submit@bugs.debian.org

Subject: sysconfig-hardware udev rule ignores INTERFACE_NAME property

Date: Wed, 24 Feb 2016 14:50:58 -0300

Package: sysconfig-hardware
Version: 0.0.11
Severity: normal
X-Debbugs-CC: brueckner@linux.vnet.ibm.com,mihajlov@linux.vnet.ibm.com

I wanted to change the network interface name without using a custom
udev rule like 70-persistent-net.rules.
To do that, In Debian 8, I created a network interface hardware config
file (/etc/sysconfig/hardware/config-ccw-0.0.xxxx) with the following
content:

CCWGROUP_CHANS=(0.0.xxxx 0.0.xxxy 0.0.xxxz)
QETH_PORTNAME=OSAPORT
QETH_PORTNO=0
QETH_OPTIONS=(layer2)
INTERFACE_NAME=ethfoo

The interface is created and is up. However the name of the
interface remains enccw0.0.xxxx

I did a little debug and verified that the udev rule in the file  /lib/udev/rules.d/65-sysconfig-hardware-net.rules was wrong:
It had:
  SUBSYSTEM=="net", IMPORT{program}="/etc/sysconfig/scripts/hardware/udev-net $DEVPATH"
  SUBSYSTEM=="net", ENV{INTERFACE_NAME}=="?*", NAME="$env{INTERFACE_NAME}"
But the correct would be:
  SUBSYSTEM=="net", IMPORT{program}="/etc/sysconfig/scripts/hardware/udev-net $env{DEVPATH}"
  SUBSYSTEM=="net", ENV{INTERFACE_NAME}=="?*", NAME="$env{INTERFACE_NAME}"

I tested the correction locally, and it worked.

I'm sure this problem also affects 0.0.12, since I took a look at the code.
  

Message #10 received at submit@bugs.debian.org (full text, mbox, reply):

From: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>

To: Raphael Philipe Mendes da Silva <raphasil@linux.vnet.ibm.com>, 815819@bugs.debian.org

Cc: submit@bugs.debian.org

Subject: Re: Bug#815819: sysconfig-hardware udev rule ignores INTERFACE_NAME property

Date: Thu, 25 Feb 2016 09:00:50 +0100

On Wed, Feb 24, 2016 at 02:50:58PM -0300, Raphael Philipe Mendes da Silva wrote:
> Package: sysconfig-hardware
> Version: 0.0.11
> Severity: normal
> X-Debbugs-CC: brueckner@linux.vnet.ibm.com,mihajlov@linux.vnet.ibm.com
> 
> I wanted to change the network interface name without using a custom
> udev rule like 70-persistent-net.rules.
> To do that, In Debian 8, I created a network interface hardware config
> file (/etc/sysconfig/hardware/config-ccw-0.0.xxxx) with the following
> content:
> 
> CCWGROUP_CHANS=(0.0.xxxx 0.0.xxxy 0.0.xxxz)
> QETH_PORTNAME=OSAPORT
> QETH_PORTNO=0
> QETH_OPTIONS=(layer2)
> INTERFACE_NAME=ethfoo
> 
> The interface is created and is up. However the name of the
> interface remains enccw0.0.xxxx
> 

Have you tried to create systemd network link file to assign a different
name?  This should be then the long-term way how to rename interface
names.  But I agree to correct the behavior in sysconfig-hardware for
correctness.

Thanks and kind regards,
  Hendrik

Message #20 received at 815819@bugs.debian.org (full text, mbox, reply):

From: Raphael Philipe Mendes da Silva <raphasil@linux.vnet.ibm.com>

To: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>, 815819@bugs.debian.org

Subject: Re: Bug#815819: sysconfig-hardware udev rule ignores INTERFACE_NAME property

Date: Thu, 25 Feb 2016 13:32:27 -0300

> Have you tried to create systemd network link file to assign a different
> name?  This should be then the long-term way how to rename interface
> names.  But I agree to correct the behavior in sysconfig-hardware for
> correctness.
Yes, I'm aware of this method. I just wanted to report this bug in case
someone else touch it.
> 
> Thanks and kind regards,
>   Hendrik
> 

Message #25 received at 815819-close@bugs.debian.org (full text, mbox, reply):

From: Philipp Kern <pkern@debian.org>

To: 815819-close@bugs.debian.org

Subject: Bug#815819: fixed in sysconfig 0.0.13

Date: Sat, 27 Feb 2016 15:58:55 +0000

Source: sysconfig
Source-Version: 0.0.13

We believe that the bug you reported is fixed in the latest version of
sysconfig, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 815819@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Philipp Kern <pkern@debian.org> (supplier of updated sysconfig package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 27 Feb 2016 15:58:58 +0100
Source: sysconfig
Binary: sysconfig-hardware
Architecture: source s390x
Version: 0.0.13
Distribution: unstable
Urgency: medium
Maintainer: Debian S/390 Team <debian-s390@lists.debian.org>
Changed-By: Philipp Kern <pkern@debian.org>
Description:
 sysconfig-hardware - Hardware configuration
Closes: 815819
Changes:
 sysconfig (0.0.13) unstable; urgency=medium
 .
   [ Raphael Philipe Mendes da Silva ]
   * Fix INTERFACE_NAME to actually rename the network interface with
     current udev. (Closes: #815819)
Checksums-Sha1:
 39c018d1cdf60766778fed5ceb27cdcd96d7a81d 1155 sysconfig_0.0.13.dsc
 3c4e3ccba29f81946fe1e7b74b31b485015e4071 9762 sysconfig_0.0.13.tar.gz
 c2a2048f99636b94cec0ee47b353f29609353ea4 9064 sysconfig-hardware_0.0.13_s390x.deb
Checksums-Sha256:
 a4f12b579963b04fbfa3e3ce73572d7c2673738f4f219693692423fac3cd630c 1155 sysconfig_0.0.13.dsc
 c817cf17d5dbf5c631aab41fcd6b2b7a91b7af0b1da9334ad714815094c187e3 9762 sysconfig_0.0.13.tar.gz
 5f899a90baa642fc3b39ac021b0632d78a448ac87ec92a319d8c4b27933d9254 9064 sysconfig-hardware_0.0.13_s390x.deb
Files:
 2790098a7f14da071e5325c1d1c9a31e 1155 admin optional sysconfig_0.0.13.dsc
 5a2bae07d36b623e381f7eb60ecb00a9 9762 admin optional sysconfig_0.0.13.tar.gz
 45a66f04f2d23d80c96e7181616e8f46 9064 admin standard sysconfig-hardware_0.0.13_s390x.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCAAGBQJW0bqIAAoJEERuJUU10FbsNGEH/j0EUVl3IWkNhsyuw1okX83M
tcRmfcl7XkPA8dj5CVjFoUp6bTjME/yBG0Tnjblbl0GarfrWAi8obj9Nh+0YF0Qo
Zg1wKwHQDbQBN0LYaU3aZlYrQfdRGj/kdgPVwXTB6xNSWdtQKUDM3ZgnFzLJ37LZ
ZMnqjRqov8jV3BoCHrybI92BhDn+AVty+BOm2SPU/lIMfYTS84l8hGeYQnW9uDTA
o5nAHVxwW3qm60RXdVeBtt6M309G7IvhGp0jaoeqjILf0gEWVhcqJkAPbP1Ie518
cW4stJFwNQFuG7At33KF8o298ZiAmCJe+uKEEsu/vBYbX47s7jLxuOhh0YL+FX4=
=gQVb
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.