Hi,

CloudStack 4.23 can run with Java 21.

Have you already configured Linux bridges on the host ?

Kind regards,
Wei


On Thu, Sep 10, 2026 at 3:43 PM Drew Weaver <[email protected]> wrote:

> Hello,
>
> I am attempting to setup version 4.23.0.0 in a basic lab environment with
> one hypervisor running AlmaLinux 10.2.
>
> The management server (also running Almalinux 10.2) seems to work okay
> meaning that the UI loads and seems to function properly.
>
> However anytime I attempt to add this hypervisor as a host I keep seeing
> this in the management-server.log
>
> 2026-09-10 09:32:44,733 DEBUG [c.c.u.s.SSHCmdHelper]
> (qtp1860491691-42:[ctx-c03b659b, ctx-0f99dae7]) (logid:5530e197) SSH
> command: sudo
> /usr/share/cloudstack-common/scripts/util/keystore-cert-import
> /etc/cloudstack/agent/agent.properties xxx /etc/cloudstack/agent/
> SSH command output:
> chmod: cannot access '/etc/cloudstack/agent/cloud.key': No such file or
> directory
>
> The file /etc/cloudstack/agent/cloud.key doesn't exist. The directory
> looks like this:
>
> drwxr-xr-x 2 root root   177 Sep 10 09:35 .
> drwxr-xr-x 3 root root    19 Sep 10 09:18 ..
> -rw------- 1 root root 22258 Sep 10 09:25 agent.properties
> -rwxr-x--- 1 root root  1814 Sep 10 09:32 cloud.ca.crt
> -rwxr-x--- 1 root root  1826 Sep 10 09:32 cloud.crt
> -rw------- 1 root root  1447 Sep 10 09:32 cloud.csr
> -rw------- 1 root root  6534 Sep 10 09:32 cloud.jks
> -rwxr-xr-x 1 root root   904 Sep  1 16:50 environment.properties
> -rwxr-xr-x 1 root root  2601 Sep  1 16:50 log4j-cloud.xml
> -rwxr-xr-x 1 root root  1114 Sep  1 16:50 uefi.properties
>
> I had two general questions.
>
>
>   1.  Does Cloudstack 4.23 require Java17 exactly or Java17 or newer? This
> system seems to have Java21 on it which I guess is the default for Alma10.
>   2.  Does Cloudstack 4.23 support/work with NetworkManager? I noticed
> last week when I was trying this on another hypervisor/lab machine that it
> seemed like CloudStack was trying to use old style 'service network
> restart' type commands when interacting with that other hypervisor which
> was also Alma10.
>
>
> Thanks for any information anyone can provide.
>
> -Drew
>
>
>

Reply via email to