Can't bootstrap a bionic bootstrap node: juju-mongodb3.2 package missing

Bug #1763654 reported by Imran Khakoo on 2018-04-13
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju
High
Unassigned

Bug Description

When bootstrapping a Bionic node, the following error comes along:

Attempt 1 to download agent binaries from https://streams.canonical.com/juju/tools/agent/2.3.5/juju-2.3.5-ubuntu-amd64.tgz...
agent binaries from https://streams.canonical.com/juju/tools/agent/2.3.5/juju-2.3.5-ubuntu-amd64.tgz downloaded: HTTP 200; time 24.000261s; size 29262301 bytes; speed 1219262.000 bytes/s Agent binaries downloaded successfully.
d2f393dafdc1095cf4e8a4cc077e9c918484bff416c91054749a21f89ef4f118 /var/lib/juju/tools/2.3.5-bionic-amd64/tools.tar.gz
892e4b979b0bcee634a928c40f05641928af433baed8e381935becf95cb6651b /var/lib/juju/gui/gui.tar.bz2
Installing Juju machine agent
2018-04-13 09:52:18 INFO juju.cmd supercommand.go:56 running jujud [2.3.5 gc go1.10]
2018-04-13 09:52:20 INFO juju.agent identity.go:22 writing system identity file
2018-04-13 09:52:20 INFO juju.mongo mongo.go:461 Ensuring mongo server is running; data directory /var/lib/juju; port 37017
2018-04-13 09:52:20 INFO juju.mongo mongo.go:662 installing [juju-mongodb3.2 juju-mongo-tools3.2]
2018-04-13 09:52:20 INFO juju.utils.packaging.manager utils.go:57 Running: apt-get --option=Dpkg::Options::=--force-confold --option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install juju-mongodb3.2
2018-04-13 09:52:20 ERROR juju.utils.packaging.manager utils.go:102 packaging command failed: encountered fatal error: unable to locate package; cmd: "apt-get --option=Dpkg::Options::=--force-confold --option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install juju-mongodb3.2"; output: Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package juju-mongodb3.2
E: Couldn't find any package by glob 'juju-mongodb3.2'
E: Couldn't find any package by regex 'juju-mongodb3.2'

2018-04-13 09:52:20 ERROR juju.mongo mongo.go:485 cannot install/upgrade mongod (will proceed anyway): packaging command failed: encountered fatal error: unable to locate package
2018-04-13 09:52:20 INFO juju.mongo mongo.go:335 could not find /usr/lib/juju/bin/mongod or mongod in $PATH
ERROR failed to start mongo: exec: "mongod": executable file not found in $PATH
ERROR failed to bootstrap model: subprocess encountered error code 1
ERROR No controllers registered.

Please either create a new controller using "juju bootstrap" or connect to
another controller that you have been given access to using "juju register".

Download full text (3.1 KiB)

Bionic has changed the system libraries that will be available. We're
enabling Bionic support in 2.4 and have some limited support coming in Juju
2.3.6

John
=:->

On Fri, Apr 13, 2018, 14:30 Imran Khakoo <email address hidden> wrote:

> Public bug reported:
>
> When bootstrapping a Bionic node, the following error comes along:
>
> Attempt 1 to download agent binaries from
> https://streams.canonical.com/juju/tools/agent/2.3.5/juju-2.3.5-ubuntu-amd64.tgz.
> ..
> agent binaries from
> https://streams.canonical.com/juju/tools/agent/2.3.5/juju-2.3.5-ubuntu-amd64.tgz
> downloaded: HTTP 200; time 24.000261s; size 29262301 bytes; speed
> 1219262.000 bytes/s Agent binaries downloaded successfully.
> d2f393dafdc1095cf4e8a4cc077e9c918484bff416c91054749a21f89ef4f118
> /var/lib/juju/tools/2.3.5-bionic-amd64/tools.tar.gz
> 892e4b979b0bcee634a928c40f05641928af433baed8e381935becf95cb6651b
> /var/lib/juju/gui/gui.tar.bz2
> Installing Juju machine agent
> 2018-04-13 09:52:18 INFO juju.cmd supercommand.go:56 running jujud [2.3.5
> gc go1.10]
> 2018-04-13 09:52:20 INFO juju.agent identity.go:22 writing system identity
> file
> 2018-04-13 09:52:20 INFO juju.mongo mongo.go:461 Ensuring mongo server is
> running; data directory /var/lib/juju; port 37017
> 2018-04-13 09:52:20 INFO juju.mongo mongo.go:662 installing
> [juju-mongodb3.2 juju-mongo-tools3.2]
> 2018-04-13 09:52:20 INFO juju.utils.packaging.manager utils.go:57 Running:
> apt-get --option=Dpkg::Options::=--force-confold
> --option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install
> juju-mongodb3.2
> 2018-04-13 09:52:20 ERROR juju.utils.packaging.manager utils.go:102
> packaging command failed: encountered fatal error: unable to locate
> package; cmd: "apt-get --option=Dpkg::Options::=--force-confold
> --option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install
> juju-mongodb3.2"; output: Reading package lists...
> Building dependency tree...
> Reading state information...
> E: Unable to locate package juju-mongodb3.2
> E: Couldn't find any package by glob 'juju-mongodb3.2'
> E: Couldn't find any package by regex 'juju-mongodb3.2'
>
> 2018-04-13 09:52:20 ERROR juju.mongo mongo.go:485 cannot install/upgrade
> mongod (will proceed anyway): packaging command failed: encountered fatal
> error: unable to locate package
> 2018-04-13 09:52:20 INFO juju.mongo mongo.go:335 could not find
> /usr/lib/juju/bin/mongod or mongod in $PATH
> ERROR failed to start mongo: exec: "mongod": executable file not found in
> $PATH
> ERROR failed to bootstrap model: subprocess encountered error code 1
> ERROR No controllers registered.
>
> Please either create a new controller using "juju bootstrap" or connect to
> another controller that you have been given access to using "juju
> register".
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1763654
>
> Title:
> Can't bootstrap a bionic bootstrap node: juju-mongodb3.2 package
> missing
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/176...

Read more...

Erik Lönroth (erik-lonroth) wrote :

I ran in the the same problem with our xenial installation which suddenly stopped working today ( April 26).

http://paste.ubuntu.com/p/XBZ8GHCgJB/

juju 2.3.2 doesn't properly stick with Xenial as its target series. So now
that Bionic has become an officially released LTS, 2.3.2 is trying to
bootstrap it (but doesn't actually support it.)

Upgrading to 2.3.7 or use "juju bootstrap --bootstrap-series=xenial" should
make things work again.

On Thu, Apr 26, 2018 at 6:48 PM, Erik Lönroth <email address hidden>
wrote:

> I ran in the the same problem with our xenial installation which
> suddenly stopped working today ( April 26).
>
> http://paste.ubuntu.com/p/XBZ8GHCgJB/
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1763654
>
> Title:
> Can't bootstrap a bionic bootstrap node: juju-mongodb3.2 package
> missing
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1763654/+subscriptions
>

John A Meinel (jameinel) wrote :

2.3.5 and newer cannot bootstrap bionic because they changed the package archive.
However, juju 2.3.7 and beyond should support this fine.
(marking 2.3.8 because it isn't worth reopening 2.3.7)

Changed in juju:
milestone: none → 2.3.8
status: New → Fix Released
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers