Somaimo opened a new issue, #10014:
URL: https://github.com/apache/cloudstack/issues/10014
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
User Interface
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.20.0 RC3
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
New installation on arm64 Hardware (Radxa Rock 5B (but I don't think this
matters). With the Management Server and KVM Host on the same hardware (as a
test environment).
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
Ubuntu 24.04
##### SUMMARY
<!-- Explain the problem/feature briefly -->
The configuration wizard on a new installation, after log in, fails to add a
host, because the wizard seems to set the cluster architecture to x86_64 and
the kvm host is aarch64. The wizard also doesn't allow an option to change the
architecture type on the cluster. A corresponding error message also is logged
in the ```management-server.log```
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
Install a new management server (either on amd64 or aarch64 hardware) and
install a new kvm host on aarch64 hardware. Use the configuration wizard on the
user interface to create a new zone, pod, cluster and add the kvm host. The
process should timeout at "Adding host".
<!-- Paste example playbooks or commands between quotes below -->
~~~
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
Able to set the cpu architecture during the cluster creation step in the
configuration wizard.
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
No optionto set the cpu architecture for the cluster in the configuration
wizard
~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
