File _patchinfo of Package patchinfo.17854

Overview Repositories Revisions Requests Users Attributes Meta

File _patchinfo of Package patchinfo.17854

<patchinfo incident="17854">
  <issue tracker="bnc" id="1176977">Derived images built with kiwi have dangling symlink in /usr/lib/sysimage/rpm</issue>
  <issue tracker="bnc" id="1170863">kiwi build-tests/s390/suse/test-image-vmx/appliance.kiwi does produce a bootable qcow2 image</issue>
  <issue tracker="bnc" id="1175729">Secure boot could not be determined when booting JeOS images from default/fallback EFI</issue>
  <issue tracker="bnc" id="1179562">kiwi race condition in multipath device lookup</issue>
  <issue tracker="bnc" id="1180781">SLES 15 (SP0) Azure gen2 images not bootable</issue>
  <issue tracker="bnc" id="1176129">SLE 12 and 15 containers have /dev 0700 permissions</issue>
  <issue tracker="bnc" id="1176134">[Build 20.3] JeOS images 15sp3 do not boot in uefi mode</issue>
  <packager>sax2</packager>
  <rating>moderate</rating>
  <category>recommended</category>
  <summary>Recommended update for python-kiwi</summary>
  <description>This update for python-kiwi fixes the following issues:

Update to version 9.21.23
 
- Azure generated images are not bootable. (bsc#1180781)
- Fixed validation of bool value in dracut module. (bsc#1179562)
  
  - The `oem-multipath-scan` setup results in a bool variable inside of the initrd code. 
  The variable `kiwi_oemmultipath_scan` is therefore either set to _true_ or _false_. 
  This update fixes the validation to make use of the `bool()` method provided for these type of variables.
    
- Omit multipath module by default (bsc#1179562)
    
  - The plain installation of the multipath toolkit activates the
    dracut multipath code. The setup if the target image runs in a
    multipath environment or not should however be decided explicitly
    in the image description via `&lt;oem-multipath-scan&gt;` and not
    implicitly by the presence of tools. 
    
- Fixed multipath disk device assignment in kiwi lib (bsc#1179562)
    
  - The former lookup of the multipath mapped disk device contained
    a race condition. If the lookup of the device mapper files happened
    before multipathd has finished the initialization, kiwi continues
    with the unix node name and fails when the device mapper keeps
    a busy state on it. This update changes the code such that in case
    of an explicit request to use multipath the lookup of the mapped
    device becomes a mandatory process that runs until the
    `DEVICE_TIMEOUT` is reached. Default timeout is set to 60 sec.
    
- Do not exclude filesystem folders in OCI images (bsc#1176129)
    
  - This update does not exclude filesystem folders during the rsync call
    in OCI images. It has been noted that including an empty `/dev` folder does
    not hurt and it can eventually help to workaround some limitations of
    container related tools such as `buildah`.
    
- Fix/Refactor s390 support (bsc#1170863)
    
  - This changes the s390 support on several stages:
    - On s390 the boot process is based on zipl which boots into an initrd from which a userspace grub process is
    started to support the grub capabilities. The implementation of this concept is provided via the 
    `grub2-s390x-emu` package. Once installed the setup of the bootloader is done via the `grub2-mkconfig` and
    `grub2-install` commands and therefore from a caller perspective the same as with any other 
    grub2 setup process. For kiwi this means no extra zipl bootloader target code is needed. Therefore
    this update deletes the zipl setup from kiwi and puts on the standard grub2 process. 
    - To support different targettypes the `grub2-s390x-emu` provided
    zipl template must be adapted. Parts of the former zipl bootloader
    setup therefore now applies to an update of the `zipl2grub` template file
    - Support for `CDL/LDL DASD` targets has been disabled in the schema.
    When testing 4k devices and a respective zipl2grub template
    setup for `CDL/LDL` targettype it has turned out that `grub2-install` is not able to run on such a device. 
    Probably the device code in `grub2-install` does not work for 4k devices with an fdasd created partition table. 
    As this needs further investigations and most probably adaptions on the grub toolchain for s390, 
    we disabled the setup of these modes for now. Emulated DASD (FBA) and SCSI targets stays supported.

- Fix compat link for rpmdb location. (bsc#1176977)

- This update fixes the symbolic link creation for `/var/lib/rpm`. More specific for derived container images 
    in which the base root tree already included the `/var/lib/rpm` the link, the `ln` command was creating a
    symbolic link inside the `/var/lib/rpm` folder givent that it was following the already existing symbolic link. 
    Adding the `--no-target-directory` force `ln` command to treat `/var/lib/rpm` path as the fully qualified 
    symlink name.
    
- Fixed s390/sle15 Virtual disk integration test. (bsc#1170863)
    
  - The integration test used FBA mode as target. As the target is expected to be KVM this is the wrong setting. 
    SCSI should be used instead. 
    
- Support dynamic `linux/linuxefi` in any case. (bsc#1175729, bsc#1176134)
    
  - Instead of restricting the dynamic linux vs. linuxefi setup to a specific grub version, 
    support this setup for any version of grub. 
    </description>
</patchinfo>

Places

File _patchinfo of Package patchinfo.17854

Places