From: Chuck Lever <chuck.lever@oracle.com>
To: mcgrof@kernel.org
Cc: kdevops@lists.linux.dev
Subject: "make bringup" broken with vagrant
Date: Sun, 7 Apr 2024 12:37:54 -0400 [thread overview]
Message-ID: <ZhLL4roiWXYZ7hu0@tissot.1015granger.net> (raw)
Hi-
Looks like de140b0f3eff ("common: move getting user and group
inference to shared role") breaks my one remaining vagrant-based
system.
TASK [devconfig : Copy the developer's gitconfig *if* it exists] *******************************************************************************
fatal: [cel-nfsd]: FAILED! => {
"changed": false,
"checksum": "4f4b923c806d9b8c7406907f05c30f360e2c2f88"
}
MSG:
Destination directory /home/kdevops does not exist
Might be this hunk?
diff --git a/group_vars/all b/group_vars/all
index 050f210a5824..008786b8d4cd 100644
--- a/group_vars/all
+++ b/group_vars/all
@@ -4,8 +4,8 @@
# ansible/extra_vars.yml
# Your default username to log in to systems
-data_user: vagrant
-data_group: vagrant
+data_user: kdevops
+data_group: kdevops
data_home_dir: "/home/{{ data_user }}"
--
Chuck Lever
next reply other threads:[~2024-04-07 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 16:37 Chuck Lever [this message]
[not found] ` <CAB=NE6Vm2g1dd4YrmWYQxQhz6of52o+GZ2pai=TeTzNAJL8sCQ@mail.gmail.com>
2024-04-07 19:56 ` "make bringup" broken with vagrant Chuck Lever
2024-04-07 21:17 ` 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=ZhLL4roiWXYZ7hu0@tissot.1015granger.net \
--to=chuck.lever@oracle.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).