juju bootstrap defaults to i386

Bug #1304407 reported by James Page
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
Critical
Nate Finch
1.18
Fix Released
Critical
Ian Booth
juju-core (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

'juju bootstrap' on a private cloud with streams data for juju tools and images defaults to i386.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: juju-core 1.18.0-0ubuntu1
ProcVersionSignature: User Name 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
Date: Tue Apr 8 12:56:12 2014
Dependencies:
 gcc-4.9-base 4.9-20140330-0ubuntu1
 libc6 2.19-0ubuntu3
 libgcc1 1:4.9-20140330-0ubuntu1
 multiarch-support 2.19-0ubuntu3
Ec2AMI: ami-00000039
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: serverstack-az-1
Ec2InstanceType: m1.small
Ec2Kernel: aki-00000002
Ec2Ramdisk: ari-00000002
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Curtis Hovey (sinzui)
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
tags: added: metadata
Revision history for this message
Curtis Hovey (sinzui) wrote :

I wonder if this is a bug in juju metadata. I noticed recently that when I generate data for tools , 1.15.0 is always the version for amd64. I think the version is selected from the oldest tool found for the series+arch.

Metadata might be unrelated. Juju is trying to be smarter about selecting sane archs for clouds. Previously it assumed the remote arch was the same as the local arch. I don't see much evidence of i386 being a sane selection for a cloud. The primary use of juju i386 is to provide a client that can work with amd64 clouds.

Changed in juju-core:
milestone: none → 1.19.1
Revision history for this message
John A Meinel (jameinel) wrote :

I would target this to a 1.18.2 if it existed.
This is a change in behavior from 1.16 to 1.18. If you just do:
 juju-1.18 bootstrap -e amazon
I end up getting a i386 target. I have to do:
 juju-1.18 bootstrap -e amazon --constraints="arch=amd64"
for it to pick a amd64 (which was always the default in 1.16).
I would probably expect the tool to default to its own architecture (so if deploying from an amd64 prefer an amd64, etc).

summary: - juju bootstrap on openstack cloud defaults to i386
+ juju bootstrap defaults to i386
Robie Basak (racb)
Changed in juju-core (Ubuntu):
status: New → Triaged
Revision history for this message
Curtis Hovey (sinzui) wrote :

I have created a 1.18.2 milestone. I cannot reproduce this behaviour. I don't see CI doing it as well.

Revision history for this message
Curtis Hovey (sinzui) wrote :

I just saw this happen testing 1.19.0 deployment on aws fom my amd64 machine.

John A Meinel (jameinel)
Changed in juju-core:
importance: High → Critical
Nate Finch (natefinch)
Changed in juju-core:
assignee: nobody → Nate Finch (natefinch)
John A Meinel (jameinel)
Changed in juju-core:
status: Triaged → In Progress
Ian Booth (wallyworld)
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
Curtis Hovey (sinzui)
Changed in juju-core (Ubuntu):
status: Triaged → Fix Released
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.