From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6767012587809800192 X-Received: by 2002:a05:6512:c7:: with SMTP id c7mr7992000lfp.120.1575628376111; Fri, 06 Dec 2019 02:32:56 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:ac2:4acf:: with SMTP id m15ls601543lfp.13.gmail; Fri, 06 Dec 2019 02:32:55 -0800 (PST) X-Google-Smtp-Source: APXvYqxdJLuvcLL5Paq8uYMmWdtH735MWxHRkz//tWuaDPiD4KbJxyVAihuJgYKcX+/XwpagK1iD X-Received: by 2002:ac2:555c:: with SMTP id l28mr7615759lfk.52.1575628375264; Fri, 06 Dec 2019 02:32:55 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575628375; cv=none; d=google.com; s=arc-20160816; b=Qjio1p+FzAy620/m3pIfjy1tAGjKZAaFZOa94acEZfW1+FoOWr1gpYfRsVbsQQq2Y6 HeteHzZazVLMdk03fl+2PytBFdH/71M5OU1lqWyuGc4wR9i6diNrbGhJ8bZjBO7AJ8PP Bta2fySVALEG9UjHPrscl/6TyNnGQqUwYovAI+MH1MXe0bUWYPc5q048oxXf49UAQBTO jk0WfbqBp59jsyPF1njuInP2E8ZNndBy7GftZxQIwhJ1i1IcBxq1hHJAJhTn0nXGKU4/ XXLO63QWV9zz/bsvz8NCK6kQF52i6sGeZCh3WArWA79DrDIecdcnjX5fBLRDQ2J3XYJ2 B6oA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date; bh=hdEmhepNDioo7yE9ll0E/p2bRejhzed1rH+/Qdfwbhk=; b=MOOZzHmw1NNyv3hx72KmuQbpzdaXkxmvBNbXEoS92lRsB6jWLNjxqw5wDHnJ+cDGoh l1n6wyC7Ieoxrfc80cOkk3v5Py2k/H84SCUR3pUoSHA8tWDIR411OfZcC85Zs0ug977Z hlVaUe/NfSfh4V5XbiVW8vg2445BdDalUGo9z9zQi4pEkqrpfpEXEXxplsGVSwLui0BU Ww6grtk+j5kq+atZZEvVoGZgwE50q28B3lNeGZtunGuabQgJ/SGtNd1CasQsFeyoOsqn k+vFFIAGMQ5qg/kYMs+0XHPTT0wbG0gBgwTVQMgbOHS2QXyHOAZRGn/llwVv7g1qmKgH YrbA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id t3si385940ljj.1.2019.12.06.02.32.55 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Dec 2019 02:32:55 -0800 (PST) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id xB6AWsfo026936 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 6 Dec 2019 11:32:54 +0100 Received: from md1za8fc.ad001.siemens.net ([139.25.69.199]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id xB6AWrXW012667; Fri, 6 Dec 2019 11:32:53 +0100 Date: Fri, 6 Dec 2019 11:32:53 +0100 From: Henning Schild To: "[ext] Jan Kiszka" Cc: Vijai Kumar K , Quirin Gylstorff , Subject: Re: [PATCH] targz-img: Ignore tar exit code 1 Message-ID: <20191206113253.5ae6ca79@md1za8fc.ad001.siemens.net> In-Reply-To: <7972e109-f8a0-6f21-bd00-4312610fd414@siemens.com> References: <20191205174441.16406-1-Vijaikumar_Kangarajan@mentor.com> <85e91f0a-da08-5345-a666-b3026bee4d96@siemens.com> <20191205191735.GA16912@oxygen> <7972e109-f8a0-6f21-bd00-4312610fd414@siemens.com> X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: OZ0rfZWxDsXg Am Thu, 5 Dec 2019 20:31:48 +0100 schrieb "[ext] Jan Kiszka" : > On 05.12.19 20:17, Vijai Kumar K wrote: > > On Thu, Dec 05, 2019 at 07:04:07PM +0100, Jan Kiszka wrote: > >> On 05.12.19 18:44, vijaikumar.kanagarajan@gmail.com wrote: > >>> From: Vijai Kumar K > >>> > >>> Sometimes during packaging tar prints a warning "file changed as > >>> we read it" and exits with return code 1. This is observed when > >>> we generete both wic-img and targz-img together. Ignore the > >>> error. > >> > >> Ignoring errors is rarely a good idea. In this case, it tells you > >> that you have a bug in your layer that missing a dependency. I > >> know this because we once had the same issue in a product layer. > >> So: NAK > >> > >> Jan > > > > Ah! Ok. Back to square one I guess. Its currently observed in our > > downstream setups only. I have no good reason to justify it. > > Reproducing this issue is gonna be difficult. Let me see if I can > > monitor file changes and pinpoint the exact condition. But this is > > going to take a while. > > > > If it helps, the scenario is IMAGE_TYPE set to wic-img and > > targz-img is inherited so both are executed for a build. Also, on a > > seperate note > > wic may have found a reason to modify the rootfs while integrating it. > So a first shot could be making targz depend on wic completion. I hope it did not. But my first guess would be /etc/fstab. Whichever file it touched, it should only affect the wic image! Worth checking whether wic changes the original and maybe fix that. Henning > BTW, this sounds similar to > https://gitlab.com/cip-project/cip-core/isar-cip-core/blob/next/classes/wic-targz-img.bbclass > - and that class may have the same issue... > > > IMAGE_TYPE's functionality could be extended to provide multiple > > image types. I believe we could specify only one right now. Former > > is more clean and particularly useful if one wants a wic for sd > > boot and tar for nfsroot. Planning to take this up next. > > Right, that is of general interest, indeed. Quirin has something > planned around the same use case as well. > > Jan >