version reports "armhf" on arm64

Bug #1304742 reported by dann frazier
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
Critical
Ian Booth
1.18
Fix Released
Critical
Ian Booth

Bug Description

On arm64, juju --version reports being on armhf:

ubuntu@dannf1:~$ uname -m
aarch64
ubuntu@dannf1:~$ juju --version
1.18.0-trusty-armhf

The issue is that arch.go uses archREs to footprint the architecture based on "runtime.GOARCH". However, as per the comment var above archREs, it is a map of `uname -m` output to juju arch. In the case of arm64, runtime.GOARCH != `uname -m`. runtime.GOARCH is "arm64" and `uname -m` is "aarch64".

This may just be a cosmetic problem, but I do see version.Current used in various places (e.g. to look for upgrades), so just in case there be dragons here....

I did some checking and confirmed that the selection of runtime.GOARCH for this platform is intentional (I first guessed a bug in gccgo).

Tags: arm64 hs-arm64

Related branches

dann frazier (dannf)
description: updated
Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 1304742] [NEW] version reports "armhf" on arm64

It should report arm64, but it certainly shouldn't be giving armhf (which
would be the 32 bit version).

We need it to say arm64 internally because when it goes to look for tools,
it will look for something matching that string.

On Wed, Apr 9, 2014 at 4:34 AM, dann frazier <email address hidden>wrote:

> Public bug reported:
>
> On arm64, juju --version reports being on armhf:
>
> ubuntu@dannf1:~$ uname -m
> aarch64
> ubuntu@dannf1:~$ juju --version
> 1.18.0-trusty-armhf
>
> The issue is that arch.go uses archREs to footprint the architecture
> based on "runtime.GOARCH". However, as per the comment var above
> archREs, it is a map of `uname -m` output to juju arch. In the case of
> arm64, runtime.GOARCH != `uname -m`. runtime.GOARCH is "arm64" and
> `uname -m` is "aarch64".
>
> This may just be a cosmetic problem, but I do see version.Current used
> in various places (e.g. to look for upgrades), so just in case there be
> dragons here....
>
> I did some checking and confirmed that the selection of runtime.GOARCH
> for this platform is intentional (I first guessed a bug in gccgo).
>
> ** Affects: juju-core
> Importance: Undecided
> Status: New
>
>
> ** Tags: arm64 hs-arm64
>
> ** Description changed:
>
> On arm64, juju --version reports being on armhf:
>
> ubuntu@dannf1:~$ uname -m
> aarch64
> ubuntu@dannf1:~$ juju --version
> 1.18.0-trusty-armhf
>
> The issue is that arch.go uses archREs to footprint the architecture
> based on "runtime.GOARCH". However, as per the comment var above
> archREs, it is a map of `uname -m` output to juju arch. In the case of
> arm64, runtime.GOARCH != `uname -m`. runtime.GOARCH is "arm64" and
> `uname -m` is "aarch64".
>
> This may just be a cosmetic problem, but I do see version.Current used
> in various places (e.g. to look for upgrades), so just in case there be
> dragons here....
> +
> + I did some checking and confirmed that the selection of runtime.GOARCH
> + for this platform is intentional (I first guessed a bug in gccgo).
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> https://bugs.launchpad.net/bugs/1304742
>
> Title:
> version reports "armhf" on arm64
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1304742/+subscriptions
>

Revision history for this message
John A Meinel (jameinel) wrote :

I think this will break --upload-tools behavior, so it seems rather important for arm64 enablement.

Changed in juju-core:
importance: Undecided → Critical
milestone: none → 1.19.0
status: New → Triaged
Ian Booth (wallyworld)
Changed in juju-core:
assignee: nobody → Ian Booth (wallyworld)
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
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.