From: Chuck Lever <cel@kernel.org>
To: Daniel Gomez <da.gomez@kernel.org>
Cc: kdevops@lists.linux.dev, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [RFC PATCH] Makefile: terraform wasn't building the kdevops_nodes file
Date: Sun, 28 Sep 2025 16:30:07 -0400 [thread overview]
Message-ID: <fe79c346-ee58-47c7-a178-bd51a0cb7f1e@kernel.org> (raw)
In-Reply-To: <827d1b8e-d489-46a9-a49b-b3cf3a4fe097@kernel.org>
On 9/28/25 12:53 PM, Daniel Gomez wrote:
> I see! Thanks for reporting. Indeed my fix introduced this bug. I think
> it'd be best to move KDEVOPS_NODES just after we assign the filename to it
> (provision.Makefile -> guestfs.Makefile):
>
> diff --git a/Makefile b/Makefile
> index 3653591d..26615b22 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -144,16 +144,16 @@ endif
> DEFAULT_DEPS += $(ANSIBLE_CFG_FILE)
> DEFAULT_DEPS += $(ANSIBLE_INVENTORY_FILE)
>
> -ifneq (,$(KDEVOPS_NODES))
> -DEFAULT_DEPS += $(KDEVOPS_NODES)
> -endif
> -
> include scripts/provision.Makefile
> include scripts/firstconfig.Makefile
> include scripts/systemd-timesync.Makefile
> include scripts/journal-server.Makefile
> include scripts/update_etc_hosts.Makefile
>
> +ifneq (,$(KDEVOPS_NODES))
> +DEFAULT_DEPS += $(KDEVOPS_NODES)
> +endif
> +
> KDEVOPS_BRING_UP_DEPS += $(KDEVOPS_BRING_UP_DEPS_EARLY)
> KDEVOPS_BRING_UP_DEPS += $(KDEVOPS_PROVISIONED_DEVCONFIG)
The above snippet seems to work without any new issues.
> @@ -264,13 +264,13 @@ ifneq (,$(KDEVOPS_BRING_UP_DEPS))
> include scripts/bringup.Makefile
> endif
>
> -$(ANSIBLE_INVENTORY_FILE): .config $(ANSIBLE_CFG_FILE) $(KDEVOPS_HOSTS_TEMPLATE) $(KDEVOPS_EXTRA_VARS)
> +$(ANSIBLE_INVENTORY_FILE): .config $(ANSIBLE_CFG_FILE) $(KDEVOPS_HOSTS_TEMPLATE) $(KDEVOPS_NODES) $(KDEVOPS_EXTRA_VARS)
> $(Q)ansible-playbook $(ANSIBLE_VERBOSE) --connection=local \
> --inventory localhost, \
> $(KDEVOPS_PLAYBOOKS_DIR)/gen_hosts.yml \
> --extra-vars=@./extra_vars.yaml
>
> -$(KDEVOPS_NODES): .config $(ANSIBLE_CFG_FILE) $(KDEVOPS_NODES_TEMPLATE) $(KDEVOPS_EXTRA_VARS)
> +$(KDEVOPS_NODES): .config $(ANSIBLE_CFG_FILE) $(ANSIBLE_INVENTORY_FILE) $(KDEVOPS_NODES_TEMPLATE) $(KDEVOPS_EXTRA_VARS)
With this snippet, "make" emits a new complaint:
TASK [ansible_cfg : Update ansible.cfg access modification time so make
sees it updated]
***************************************************************************************************************************************************
changed: [localhost]
PLAY RECAP
*********************************************************************************************************************************************************************************************************************************
localhost : ok=4 changed=2 unreachable=0
failed=0 skipped=0 rescued=0 ignored=0
make: Circular terraform/aws/nodes.tf <-
/home/cel/src/kdevops/buildbot-configs/hosts dependency dropped.
PLAY [Generate target node configuration]
But otherwise, "make bringup" works as expected.
--
Chuck Lever
next prev parent reply other threads:[~2025-09-28 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 15:53 [RFC PATCH] Makefile: terraform wasn't building the kdevops_nodes file Chuck Lever
2025-09-28 19:53 ` Daniel Gomez
2025-09-28 19:57 ` Chuck Lever
2025-09-28 20:08 ` Daniel Gomez
2025-09-28 20:30 ` Chuck Lever [this message]
2025-09-29 19:16 ` 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=fe79c346-ee58-47c7-a178-bd51a0cb7f1e@kernel.org \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=da.gomez@kernel.org \
--cc=kdevops@lists.linux.dev \
/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