Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionChristian Kellner
2021-09-14 15:17:11 UTC
Copy of Bug #2004139, this one is for osbuild-composer:
OSTree has special handling for bootloader: firstly, it creates BLS snippets, secondly, depending on what `sysroot.backend` is selected it will also execute bootlader-specifc tooling like `grub2-mkconfig`.
The default backend for OSTree is `auto`, which detects the installed bootloader and uses that backend. But since both grub2 and zipl now use the BLS we actually do _not_ want any boot loader specific tooling to be run, especially since this will prevent upgrade commits to be deployed, like e.g.:
# ostree admin deploy cs8/x86_64/osbuild
note: Deploying commit 4db806215547c9893fde7a7795408a06e1c7ba6759740c31eb78b74a299d5ae2 which contains content in /var/lib that will be ignored.
Copying /etc changes: 2 modified, 0 removed, 12 added
error: Bootloader write config: grub2-mkconfig: Child process exited with code 1
Use the new osbuild option (sysroot.bootloader in ostree.config) to set the backend to `none`.
Comment 7Christian Kellner
2021-09-18 12:33:46 UTC
Mixed up component (osbuild vs composer), sorry for the noise.
Verified this bug with the latest build, fixed, will set the status to VERIFIED.
Environment:
[root@85iso2 images]# cat /etc/os-release
NAME="Red Hat Enterprise Linux"
VERSION="8.5 (Ootpa)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="8.5"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Red Hat Enterprise Linux 8.5 Beta (Ootpa)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:8::baseos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://access.redhat.com/documentation/red_hat_enterprise_linux/8/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_BUGZILLA_PRODUCT_VERSION=8.5
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.5 Beta"
Build version:
[root@85iso2 workspace]# rpm -qa|grep osbuild
python3-osbuild-35-3.el8.noarch
osbuild-ostree-35-3.el8.noarch
osbuild-35-3.el8.noarch
osbuild-selinux-35-3.el8.noarch
osbuild-composer-33.2-1.el8.x86_64
osbuild-composer-core-33.2-1.el8.x86_64
osbuild-composer-worker-33.2-1.el8.x86_64
Check ostree bootloader in an edge deployment:
[admin@vm-bios ~]$ ostree config get sysroot.bootloader
none
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (osbuild bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2021:4273