With change [1] things changed from a patching out of the initial portion of /bin/kernel-install to becoming a plug-in called later during the script. There's been a slight change though, in that the checks for /etc/machine-id [2] are now triggered, which didn't happen before. AFAICT, the actuall new-kernel-pkg call doesn't in any way depend on this. I don't believe I want it to anyway, because I'm actually building a generic .qcow2 image where /etc/machine-id should be blank at boot anyway. I'm in the slightly unusual position of modifying a base .qcow2 image using diskimage-builder [3]. I'm still getting my head 100% around the root cause path here, but what I'm seeing fail is our kernel cleanup path, that removes extra kernels [4] --- 2017-08-28 00:28:01.401364 | [fedora/build-succeeds] Preparing : 1/1 2017-08-28 00:28:01.407940 | [fedora/build-succeeds] Running scriptlet: kernel-core-4.11.8-300.fc26.x86_64 1/1 2017-08-28 00:28:01.408018 | [fedora/build-succeeds] Could not determine your machine ID from /etc/machine-id. 2017-08-28 00:28:01.408055 | [fedora/build-succeeds] Please run 'systemd-machine-id-setup' as root. See man:machine-id(5) 2017-08-28 00:28:01.408095 | [fedora/build-succeeds] error: %preun(kernel-core-4.11.8-300.fc26.x86_64) scriptlet failed, exit status 1 2017-08-28 00:28:01.490799 | [fedora/build-succeeds] Error in PREUN scriptlet in rpm package kernel-core 2017-08-28 00:28:01.490892 | [fedora/build-succeeds] Error in PREUN scriptlet in rpm package kernel-core ---- [1] https://src.fedoraproject.org/rpms/systemd/c/12da227455a6872d695cdcac1093b6b5fe9f9008?branch=master [2] https://github.com/systemd/systemd/blame/a827e37371be78ba7eda63fa6edca1074c431524/src/kernel-install/kernel-install#L35 [3] https://git.openstack.org/cgit/openstack/diskimage-builder/ [4] http://logs.openstack.org/34/497734/3/check/gate-dib-dsvm-functests-python2-ubuntu-trusty-image-nv/b9cf382/console.html
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.