manual provider: fail to bootstrap on noble cannot determine host series: could not determine series

Bug #2065593 reported by Guillaume Boutry

This bug report will be marked for expiration in 48 days if no further activity occurs. (find out why)

6
This bug affects 1 person
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 a80becbb4da5985fa53c63824a4bd809e9d03954 gc go1.21.8]
13:40:24 DEBUG juju.cmd supercommand.go:57 args: []string{"/snap/juju/26968/bin/juju", "bootstrap", "--debug", "sunbeam", "sunbeam-controller"}
13:40:24 INFO cmd cloudcredential.go:91 no credentials found, checking environment
13:40:24 DEBUG juju.cmd.juju.commands bootstrap.go:1413 authenticating with region "" and credential "default" ()
13:40:24 DEBUG juju.cmd.juju.commands bootstrap.go:1572 provider attrs: map[]
13:40:24 INFO cmd authkeys.go:113 Adding contents of "/home/ubuntu/.local/share/juju/ssh/juju_id_rsa.pub" to authorized-keys
13:40:24 INFO cmd authkeys.go:113 Adding contents of "/home/ubuntu/.ssh/id_rsa.pub" to authorized-keys
<...>
2024-05-13 13:40:41 INFO juju.cmd supercommand.go:56 running jujud [3.4.2 a80becbb4da5985fa53c63824a4bd809e9d03954 gc go1.20.14]
2024-05-13 13:40:41 DEBUG juju.cmd supercommand.go:57 args: []string{"/var/lib/juju/tools/3.4.2-ubuntu-amd64/jujud", "bootstrap-state", "--timeout", "20m0s", "--data-dir", "/var/lib/juju", "--debug", "/var/lib/juju/bootstrap-params"}
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 EnsureMongoServerInstalled
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.com/juju/os/v2/series.getValueFromSeriesVersion:62: could not determine series
github.com/juju/os/v2/series.hostSeries.func1:47: cannot determine host series
github.com/juju/juju/mongo.ensureServer:229: cannot get host series
github.com/juju/juju/cmd/jujud/agent.(*BootstrapCommand).Run:295: failed to start mongo
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.juju.commands bootstrap.go:989 failed to bootstrap model: subprocess encountered error code 1
13:40:42 DEBUG juju.cmd.juju.commands bootstrap.go:990 (error details: [{github.com/juju/juju/cmd/juju/commands.(*bootstrapCommand).Run:1088: failed to bootstrap model} {github.com/juju/juju/environs/bootstrap.Bootstrap:738: } {github.com/juju/juju/environs/bootstrap.bootstrapIAAS:669: } {subprocess encountered error code 1}])
13:40:42 DEBUG juju.cmd.juju.commands bootstrap.go:1814 cleaning up after failed bootstrap
13:40:42 DEBUG juju.utils.ssh ssh.go:305 using OpenSSH ssh client
13:40:42 DEBUG juju.provider.manual environ.go:308 script stdout:
jujud stopped

13:40:42 DEBUG juju.provider.manual environ.go:309 script stderr:
+ 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
Revision history for this message
Ian Booth (wallyworld) wrote (last edit ):

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.

Changed in juju:
status: New → Incomplete
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.