[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Changed in: s390-tools-signed (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: s390-tools-signed (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
This bug was fixed in the package s390-tools - 2.12.0-0ubuntu3.3 --- s390-tools (2.12.0-0ubuntu3.3) focal; urgency=medium * debian/patches/0001-zdev-Add-build-option-to-update-initial-RAM-disk-by-default.patch Compile with ZDEV_ALWAYS_UPDATE_INITRD=1 option. This fixes calls to chzdev to trigger update-initramfs -u. Thanks to Vineeth Vijayan (LP: #1892367) -- Frank Heimes Thu, 11 Mar 2021 18:13:30 +0100 ** Changed in: s390-tools (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
This bug was fixed in the package s390-tools - 2.14.0-1ubuntu1.2 --- s390-tools (2.14.0-1ubuntu1.2) groovy; urgency=medium * debian/patches/0001-zdev-Add-build-option-to-update-initial-RAM-disk-by-default.patch Compile with ZDEV_ALWAYS_UPDATE_INITRD=1 option. This fixes calls to chzdev to trigger update-initramfs -u. Thanks to Vineeth Vijayan (LP: #1892367) -- Frank Heimes Fri, 12 Mar 2021 10:21:37 +0100 ** Changed in: s390-tools (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
Thank you Vineeth for the verification (and sorry for the hick-up with the s390-tools-signed package) - I'm updating the tags accordingly ... ** Tags removed: verification-needed verification-needed-focal verification-needed-groovy ** Tags added: verification-done verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
So this is fixed now (thx to Brian). s390-tools | 2.12.0-0ubuntu3.3 | focal-proposed | s390x s390-tools-signed | 2.12.0-0ubuntu3.3 | focal-proposed | s390x respectively s390-tools | 2.14.0-1ubuntu1.2 | groovy-proposed | s390x s390-tools-signed | 2.14.0-1ubuntu1.2 | groovy-proposed | s390x After activating proposed: sudo add-apt-repository "deb http://us.ports.ubuntu.com/ubuntu-ports/ $(lsb_release -sc)-proposed main" sudo apt update s390-tools installs fine (and pulls in s390-tools-signed): sudo apt install s390-tools as one can check with: dpkg -l | grep s390-tools Wold yu please give it another try for verification? ** Changed in: s390-tools-signed (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: s390-tools-signed (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: s390-tools-signed (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Also affects: s390-tools-signed (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Changed in: s390-tools (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: s390-tools (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: s390-tools (Ubuntu Groovy) Importance: Undecided => Medium ** Project changed: subiquity => ubuntu-translations ** No longer affects: ubuntu-translations -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Tags removed: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
Hello bugproxy, or anyone else affected, Accepted s390-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/s390-tools/2.12.0-0ubuntu3.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: s390-tools (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
Hello bugproxy, or anyone else affected, Accepted s390-tools into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/s390-tools/2.14.0-1ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: s390-tools (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Changed in: s390-tools (Ubuntu Focal) Status: New => In Progress ** Changed in: s390-tools (Ubuntu Groovy) Status: New => In Progress ** Changed in: s390-tools (Ubuntu Focal) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: s390-tools (Ubuntu Groovy) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
I've sponsored this for Focal and Groovy - thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Merge proposal linked: https://code.launchpad.net/~fheimes/ubuntu/+source/s390-tools/+git/s390-tools/+merge/399467 ** Merge proposal linked: https://code.launchpad.net/~fheimes/ubuntu/+source/s390-tools/+git/s390-tools/+merge/399570 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Patch added: "needed to update due to a broken link in dep3 and a more specific upstream version reference" https://bugs.launchpad.net/subiquity/+bug/1892367/+attachment/5476076/+files/debdiff_groovy.diff ** Patch removed: "debdiff_groovy.diff" https://bugs.launchpad.net/subiquity/+bug/1892367/+attachment/5475474/+files/debdiff_groovy.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Merge proposal unlinked: https://code.launchpad.net/~fheimes/ubuntu/+source/s390-tools/+git/s390-tools/+merge/399467 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
Test builds for groovy and focal are available from here: https://launchpad.net/~fheimes/+archive/ubuntu/lp1892367/+packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Patch added: "debdiff_focal.diff" https://bugs.launchpad.net/subiquity/+bug/1892367/+attachment/5475917/+files/debdiff_focal.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Merge proposal linked: https://code.launchpad.net/~fheimes/ubuntu/+source/s390-tools/+git/s390-tools/+merge/399532 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Patch added: "debdiff_groovy.diff" https://bugs.launchpad.net/subiquity/+bug/1892367/+attachment/5475474/+files/debdiff_groovy.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Merge proposal linked: https://code.launchpad.net/~fheimes/ubuntu/+source/s390-tools/+git/s390-tools/+merge/399467 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Description changed: + SRU: + + + [Impact] + + * In case a ccw (special s390x hardware) device is configured +in a special (non-default) way using chzdev +(like for example increasing the qeth buffer_count to 128), +the modifications are not persistent by default, since the +generated udev rules are not automatically incuded/added to the initramfs. + + * One needs to either manually re-create the initramfs, +e.g. with 'sudo update-initramfs -k all -u' (maybe triggered by zipl) + + * or pass the arguments '-p -r zdev:early' to chzdev. + + * This is not really intuitive and what people expect +and partly leads to confusion. + + * The solution is to compile with the ZDEV_ALWAYS_UPDATE_INITRD=1 option set. +This makes sure that executions of chzdev always trigger 'update-initramfs -u'. + + [Test Plan] + + * Prepare an Ubuntu Server 20.04 or 20.04 on IBM Z with at least +one ccw device, for example a qeth network device, here '0.0.1234'. +(better to do that with a second spare qeth device, + other than the one that is in use by your remote connection). + + * Configure the device using: +sudo chzdev qeth -e 1234 + + * Check the (default) value of a certain attribute, like qeth buffer_count: +cat /sys/devices/qeth/0.0.1234/buffer_count +64 + + * Disable the ccw device again: +sudo chzdev qeth -d 1234 + + * And enable (re-)enable it with an increased buffer_count: +sudo chzdev -e 1234 buffer_count=128 + + * Check the (increased) value of the qeth buffer_count: +cat /sys/devices/qeth/0.0.1234/buffer_count +128 + + * Restart the system (without manually running update-initramfs or zipl): +sudo shutdown -r now + + * Once the system is up again, re-check if the ccw device was enabled again +and if it still has the increased buffer_count value: +lszdev qeth 1234 +TYPE ID ON PERS NAMES +qeth 0.0.1234:0.0.1235:0.0.1236 yes yes enc1234 +cat /sys/devices/qeth/0.0.1234/buffer_count +128 +(alternatively check with: lsqeth enc1234 | grep buffer_count) + + [Where problems could occur] + + * The logic of handling DZDEV_ALWAYS_UPDATE_INITRD could be wrong, e.g. inversed. +Then the initramfs is re-build even if not desired +and in case needed not done, hence similar result than before. + + * The setting of 'ZDEV_ALWAYS_UPDATE_INITRD=1' could have been missed, +which would lead to the similar behaviour than w/o the patch. + + * 'add_pers_removed' could handle wrong device types or not all devices, +in case of potential array index errors. + + * 'is_zdev_early_0' could identify wrong persistent devices as some to be +included early in the boot process (means added to the initramfs). + + * Problems in 'if (all_pers)' could lead to a wrong set of persistent devices +that are considered (or not all), +which could lead to unexpected (de-)configurations. + + * Finally the handling of the confirmation +or the 'build of the command line' could be errornous, +since the encapsulated if condition(s) changed (sightly). + + [Other Info] + + * This patch became upstream accepted with s390-tools 2.16.0 and is +with that already included in hirsute, based on LP:1914574. + + __ + 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@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@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,
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
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 Wed, 24 Feb 2021 05:49:54 + ** Changed in: s390-tools (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Changed in: ubuntu-z-systems Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Changed in: s390-tools (Ubuntu Hirsute) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
The idea is to pick this up once 2.16 is out (LP#1892367), since with 2.16 the udev topic is solved for hirsute, hence just the SRU to G and F is remaining. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Changed in: ubuntu-z-systems Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Changed in: s390-tools (Ubuntu Focal) Milestone: None => ubuntu-20.04.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Changed in: ubuntu-z-systems Status: Incomplete => Triaged ** Changed in: ubuntu-z-systems Assignee: Canonical Foundations Team (canonical-foundations) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: s390-tools (Ubuntu) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Also affects: s390-tools (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: s390-tools (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: s390-tools (Ubuntu Hirsute) Importance: Undecided Assignee: Canonical Foundations Team (canonical-foundations) Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Changed in: ubuntu-z-systems Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
Sounds good! Looking forward to that patch. And then we will most likely try to pick it up for stable release updates too. Cause yes, this behaviour needs to be fixed properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Changed in: ubuntu-z-systems Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
Hi Vineeth, that is correct that Debian/Ubuntu always copy all the udev rules from host, to the initramfs by default. And for us, stopping to do that will cause change of behavior which may trigger bug. Same as it would on RHEL/SUSE side if those would start doing this. If I understand you correctly, an Ubuntu-only change to internal_attr_early to have .defval="1" is the sort of thing you are proposing right? Which should lead to any persistent commands that affect udev rules to trigger initramfs rebuild? https://github.com/ibm-s390-tools/s390-tools/blob/58ecf1f363c35f452f5d00697620e520029bef83/zdev/src/internal.c#L23 That should fix the originally reported UX issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
** Also affects: s390-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Re: [UBUNTU 20.04] udev rule change did not get applied
Triaged to the subiquity project, as this issue appears to be related to a subiquity 20.04 installation. Please feel free to reclassify if that's inappropriate. ** Also affects: subiquity Importance: Undecided Status: New ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** No longer affects: subiquity ** Package changed: linux (Ubuntu) => subiquity ** Changed in: ubuntu-z-systems Importance: Undecided => Medium ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
