question

MateuszAszyk avatar image
0 Votes"
MateuszAszyk asked MateuszAszyk commented

API returns wrong number of Cores

When I tried to get a number of Cores from AZ CLI or Python SDK then I got the wrong value.

Did you know about it?


[1]: https://pbs.twimg.com/media/EUty9OlWkAM3Ga0?format=png&name=360x360

azure-virtual-machines
· 6
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Can you share the document you are following or the API doc, so that I can try reproducing the issue? Thanks.

0 Votes 0 ·

@MateuszAszyk-7973 Is there any update?

0 Votes 0 ·

I replied below, please check.

0 Votes 0 ·

@karishmatiwari-msft Could you help me ?

0 Votes 0 ·
Show more comments
MateuszAszyk avatar image
0 Votes"
MateuszAszyk answered vipullag-MSFT commented

Hello,

First scenario:

The simplest reproducing is running the command:

 az vm list-sizes -l westeurope -o json

Then the command return:

   {
     "maxDataDiskCount": 32,
     "memoryInMb": 262144,
     "name": "Standard_E32-8s_v3",
     "numberOfCores": 32,
     "osDiskSizeInMb": 1047552,
     "resourceDiskSizeInMb": 524288
   },

The second scenario is when I tried called to API by Python.

I used method list from VirtualMachineSizesOperations and the number is the same.

Both scenarios are run in West and North Europe.

Regards,
Mateusz.


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@MateuszAszyk

Just an update on the issue. Internal team has acknowledged the wrong cpu in CLI response for few VM sizes. Standard_E4-2s_v3, Standard_E4-2ds_v4 & Standard_E4-2s_v4 has wrong vCPUsAvailable and team is working on fixing these.

However, for other VM sizes mentioned in the constrained doc, the sizes are showing correct on CLI, you can verify once from API also.

Below is one screenshot for your reference(Standard_E8-4ds_v4). You need to check the vCPUsAvailable value from the response.

10160-4-cpu.jpg

10382-standard-e8-4ds-v4.jpg

10335-standard-e8ds-v4.jpg


0 Votes 0 ·
4-cpu.jpg (11.2 KiB)
vipullag-MSFT avatar image
0 Votes"
vipullag-MSFT answered MateuszAszyk commented

@MateuszAszyk Apologies for the delay in getting back on this.
Thanks for sharing the details.

As per this document for Standard_E4s_v3 cores are 4 and also this VM size has the Constrained core sizes availability.
In the Constrained vCPU capable VM sizes document CPU mentioned from Standard_E4-2s_v3 is 2.

As per the Constrained vCPU capable VM sizes document, The vCPU count can be constrained to one half or one quarter of the original VM size. These new VM sizes have a suffix that specifies the number of active vCPUs to make them easier for you to identify.

I have checked this Azure CLI and see that the cores returned from the CLI response is the original cores for the Standard_E4s_v3 and not the Constrained size.

I have reached to internal team to get more information on this. I will update you back on this.

10254-cpu-cores.jpg



cpu-cores.jpg (77.9 KiB)
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@vipullag-MSFT

A year later,

Azure CLI is working the same, returns the wrong count of CPUs.

Do you have a roadmap to fix it?

Regards,
Mateusz

0 Votes 0 ·