bootstrap fails with fork/exec /usr/bin/ssh: permission denied

Bug #2060315 reported by Marian Gasparovic
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Snap
Fix Committed
High
Guillaume Boutry

Bug Description

2023.2/edge, testing MAAS deployments

When running sunbeam cluster bootstrap -m manifest.yaml it deploys juju controller but cannot connect to it and cancels the bootstrap.

During that time I am able to ssh manually.

Running with debug I saw this

15:46:36 INFO cmd bootstrap.go:334 - yfcmft (arch=amd64 mem=4G cores=2)
15:46:36 INFO juju.environs.bootstrap bootstrap.go:1014 newest version: 3.4.1
15:46:36 INFO juju.environs.bootstrap bootstrap.go:1029 picked bootstrap agent binary version: 3.4.1
15:46:36 INFO cmd bootstrap.go:629 Installing Juju agent on bootstrap instance
15:54:38 DEBUG juju.cloudconfig.instancecfg instancecfg.go:947 Setting numa ctl preference to false
Waiting for address
15:54:39 DEBUG juju.provider.maas instance.go:88 "juju-1" has addresses ["local-cloud:10.244.40.102@oam-space(id:1)"]
Attempting to connect to 10.244.40.102:22
15:54:39 DEBUG juju.provider.common bootstrap.go:708 connection attempt for 10.244.40.102 failed: fork/exec /usr/bin/ssh: permission denied
15:54:44 DEBUG juju.provider.common bootstrap.go:708 connection attempt for 10.244.40.102 failed: fork/exec /usr/bin/ssh: permission denied
15:54:49 DEBUG juju.provider.maas instance.go:88 "juju-1" has addresses ["local-cloud:10.244.40.102@oam-space(id:1)"]
15:54:49 DEBUG juju.provider.common bootstrap.go:708 connection attempt for 10.244.40.102 failed: fork/exec /usr/bin/ssh: permission denied
15:54:54 DEBUG juju.provider.common bootstrap.go:708 connection attempt for 10.244.40.102 failed: fork/exec /usr/bin/ssh: permission denied
15:54:59 DEBUG juju.provider.common bootstrap.go:708 connection attempt for 10.244.40.102 failed: fork/exec /usr/bin/ssh: permission denied

Message repeats many times and then cancels the process

Tags: cdo-qa
Revision history for this message
Marian Gasparovic (marosg) wrote :

As suggested by @gboutry `sudo snap connect openstack:ssh-keys` helped

Changed in snap-openstack:
status: New → Fix Committed
importance: Undecided → High
assignee: nobody → Guillaume Boutry (gboutry)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.