juju uses tools for the wrong architecture when unable to find correct tools

Bug #1227722 reported by Raphaël Badin on 2013-09-19
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
juju-core
Critical
Ian Booth

Bug Description

When bootstrapping an ARM/highbank MAAS node with juju version 1.14.0-saucy-amd64, the tools used where amd64 tools and thus the invocation of jujud by cloud-init on the bootstrap node failed (http://paste.ubuntu.com/6128521/).

Since I was bootstrapping with --upload-tools, I don't think tools for ARM could have been uploaded but juju should probably fail if it does not find the right tools instead of firing up a node and using the wrong tools on it.

Related branches

Raphaël Badin (rvb) wrote :

Looking at provider/maas/environ.go:acquireNode, it seems juju picks arbitrary tools (there is even a warning printed in verbose mode) instead of using compatible tools or erroring if nothing suitable can be found.

tags: added: maas
summary: - juju uses tools for the wrong architecture when boostraping a MAAS node
+ juju uses tools for the wrong architecture when boostrapping a MAAS node
summary: - juju uses tools for the wrong architecture when boostrapping a MAAS node
+ juju uses tools for the wrong architecture when bootstrapping a MAAS
+ node
John A Meinel (jameinel) wrote :

I have the feeling this has nothing to do with MaaS specifically. Just that Juju tries to find what tools are available, and what instance types would match, and then if it fails to match them it still tries to boot with a random configuration.

summary: - juju uses tools for the wrong architecture when bootstrapping a MAAS
- node
+ juju uses tools for the wrong architecture when unable to find correct
+ tools
Changed in juju-core:
importance: Undecided → High
status: New → Triaged
Curtis Hovey (sinzui) on 2013-10-14
tags: added: upload-tools
Curtis Hovey (sinzui) on 2014-02-27
tags: added: arm64
tags: added: server-hwe

This is related to https://bugs.launchpad.net/juju-core/+bug/1282869

On Fri, Feb 28, 2014 at 9:42 AM, Jason Hobbs <email address hidden> wrote:
> ** Tags added: server-hwe
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https://bugs.launchpad.net/bugs/1227722
>
> Title:
> juju uses tools for the wrong architecture when unable to find correct
> tools
>
> Status in juju-core:
> Triaged
>
> Bug description:
> When bootstrapping an ARM/highbank MAAS node with juju version 1.14.0
> -saucy-amd64, the tools used where amd64 tools and thus the invocation
> of jujud by cloud-init on the bootstrap node failed
> (http://paste.ubuntu.com/6128521/).
>
> Since I was bootstrapping with --upload-tools, I don't think tools for
> ARM could have been uploaded but juju should probably fail if it does
> not find the right tools instead of firing up a node and using the
> wrong tools on it.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1227722/+subscriptions

tags: added: ppc64el
Dave Cheney (dave-cheney) wrote :

Marking as critical as discussed due to the ppc64el depdendency.

Changed in juju-core:
importance: High → Critical
milestone: none → 1.18.0
Ian Booth (wallyworld) on 2014-03-16
Changed in juju-core:
assignee: nobody → Ian Booth (wallyworld)
status: Triaged → In Progress
John A Meinel (jameinel) on 2014-03-17
Changed in juju-core:
milestone: 1.18.0 → 1.17.6
Ian Booth (wallyworld) on 2014-03-19
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui) wrote :

This fix may be too strict. bug 1294632 reports that lxc bootstrap fails when it previously worked.

Curtis Hovey (sinzui) on 2014-03-20
Changed in juju-core:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers