Re: [PATCH 09/40] ansible.cfg: Explicitly set the ssh user

[Luis Chamberlain <mcgrof@kernel.org>]

On Sun, Jul 27, 2025 at 08:24:49PM -0400, Chuck Lever wrote:
> On 7/27/25 8:17 PM, Luis Chamberlain wrote:
> > From: Chuck Lever <chuck.lever@oracle.com>
> > 
> > I've been seeing tasks that are marked "become: true" fail with
> > this message:
> > 
> >   Timeout (12s): waiting for privilege escalation promt:
> > 
> > This appears to be a common failure mode, but it is due to a broad
> > variety of causes. I think I've nailed this one with this addition
> > to ansible.cfg. It changes "ESTABLISHING SSH SESSION FOR: NONE"
> > to "... FOR: <user>" where <user> is always a user that is allowed
> > to use sudo.
> > 
> > The current Terraform Kconfig menu sets this user, but guestfs does
> > not -- the Ansible ssh user for guestfs is always "kdevops". The
> > ansible.cfg.j2 file reflects this.
> > 
> > Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> 
> Whoops, Daniel wanted changes to this one. It shouldn't be included
> in this series.
> 
> 8/40 has some formatting problems, and 10/40 is for my own CI.
> 
> The switch to the cloud.terraform module is under test and not related
> to the builder work.
> 
> I can refresh/rebase my "builder" branch to remove the leaked patches.
> Let me know what you'd prefer.

Since I did the vagrant removal first and then your patches on top,
and you know what to remove of what not, could you shuffle as you need
and chop away / merge whatever patches you see fit for a v2 posting?
You can use this as a base:

https://github.com/linux-kdevops/kdevops/tree/mcgrof/chuck-builder-vagrant

  Luis