[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied

[Dimitri John Ledkov]

** Also affects: s390-tools (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to s390-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1892367

Title:
  [UBUNTU 20.04] udev rule change did not get applied

Status in subiquity:
  Invalid
Status in Ubuntu on IBM z Systems:
  Incomplete
Status in s390-tools package in Ubuntu:
  New

Bug description:
  During the ubuntu installation in tessia, we do chzdev for both dasd
  and qeth devices, as below.

  2020-08-20 09:54:45 | INFO | START subiquity/Early/run/command_1 : chzdev -e dasd 385c
  2020-08-20 09:54:45 | INFO | SUCCESS subiquity/Early/run/command_1 : chzdev -e dasd 385c
  2020-08-20 09:54:45 | INFO | START subiquity/Early/run/command_2 : chzdev -e qeth 0.0.bdf0
  2020-08-20 09:54:47 | INFO | SUCCESS subiquity/Early/run/command_2 : chzdev -e qeth 0.0.bdf0

  and we can see the below files in the /etc/udev/rules.d/
  oot at m8360024:~# ls -l /etc/udev/rules.d/
  total 76
  -rw-r--r-- 1 root root   154 Aug 20 09:08 41-cio-ignore.rules
  -rw-r--r-- 1 root root   430 Aug 20 09:08 41-dasd-eckd-0.0.385c.rules
  -rw-r--r-- 1 root root   357 Aug 20 09:08 41-generic-ccw-0.0.0009.rules
  -rw-r--r-- 1 root root  1049 Aug 20 09:08 41-qeth-0.0.bdf0.rules
  -rw-r--r-- 1 root root 58549 Aug 20 09:10 70-snap.snapd.rules

  Now, lsinitramfs shows files as below,

  root at m8360024:~# lsinitramfs /boot/initrd.img-5.4.0-42-generic | grep 41
  etc/udev/rules.d/41-cio-ignore-root.rules
  etc/udev/rules.d/41-dasd-eckd-0.0.385c.rules
  usr/lib/udev/rules.d/41-cio-ignore.rules
  usr/lib/udev/rules.d/41-dasd-eckd-0.0.385c.rules
  usr/lib/udev/rules.d/41-generic-ccw-0.0.0009.rules
  usr/lib/udev/rules.d/41-qeth-0.0.bdf0.rules

  Even though lsinitramfs shows the below files, they are overruled by
  the filesystem files.

  Next thing we did was to modify the 41-qeth-0.0.bdf0.rules and
  modified the buffer_count to 128 (As in the attached file). In ideal
  scenario, the value should we modified as mentioned in the bug. But,
  in our case, if we are not doing a zipl or update-initramfs -u, the
  value is not getting modified.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions