RE: [PATCH v3 1/1] add uuid to schroot folder

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

> -----Original Message-----
> From: Anton Mikanovich <amikan@ilbers.de>
> Sent: Friday, July 8, 2022 2:47 PM
> To: Moessbauer, Felix (T CED SES-DE) <felix.moessbauer@siemens.com>; isar-
> users@googlegroups.com
> Cc: Bezdeka, Florian (T CED SES-DE) <florian.bezdeka@siemens.com>; Schild,
> Henning (T CED SES-DE) <henning.schild@siemens.com>
> Subject: Re: [PATCH v3 1/1] add uuid to schroot folder
> 
> 04.07.2022 12:15, Felix Moessbauer wrote:
> > PIDs are not unique across containers.
> > When running the build in a container (e.g. the kas container), the
> > PID of bitbake is likely the same across multiple simultaneously
> > running builds.
> >
> > This is especially the case for CI runners, where it is common that
> > multiple jobs run in parallel.
> >
> > This patch adds an additional UUID component that is injected from the
> > ISAR environment.
> >
> > Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> I'm still think placing ISAR_BUILD_UUID generaion outside bitbake is not really
> good idea. This is ok for single run inside container but not so suitable for
> running several builds in one build environment (when we source isar-init-build-
> env only once and then execute bitbake over and over again).
> Current implementation is more env-unique but not build-unique.

We need both, and that is exactly what is implemented in this patch.
We need an external UUID to solve the non-unique PID problem when running in multiple containers simultaneously (like in the gitlab-ci), and we need the PID to support multiple builds in the same dir.

In the future we might want to use the unshare backend and get rid of the mountpoint altogether, but currently this is not mature enough. Hence, we need a solution to fix the sporadic breaks of the CI by PID collisions in the schroot mountpoint.

Felix