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

Launchpad Bug Tracker 1892367 at bugs.launchpad.net
Sat Feb 27 00:35:39 UTC 2021


This bug was fixed in the package s390-tools - 2.16.0-0ubuntu1

---------------
s390-tools (2.16.0-0ubuntu1) hirsute; urgency=medium

  * New upstream release. LP: #1914574
  * Drop patches applied upstream.
  * Compile with ZDEV_ALWAYS_UPDATE_INITRD=1 option. This fixes calls to
    chzdev to trigger update-initramfs -u. LP: #1892367
  * Set install path via make variables, instead of patching source
    Makefiles.
  * Update homepage to github.com.

s390-tools (2.15.1-1ubuntu3) hirsute; urgency=medium

  * No-change rebuild to drop the udeb package.

s390-tools (2.15.1-1ubuntu2) hirsute; urgency=medium

  * No change rebuild with fixed ownership.

s390-tools (2.15.1-1ubuntu1) hirsute; urgency=low

  * Update debian/watch for new ibm-s390-linux repo
  * Update debian/control for [XC-]Package-Type
  * Merge from Debian unstable. Remaining changes:
    - keep providing zkey
    - split some tools into individuall packages
    - Drop udevadm-path.patch
    - Drop ziomon package
    - Linux on z Systems naming
    - 0001-ziomon-Use-exit-code-0-for-version-and-help.patch
    - 0001-zkey-add-initramfs-hook.patch
    - 0001-zkey-on-Ubuntu-use-default-benchmarked-Argon2i-with-.patch
    - 0001-dumpconf-Don-t-run-the-service-in-LXC.patch
    - update-install-paths.patch
    - 0010-no-pie-is-not-a-valid-option-for-ld.patch
    - s390-tools-lp1903984-hirsute.patch

s390-tools (2.15.1-2) unstable; urgency=medium

  * Remove myself as a maintainer.

s390-tools (2.15.1-1) unstable; urgency=medium

  * New upstream release
    - Install new tool lsstp.
    - Continue to skip out on zkey for now.

 -- Dimitri John Ledkov <xnox at ubuntu.com>  Wed, 24 Feb 2021 05:49:54
+0000

** Changed in: s390-tools (Ubuntu Hirsute)
       Status: Fix Committed => Fix Released

-- 
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:
  In Progress
Status in s390-tools package in Ubuntu:
  Fix Released
Status in s390-tools source package in Focal:
  New
Status in s390-tools source package in Groovy:
  New
Status in s390-tools source package in Hirsute:
  Fix Released

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



More information about the foundations-bugs mailing list