juju status reports incorrect number of cores for arm64 machines

[Paul Gear]

juju on amd64 reports the number of CPU cores correctly, but in the same environment on arm64, it reports 1 CPU when there are in fact 4: http://pastebin.ubuntu.com/17347848/

[Cheryl Jennings (cherylj)]

Looks like we're looking for "cpu cores". Can you paste the output of `cat /proc/cpuinfo | grep "cpu cores"`?

[Paul Gear (paulgear)]

No "cpu cores" on this architecture: http://pastebin.ubuntu.com/17351947/

[Sean Feole (sfeole)]

$ apt-cache policy juju
juju:
  Installed: 1:2.0.0-0ubuntu1~16.04.2~juju1
  Candidate: 1:2.0.0-0ubuntu1~16.04.2~juju1

I'm using juju 2.0.0

This no longer appears to be an issue as far as I can tell. JuJu is correctly Identifying the # of cores on 2 different platforms.

$ juju models
Controller: sfeoletest

Model Owner Status Machines Cores Access Last connection
controller* admin available 1 8 admin just now

Full bootstrap output below.

$ juju bootstrap --debug qa sfeoletest --constraints arch=arm64
13:56:56 INFO juju.cmd supercommand.go:63 running juju [2.0.0 gc go1.6.2]
13:56:56 DEBUG juju.cmd supercommand.go:64 args: []string{"juju", "bootstrap", "--debug", "qa", "sfeoletest", "--constraints", "arch=arm64"}
13:56:56 DEBUG juju.cmd.juju.commands bootstrap.go:538 provider attrs: map[]
13:56:59 INFO cmd cmd.go:141 Adding contents of "/home/ubuntu/.local/share/juju/ssh/juju_id_rsa.pub" to authorized-keys
13:56:59 DEBUG juju.cmd.juju.commands bootstrap.go:601 preparing controller with config: map[type:maas name:controller uuid:1cdcbbbb-bc53-49ef-8fd6-171c4c8301d8 authorized-keys:ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDIMa3p5qjBwrJBe+QB9iZvjkAkOe4I3VjRd3dsXJfjvfvspIlVkAdImIiXHStv5R0re0kzc/wIZrbhwTx7dpli94LFJQuhfmd1QuBaPi2ql1XcMyjOcstrOpojGsAa7uMOnPRPX/U5UT2/oqewpK/nsfxqulXb0ZxY9TtYMscaew6JbDHpHjhZQz21ja7t0v5kXFqN9MrRBN+o9bvO/Z9GvfPhDRgMLRgigKDUqD6oRbyhagp0dBm6SaLzsTdvMle+hLw9hg8WjazgBIJgOVY89h6maqayCSUoiYt1wLOTswy8tt6d9vD8xL3D101bqGY8mbf9cJ2NLhHLaAzNI0q3 juju-client-key
]
13:56:59 DEBUG juju.provider.maas environprovider.go:32 opening model "controller".
13:56:59 INFO cmd cmd.go:129 Creating Juju controller "sfeoletest" on qa
13:56:59 INFO juju.cmd.juju.commands bootstrap.go:744 combined bootstrap constraints: arch=arm64
13:56:59 DEBUG juju.environs.bootstrap bootstrap.go:185 model "controller" supports service/machine networks: true
13:56:59 DEBUG juju.environs.bootstrap bootstrap.go:187 network management by juju enabled: true
13:56:59 INFO cmd cmd.go:141 Loading image metadata
13:56:59 INFO cmd cmd.go:129 Looking for packaged Juju agent version 2.0.0 for arm64
13:56:59 INFO juju.environs.bootstrap tools.go:72 looking for bootstrap agent binaries: version=2.0.0
13:56:59 INFO juju.environs.tools tools.go:101 finding agent binaries in stream "released"
13:56:59 INFO juju.environs.tools tools.go:103 reading agent binaries with major.minor version 2.0
13:56:59 INFO juju.environs.tools tools.go:111 filtering agent binaries by version: 2.0.0
13:56:59 INFO juju.environs.tools tools.go:117 filtering agent binaries by architecture: arm64
13:56:59 DEBUG juju.environs.tools urls.go:109 trying datasource "keystone catalog"
13:56:59 DEBUG juju.environs.simplestreams simplestreams.go:680 using default candidate for content id "com.ubuntu.juju:released:tools" are {20161007 mirrors:1.0 content-download streams/v1/cpc-mirrors.sjson []}
13:57:01 INFO juju.environs.bootstrap tools.go:74 found 3 packaged agent binaries
13:57:01 INFO cmd cmd.go:141 Starting new instance for initial controller
Launching controller instance(s) on qa...
13:57:01 DEBUG juju.cloudconfig.instancecfg instancecfg.go:782 Setting numa c...

[Anastasia (anastasia-macmood)]

Thank you, Sean \o/