Cannot bootstrap with --bootstrap-series jammy on focal machine
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
Deploying juju on Focal machine with --bootstrap-series jammy fails
as it cannot connect over SSH to the instance
juju 2.9.38 (stable 2023-01-17)
mastier@foauld:~$ snap info juju|grep installed
installed: 2.9.38 (21790) 97MB classic
mastier@foauld:~$ lsb_release -r
Release: 20.04
mastier@foauld:~$ juju --debug bootstrap localhost testjammyonfocal --bootstrap-series jammy
20:09:38 INFO juju.cmd supercommand.go:56 running juju [2.9.38 6d211be0d72d6f4
20:09:38 DEBUG juju.cmd supercommand.go:57 args: []string{
20:09:38 DEBUG juju.container.lxd connection.go:180 using LXD socket at path: "/var/snap/
20:09:51 DEBUG juju.container.lxd network.go:181 created new nic device "eth0" in profile "default"
20:09:51 DEBUG juju.container.lxd connection.go:180 using LXD socket at path: "/var/snap/
20:09:53 DEBUG juju.container.lxd storage.go:85 created new disk device "root" in profile "default"
20:09:53 INFO cmd provider.go:356 Resolved LXD host address on bridge lxdbr0: https:/
20:09:53 INFO cmd cloudcredential
20:09:53 DEBUG juju.cmd.
20:09:53 DEBUG juju.cmd.
20:09:54 INFO cmd authkeys.go:114 Adding contents of "/home/
20:09:54 DEBUG juju.cmd.
automatically-
20:09:54 INFO cmd bootstrap.go:856 Creating Juju controller "testjammyonfocal" on localhost/localhost
20:09:54 INFO juju.cmd.
20:09:54 DEBUG juju.environs.
20:09:54 DEBUG juju.environs.
20:09:54 INFO cmd bootstrap.go:397 Loading image metadata
20:09:54 INFO cmd bootstrap.go:470 Looking for packaged Juju agent version 2.9.38 for amd64
20:09:54 INFO juju.environs.
20:09:54 DEBUG juju.environs.tools tools.go:87 finding agent binaries in stream: "released"
20:09:54 DEBUG juju.environs.tools tools.go:89 reading agent binaries with major.minor version 2.9
20:09:54 DEBUG juju.environs.tools tools.go:98 filtering agent binaries by version: 2.9.38
20:09:54 DEBUG juju.environs.tools tools.go:101 filtering agent binaries by os type: ubuntu
20:09:54 DEBUG juju.environs.tools tools.go:104 filtering agent binaries by architecture: amd64
20:09:54 DEBUG juju.environs.tools urls.go:133 trying datasource "keystone catalog"
20:09:54 DEBUG juju.environs.
20:09:54 DEBUG juju.environs.
20:09:56 DEBUG juju.environs.
20:09:56 DEBUG juju.environs.
20:09:56 DEBUG juju.environs.
20:09:56 DEBUG juju.environs.
20:09:57 INFO juju.environs.
20:09:57 INFO cmd bootstrap.go:483 Located Juju agent version 2.9.38-ubuntu-amd64 at https:/
20:09:57 INFO cmd bootstrap.go:581 Starting new instance for initial controller
20:09:57 INFO cmd environ.go:212 To configure your system to better support LXD containers, please see: https:/
20:09:58 INFO cmd bootstrap.go:171 Launching controller instance(s) on localhost/
20:09:58 DEBUG juju.provider.lxd environ_
20:09:58 DEBUG juju.cloudconfi
20:09:58 DEBUG juju.environs imagemetadata.
20:09:58 DEBUG juju.container.lxd connection.go:197 LXD requires https://, using: https:/
20:10:03 DEBUG juju.container.lxd image.go:95 Found image remotely - "default ubuntu cloud images" "ubuntu-
20:10:03 DEBUG juju.container.lxd image.go:128 Copying image from remote server
20:11:24 DEBUG juju.service discovery.go:67 discovered init system "systemd" from series "jammy"
20:11:24 DEBUG juju.provider.lxd environ_
20:11:24 INFO juju.container.lxd container.go:256 starting new container "juju-2dd13f-0" (image "ubuntu-
20:11:24 DEBUG juju.container.lxd container.go:257 new container has profiles [default juju-controller]
20:12:05 DEBUG juju.container.lxd container.go:286 created container "juju-2dd13f-0", waiting for start...
20:12:10 INFO juju.provider.lxd environ_
20:12:10 INFO cmd bootstrap.go:309 - juju-2dd13f-0 (arch=amd64)
20:12:10 INFO juju.environs.
20:12:10 INFO juju.environs.
20:12:10 INFO cmd bootstrap.go:629 Installing Juju agent on bootstrap instance
20:12:13 DEBUG juju.environs.
20:12:13 DEBUG juju.environs.
20:12:15 DEBUG juju.environs.
20:12:15 DEBUG juju.environs.
20:12:15 DEBUG juju.environs.
20:12:16 DEBUG juju.environs.
20:12:16 DEBUG juju.environs.
20:12:17 INFO cmd bootstrap.go:786 Fetching Juju Dashboard 0.8.1
20:12:17 DEBUG juju.cloudconfi
Waiting for address
Attempting to connect to 10.111.175.125:22
20:12:18 DEBUG juju.provider.
20:12:23 DEBUG juju.provider.
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:
Please contact your system administrator.
Add correct host key in /tmp/juju-
Offending ED25519 key in /tmp/juju-
remove with:
ssh-keygen -f "/tmp/juju-
ECDSA host key for 10.111.175.125 has changed and you have requested strict checking.
Host key verification failed.
20:12:28 DEBUG juju.provider.
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:
Please contact your system administrator.
Add correct host key in /tmp/juju-
Offending ED25519 key in /tmp/juju-
remove with:
ssh-keygen -f "/tmp/juju-
ECDSA host key for 10.111.175.125 has changed and you have requested strict checking.
Host key verification failed.
20:12:33 DEBUG juju.provider.
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:
Please contact your system administrator.
Add correct host key in /tmp/juju-
Offending ED25519 key in /tmp/juju-
remove with:
ssh-keygen -f "/tmp/juju-
ECDSA host key for 10.111.175.125 has changed and you have requested strict checking.
Host key verification failed.
...
@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:
Please contact your system administrator.
Add correct host key in /tmp/juju-
Offending ED25519 key in /tmp/juju-
remove with:
ssh-keygen -f "/tmp/juju-
ECDSA host key for 10.111.175.125 has changed and you have requested strict checking.
Host key verification failed.
20:24:08 ERROR juju.provider.lxd environ_
20:24:08 ERROR juju.cmd.
20:24:08 DEBUG juju.cmd.
20:24:08 DEBUG juju.cmd.
20:24:08 INFO juju.provider.
20:24:08 INFO juju.provider.
20:24:08 ERROR juju.cmd.
20:24:08 INFO cmd supercommand.go:544 command finished
Changed in juju: | |
milestone: | none → 2.9.41 |
status: | New → Triaged |
importance: | Undecided → High |
Changed in juju: | |
milestone: | 2.9.41 → 2.9.42 |
Changed in juju: | |
milestone: | 2.9.42 → 2.9.43 |
Changed in juju: | |
milestone: | 2.9.43 → 2.9.44 |
Changed in juju: | |
milestone: | 2.9.44 → 2.9.45 |
Changed in juju: | |
milestone: | 2.9.45 → 2.9.46 |
Full log attached. repetition of connection trials removed.