public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Scott Mayhew <smayhew@redhat.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: kdevops@lists.linux.dev
Subject: Re: [PATCH 6/6] gen_nodes: ensure kdevops prefix has no dashes
Date: Mon, 31 Mar 2025 13:35:41 -0400	[thread overview]
Message-ID: <Z-rSbQg_vUY_UrE2@aion> (raw)
In-Reply-To: <20250329230141.3718282-7-mcgrof@kernel.org>

On Sat, 29 Mar 2025, Luis Chamberlain wrote:

> Folks trying to use kdevops and testing with fstests will quickly
> find out a surprise that their config is not being parsed correctly
> until later.
> 
> Fix this by preventing bringup if the prefix has a dash.
> 
> We use the dash to help parallelize testing filesystem profiles and
> so the host prefix goes before the filesystem name and test profile.

Where does that happen?  All of my kdevops setups use multiple dashes in
the host prefix (e.g. "kdevops-nfs-fstests-rhel-10-nightly"), so this
breaks my setup, and I'd imagine it breaks Chuck's too.

-Scott
> 
> Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
> ---
>  playbooks/roles/gen_nodes/tasks/main.yml | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/playbooks/roles/gen_nodes/tasks/main.yml b/playbooks/roles/gen_nodes/tasks/main.yml
> index d541dcbf1f54..8c6a1f705ee2 100644
> --- a/playbooks/roles/gen_nodes/tasks/main.yml
> +++ b/playbooks/roles/gen_nodes/tasks/main.yml
> @@ -18,6 +18,11 @@
>    command: "id -g -n"
>    register: my_group
>  
> +- name: Fail if kdevops_host_prefix contains a dash
> +  fail:
> +    msg: "Invalid kdevops_host_prefix '{{ kdevops_host_prefix }}'. The prefix cannot contain a dash ('-')."
> +  when: kdevops_host_prefix is search("-")
> +
>  - name: Create guestfs directory
>    ansible.builtin.file:
>      path: "{{ guestfs_path }}"
> -- 
> 2.47.2
> 
> 


  reply	other threads:[~2025-03-31 17:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-29 23:01 [PATCH 0/6] debian / libvirt / devconfig fixes Luis Chamberlain
2025-03-29 23:01 ` [PATCH 1/6] scripts/bringup_guestfs.sh: uninstall unattended-upgrades on debian guests Luis Chamberlain
2025-03-29 23:01 ` [PATCH 2/6] devconfig: ensure unattended-upgrades is not installed on debian Luis Chamberlain
2025-03-29 23:01 ` [PATCH 3/6] libvirt: use consistent pool path variables and use optional yaml output Luis Chamberlain
2025-03-29 23:01 ` [PATCH 4/6] Kconfig: adopt output yaml for KDEVOPS_FIRST_RUN Luis Chamberlain
2025-03-29 23:01 ` [PATCH 5/6] guestfs: replace ansible group permisison requirement on libvirt system uri Luis Chamberlain
2025-03-29 23:01 ` [PATCH 6/6] gen_nodes: ensure kdevops prefix has no dashes Luis Chamberlain
2025-03-31 17:35   ` Scott Mayhew [this message]
2025-03-31 18:33     ` Luis Chamberlain
2025-03-31 19:14       ` Scott Mayhew
2025-03-31 19:36         ` Luis Chamberlain
2025-03-31 20:49           ` Scott Mayhew
2025-04-01 21:11             ` Luis Chamberlain
  -- strict thread matches above, loose matches on Subject: below --
2025-03-23 11:50 [PATCH 0/6] debian / libvirt / devconfig fixes Luis Chamberlain
2025-03-23 11:50 ` [PATCH 6/6] gen_nodes: ensure kdevops prefix has no dashes Luis Chamberlain

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=Z-rSbQg_vUY_UrE2@aion \
    --to=smayhew@redhat.com \
    --cc=kdevops@lists.linux.dev \
    --cc=mcgrof@kernel.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