sunbeam cluster bootstrap with ssh error

juju
1

I follow the https://ubuntu.com/tutorials/install-openstack-on-your-workstation-and-launch-your-first-instance#2-install-openstack and https://microstack.run/docs/single-node-guided to deploy but failed at execute “sunbeam cluster bootstrap --accept-defaults” or “sunbeam cluster bootstrap”, the logs show:

ubuntu@ubuntu:~$ sunbeam cluster bootstrap
Management networks shared by hosts (CIDRs, separated by comma) (192.168.1.0/24): 
Error bootstrapping Juju
Traceback (most recent call last):
  File "/snap/openstack/247/lib/python3.10/site-packages/sunbeam/commands/juju.py", line 290, in run
    process = subprocess.run(cmd, capture_output=True, text=True, check=True)
  File "/usr/lib/python3.10/subprocess.py", line 526, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/snap/openstack/247/juju/bin/juju', 'bootstrap', 'sunbeam', 'sunbeam-controller', '--agent-version=3.2.0']' 
returned non-zero exit status 1.
ERROR initializing ubuntu user: subprocess encountered error code 255 (/bin/bash: line 1: /usr/bin/sss_ssh_knownhostsproxy: No such file or directory
kex_exchange_identification: Connection closed by remote host
Connection closed by UNKNOWN port 65535)
ERROR subprocess encountered error code 255 (/bin/bash: line 1: /usr/bin/sss_ssh_knownhostsproxy: No such file or directory
kex_exchange_identification: Connection closed by remote host
Connection closed by UNKNOWN port 65535)

Error: Command '['/snap/openstack/247/juju/bin/juju', 'bootstrap', 'sunbeam', 'sunbeam-controller', '--agent-version=3.2.0']' returned non-zero exit status 1.

How can I fix it to proceed?

2

I joined the pc with ipa client before, I can find the config file from here:

ubuntu@ubuntu:/etc/ssh/ssh_config.d$ cat 04-ipa.conf

# IPA-related configuration changes to ssh_config
#
PubkeyAuthentication yes
GlobalKnownHostsFile /var/lib/sss/pubconf/known_hosts
#VerifyHostKeyDNS yes

# assumes that if a user does not have shell (/sbin/nologin),
# this will return nonzero exit code and proxy command will be ignored
Match exec true   
	ProxyCommand /usr/bin/sss_ssh_knownhostsproxy -p %p %h

I think it may cause conflict with juju, but how can it work with juju?