From: Anthony Iliopoulos <ailiop@suse.com>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Goldwyn Rodrigues <rgoldwyn@suse.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Chuck Lever <cel@kernel.org>,
"kdevops@lists.linux.dev" <kdevops@lists.linux.dev>
Subject: Re: [RFC PATCH 00/22] Replace community.general.zypper
Date: Tue, 16 Apr 2024 00:38:58 +0200 [thread overview]
Message-ID: <Zh2sgs2R-V34kdTJ@technoir> (raw)
In-Reply-To: <B1D9CD76-7AC6-476D-916D-25E5BCF140E6@oracle.com>
On Mon, Apr 15, 2024 at 09:41:38PM +0000, Chuck Lever III wrote:
>
>
> > On Apr 15, 2024, at 5:35 PM, Goldwyn Rodrigues <rgoldwyn@suse.com> wrote:
> >
> > On Mon, Apr 15, 2024 at 4:11 PM Chuck Lever <chuck.lever@oracle.com> wrote:
> >>
> >> On Mon, Apr 15, 2024 at 03:32:59PM -0500, Goldwyn Rodrigues wrote:
> >>> On Mon, Apr 15, 2024 at 9:39 AM Chuck Lever III <chuck.lever@oracle.com> wrote:
> >>>>
> >>>> I've been able to test some of this series with OpenSuSE 15.3.
> >>>> Found and fixed one bug. I've pushed the result to:
> >>>>
> >>>> https://github.com/chucklever/kdevops/tree/replace-zypper-module
> >>>>
> >>>> However it looks like the fstests workflow hasn't been tested
> >>>> on SuSE for quite some time.
> >>>>
> >>>> OpenSuSE doesn't like the group name "123456-fsgqa" (and probably
> >>>> the user name is rejected too, but kdevops tries the group first,
> >>>> and that's where the workflow fails).
> >>>
> >>> I am able to add users without any issue here.
> >>
> >> Is "here" on an OpenSuSE 15.3 system? I did log into the test system
> >> and try "groupadd" directly, and it failed in the same way.
> >
> > openSUSE Tumbleweed, but I am sure nothing has changed since openSUSE 15.3
> > I am able to add the group 123456-fsgqa. However, if you have added a
> > 123456-fsgqa *user* before it may fail. What is the error message you
> > get?
>
> TASK [fstests : Add missing groups for fstests] ************************************************************************************************
> changed: [cel-tmpfs-default] => (item=Ensuring the group sys exists)
> failed: [cel-tmpfs-default] (item=Ensuring the group 123456-fsgqa exists) => {
> "ansible_loop_var": "item",
> "changed": false,
> "item": "123456-fsgqa",
> "name": "123456-fsgqa"
> }
>
> MSG:
>
> groupadd: '123456-fsgqa' is not a valid group name
>
> I logged in at the time, and tried by hand:
>
> cel-tmpfs-default:~ # groupadd 123456-fsgqa
> groupadd: '123456-fsgqa' is not a valid group name
> cel-tmpfs-default:~ #
The issue is that SLE is using shadow v4.8, and it doesn't allow
user/group names starting with digits. This was later on relaxed via
shadow upstream commit cfc981df2afc ("shadow: use relaxed usernames")
which was released in v4.13. This is why this works in TW.
I had a local old kdevops patch that did "useradd --badnames -U" to
bypass the check for SLE.
Regards,
Anthony
next prev parent reply other threads:[~2024-04-15 22:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 17:46 [RFC PATCH 00/22] Replace community.general.zypper cel
2024-04-12 17:46 ` [RFC PATCH 01/22] blktests: Replace the use of community.general.zypper cel
2024-04-12 17:46 ` [RFC PATCH 02/22] bootlinux: Replace the use of the community.general.zypper module cel
2024-04-12 17:46 ` [RFC PATCH 03/22] btrfs_progs: " cel
2024-04-12 17:46 ` [RFC PATCH 04/22] build-qemu: " cel
2024-04-12 17:46 ` [RFC PATCH 05/22] create_partition: " cel
2024-04-12 17:46 ` [RFC PATCH 06/22] cxl: " cel
2024-04-12 17:46 ` [RFC PATCH 07/22] devconfig: " cel
2024-04-12 17:46 ` [RFC PATCH 08/22] kotd-rev-kernel: " cel
2024-04-12 17:46 ` [RFC PATCH 09/22] fstests: " cel
2024-04-12 17:46 ` [RFC PATCH 10/22] fstests_prep_localhost: Replace the use of the community.general zypper module cel
2024-04-12 17:46 ` [RFC PATCH 11/22] install-menuconfig-deps: Replace the use of the community.general.zypper module cel
2024-04-12 17:46 ` [RFC PATCH 12/22] install_systemd_journal: " cel
2024-04-12 17:46 ` [RFC PATCH 13/22] install_systemd_timesyncd: " cel
2024-04-12 17:46 ` [RFC PATCH 14/22] install_terraform: " cel
2024-04-12 17:46 ` [RFC PATCH 15/22] install_vagrant: " cel
2024-04-12 17:46 ` [RFC PATCH 16/22] kdc: " cel
2024-04-12 17:46 ` [RFC PATCH 17/22] krb5: " cel
2024-04-12 17:46 ` [RFC PATCH 18/22] ktls: " cel
2024-04-12 17:46 ` [RFC PATCH 19/22] libvirt_user: " cel
2024-04-12 17:46 ` [RFC PATCH 20/22] nfsd: " cel
2024-04-12 17:46 ` [RFC PATCH 21/22] pynfs: " cel
2024-04-12 17:46 ` [RFC PATCH 22/22] selftests: " cel
2024-04-12 18:30 ` [RFC PATCH 00/22] Replace community.general.zypper Luis Chamberlain
2024-04-15 14:39 ` Chuck Lever III
2024-04-15 20:32 ` Goldwyn Rodrigues
2024-04-15 21:11 ` Chuck Lever
2024-04-15 21:35 ` Goldwyn Rodrigues
2024-04-15 21:41 ` Chuck Lever III
2024-04-15 22:38 ` Anthony Iliopoulos [this message]
2024-04-17 16:57 ` Chuck Lever III
2024-04-17 18:39 ` Anthony Iliopoulos
2024-04-17 18:48 ` Chuck Lever III
2024-04-17 18:48 ` Chuck Lever III
2024-04-17 19:12 ` Anthony Iliopoulos
2024-04-17 16:50 ` Chuck Lever III
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=Zh2sgs2R-V34kdTJ@technoir \
--to=ailiop@suse.com \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=kdevops@lists.linux.dev \
--cc=mcgrof@kernel.org \
--cc=rgoldwyn@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.