public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Kowalsky, Clara" <clara.kowalsky@siemens.com>
Cc: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
Subject: Re: [PATCH v2 1/1] fix: rebuild rootfs on change of USERS
Date: Tue, 29 Apr 2025 08:31:10 +0000	[thread overview]
Message-ID: <e77a66df5232c6c445c256256d024a21762f9e04.camel@siemens.com> (raw)
In-Reply-To: <45679a80-dea9-4bc6-91ef-628e3848e403@siemens.com>

On Fri, 2025-04-11 at 17:56 +0200, Clara Kowalsky wrote:
> 
> 
> On 11.04.25 13:26, Felix Moessbauer wrote:
> > In case a change to the Isar created users is done, this currently
> > only re-triggers the do_rootfs_postprocess task. This task changes
> > the
> > rootfs (e.g. home dirs are moved) and by that needs to operate on a
> > clean one. Otherwise old homedirs might still remain in the final
> > rootfs
> > or move operations are not possible.
> > 
> > We fix this by ensuring that the do_rootfs_install task is executed
> > whenever a change to USERS is done. By that, we enter the
> > do_rootfs_postinstall with a clean rootfs.
> > 
> > Reported-by: Clara Kowalsky <clara.kowalsky@siemens.com>
> > Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> > ---
> > Changes since v1:
> > 
> > - Also add dependency to USER_<x> for all x in USERS
> > 
> >   meta/classes/image-account-extension.bbclass | 6 ++++++
> >   1 file changed, 6 insertions(+)
> > 
> > diff --git a/meta/classes/image-account-extension.bbclass
> > b/meta/classes/image-account-extension.bbclass
> > index ea956cd5..3c461b1a 100644
> > --- a/meta/classes/image-account-extension.bbclass
> > +++ b/meta/classes/image-account-extension.bbclass
> > @@ -8,6 +8,10 @@
> >   USERS ??= ""
> >   GROUPS ??= ""
> >   
> > +# rebuild rootfs on change of USERS as homes might be moved /
> > created
> > +# no need to depend on GROUPS as they don't create directories
> > +# groups need to be created before users, hence do not move the
> > user creation into
> > +# the do_rootfs_install task but only add a dependency
> >   python() {
> >       for entry in (d.getVar("GROUPS") or "").split():
> >           group_entry = "GROUP_{}".format(entry)
> > @@ -16,7 +20,9 @@ python() {
> >       for entry in (d.getVar("USERS") or "").split():
> >           user_entry = "USER_{}".format(entry)
> >           d.appendVarFlag("image_postprocess_accounts", "vardeps",
> > " {}".format(user_entry))
> > +        d.appendVarFlag("do_rootfs_install", "vardeps", "
> > {}".format(user_entry))
> >   }
> > +do_rootfs_install[vardeps] += "USERS"
> >   
> >   def image_create_groups(d: "DataSmart") -> None:
> >       """Creates the groups defined in the ``GROUPS`` bitbake
> > variable.
> 
> This works, at least for the case of adding / moving the home
> directory 
> of an existing user. Only removing an existing home dir when removing
> all home flags of a user is not covered, but we can ignore this for
> now.

Hi, this can only happen if a user is created by a package and then
transformed using ISAR, right?. IMHO this is simply not in scope, as we
have no way to express "remove-this-homedir".

Anyways, IMHO this patch is good to be merged.

Best regards,
Felix

> BR,
> Clara

-- 
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/e77a66df5232c6c445c256256d024a21762f9e04.camel%40siemens.com.

      reply	other threads:[~2025-04-29  8:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11 11:26 'Felix Moessbauer' via isar-users
2025-04-11 15:56 ` 'Clara Kowalsky' via isar-users
2025-04-29  8:31   ` 'MOESSBAUER, Felix' via isar-users [this message]

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=e77a66df5232c6c445c256256d024a21762f9e04.camel@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=clara.kowalsky@siemens.com \
    --cc=felix.moessbauer@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