juju-core on openstack failing with trusty

[Jonathan Davies]

When bootstrapping an instance of juju with trusty's juju (1.18.1) on a trusty image on OpenStack, I get:

The following packages have unmet dependencies:
 mongodb-server : Depends: mongodb-clients but it is not going to be installed
                  Depends: libboost-filesystem1.46.1 (>= 1.46.1-1) but it is not installable
                  Depends: libboost-program-options1.46.1 (>= 1.46.1-1) but it is not installable
                  Depends: libboost-system1.46.1 (>= 1.46.1-1) but it is not installable
                  Depends: libboost-thread1.46.1 (>= 1.46.1-1) but it is not installable
                  Depends: libgoogle-perftools0 but it is not installable

And bootstrap fails. Similar to bug #1168196.

[Curtis Hovey (sinzui)]

Was the default-series in environments.yaml set to trusty? The unmet deps are for precise state-servers....trusty would use juju-mongodb. If you mean to bootstrap the state-server on precise, you will need to allow the machine access to the cloud-tools archive. As your juju client is trusty, maybe you expect the state-server to also be trusty, and maybe it should be, but setting default-series in environments.yaml is the right way to specify the a trusty state-server.

[Jonathan Davies (jpds)]

There was no default-series set.

[Dave Cheney (dave-cheney)]

What has happened is *both* precise and *trusty* tools are available,
and juju chose the *precise* series tools and deployed them on a
trusty machine.

The tools know their series, that is why we have different tools for
different series. So these tools know they are for precise and apply
precise logic, specifically adding the cloud archive ppa and trying to
install mongodb-server.

The fault is the wrong tools were chosen.

On Wed, Jun 18, 2014 at 12:59 AM, Jonathan Davies
<email address hidden> wrote:
> There was no default-series set.
>
> ** Changed in: juju-core
> Status: Incomplete => Confirmed
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https://bugs.launchpad.net/bugs/1329256
>
> Title:
> juju-core on openstack failing with trusty
>
> Status in juju-core:
> Confirmed
>
> Bug description:
> When bootstrapping an instance of juju with trusty's juju (1.18.1) on
> a trusty image on OpenStack, I get:
>
> The following packages have unmet dependencies:
> mongodb-server : Depends: mongodb-clients but it is not going to be installed
> Depends: libboost-filesystem1.46.1 (>= 1.46.1-1) but it is not installable
> Depends: libboost-program-options1.46.1 (>= 1.46.1-1) but it is not installable
> Depends: libboost-system1.46.1 (>= 1.46.1-1) but it is not installable
> Depends: libboost-thread1.46.1 (>= 1.46.1-1) but it is not installable
> Depends: libgoogle-perftools0 but it is not installable
>
> And bootstrap fails. Similar to bug #1168196.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1329256/+subscriptions

[Pavel Malyshev (afunix)]

Please also update documents, because this page instructs to configure precise: http://maas.ubuntu.com/docs1.5/juju-quick-start.html and bootstrap fails.

[Anastasia (anastasia-macmood)]

We are closing this bug since "juju-core" project is now only open to Critical bugs against current Juju 1 series: 1.25.x

Logic for choosing tools has changed dramatically in both 1.25 and 2.0. Also precise is no longer supported.

If you disagree, please file a new bug against "juju" project with newer logs.