arm64 shows 1 vs. 96 cores via Juju GUI version 2.10.2

Bug #1732004 reported by mahmoh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Expired
Undecided
Unassigned

Bug Description

2.0.2-xenial-amd64

2.0.2-0ubuntu0.16.04.2

0
0 units, xenial, arch: arm64, cpuCores: 1, mem: 125.85GB

$ juju ssh 0 'cat /proc/cpuinfo| tail'
sign_and_send_pubkey: signing failed: agent refused operation

processor : 95
BogoMIPS : 200.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x43
CPU architecture: 8
CPU variant : 0x1
CPU part : 0x0a1
CPU revision : 1

Revision history for this message
Witold Krecicki (wpk) wrote :

Could you paste the output of juju show-machine 0?
Could you also paste the full output of /proc/cpuinfo so that we could include it in our tests when we find out what's the problem?

Revision history for this message
mahmoh (mahmoh) wrote :

Gladly. This has happened before: https://bugs.launchpad.net/juju/+bug/1592613

$ juju show-machine 0
model: default
machines:
  "0":
    juju-status:
      current: started
      since: 13 Nov 2017 13:49:43-05:00
      version: 2.0.2
    dns-name: 147.75.33.34
    ip-addresses:
    - 147.75.33.34
    - 2604:1380:2000:2b00::9
    - 10.80.7.139
    instance-id: manual:147.75.33.34
    machine-status:
      current: pending
      since: 13 Nov 2017 13:47:53-05:00
    series: xenial
    hardware: arch=arm64 cores=1 mem=128872M
$ juju ssh 0 'cat /proc/cpuinfo' > cpuinfo-arm64-thunderx.txt
sign_and_send_pubkey: signing failed: agent refused operation
Connection to 147.75.33.34 closed.
$ juju ssh 0 'uname -a '
sign_and_send_pubkey: signing failed: agent refused operation
Linux node0 4.10.0-38-generic #42~16.04.1-Ubuntu SMP Tue Oct 10 16:33:57 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux
Connection to 147.75.33.34 closed.
$ juju ssh 0 'lsb_release -a'
sign_and_send_pubkey: signing failed: agent refused operation
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
Connection to 147.75.33.34 closed.

Revision history for this message
mahmoh (mahmoh) wrote :

This was using juju manual provider.

Revision history for this message
Witold Krecicki (wpk) wrote :

This issue should be fixed in Juju 2.2, could you try using it?

Changed in juju-core:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for juju-core because there has been no activity for 60 days.]

Changed in juju-core:
status: Incomplete → Expired
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.