RE: [PATCH] ci-build: Protect bullseye container with KFAIL

["Moessbauer, Felix" <felix.moessbauer@siemens.com>]

Hi,

I stumbled upon that while debugging the build errors on the DKMS module patch.
If possible, we could just bump QEMU in the KAS image to have a proper fix.

Otherwise, we might run into that issue here and there and it's not obvious that this is the root cause.
I don't think that the patch will be integrated into buster, so we can't just wait for it. 

Anyways, at least a warning message should be emitted when running on the broken version.

PS: sending this to the list as well.

Best regards,
Felix

> -----Original Message-----
> From: Anton Mikanovich <amikan@ilbers.de>
> Sent: Thursday, April 29, 2021 4:01 PM
> To: Moessbauer, Felix (T RDA IOT SES-DE) <felix.moessbauer@siemens.com>
> Cc: Kiszka, Jan (T RDA IOT) <jan.kiszka@siemens.com>
> Subject: Re: [PATCH] ci-build: Protect bullseye container with KFAIL
> 
> 29.04.2021 16:42, Moessbauer, Felix wrote:
> > Hi Anton,
> >
> > I can confirm that the CI patch does not solve the issue (on mc:qemuarm64-
> focal).
> > In case of the gitlab-ci, the KAS image provides the qemu-user-static.
> >
> > I just tried to install qemu-user-static from buster-backports into the KAS
> container and that solved the issue.
> > Maybe Jan might have a look into that. IMO this would be way better than
> trying to work-around in ISAR.
> >
> > Best regards,
> > Felix
> 
> Sure that was just an ugly hotfix to not have all CI builds 'red'
> because of that.
> When the original issue will be solved we can remove those KFAILs.
> 
> --
> Anton Mikanovich
> Promwad Ltd.
> External service provider of ilbers GmbH Maria-Merian-Str. 8
> 85521 Ottobrunn, Germany
> +49 (89) 122 67 24-0
> Commercial register Munich, HRB 214197
> General Manager: Baurzhan Ismagulov