From: Henning Schild <henning.schild@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: "Q. Gylstorff" <Quirin.Gylstorff@siemens.com>,
jan.kiszka@siemens.com, isar-users@googlegroups.com
Subject: Re: [PATCH v14 0/2] CPIO & OVA Images
Date: Tue, 14 Sep 2021 12:54:45 +0200 [thread overview]
Message-ID: <20210914125445.57ce08e5@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <d7a74ff2-fb14-5316-dd51-589cff947907@ilbers.de>
I kind of want to bet this has to do with mounting again.
generate_wic_image does quite a bit of layer mounting and umounting. If
mounting the base isar layer fails that script can probably "go
missing". And i am not sure those mounts will be cleaned up when the
task does not finish correctly.
regards,
Henning
Am Fri, 20 Aug 2021 12:07:53 +0300
schrieb Anton Mikanovich <amikan@ilbers.de>:
> 08.07.2021 11:42, Q. Gylstorff wrote:
> > From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> >
> > - Generate cpio images for rescue images
> > - generate ova images for VMWare & Virtualbox
> >
> We've experienced floating issue during full CI testing if include
> this patchset:
>
> 00:14:20 INFO: Creating image(s)...
> 00:14:20
> 00:14:20 ERROR: _exec_cmd: export
> PATH=//sbin://usr/sbin://usr/bin://bin:None:$PATH;export
> PSEUDO_PREFIX=//usr;export
> PSEUDO_LOCALSTATEDIR=/workspace/build/isar_am_devel/110/build/tmp/work/debian-buster-amd64/isar-image-base-qemuamd64-wic-img/1.0-r0/rootfs/../pseudo;export
> PSEUDO_PASSWD=/workspace/build/isar_am_devel/110/build/tmp/work/debian-buster-amd64/isar-image-base-qemuamd64-wic-img/1.0-r0/rootfs;export
> PSEUDO_NOSYMLINKEXP=1;export
> PSEUDO_IGNORE_PATHS=/tmp/tmp.nSYNbkMHKq/isar-image-base-debian-buster-qemuamd64.wic/tmp.wic.4t1qlax6/rootfs_platform.2.ext4,/;/workspace/build/isar_am_devel/110/scripts/wic_fakeroot
> fsck.ext4 -pvfD
> /tmp/tmp.nSYNbkMHKq/isar-image-base-debian-buster-qemuamd64.wic/tmp.wic.4t1qlax6/rootfs_platform.2.ext4
> returned '127' instead of 0
> 00:14:20 output: /bin/sh: 1:
> /workspace/build/isar_am_devel/110/scripts/wic_fakeroot: not found
> 00:14:20
> 00:14:20 WARNING: exit code 1 from a shell command.
>
> It doesn't looks like something virtual images related, so not sure
> if it was caused by this patchset.
> But for some reason it was happened only if CPIO&OVA v14 was included.
>
> The failed builds are:
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fci.isar-build.org%3A8080%2Fjob%2Fisar_am_devel%2F110%2FconsoleFull&data=04%7C01%7Cde173c00-e982-4fda-8644-47edf4671d63%40ad011.siemens.com%7C11c07c50cd7c46b53c8d08d963ba0572%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637650473333123853%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=N%2Bwdk5CdmnSnxZSYawz9V9N5Doo5lBsWrU5bUodPNfY%3D&reserved=0
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fci.isar-build.org%3A8080%2Fjob%2Fisar_am_devel%2F111%2FconsoleFull&data=04%7C01%7Cde173c00-e982-4fda-8644-47edf4671d63%40ad011.siemens.com%7C11c07c50cd7c46b53c8d08d963ba0572%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637650473333123853%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=AOlB1MufUym42Fx9MxA9i75lM%2FmgDYuH6pqYI93Ibek%3D&reserved=0
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fci.isar-build.org%3A8080%2Fjob%2Fisar_am_devel%2F115%2FconsoleFull&data=04%7C01%7Cde173c00-e982-4fda-8644-47edf4671d63%40ad011.siemens.com%7C11c07c50cd7c46b53c8d08d963ba0572%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637650473333133842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=W7WUqLyo0VrLMGiJMEUc%2Bpvoqzj7xutMRo2wjhmBPnE%3D&reserved=0
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fci.isar-build.org%3A8080%2Fjob%2Fisar_am_devel%2F123%2FconsoleFull&data=04%7C01%7Cde173c00-e982-4fda-8644-47edf4671d63%40ad011.siemens.com%7C11c07c50cd7c46b53c8d08d963ba0572%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637650473333133842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=4z1JroTZd%2Fdwf7T%2F4ptKvV30AfdEYvQqgu0p861EbSw%3D&reserved=0
>
next prev parent reply other threads:[~2021-09-14 10:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 8:42 Q. Gylstorff
2021-07-08 8:42 ` [PATCH v14 1/2] meta/classes: Generate ova image for VMWare or Virtualbox Q. Gylstorff
2021-07-08 8:42 ` [PATCH v14 2/2] meta/classes: add cpiogz-img Q. Gylstorff
2021-08-20 9:07 ` [PATCH v14 0/2] CPIO & OVA Images Anton Mikanovich
2021-09-07 10:48 ` Gylstorff Quirin
2021-09-07 13:06 ` Jan Kiszka
2021-09-07 13:49 ` Anton Mikanovich
2021-09-13 9:39 ` Anton Mikanovich
2021-09-14 10:54 ` Henning Schild [this message]
2021-09-16 10:01 ` Henning Schild
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210914125445.57ce08e5@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=Quirin.Gylstorff@siemens.com \
--cc=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox