From: Chuck Lever <chuck.lever@oracle.com>
To: Daniel Gomez <da.gomez@kernel.org>, Luis Chamberlain <mcgrof@kernel.org>
Cc: kdevops@lists.linux.dev, Daniel Gomez <da.gomez@samsung.com>
Subject: Re: [PATCH 3/9] base_image: fix template dest fields in custom-image task
Date: Wed, 20 Aug 2025 09:29:02 -0400 [thread overview]
Message-ID: <e8090926-5300-4c04-9c8a-9019808558b9@oracle.com> (raw)
In-Reply-To: <20250820-guestfs-custom-image-fixes-v1-3-0fe1d69c3f33@samsung.com>
On 8/20/25 8:51 AM, Daniel Gomez wrote:
> From: Daniel Gomez <da.gomez@samsung.com>
>
> The Ansible built-in template was using the wrong destiny module
s/destiny/destination
As I mentioned in the cover letter for the guestfs playbook series,
the "custom image" piece of that series was entirely untested, and the
category of fixes you've done in this series demonstrate that clearly.
Thank you for taking care of these!
For the series,
Reviewed-by: Chuck Lever <chuck.lever@oracle.com>
> parameter name. Fix the typo.
>
> https://docs.ansible.com/ansible/latest/collections/ansible/builtin/template_module.html#parameter-dest
>
> Signed-off-by: Daniel Gomez <da.gomez@samsung.com>
> ---
> playbooks/roles/base_image/tasks/custom-image.yml | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/playbooks/roles/base_image/tasks/custom-image.yml b/playbooks/roles/base_image/tasks/custom-image.yml
> index ede44bd7..609dc515 100644
> --- a/playbooks/roles/base_image/tasks/custom-image.yml
> +++ b/playbooks/roles/base_image/tasks/custom-image.yml
> @@ -102,7 +102,7 @@
> - name: Build the custom source
> ansible.builtin.template:
> src: "{{ role_path }}/templates/custom-source.j2"
> - dst: "{{ custom_source }}"
> + dest: "{{ custom_source }}"
> mode: "u=rw,g=r,o=r"
> when:
> - not result.stat.exists
> @@ -118,7 +118,7 @@
> - name: Build the custom index
> ansible.builtin.template:
> src: "{{ role_path }}/templates/custom-index.j2"
> - dst: "{{ custom_index }}"
> + dest: "{{ custom_index }}"
> mode: "u=rw,g=r,o=r"
> when:
> - not result.stat.exists
>
--
Chuck Lever
next prev parent reply other threads:[~2025-08-20 13:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 12:51 [PATCH 0/9] Fix guestfs custom-image path Daniel Gomez
2025-08-20 12:51 ` [PATCH 1/9] guestfs: base_image: fix custom-image include_tasks filename Daniel Gomez
2025-08-20 12:51 ` [PATCH 2/9] guestfs: export kconfig yaml missing variables Daniel Gomez
2025-08-20 12:51 ` [PATCH 3/9] base_image: fix template dest fields in custom-image task Daniel Gomez
2025-08-20 13:29 ` Chuck Lever [this message]
2025-08-21 8:22 ` Daniel Gomez
2025-08-20 12:51 ` [PATCH 4/9] base_image: custom-image: fix variable scoping conflicts Daniel Gomez
2025-08-20 12:51 ` [PATCH 5/9] guestfs: bringup: fix ssh key injection Daniel Gomez
2025-08-20 12:51 ` [PATCH 6/9] base_image: add become privileges for custom image setup Daniel Gomez
2025-08-20 12:51 ` [PATCH 7/9] guestfs: debian: ensure dhcpcd-base runtime dependency Daniel Gomez
2025-08-20 12:51 ` [PATCH 8/9] guestfs: add unified LIBVIRT_IMAGE_SIZE configuration Daniel Gomez
2025-08-20 12:51 ` [PATCH 9/9] guestfs: fix locale warnings in VM deployments Daniel Gomez
2025-08-21 7:26 ` [PATCH 0/9] Fix guestfs custom-image path Daniel Gomez
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=e8090926-5300-4c04-9c8a-9019808558b9@oracle.com \
--to=chuck.lever@oracle.com \
--cc=da.gomez@kernel.org \
--cc=da.gomez@samsung.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