manual provider: fail to bootstrap on noble cannot determine host series: could not determine series
This bug report will be marked for expiration in 48 days if no further activity occurs. (find out why)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Bootstrapping a juju controller on a 24.04 LXD VM fails with "cannot determine host series: could not determine series" error
JUJU: 3.4.2
LXD: 5.21.1 LTS
OS: Ubuntu 24.04 LTS, fingerprint: 63e801c05439
(can be tested by trying to bootstrap a Sunbeam)
ubuntu@rayon:~$ juju bootstrap --debug sunbeam sunbeam-controller
13:40:24 INFO juju.cmd supercommand.go:56 running juju [3.4.2 a80becbb4da5985
13:40:24 DEBUG juju.cmd supercommand.go:57 args: []string{
13:40:24 INFO cmd cloudcredential
13:40:24 DEBUG juju.cmd.
13:40:24 DEBUG juju.cmd.
13:40:24 INFO cmd authkeys.go:113 Adding contents of "/home/
13:40:24 INFO cmd authkeys.go:113 Adding contents of "/home/
<...>
2024-05-13 13:40:41 INFO juju.cmd supercommand.go:56 running jujud [3.4.2 a80becbb4da5985
2024-05-13 13:40:41 DEBUG juju.cmd supercommand.go:57 args: []string{
2024-05-13 13:40:41 DEBUG juju.agent agent.go:600 read agent config, format "2.0"
2024-05-13 13:40:42 INFO juju.agent identity.go:22 writing system identity file
2024-05-13 13:40:42 DEBUG juju.cmd.jujud bootstrap.go:444 starting mongo
2024-05-13 13:40:42 DEBUG juju.agent agent.go:978 potential mongo addresses: [localhost:37017]
2024-05-13 13:40:42 DEBUG juju.cmd.jujud bootstrap.go:473 calling EnsureMongoServ
ERROR failed to start mongo: cannot get host series: cannot determine host series: could not determine series
2024-05-13 13:40:42 DEBUG cmd supercommand.go:549 error stack:
github.
github.
github.
github.
2024-05-13 13:40:42 DEBUG juju.cmd.jujud main.go:287 jujud complete, code 0, err <nil>
13:40:42 ERROR juju.cmd.
13:40:42 DEBUG juju.cmd.
13:40:42 DEBUG juju.cmd.
13:40:42 DEBUG juju.utils.ssh ssh.go:305 using OpenSSH ssh client
13:40:42 DEBUG juju.provider.
jujud stopped
13:40:42 DEBUG juju.provider.
+ stopped=0
+ pkill -SIGABRT jujud
+ wait_for_jujud
+ for i in {1..30}
+ pgrep jujud
+ echo jujud stopped
+ stopped=1
+ logger --id jujud stopped on attempt 1
+ break
+ [[ 1 -ne 1 ]]
+ [[ 1 -ne 1 ]]
+ service juju-db stop
Failed to stop juju-db.service: Unit juju-db.service not loaded.
+ exit 0
13:40:42 INFO cmd supercommand.go:556 command finished
description: | updated |
Juju 3.4 does not officially support noble.
When 3.4.2 was released, noble was not known to it IIANM. Juju would have been relying on the distroinfo package to supply the mapping from os version to series name. It should have worked if this was up to date. Perhaps the manual machine needed a package update.
Having said that, when 3.4.3 comes out, you should be able to opt in to 24.04 (use --base not --series). But again, 24.04 is not officially supported on 3.4.
I'll mark as incomplete and feel free to ask again if 3.4.3 shows the same issue.