public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: uvv.mail@gmail.com
To: openembedded-core@lists.openembedded.org
Cc: Vyacheslav Yurkov <uvv.mail@gmail.com>
Subject: [PATCH v3 1/3] overlayfs: Fix the QA skip for ignored mounts
Date: Wed, 14 Jan 2026 18:54:12 +0000	[thread overview]
Message-ID: <20260114185508.380709-2-uvv.mail@gmail.com> (raw)
In-Reply-To: <20260114185508.380709-1-uvv.mail@gmail.com>

From: Vyacheslav Yurkov <uvv.mail@gmail.com>

The supressing of QA check for mounts should happens twice, at parsing stage
and at rootfs postprocessing. If the mount point is configured to be skipped,
but it is still present in the configuration (machine or distro), then the
parsing would complain.

Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com>
---
 meta/lib/oe/overlayfs.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/lib/oe/overlayfs.py b/meta/lib/oe/overlayfs.py
index 5a5ea03d45..3805746d90 100644
--- a/meta/lib/oe/overlayfs.py
+++ b/meta/lib/oe/overlayfs.py
@@ -33,7 +33,8 @@ def unitFileList(d):
     # check that we have required mount points set first
     requiredMountPoints = d.getVarFlags('OVERLAYFS_WRITABLE_PATHS')
     for mountPoint in requiredMountPoints:
-        if mountPoint not in overlayMountPoints:
+        qaSkip = (d.getVarFlag("OVERLAYFS_QA_SKIP", mountPoint) or "").split()
+        if mountPoint not in overlayMountPoints and not "mount-configured" in qaSkip:
             bb.fatal("Missing required mount point for OVERLAYFS_MOUNT_POINT[%s] in your MACHINE configuration" % mountPoint)
 
     for mountPoint in overlayMountPoints:


  reply	other threads:[~2026-01-14 18:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14 18:54 [PATCH v3 0/3] Overlayfs improvements uvv.mail
2026-01-14 18:54 ` uvv.mail [this message]
2026-01-15 13:41   ` [OE-core] [PATCH v3 1/3] overlayfs: Fix the QA skip for ignored mounts Paul Barker
2026-01-15 21:18     ` Vyacheslav Yurkov
2026-01-14 18:54 ` [PATCH v3 2/3] oe-selftest: overlayfs: Make the test more deterministic uvv.mail
2026-01-15 13:53   ` [OE-core] " Paul Barker
2026-01-14 18:54 ` [PATCH v3 3/3] oe-selftest: overlayfs: Add a demo case for /etc uvv.mail
2026-01-15 14:01   ` [OE-core] " Paul Barker

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=20260114185508.380709-2-uvv.mail@gmail.com \
    --to=uvv.mail@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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