public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
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 RFT 0/6] Fix Ansible warnings and simplify build dependency order
Date: Mon, 22 Sep 2025 10:15:08 -0400	[thread overview]
Message-ID: <d2e5a8f5-7141-4718-a795-87d12aa7342c@oracle.com> (raw)
In-Reply-To: <20250922-makefile-targets-order-v1-0-d4adb19ffa88@samsung.com>

On 9/22/25 4:13 AM, Daniel Gomez wrote:
> This series fixes Ansible warnings that appear during terraform setup
> and simplifies ansible-playbook calls by establishing proper Makefile
> target dependency order.
> 
> Problem: Terraform targets were executing before ansible.cfg and hosts
> files existed, causing "No inventory was parsed" and "provided hosts
> list is empty" warnings.
> 
> Root cause: The include order in Makefile caused terraform dependencies
> to be added to DEFAULT_DEPS before core Ansible files.
> 
> Solution:
> 1. Establish correct dependency order: extra_vars.yaml → ansible.cfg →
> hosts → nodes → rest
> 2. Add missing localhost entry in the new generic inventory template
> (generic.j2)
> 3. Use explicit connection flags for bootstrap operations and remove
> warning suppressions. Note, this reintroduces the --connection and
> --inventory flags to the ansible.cfg and inventory targets. We only need
> these 2 here for obvious reasons. This allows to remove the warnings
> variables introduced after actually removing the flags. Being explicit
> with flags is preferred here than using ANSIBLE_* variables.
> 
> Signed-off-by: Daniel Gomez <da.gomez@samsung.com>
> ---
> Daniel Gomez (6):
>       Makefile: fix target dependency order
>       gen_hosts: add localhost to generic workflow template
>       ansible_cfg: fix Python interpreter discovery warning
>       Makefile: remove warnings from ANSIBLE_CFG_FILE target
>       Makefile: simplify KDEVOPS_NODES ansible-playbook call
>       Makefile: add explicit connection for inventory generation
> 
>  Makefile                                           | 41 ++++++++++++----------
>  playbooks/ansible_cfg.yml                          |  2 ++
>  .../roles/gen_hosts/templates/workflows/generic.j2 |  1 +
>  3 files changed, 25 insertions(+), 19 deletions(-)
> ---
> base-commit: 53943da513f1cfc857844bf5f961c27a13d3060d
> change-id: 20250922-makefile-targets-order-d917a35f550a
> 
> Best regards,
> --  
> Daniel Gomez <da.gomez@samsung.com>
> 

I didn't look closely at the details, but this series makes a world
of sense.

Reviewed-by: Chuck Lever <chuck.lever@oracle.com>


-- 
Chuck Lever

  parent reply	other threads:[~2025-09-22 14:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 11:13 [PATCH RFT 0/6] Fix Ansible warnings and simplify build dependency order Daniel Gomez
2025-09-22 11:13 ` [PATCH RFT 1/6] Makefile: fix target " Daniel Gomez
2025-09-22 11:13 ` [PATCH RFT 2/6] gen_hosts: add localhost to generic workflow template Daniel Gomez
2025-09-22 11:13 ` [PATCH RFT 3/6] ansible_cfg: fix Python interpreter discovery warning Daniel Gomez
2025-09-22 11:13 ` [PATCH RFT 4/6] Makefile: remove warnings from ANSIBLE_CFG_FILE target Daniel Gomez
2025-09-22 11:13 ` [PATCH RFT 5/6] Makefile: simplify KDEVOPS_NODES ansible-playbook call Daniel Gomez
2025-09-22 11:13 ` [PATCH RFT 6/6] Makefile: add explicit connection for inventory generation Daniel Gomez
2025-09-22 14:15 ` Chuck Lever [this message]
2025-09-23 20:12   ` [PATCH RFT 0/6] Fix Ansible warnings and simplify build dependency order 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=d2e5a8f5-7141-4718-a795-87d12aa7342c@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