juju bootstrap defaults to i386
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
ProcVersionSign
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-
libc6 2.19-0ubuntu3
libgcc1 1:4.9-20140330-
multiarch-support 2.19-0ubuntu3
Ec2AMI: ami-00000039
Ec2AMIManifest: FIXME
Ec2Availability
Ec2InstanceType: m1.small
Ec2Kernel: aki-00000002
Ec2Ramdisk: ari-00000002
ProcEnviron:
TERM=screen
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
- Juju Engineering: Pending requested
-
Diff: 148 lines (+69/-3)4 files modifiedenvirons/instances/image.go (+22/-1)
environs/instances/image_test.go (+39/-0)
provider/ec2/ec2.go (+1/-1)
provider/ec2/image.go (+7/-1)
- Juju Engineering: Pending requested
-
Diff: 138 lines (+65/-2)4 files modifiedenvirons/instances/image.go (+24/-1)
environs/instances/image_test.go (+39/-0)
provider/ec2/export_test.go (+1/-0)
provider/ec2/image_test.go (+1/-1)
- Juju Engineering: Pending requested
-
Diff: 149 lines (+68/-5)4 files modifiedenvirons/instances/image.go (+27/-4)
environs/instances/image_test.go (+39/-0)
provider/ec2/export_test.go (+1/-0)
provider/ec2/image_test.go (+1/-1)
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: metadata |
Changed in juju-core (Ubuntu): | |
status: | New → Triaged |
Changed in juju-core: | |
importance: | High → Critical |
Changed in juju-core: | |
assignee: | nobody → Nate Finch (natefinch) |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Changed in juju-core (Ubuntu): | |
status: | Triaged → Fix Released |
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.