manual: detection of cores fails on Packet Type 2A

[Andrew Wilkins]

I used manual provisioning to get Juju onto a Packet.net Type 2A machine (https://www.packet.net/bare-metal/servers/type-2a/). These machines have 96 cores, but Juju detects only 1 core, according to "juju status --format=yaml":

    hardware: arch=arm64 cores=1 mem=128878M

[Anastasia (anastasia-macmood)]

I am raising the Importance of this bug as incorrect cores value in status impacts usability.

[Edward Vielmetti (edward-vielmetti)]

What code does Juju execute to determine the number of cores on a system? I ask because there are several routines on the arm64 Type 2A machine at Packet.net that will return the right number for this system.

[Andrew Wilkins (axwalk)]

Edward, we cat /proc/cpuinfo and process it with the code here: https://github.com/juju/juju/blob/staging/environs/manual/sshprovisioner/sshprovisioner.go#L126

[Witold Krecicki (wpk)]

That's (google found) cpuinfo from Packet type 2A - https://gist.github.com/anonymous/d81912859fa1a26032c8e22f3af6bdc3

Current parser won't parse it correctly as there's no 'physical id'.

[Witold Krecicki (wpk)]

https://github.com/juju/juju/pull/7280