aarch64 Ubuntu 2204 with cloudstack 4.20.1 fails to create system vms, cloudstack agent log is still ''Unexpected arch null, expected aarch64''

[longxiaotian799]

Fixed by #10080

Originally posted by @rohityadavcloud in #10014
Have you ever tested on aarch64 Ubuntu 2204, or just on aarch64 Ubuntu 2404? I have chosen the aarch64 on the cluster creation step on the zone creation wizard.

[shwstppr]

@longxiaotian799 do you have agent logs in DEBUG mode?

[longxiaotian799]

agent.log

agent.err.log

some of the management-server.log

management-server.err.log

@longxiaotian799 do you have agent logs in DEBUG mode?

[longxiaotian799]

it is /usr/bin/arch cat /etc/os-release lscpu results.

[shwstppr]

@longxiaotian799 Logs are not in DEBUG but lets skip that for now. As you are on 4.20.1, can you please check the following:

1. Value of config - system.vm.preferred.architecture. Change it to aarch64 and check if it helps
2. What is the arch shown for the host in CloudStack UI?
3. Is there an aarch64 systemvm template registered for the zone?
4. Check if system VMs creation attempt is done using aarch64 template (check template used by errored VMs)

[shwstppr]

@longxiaotian799 Also, I've created #11254 which should solve the null arch being retrieved for the host

[longxiaotian799]

@longxiaotian799 Also, I've created #11254 which should solve the null arch being retrieved for the host

thanks a lot.how can I verify your PR works in easiest way？I installed it by deb，do i need to recompile deb？

[shwstppr]

@longxiaotian799 you can:

• Checkout 4.20.1.0 tag from repo
• Cherry-pick d62032f from agent: increase timeout for host arch retrieval #11254
• Compile the source
• Replace agent/target/cloud-agent-4.20.1.0.jar on host at /usr/share/cloudstack-agent/lib/

[longxiaotian799]

@longxiaotian799 Also, I've created #11254 which should solve the null arch being retrieved for the host

Can you please tell me why do you modify like this, and can you bet this cannot be wrong, and did you verify this PR on what OS and arch?

[shwstppr]

@longxiaotian799 I increased the timeout for /usr/bin/arch call done by the Agent Java code from 500ms to 1000ms.
I was running my test host on Oracle Linux 8, x86_64, and without changes, I was getting the null arch error.

[longxiaotian799]

@longxiaotian799 I increased the timeout for /usr/bin/arch call done by the Agent Java code from 500ms to 1000ms. I was running my test host on Oracle Linux 8, x86_64, and without changes, I was getting the null arch error.

why adding timeout can work? I am a software engineer doing a project of migrating CloudStack from x86 to arm, and eagerly can make it. Thanks very much.

[DaanHoogland]

@longxiaotian799 I increased the timeout for /usr/bin/arch call done by the Agent Java code from 500ms to 1000ms. I was running my test host on Oracle Linux 8, x86_64, and without changes, I was getting the null arch error.

why adding timeout can work? I am a software engineer doing a project of migrating CloudStack from x86 to arm, and eagerly can make it. Thanks very much.

Because the arch does not return in time to decide that it is arm64 and it reverts to the default (x86_64), @longxiaotian799 .