From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Schaffner, Tobias" <tobias.schaffner@siemens.com>
Subject: Custom group logic broken since 032be24
Date: Wed, 26 Jul 2023 03:10:29 +0000 [thread overview]
Message-ID: <2a9a2e5bb85179c012011a99fe7d3109d7fd7625.camel@siemens.com> (raw)
Hi,
when using custom user groups the do_rootfs_postprocess task fails,
because the groups are not correctly expanded. This error has been
introduced in 032be24. I don't know why the CI did not catch it.
Reproducer:
local.conf
GROUPS += "plugdev render"
GROUP_plugdev[flags] += "system"
GROUP_render[flags] += "system"
USERS += "industrial"
USER_industrial[uid] = "1000"
USER_industrial[shell] = "/bin/bash"
USER_industrial[flags] += "create-home"
USER_industrial[groups] += "plugdev render"
log.do_rootfs_postprocess:
<redacted> do_rootfs_postprocess: ExecutionError(['sudo', '-E',
'chroot', '/build/tmp/work/<redacted>/img-<redacted>/1.0-r0/rootfs',
'/usr/sbin/usermod', '--uid', '1000', '--shell', '/bin/bash', '--
groups', ',plugdev,render', 'industrial'], 6, '', "usermod: group ''
does not exist\n")
Best regards,
Felix
reply other threads:[~2023-07-26 3:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2a9a2e5bb85179c012011a99fe7d3109d7fd7625.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=tobias.schaffner@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