| 2023-08-07 13:54:45 |
Peter Jose De Sousa |
description |
Hello,
When using manual provider on juju 3.1, manual provider is unable to authenticate using my SSH keys.
ap-http-proxy: snap-https-proxy: snap-store-assertions: snap-store-proxy: snap-store-proxy-url: ssl-hostname-verification:true test-mode:false transmit-vendor-metrics:true type:manual update-status-hook-interval:5m uuid:2554b2d3-345e-48f6-8f97-bca3b4427502]
14:32:45 INFO juju.environs.manual.sshprovisioner sshprovisioner.go:44 initialising "10.10.32.80", user "ubuntu"
14:32:45 DEBUG juju.utils.ssh ssh.go:305 using OpenSSH ssh client
14:32:45 DEBUG juju.utils.ssh ssh.go:305 using OpenSSH ssh client
14:32:45 ERROR juju.provider.manual provider.go:39 initializing ubuntu user: subprocess encountered error code 255 (ubuntu@10.10.32.80: Permission denied (publickey).)
ERROR subprocess encountered error code 255 (ubuntu@10.10.32.80: Permission denied (publickey).)
14:32:45 DEBUG cmd supercommand.go:548 error stack:
subprocess encountered error code 255 (ubuntu@10.10.32.80: Permission denied (publickey).)
github.com/juju/juju/environs/bootstrap.PrepareController:145:
github.com/juju/juju/cmd/juju/commands.(*bootstrapCommand).Run:872:
If I reinstall juju 3.1 using devmode and re-run the same command I am able to bootstrap successfully.
[Steps to reproduce]
1. Install juju 3.1/stable confined
2. Attempt to bootstrap a manual controller
Oberve the above error
[Workaround]
Install with devmode (not recommended)
Thanks,
Peter |
Hello,
When using manual provider on juju 3.1, manual provider is unable to authenticate using my SSH keys.
ap-http-proxy: snap-https-proxy: snap-store-assertions: snap-store-proxy: snap-store-proxy-url: ssl-hostname-verification:true test-mode:false transmit-vendor-metrics:true type:manual update-status-hook-interval:5m uuid:2554b2d3-345e-48f6-8f97-bca3b4427502]
14:32:45 INFO juju.environs.manual.sshprovisioner sshprovisioner.go:44 initialising "10.10.32.80", user "ubuntu"
14:32:45 DEBUG juju.utils.ssh ssh.go:305 using OpenSSH ssh client
14:32:45 DEBUG juju.utils.ssh ssh.go:305 using OpenSSH ssh client
14:32:45 ERROR juju.provider.manual provider.go:39 initializing ubuntu user: subprocess encountered error code 255 (ubuntu@10.10.32.80: Permission denied (publickey).)
ERROR subprocess encountered error code 255 (ubuntu@10.10.32.80: Permission denied (publickey).)
14:32:45 DEBUG cmd supercommand.go:548 error stack:
subprocess encountered error code 255 (ubuntu@10.10.32.80: Permission denied (publickey).)
github.com/juju/juju/environs/bootstrap.PrepareController:145:
github.com/juju/juju/cmd/juju/commands.(*bootstrapCommand).Run:872:
If I reinstall juju 3.1 using devmode and re-run the same command I am able to bootstrap successfully.
[Steps to reproduce]
1. Install juju 3.1/stable confined
2. Attempt to bootstrap a manual controller
Observe the above error
[Workaround]
Install with devmode (not recommended)
Thanks,
Peter |
|
