Re: ha checks on kvm hosts running even with ha disabled

[Slavka Peleva]

Hi Swen,

The KVMHAMonitor is initialised here

even
if you didn't enable the HA.
If I may advise you to disable in the `agent.properties` file the property
`reboot.host.and.alert.management.on.heartbeat.timeout=false`. CloudStack
will still execute the heartbeat check but won't restart the agent host on
failure.

Best regards,
Slavka

On Tue, Feb 20, 2024 at 12:41 AM Swen  wrote:

> Hi all,
>
> we encountered a strange issue today in our lab installation. We are
> running
> CS 4.19.0 upgraded from CS 4.18.1 with linstor as primary storage. We are
> using a linstor jar file provided by Linbit which is not the default one
> part of default
> 4.19.0!
>
> This updated plugin already includes a new feature to use linstor storage
> for host
> ha. I provide this only for information reasons.
>
> The issue we encountered was that even we do not have HA enabled on
> cluster and host level, cloudstack agent on our KVM hosts triggered HA
> actions and rebooted our hosts. We found this on our agent.log:
>
> Feb 19 11:53:05 pc-kvm-2 java[6617]: WARN  [kvm.resource.KVMHAMonitor]
> (Thread-1:) (logid:) Write heartbeat for pool
> [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 2 of 5.
>
> Feb 19 11:58:58 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
> (Thread-1:) (logid:) Write heartbeat for pool
> [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 3 of 5.
>
> Feb 19 12:00:08 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
> (Thread-1:) (logid:) Write heartbeat for pool
> [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 4 of 5.
>
> Feb 19 12:01:08 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
> (Thread-1:) (logid:) Write heartbeat for pool
> [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 5 of 5.
>
> Feb 19 12:01:08 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
> (Thread-1:) (logid:) Write heartbeat for pool
> [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; stopping
> cloudstack-agent.
>
> Feb 19 12:02:08 pc-kvm-2 heartbeat: kvmspheartbeat.sh will reboot system
> because it was unable to write the heartbeat to the storage.
>
> We and Linbit did some debugging. We tried to understand why the
> cloudstack agent is running those checks in the first place. We were unable
> to find any code which
> checks if host HA is enabled or not and will not perform HA tasks if HA is
> disabled. Can somebody please double-check this?
>
> Thank you very much!
>
> Regards,
> Swen
>
>
>

Re: K8s Dashboard Not Found

[Bharat Bhushan Saini]

Hi Wei,

I made the ISO from cloudstack-comman and that ISO was of latest version 1.29.1.

Thanks and Regards,
Bharat Saini

[signature_698188016]

From: Wei ZHOU 
Date: Tuesday, 20 February 2024 at 12:28 PM
To: users@cloudstack.apache.org 
Subject: Re: K8s Dashboard Not Found
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Which CKS ISO do you use?

On Tuesday, February 20, 2024, Bharat Bhushan Saini
 wrote:

> Hi All,
>
> I enabled the CKS service in the cloudstack dashboard. After all the
> things done I am unable to access the K8s dashboard.
>
> I encountered in the browser that ‘services “Kubernetes-dashboard” not
> found’.
>
> Kindly suggest any resolvement for this.
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_2321445983]
>
> --- Disclaimer: --
> This message and its contents are intended solely for the designated
> addressee and are proprietary to Kloudspot. The information in this email
> is meant exclusively for Kloudspot business use. Any use by individuals
> other than the addressee constitutes misuse and an infringement of
> Kloudspot's proprietary rights. If you are not the intended recipient,
> please return this email to the sender. Kloudspot cannot guarantee the
> security or error-free transmission of e-mail communications. Information
> could be intercepted, corrupted, lost, destroyed, arrive late or
> incomplete, or contain viruses. Therefore, Kloudspot shall not be liable
> for any issues arising from the transmission of this email.
>

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. Therefore, Kloudspot 
shall not be liable for any issues arising from the transmission of this email.

Re: K8s Dashboard Not Found

[Bharat Bhushan Saini]

Hi,

I am hitting below URL
http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/
http://10.x.x.185:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/
 (mentioned in the config cluster)
Below some more info that will help you to recognise as below

kubectl --kubeconfig kube.conf get pods --all-namespaces

NAMESPACE  NAME 
   READY   STATUSRESTARTS  AGE

kube-systemcoredns-76f75df574-lfgzj 
   1/1 Running   0 22h

kube-systemcoredns-76f75df574-mtktc 
   1/1 Running   0 22h

kube-systemetcd-kloudspot-app-control-18dc0a3d55e   
   1/1 Running   0 22h

kube-systemkube-apiserver-kloudspot-app-control-18dc0a3d55e 
   1/1 Running   0 22h

kube-system
kube-controller-manager-kloudspot-app-control-18dc0a3d55e   1/1 Running   0 
22h

kube-systemkube-proxy-74zcb 
   1/1 Running   0 22h

kube-systemkube-proxy-hts4p 
   1/1 Running   0 22h

kube-systemkube-scheduler-kloudspot-app-control-18dc0a3d55e 
   1/1 Running   0 22h

kube-systemweave-net-8j6j2  
   2/2 Running   0 22h

kube-systemweave-net-mlv6t  
   2/2 Running   1 (22h ago)   22h

kubernetes-dashboard   kubernetes-dashboard-api-645688966c-8xqjp
   1/1 Running   0 22h

kubernetes-dashboard   kubernetes-dashboard-metrics-scraper-b847579df-tjw86 
   1/1 Running   0 22h

kubernetes-dashboard   kubernetes-dashboard-web-648b489598-psn94
   1/1 Running   0 22h


kubectl --kubeconfig kube.conf get nodes --all-namespaces

NAMESTATUS   ROLES   AGE   VERSION

kloudspot-app-control-18dc0a3d55e   Readycontrol-plane   22h   v1.29.2

kloudspot-app-node-18dc0a3f52e  Ready  22h   v1.29.2


kubectl --kubeconfig kube.conf get services --all-namespaces

NAMESPACE  NAME   TYPE
CLUSTER-IP   EXTERNAL-IP   PORT(S)  AGE

defaultkubernetes ClusterIP   
10.96.0.1443/TCP  22h

kube-systemkube-dns   ClusterIP   
10.96.0.10   53/UDP,53/TCP,9153/TCP   22h

kubernetes-dashboard   kubernetes-dashboard-api   ClusterIP   
10.102.124.599000/TCP 22h

kubernetes-dashboard   kubernetes-dashboard-metrics-scraper   ClusterIP   
10.111.159.255   8000/TCP 22h

kubernetes-dashboard   kubernetes-dashboard-web   ClusterIP   
10.108.135.214   8000/TCP 22h


Thanks and Regards,
Bharat Saini

[signature_828139211]

From: Vivek Kumar 
Date: Tuesday, 20 February 2024 at 12:17 PM
To: Bharat Bhushan Saini 
Cc: users@cloudstack.apache.org 
Subject: Re: K8s Dashboard Not Found
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.

Can you share me the URL which you are hitting on the browser ?


Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies
[Image removed by sender.]
vivek.ku...@indiqus.com
[Image removed by sender.]
www.indiqus.com



On 20-Feb-2024, at 12:12 PM, Bharat Bhushan Saini  
wrote:

Hi Vivek,

I am trying to access the dashboard from kubectl proxy.

Thanks and Regards,
Bharat Saini



From: Vivek Kumar via users 
mailto:users@cloudstack.apache.org>>
Date: Tuesday, 20 February 2024 at 12:08 PM
To: users@cloudstack.apache.org 
mailto:users@cloudstack.apache.org>>
Subject: Re: K8s Dashboard Not Found
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,

How are you accessing the dashboard ?  Using the kubeclt proxy ?

Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 

www.indiqus.com 




> On 20-Feb-2024, at 12:00 PM, Bharat Bhushan Saini 
> mailto:bharat.sa...@kloudspot.com.INVALID>>
>  wrote:
>
> Hi All,
>
> I enabled the CKS service in the cloudstack dashboard. After all the things 
> done I am unable to access the K8s dashboard.

Re: K8s Dashboard Not Found

[Bharat Bhushan Saini]

Hi,

I am hittine below URL
http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/

Below some more info that will help you to recognise as below

kubectl --kubeconfig kube.conf get pods --all-namespaces

NAMESPACE  NAME 
   READY   STATUSRESTARTS  AGE

kube-systemcoredns-76f75df574-lfgzj 
   1/1 Running   0 22h

kube-systemcoredns-76f75df574-mtktc 
   1/1 Running   0 22h

kube-systemetcd-kloudspot-app-control-18dc0a3d55e   
   1/1 Running   0 22h

kube-systemkube-apiserver-kloudspot-app-control-18dc0a3d55e 
   1/1 Running   0 22h

kube-system
kube-controller-manager-kloudspot-app-control-18dc0a3d55e   1/1 Running   0 
22h

kube-systemkube-proxy-74zcb 
   1/1 Running   0 22h

kube-systemkube-proxy-hts4p 
   1/1 Running   0 22h

kube-systemkube-scheduler-kloudspot-app-control-18dc0a3d55e 
   1/1 Running   0 22h

kube-systemweave-net-8j6j2  
   2/2 Running   0 22h

kube-systemweave-net-mlv6t  
   2/2 Running   1 (22h ago)   22h

kubernetes-dashboard   kubernetes-dashboard-api-645688966c-8xqjp
   1/1 Running   0 22h

kubernetes-dashboard   kubernetes-dashboard-metrics-scraper-b847579df-tjw86 
   1/1 Running   0 22h

kubernetes-dashboard   kubernetes-dashboard-web-648b489598-psn94
   1/1 Running   0 22h


kubectl --kubeconfig kube.conf get nodes --all-namespaces

NAMESTATUS   ROLES   AGE   VERSION

kloudspot-app-control-18dc0a3d55e   Readycontrol-plane   22h   v1.29.2

kloudspot-app-node-18dc0a3f52e  Ready  22h   v1.29.2


kubectl --kubeconfig kube.conf get services --all-namespaces

NAMESPACE  NAME   TYPE
CLUSTER-IP   EXTERNAL-IP   PORT(S)  AGE

defaultkubernetes ClusterIP   
10.96.0.1443/TCP  22h

kube-systemkube-dns   ClusterIP   
10.96.0.10   53/UDP,53/TCP,9153/TCP   22h

kubernetes-dashboard   kubernetes-dashboard-api   ClusterIP   
10.102.124.599000/TCP 22h

kubernetes-dashboard   kubernetes-dashboard-metrics-scraper   ClusterIP   
10.111.159.255   8000/TCP 22h

kubernetes-dashboard   kubernetes-dashboard-web   ClusterIP   
10.108.135.214   8000/TCP 22h


Thanks and Regards,
Bharat Saini

[signature_828139211]

From: Vivek Kumar 
Date: Tuesday, 20 February 2024 at 12:17 PM
To: Bharat Bhushan Saini 
Cc: users@cloudstack.apache.org 
Subject: Re: K8s Dashboard Not Found
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.

Can you share me the URL which you are hitting on the browser ?


Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies
[Image removed by sender.]
vivek.ku...@indiqus.com
[Image removed by sender.]
www.indiqus.com




On 20-Feb-2024, at 12:12 PM, Bharat Bhushan Saini  
wrote:

Hi Vivek,

I am trying to access the dashboard from kubectl proxy.

Thanks and Regards,
Bharat Saini



From: Vivek Kumar via users 
mailto:users@cloudstack.apache.org>>
Date: Tuesday, 20 February 2024 at 12:08 PM
To: users@cloudstack.apache.org 
mailto:users@cloudstack.apache.org>>
Subject: Re: K8s Dashboard Not Found
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,

How are you accessing the dashboard ?  Using the kubeclt proxy ?

Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 

www.indiqus.com 




> On 20-Feb-2024, at 12:00 PM, Bharat Bhushan Saini 
> mailto:bharat.sa...@kloudspot.com.INVALID>>
>  wrote:
>
> Hi All,
>
> I enabled the CKS service in the cloudstack dashboard. After all the things 
> done I am unable to access the K8s dashboard.
> I encountered in the browser that ‘services “Kubernetes-dashboard” not found’.
>
> Kindly suggest any resolvement for this.
>
> Thanks 

Re: K8s Dashboard Not Found

[Wei ZHOU]

Which CKS ISO do you use?

On Tuesday, February 20, 2024, Bharat Bhushan Saini
 wrote:

> Hi All,
>
> I enabled the CKS service in the cloudstack dashboard. After all the
> things done I am unable to access the K8s dashboard.
>
> I encountered in the browser that ‘services “Kubernetes-dashboard” not
> found’.
>
> Kindly suggest any resolvement for this.
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_2321445983]
>
> --- Disclaimer: --
> This message and its contents are intended solely for the designated
> addressee and are proprietary to Kloudspot. The information in this email
> is meant exclusively for Kloudspot business use. Any use by individuals
> other than the addressee constitutes misuse and an infringement of
> Kloudspot's proprietary rights. If you are not the intended recipient,
> please return this email to the sender. Kloudspot cannot guarantee the
> security or error-free transmission of e-mail communications. Information
> could be intercepted, corrupted, lost, destroyed, arrive late or
> incomplete, or contain viruses. Therefore, Kloudspot shall not be liable
> for any issues arising from the transmission of this email.
>

Re: K8s Dashboard Not Found

[Vivek Kumar]

Can you share me the URL which you are hitting on the browser ?


Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 20-Feb-2024, at 12:12 PM, Bharat Bhushan Saini 
>  wrote:
> 
> Hi Vivek,
>  
> I am trying to access the dashboard from kubectl proxy.
>  
> Thanks and Regards,
> Bharat Saini
>  
> 
>  
> From: Vivek Kumar via users  >
> Date: Tuesday, 20 February 2024 at 12:08 PM
> To: users@cloudstack.apache.org  
> mailto:users@cloudstack.apache.org>>
> Subject: Re: K8s Dashboard Not Found
> 
> EXTERNAL EMAIL: Please verify the sender email address before taking any 
> action, replying, clicking any link or opening any attachment.
> 
> 
> Hello Bharat,
> 
> How are you accessing the dashboard ?  Using the kubeclt proxy ?
> 
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> TechOps | Indiqus Technologies
> 
> vivek.ku...@indiqus.com  
> 
> www.indiqus.com  
> 
> 
> 
> 
> > On 20-Feb-2024, at 12:00 PM, Bharat Bhushan Saini 
> >  > > wrote:
> >
> > Hi All,
> >
> > I enabled the CKS service in the cloudstack dashboard. After all the things 
> > done I am unable to access the K8s dashboard.
> > I encountered in the browser that ‘services “Kubernetes-dashboard” not 
> > found’.
> >
> > Kindly suggest any resolvement for this.
> >
> > Thanks and Regards,
> > Bharat Saini
> >
> >
> > --- Disclaimer: --
> > This message and its contents are intended solely for the designated 
> > addressee and are proprietary to Kloudspot. The information in this email 
> > is meant exclusively for Kloudspot business use. Any use by individuals 
> > other than the addressee constitutes misuse and an infringement of 
> > Kloudspot's proprietary rights. If you are not the intended recipient, 
> > please return this email to the sender. Kloudspot cannot guarantee the 
> > security or error-free transmission of e-mail communications. Information 
> > could be intercepted, corrupted, lost, destroyed, arrive late or 
> > incomplete, or contain viruses. Therefore, Kloudspot shall not be liable 
> > for any issues arising from the transmission of this email.
> >
> 
> 
> --
> This message is intended only for the use of the individual or entity to
> which it is addressed and may contain confidential and/or privileged
> information. If you are not the intended recipient, please delete the
> original message and any copy of it from your computer system. You are
> hereby notified that any dissemination, distribution or copying of this
> communication is strictly prohibited unless proper authorization has been
> obtained for such action. If you have received this communication in error,
> please notify the sender immediately. Although IndiQus attempts to sweep
> e-mail and attachments for viruses, it does not guarantee that both are
> virus-free and accepts no liability for any damage sustained as a result of
> viruses.
> --- Disclaimer: -- 
> This message and its contents are intended solely for the designated 
> addressee and are proprietary to Kloudspot. The information in this email is 
> meant exclusively for Kloudspot business use. Any use by individuals other 
> than the addressee constitutes misuse and an infringement of Kloudspot's 
> proprietary rights. If you are not the intended recipient, please return this 
> email to the sender. Kloudspot cannot guarantee the security or error-free 
> transmission of e-mail communications. Information could be intercepted, 
> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. 
> Therefore, Kloudspot shall not be liable for any issues arising from the 
> transmission of this email.
> 


-- 
This message is intended only for the use of the individual or entity to 
which it is addressed and may contain confidential and/or privileged 
information. If you are not the intended recipient, please delete the 
original message and any copy of it from your computer system. You are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited unless proper authorization has been 
obtained for such action. If you have received this communication in error, 
please notify the sender immediately. Although IndiQus attempts to sweep 
e-mail and attachments for viruses, it does not guarantee that both are 
virus-free and accepts no liability for any damage sustained as a result of 
viruses.

Re: K8s Dashboard Not Found

[Bharat Bhushan Saini]

Hi Vivek,

I am trying to access the dashboard from kubectl proxy.

Thanks and Regards,
Bharat Saini

[signature_1904648499]

From: Vivek Kumar via users 
Date: Tuesday, 20 February 2024 at 12:08 PM
To: users@cloudstack.apache.org 
Subject: Re: K8s Dashboard Not Found
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,

How are you accessing the dashboard ?  Using the kubeclt proxy ?

Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 20-Feb-2024, at 12:00 PM, Bharat Bhushan Saini 
>  wrote:
>
> Hi All,
>
> I enabled the CKS service in the cloudstack dashboard. After all the things 
> done I am unable to access the K8s dashboard.
> I encountered in the browser that ‘services “Kubernetes-dashboard” not found’.
>
> Kindly suggest any resolvement for this.
>
> Thanks and Regards,
> Bharat Saini
>
>
> --- Disclaimer: --
> This message and its contents are intended solely for the designated 
> addressee and are proprietary to Kloudspot. The information in this email is 
> meant exclusively for Kloudspot business use. Any use by individuals other 
> than the addressee constitutes misuse and an infringement of Kloudspot's 
> proprietary rights. If you are not the intended recipient, please return this 
> email to the sender. Kloudspot cannot guarantee the security or error-free 
> transmission of e-mail communications. Information could be intercepted, 
> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. 
> Therefore, Kloudspot shall not be liable for any issues arising from the 
> transmission of this email.
>


--
This message is intended only for the use of the individual or entity to
which it is addressed and may contain confidential and/or privileged
information. If you are not the intended recipient, please delete the
original message and any copy of it from your computer system. You are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited unless proper authorization has been
obtained for such action. If you have received this communication in error,
please notify the sender immediately. Although IndiQus attempts to sweep
e-mail and attachments for viruses, it does not guarantee that both are
virus-free and accepts no liability for any damage sustained as a result of
viruses.

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. Therefore, Kloudspot 
shall not be liable for any issues arising from the transmission of this email.

Re: K8s Dashboard Not Found

[Vivek Kumar via users]

Hello Bharat, 

How are you accessing the dashboard ?  Using the kubeclt proxy ? 

Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 20-Feb-2024, at 12:00 PM, Bharat Bhushan Saini 
>  wrote:
> 
> Hi All,
> 
> I enabled the CKS service in the cloudstack dashboard. After all the things 
> done I am unable to access the K8s dashboard.
> I encountered in the browser that ‘services “Kubernetes-dashboard” not found’.
> 
> Kindly suggest any resolvement for this.
>  
> Thanks and Regards,
> Bharat Saini
>  
> 
> --- Disclaimer: -- 
> This message and its contents are intended solely for the designated 
> addressee and are proprietary to Kloudspot. The information in this email is 
> meant exclusively for Kloudspot business use. Any use by individuals other 
> than the addressee constitutes misuse and an infringement of Kloudspot's 
> proprietary rights. If you are not the intended recipient, please return this 
> email to the sender. Kloudspot cannot guarantee the security or error-free 
> transmission of e-mail communications. Information could be intercepted, 
> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. 
> Therefore, Kloudspot shall not be liable for any issues arising from the 
> transmission of this email.
> 


-- 
This message is intended only for the use of the individual or entity to 
which it is addressed and may contain confidential and/or privileged 
information. If you are not the intended recipient, please delete the 
original message and any copy of it from your computer system. You are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited unless proper authorization has been 
obtained for such action. If you have received this communication in error, 
please notify the sender immediately. Although IndiQus attempts to sweep 
e-mail and attachments for viruses, it does not guarantee that both are 
virus-free and accepts no liability for any damage sustained as a result of 
viruses.

K8s Dashboard Not Found

[Bharat Bhushan Saini]

Hi All,

I enabled the CKS service in the cloudstack dashboard. After all the things 
done I am unable to access the K8s dashboard.
I encountered in the browser that ‘services “Kubernetes-dashboard” not found’.

Kindly suggest any resolvement for this.

Thanks and Regards,
Bharat Saini

[signature_2321445983]

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. Therefore, Kloudspot 
shall not be liable for any issues arising from the transmission of this email.

Re: CPU Core Consumption High

[Bharat Bhushan Saini]

Hi Jithin,

Thanks for the information.

Thanks and Regards,
Bharat Saini

[signature_2056135577]

From: Jithin Raju 
Date: Monday, 19 February 2024 at 4:26 PM
To: users@cloudstack.apache.org 
Subject: Re: CPU Core Consumption High
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hi Bharat,

The VM’s CPU and Memory capacity won’t be released by cloudstack instantly 
after a stop. It is reserved for starting them upto 
‘capacity.skipcounting.hours’. You could reduce this value in the global 
settings.

-Jithin

From: Bharat Bhushan Saini 
Date: Monday, 19 February 2024 at 4:18 PM
To: users@cloudstack.apache.org 
Subject: Re: CPU Core Consumption High
Hi Wei,

Sure I will do that. Thanks for the suggestion.

Thanks and Regards,
Bharat Saini

[signature_527882427]

From: Wei ZHOU 
Date: Monday, 19 February 2024 at 3:37 PM
To: users@cloudstack.apache.org 
Subject: Re: CPU Core Consumption High
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hi,

Can you perform the same steps again ? If the result is same, you can
create an issue on github: https://github.com/apache/cloudstack/issues/new


-Wei



On Mon, 19 Feb 2024 at 10:30, Bharat Bhushan Saini
 wrote:

> Hi Wei,
>
>
>
> First I did poweroff from inside the vm the it is going off but the status
> show that it is running then I do turned off from the UI as well then
> status shows in UI stopped
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_615347824]
>
>
>
> *From: *Wei ZHOU 
> *Date: *Monday, 19 February 2024 at 2:45 PM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CPU Core Consumption High
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
> Hi,
>
> Did you poweroff from inside the VM or on cloudstack UI ?
>
> -Wei
>
> On Mon, 19 Feb 2024 at 09:53, Bharat Bhushan Saini
>  wrote:
>
> > Hi Wei/Darren,
> >
> >
> >
> > The issue was again trigged after the enable the
> resource.count.running.vms.only
> > option.
> > I shut down all the vm’s but the resource utilization is same as before
> > when vm’s are running.
> >
> >
> >
> > Thanks and Regards,
> >
> > Bharat Saini
> >
> >
> >
> > [image: signature_2781584380]
> >
> >
> >
> > *From: *Wei ZHOU 
> > *Date: *Tuesday, 13 February 2024 at 12:59 AM
> > *To: *users@cloudstack.apache.org 
> > *Subject: *Re: CPU Core Consumption High
> >
> > EXTERNAL EMAIL: Please verify the sender email address before taking any
> > action, replying, clicking any link or opening any attachment.
> >
> >
> > +1.
> >
> > The setting was introduced in 4.14 by my PR
> > https://github.com/apache/cloudstack/pull/3760
> > However, to keep backwards compatibility, the default value was set to
> > false, which does not make sense IMHO.
> >
> > -Wei
> >
> > 在 2024年2月12日星期一，Darren Cole  写道：
> >
> > > This caught me before as well.
> > > By default resource.count.running.vms.only is set to false, so
> resources
> > > are counted for all VMs.
> > > On clusters I run I set this to true so that only running VMs are
> counted
> > > for resource use.
> > >
> > > I have not tested 4.19 yet, but assume the setting stayed the same.
> > > There are also some similar/related settings to determine how running
> > > resources are counted.
> > > Some of these are specific what is backing the VMs.
> > > ie KVM, Xen, etc.
> > >
> > > Darren
> > > --
> > > This e-mail is confidential. Any distribution, use or copying of this
> > > e-mail or the information it contains other than by the intended
> > recipient
> > > is forbidden. If you are not the intended recipient, please advise the
> > > sender (by return e-mail or otherwise) immediately and delete this
> > e-mail.
> > >
> > >
> > > From: "Bharat Bhushan Saini" 
> > > To: "users" 
> > > Sent: Sunday, February 11, 2024 11:14:58 PM
> > > Subject: CPU Core Consumption High
> > >
> > >
> > >
> > > Hi All,
> > >
> > >
> > >
> > > I am facing an issue regarding the core consumption by the cloudstack.
> I
> > > started 2 vm with 6 cores and it takes 18 cores but when I poweroff the
> > vm
> > > the cores remains same in the dashboard.
> > >
> > >
> > >
> > >
> > > Thanks and Regards,
> > >
> > > Bharat Saini
> > >
> > >
> > >
> > >
> > >
> > >
> > > --- Disclaimer: --
> > > This message and its contents are intended solely for the designated
> > > addressee and are proprietary to Kloudspot. The information in this
> email
> > > is meant exclusively for Kloudspot business use. Any use by individuals
> > > other than the addressee constitutes misuse and an infringement of
> > > Kloudspot's proprietary rights. If you are not the intended recipient,
> > > please return this email to the sender. Kloudspot cannot guarantee the
> > > security or error-free 

Re: [VOTE] next version 20 instead of 4.20

[Vivek Kumar]

Why not 5.0 ? Then it will be like 5.1, 5.2 in the future.  Just asking ..!  


> On 19-Feb-2024, at 10:49 PM, Paul Angus  wrote:
> 
> Hi Daan,
> 
> Can you clarify what we are actually voting on please.
> 
> In thread that is linked I've seen:
> 
> "[the vote] will be to adjust to the semantic versioning system."
> - you can't go to 20 AND keep semantic versioning. The act of going to 20 
> breaks semantic versioning [1].
> 
> " drop the 4 at version 20 and continue as usual with minor and patch level 
> updates as we have in the past."
> - what's supposed to come next ? in lieu of what would have been 4.21 will it 
> be 21 ?  is it going to be 20.1 then 20.2 ?
> 
> From the thread and how people are referring to 'minor versions', there is a 
> misunderstanding as to what semantic versioning means. For our project its 
> explained here [1].   Major versions meaning "probably going to break a load 
> of people's stuff', with minor versions not breaking stuff (at least not on 
> purpose). So I get calling them minor versions really underplays the changes 
> it can hold.
> 
> 
> I'm going to stick in a -1.  Not as hard 'no' to any changes, but I think the 
> vote should be on 'A change to the version numbering scheme' and then what is 
> proposed properly laid out.  
> 
> 
> 
> 
> [1]   https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases 
> (section on versioning about 2/3 down)
> 
> -Original Message-
> From: Daan Hoogland  
> Sent: Monday, February 19, 2024 12:50 PM
> To: dev 
> Cc: users 
> Subject: [VOTE] next version 20 instead of 4.20
> 
> LS,
> 
> This is a vote on dev@c.a.o with cc to users@c.a.o. If you want to be counted 
> please reply to dev@.
> 
> As discussed in [1] we are deciding to drop the 4 from our versioning scheme. 
> The result would be that the next major version will be 20 instead of 4.20, 
> as it would be in a traditional upgrade. As 20 > 4 and the versions are 
> processed numerically there are no technical impediments.
> 
> +1 agree (next major version as 20
> 0 (no opinion)
> -1 disagree (keep 4.20 as the next version, give a reason)
> 
> As this is a lazy consensus vote any -1 should be accompanied with a reason.
> 
> [1] https://lists.apache.org/thread/lh45w55c3jmhm7w2w0xgdvlw78pd4p87
> 
> --
> Daan


-- 
This message is intended only for the use of the individual or entity to 
which it is addressed and may contain confidential and/or privileged 
information. If you are not the intended recipient, please delete the 
original message and any copy of it from your computer system. You are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited unless proper authorization has been 
obtained for such action. If you have received this communication in error, 
please notify the sender immediately. Although IndiQus attempts to sweep 
e-mail and attachments for viruses, it does not guarantee that both are 
virus-free and accepts no liability for any damage sustained as a result of 
viruses.

ha checks on kvm hosts running even with ha disabled

[Swen]

Hi all,

we encountered a strange issue today in our lab installation. We are running
CS 4.19.0 upgraded from CS 4.18.1 with linstor as primary storage. We are
using a linstor jar file provided by Linbit which is not the default one part 
of default
4.19.0!

This updated plugin already includes a new feature to use linstor storage for 
host
ha. I provide this only for information reasons.

The issue we encountered was that even we do not have HA enabled on
cluster and host level, cloudstack agent on our KVM hosts triggered HA
actions and rebooted our hosts. We found this on our agent.log:

Feb 19 11:53:05 pc-kvm-2 java[6617]: WARN  [kvm.resource.KVMHAMonitor]
(Thread-1:) (logid:) Write heartbeat for pool
[71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 2 of 5.

Feb 19 11:58:58 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
(Thread-1:) (logid:) Write heartbeat for pool
[71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 3 of 5.

Feb 19 12:00:08 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
(Thread-1:) (logid:) Write heartbeat for pool
[71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 4 of 5.

Feb 19 12:01:08 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
(Thread-1:) (logid:) Write heartbeat for pool
[71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 5 of 5.

Feb 19 12:01:08 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
(Thread-1:) (logid:) Write heartbeat for pool
[71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; stopping
cloudstack-agent.

Feb 19 12:02:08 pc-kvm-2 heartbeat: kvmspheartbeat.sh will reboot system
because it was unable to write the heartbeat to the storage.

We and Linbit did some debugging. We tried to understand why the cloudstack 
agent is running those checks in the first place. We were unable to find any 
code which
checks if host HA is enabled or not and will not perform HA tasks if HA is
disabled. Can somebody please double-check this?

Thank you very much!

Regards,
Swen

Re: restrict Instance console access

[Wei ZHOU]

In 4.18+, an API is used to create the console URL:
https://cloudstack.apache.org/api/apidocs-4.19/apis/createConsoleEndpoint.html
Denying the API can disable the VM console.

It is not available in 4.15.2

-Wei
Nux  于 2024年2月19日周一 22:23写道：

> Hi,
>
> I do not think there is one in that version - or later ones, although
> certain things do change, you'll have to do it outside Cloudstack
> somehow.
>
> On 2024-02-19 15:52, Gary Dixon wrote:
> > HI
> >
> > ACS 4.15.2
> >
> > Ubuntu 20.04
> >
> > We have a requirement to restrict access to the VM console for certain
> > tenants within our ACS implementation - however I cannot see a way to
> > accomplish this via Role permissions.
> >
> > Is there a way to restrict VM Console access for specific users ?
> >
> > BR
> >
> > Gary
> >
> >   Gary Dixon
> >
> >   Quadris Cloud Manager
> >
> >   0161 537 4980 [1]
> >
> >+44 7989717661 [2]
> >
> >   gary.di...@quadris.co.uk
> >
> > www.quadris.com
> >
> > Innovation House, 12‑13 Bredbury Business Park
> > Bredbury Park Way, Bredbury, Stockport, SK6 2SN
> >
> >
> >
> > Links:
> > --
> > [1] tel:0161%20537%204980
> > [2] tel:+44%207989717661
>

Re: [VOTE] next version 20 instead of 4.20

[Nux]

+1

On 2024-02-19 15:09, Andrija Panic wrote:

+1

On Mon, 19 Feb 2024 at 13:50, Daan Hoogland  
wrote:



LS,

This is a vote on dev@c.a.o with cc to users@c.a.o. If you want to be
counted please reply to dev@.

As discussed in [1] we are deciding to drop the 4 from our versioning
scheme. The result would be that the next major version will be 20
instead of 4.20, as it would be in a traditional upgrade. As 20 > 4
and the versions are processed numerically there are no technical
impediments.

+1 agree (next major version as 20
0 (no opinion)
-1 disagree (keep 4.20 as the next version, give a reason)

As this is a lazy consensus vote any -1 should be accompanied with a
reason.

[1] https://lists.apache.org/thread/lh45w55c3jmhm7w2w0xgdvlw78pd4p87

--
Daan

Re: Site-to-Site VPN to Opnsense

[Nux]

Thanks for solving this and sharing the solution!

BTW, the pictures were not sent, perhaps try to "paste" them in rather 
than "attach" them to the email.



On 2024-02-19 20:42, Wally B wrote:

Got this resolved!

The issue is the way StrongSwan (OPNSense IPSec Provider) manages
Phase 2 selectors. For the future if anyone runs into this. Just add
your networks into CloudStack like the documentation says to do. Then
in your OPNSense config add additional networks to Manual SPD entries
under Advanced options on the Phase 2 Settings.

CloudStack VPN Customer Gateway

OPNSense Phase 2:

Thanks!
Wally

On Mon, Feb 19, 2024 at 1:27 PM Wally B 
wrote:


Tried to change the phase 2 selector at 172.16.192.0/16 [5] to a
network on the firewall directly (not just a route the firewall
knows). Getting the same error.

 cat /var/log/daemon.log | grep 10.2.200.0/23 [6]
===

Feb 19 03:45:10 r-407-VM ipsec[174957]: 07[CFG] unable to install
policy 10.2.200.0/23 [6] === 10.241.0.0/16 [4] in for reqid 4, the
same policy for reqid 3 exists
Feb 19 03:45:10 r-407-VM ipsec[174957]: 07[CFG] unable to install
policy 10.2.200.0/23 [6] === 10.241.0.0/16 [4] fwd for reqid 4, the
same policy for reqid 3 exists
Feb 19 03:45:10 r-407-VM ipsec[174957]: 07[CFG] unable to install
policy 10.241.0.0/16 [4] === 10.2.200.0/23 [6] out for reqid 4, the
same policy for reqid 3 exists

=== ipsec statusall =

vpn-xxx.xxx.xxx.171:  xxx.xxx.xxx.154...xxx.xxx.xxx.171  IKEv1,
dpddelay=30s
vpn-xxx.xxx.xxx.171:   local:  [xxx.xxx.xxx.154] uses pre-shared key
authentication
vpn-xxx.xxx.xxx.171:   remote: [xxx.xxx.xxx.171] uses pre-shared key
authentication
vpn-xxx.xxx.xxx.171:   child:  10.241.0.0/16 [4] ===
192.168.251.0/26 [2] 10.2.200.0/23 [6] TUNNEL, dpdaction=restart
L2TP-PSK:  172.26.0.151...%any  IKEv1/2
L2TP-PSK:   local:  [172.26.0.151] uses pre-shared key
authentication
L2TP-PSK:   remote: uses pre-shared key authentication
L2TP-PSK:   child:  dynamic[udp/l2f] === 0.0.0.0/0[udp] [7]
TRANSPORT
Routed Connections:
L2TP-PSK{517}:  ROUTED, TRANSPORT, reqid 4
L2TP-PSK{517}:   0.0.0.0/0[udp/l2f] [8] === 0.0.0.0/0[udp] [7]
vpn-xxx.xxx.xxx.171{516}:  ROUTED, TUNNEL, reqid 3
vpn-xxx.xxx.xxx.171{516}:   10.241.0.0/16 [4] === 10.2.200.0/23 [6]
192.168.251.0/26 [2]

Any help would be appreciated, currently stuck.

Thanks Again
-Wally

On Sun, Feb 18, 2024 at 12:17 AM Wally B 
wrote:


I'm working on a site to site connection from my VPC to my on prem
OPNsense VPN.

Cloudstack Version 4.19.0
OPNSense Version 23.4.2

I have two P2 selectors setup in OPNsense and i've got a VPN
customer gateway setup with two subnets (
192.168.251.0/26,172.16.192.0/20 [1] ) in Cloudstack.

The issue im running into is, only the first address in my  VPN
customer gateway gets added to the SAD. So, In the above example,
since 192.168.251.0/26 [2] is first I can pass traffic to and from
the VPC to that subnet on prem. However, 172.16.192.0/20 [3] is
not added.

I checked the logs on my VPC VR and found the following.

Feb 18 06:11:56 r-407-VM charon: 07[CFG] unable to install policy
172.16.192.0/20 [3] === 10.241.0.0/16 [4] in for reqid 3, the same
policy for reqid 5 exists
Feb 18 06:11:56 r-407-VM charon: 07[CFG] unable to install policy
172.16.192.0/20 [3] === 10.241.0.0/16 [4] fwd for reqid 3, the
same policy for reqid 5 exists
Feb 18 06:11:56 r-407-VM charon: 07[CFG] unable to install policy
10.241.0.0/16 [4] === 172.16.192.0/20 [3] out for reqid 3, the
same policy for reqid 5 exists

Wondering if i'm just formatting my  VPN customer gateway CIDRs
wrong?

Thanks!
Wally



Links:
--
[1] http://192.168.251.0/26,172.16.192.0/20
[2] http://192.168.251.0/26
[3] http://172.16.192.0/20
[4] http://10.241.0.0/16
[5] http://172.16.192.0/16
[6] http://10.2.200.0/23
[7] http://0.0.0.0/0%5Budp%5D
[8] http://0.0.0.0/0%5Budp/l2f%5D

Re: restrict Instance console access

[Nux]

Hi,

I do not think there is one in that version - or later ones, although 
certain things do change, you'll have to do it outside Cloudstack 
somehow.


On 2024-02-19 15:52, Gary Dixon wrote:

HI

ACS 4.15.2

Ubuntu 20.04

We have a requirement to restrict access to the VM console for certain
tenants within our ACS implementation - however I cannot see a way to
accomplish this via Role permissions.

Is there a way to restrict VM Console access for specific users ?

BR

Gary

Gary Dixon

Quadris Cloud Manager

0161 537 4980 [1]

 +44 7989717661 [2]

gary.di...@quadris.co.uk

www.quadris.com

Innovation House, 12‑13 Bredbury Business Park
Bredbury Park Way, Bredbury, Stockport, SK6 2SN



Links:
--
[1] tel:0161%20537%204980
[2] tel:+44%207989717661

Re: Site-to-Site VPN to Opnsense

[Wally B]

Got this resolved!

The issue is the way StrongSwan (OPNSense IPSec Provider) manages Phase 2
selectors. For the future if anyone runs into this. Just add your networks
into CloudStack like the documentation says to do. Then in your OPNSense
config add additional networks to Manual SPD entries under Advanced options
on the Phase 2 Settings.

CloudStack VPN Customer Gateway

[image: image.png]

OPNSense Phase 2:

[image: image.png]

Thanks!
Wally

On Mon, Feb 19, 2024 at 1:27 PM Wally B  wrote:

> Tried to change the phase 2 selector at 172.16.192.0/16 to a network on
> the firewall directly (not just a route the firewall knows). Getting the
> same error.
>
>  cat /var/log/daemon.log | grep 10.2.200.0/23 ===
>
> Feb 19 03:45:10 r-407-VM ipsec[174957]: 07[CFG] unable to install policy
> 10.2.200.0/23 === 10.241.0.0/16 in for reqid 4, the same policy for reqid
> 3 exists
> Feb 19 03:45:10 r-407-VM ipsec[174957]: 07[CFG] unable to install policy
> 10.2.200.0/23 === 10.241.0.0/16 fwd for reqid 4, the same policy for
> reqid 3 exists
> Feb 19 03:45:10 r-407-VM ipsec[174957]: 07[CFG] unable to install policy
> 10.241.0.0/16 === 10.2.200.0/23 out for reqid 4, the same policy for
> reqid 3 exists
>
>
>
>
>
> === ipsec statusall =
>
> vpn-xxx.xxx.xxx.171:  xxx.xxx.xxx.154...xxx.xxx.xxx.171  IKEv1,
> dpddelay=30s
> vpn-xxx.xxx.xxx.171:   local:  [xxx.xxx.xxx.154] uses pre-shared key
> authentication
> vpn-xxx.xxx.xxx.171:   remote: [xxx.xxx.xxx.171] uses pre-shared key
> authentication
> vpn-xxx.xxx.xxx.171:   child:  10.241.0.0/16 === 192.168.251.0/26
> 10.2.200.0/23 TUNNEL, dpdaction=restart
> L2TP-PSK:  172.26.0.151...%any  IKEv1/2
> L2TP-PSK:   local:  [172.26.0.151] uses pre-shared key authentication
> L2TP-PSK:   remote: uses pre-shared key authentication
> L2TP-PSK:   child:  dynamic[udp/l2f] === 0.0.0.0/0[udp]
>  TRANSPORT
> Routed Connections:
> L2TP-PSK{517}:  ROUTED, TRANSPORT, reqid 4
> L2TP-PSK{517}:   0.0.0.0/0[udp/l2f] 
> === 0.0.0.0/0[udp] 
> vpn-xxx.xxx.xxx.171{516}:  ROUTED, TUNNEL, reqid 3
> vpn-xxx.xxx.xxx.171{516}:   10.241.0.0/16 === 10.2.200.0/23
> 192.168.251.0/26
>
>
>
>
> Any help would be appreciated, currently stuck.
>
> Thanks Again
> -Wally
>
> On Sun, Feb 18, 2024 at 12:17 AM Wally B  wrote:
>
>> I'm working on a site to site connection from my VPC to my on prem
>> OPNsense VPN.
>>
>>
>> Cloudstack Version 4.19.0
>> OPNSense Version 23.4.2
>>
>> I have two P2 selectors setup in OPNsense and i've got a VPN customer
>> gateway setup with two subnets (  192.168.251.0/26,172.16.192.0/20 ) in
>> Cloudstack.
>>
>> The issue im running into is, only the first address in my  VPN customer
>> gateway gets added to the SAD. So, In the above example, since
>> 192.168.251.0/26 is first I can pass traffic to and from the VPC to that
>> subnet on prem. However, 172.16.192.0/20 is not added.
>>
>> I checked the logs on my VPC VR and found the following.
>>
>>
>> Feb 18 06:11:56 r-407-VM charon: 07[CFG] unable to install policy
>> 172.16.192.0/20 === 10.241.0.0/16 in for reqid 3, the same policy for
>> reqid 5 exists
>> Feb 18 06:11:56 r-407-VM charon: 07[CFG] unable to install policy
>> 172.16.192.0/20 === 10.241.0.0/16 fwd for reqid 3, the same policy for
>> reqid 5 exists
>> Feb 18 06:11:56 r-407-VM charon: 07[CFG] unable to install policy
>> 10.241.0.0/16 === 172.16.192.0/20 out for reqid 3, the same policy for
>> reqid 5 exists
>>
>>
>> Wondering if i'm just formatting my  VPN customer gateway CIDRs wrong?
>>
>>
>> Thanks!
>> Wally
>>
>>
>>

Re: Site-to-Site VPN to Opnsense

[Wally B]

Tried to change the phase 2 selector at 172.16.192.0/16 to a network on the
firewall directly (not just a route the firewall knows). Getting the same
error.

 cat /var/log/daemon.log | grep 10.2.200.0/23 ===

Feb 19 03:45:10 r-407-VM ipsec[174957]: 07[CFG] unable to install policy
10.2.200.0/23 === 10.241.0.0/16 in for reqid 4, the same policy for reqid 3
exists
Feb 19 03:45:10 r-407-VM ipsec[174957]: 07[CFG] unable to install policy
10.2.200.0/23 === 10.241.0.0/16 fwd for reqid 4, the same policy for reqid
3 exists
Feb 19 03:45:10 r-407-VM ipsec[174957]: 07[CFG] unable to install policy
10.241.0.0/16 === 10.2.200.0/23 out for reqid 4, the same policy for reqid
3 exists





=== ipsec statusall =

vpn-xxx.xxx.xxx.171:  xxx.xxx.xxx.154...xxx.xxx.xxx.171  IKEv1, dpddelay=30s
vpn-xxx.xxx.xxx.171:   local:  [xxx.xxx.xxx.154] uses pre-shared key
authentication
vpn-xxx.xxx.xxx.171:   remote: [xxx.xxx.xxx.171] uses pre-shared key
authentication
vpn-xxx.xxx.xxx.171:   child:  10.241.0.0/16 === 192.168.251.0/26
10.2.200.0/23 TUNNEL, dpdaction=restart
L2TP-PSK:  172.26.0.151...%any  IKEv1/2
L2TP-PSK:   local:  [172.26.0.151] uses pre-shared key authentication
L2TP-PSK:   remote: uses pre-shared key authentication
L2TP-PSK:   child:  dynamic[udp/l2f] === 0.0.0.0/0[udp] TRANSPORT
Routed Connections:
L2TP-PSK{517}:  ROUTED, TRANSPORT, reqid 4
L2TP-PSK{517}:   0.0.0.0/0[udp/l2f] === 0.0.0.0/0[udp]
vpn-xxx.xxx.xxx.171{516}:  ROUTED, TUNNEL, reqid 3
vpn-xxx.xxx.xxx.171{516}:   10.241.0.0/16 === 10.2.200.0/23 192.168.251.0/26




Any help would be appreciated, currently stuck.

Thanks Again
-Wally

On Sun, Feb 18, 2024 at 12:17 AM Wally B  wrote:

> I'm working on a site to site connection from my VPC to my on prem
> OPNsense VPN.
>
>
> Cloudstack Version 4.19.0
> OPNSense Version 23.4.2
>
> I have two P2 selectors setup in OPNsense and i've got a VPN customer
> gateway setup with two subnets (  192.168.251.0/26,172.16.192.0/20 ) in
> Cloudstack.
>
> The issue im running into is, only the first address in my  VPN customer
> gateway gets added to the SAD. So, In the above example, since
> 192.168.251.0/26 is first I can pass traffic to and from the VPC to that
> subnet on prem. However, 172.16.192.0/20 is not added.
>
> I checked the logs on my VPC VR and found the following.
>
>
> Feb 18 06:11:56 r-407-VM charon: 07[CFG] unable to install policy
> 172.16.192.0/20 === 10.241.0.0/16 in for reqid 3, the same policy for
> reqid 5 exists
> Feb 18 06:11:56 r-407-VM charon: 07[CFG] unable to install policy
> 172.16.192.0/20 === 10.241.0.0/16 fwd for reqid 3, the same policy for
> reqid 5 exists
> Feb 18 06:11:56 r-407-VM charon: 07[CFG] unable to install policy
> 10.241.0.0/16 === 172.16.192.0/20 out for reqid 3, the same policy for
> reqid 5 exists
>
>
> Wondering if i'm just formatting my  VPN customer gateway CIDRs wrong?
>
>
> Thanks!
> Wally
>
>
>

RE: [VOTE] next version 20 instead of 4.20

[Paul Angus]

Hi Daan,

Can you clarify what we are actually voting on please.

In thread that is linked I've seen:

"[the vote] will be to adjust to the semantic versioning system."
- you can't go to 20 AND keep semantic versioning. The act of going to 20 
breaks semantic versioning [1].

" drop the 4 at version 20 and continue as usual with minor and patch level 
updates as we have in the past."
- what's supposed to come next ? in lieu of what would have been 4.21 will it 
be 21 ?  is it going to be 20.1 then 20.2 ?

>From the thread and how people are referring to 'minor versions', there is a 
>misunderstanding as to what semantic versioning means. For our project its 
>explained here [1].   Major versions meaning "probably going to break a load 
>of people's stuff', with minor versions not breaking stuff (at least not on 
>purpose). So I get calling them minor versions really underplays the changes 
>it can hold.


I'm going to stick in a -1.  Not as hard 'no' to any changes, but I think the 
vote should be on 'A change to the version numbering scheme' and then what is 
proposed properly laid out.  




[1]   https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases (section 
on versioning about 2/3 down)

-Original Message-
From: Daan Hoogland  
Sent: Monday, February 19, 2024 12:50 PM
To: dev 
Cc: users 
Subject: [VOTE] next version 20 instead of 4.20

LS,

This is a vote on dev@c.a.o with cc to users@c.a.o. If you want to be counted 
please reply to dev@.

As discussed in [1] we are deciding to drop the 4 from our versioning scheme. 
The result would be that the next major version will be 20 instead of 4.20, as 
it would be in a traditional upgrade. As 20 > 4 and the versions are processed 
numerically there are no technical impediments.

+1 agree (next major version as 20
0 (no opinion)
-1 disagree (keep 4.20 as the next version, give a reason)

As this is a lazy consensus vote any -1 should be accompanied with a reason.

[1] https://lists.apache.org/thread/lh45w55c3jmhm7w2w0xgdvlw78pd4p87

--
Daan

restrict Instance console access

[Gary Dixon]

HI

ACS 4.15.2
Ubuntu 20.04

We have a requirement to restrict access to the VM console for certain tenants 
within our ACS implementation - however I cannot see a way to accomplish this 
via Role permissions.
Is there a way to restrict VM Console access for specific users ?

BR

Gary



Gary Dixon
Quadris Cloud Manager
0161 537 4980 +44 7989717661
gary.di...@quadris.co.uk
www.quadris.com
Innovation House, 12-13 Bredbury Business Park
Bredbury Park Way, Bredbury, Stockport, SK6 2SN

Re: [VOTE] next version 20 instead of 4.20

[Andrija Panic]

+1

On Mon, 19 Feb 2024 at 13:50, Daan Hoogland  wrote:

> LS,
>
> This is a vote on dev@c.a.o with cc to users@c.a.o. If you want to be
> counted please reply to dev@.
>
> As discussed in [1] we are deciding to drop the 4 from our versioning
> scheme. The result would be that the next major version will be 20
> instead of 4.20, as it would be in a traditional upgrade. As 20 > 4
> and the versions are processed numerically there are no technical
> impediments.
>
> +1 agree (next major version as 20
> 0 (no opinion)
> -1 disagree (keep 4.20 as the next version, give a reason)
>
> As this is a lazy consensus vote any -1 should be accompanied with a
> reason.
>
> [1] https://lists.apache.org/thread/lh45w55c3jmhm7w2w0xgdvlw78pd4p87
>
> --
> Daan
>


-- 

Andrija Panić

Re: [D] Changing compute offering / scaling VM and root disk [cloudstack]

[via GitHub]

GitHub user vonlo123 added a comment to the discussion: Changing compute 
offering / scaling VM and root disk

We solved this issue by denying _updateDIskOffering_
`disk offering strictness` needs to be set to `false`  

But this only works when the root disk in the compute offering has the 
_Provisioning type_ _fat_. With _thin provisioning_ I still can resize the 
disk. 
It looks like a bug...


GitHub link: 
https://github.com/apache/cloudstack/discussions/8578#discussioncomment-8517770


This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org

Re: [VOTE] next version 20 instead of 4.20

[Wido den Hollander]

+1

Op 19/02/2024 om 13:49 schreef Daan Hoogland:

LS,

This is a vote on dev@c.a.o with cc to users@c.a.o. If you want to be
counted please reply to dev@.

As discussed in [1] we are deciding to drop the 4 from our versioning
scheme. The result would be that the next major version will be 20
instead of 4.20, as it would be in a traditional upgrade. As 20 > 4
and the versions are processed numerically there are no technical
impediments.

+1 agree (next major version as 20
0 (no opinion)
-1 disagree (keep 4.20 as the next version, give a reason)

As this is a lazy consensus vote any -1 should be accompanied with a reason.

[1] https://lists.apache.org/thread/lh45w55c3jmhm7w2w0xgdvlw78pd4p87

RE: [VOTE] next version 20 instead of 4.20

[Alex Mattioli]

+1

 


-Original Message-
From: Daan Hoogland  
Sent: Monday, February 19, 2024 1:50 PM
To: dev 
Cc: users 
Subject: [VOTE] next version 20 instead of 4.20

LS,

This is a vote on dev@c.a.o with cc to users@c.a.o. If you want to be counted 
please reply to dev@.

As discussed in [1] we are deciding to drop the 4 from our versioning scheme. 
The result would be that the next major version will be 20 instead of 4.20, as 
it would be in a traditional upgrade. As 20 > 4 and the versions are processed 
numerically there are no technical impediments.

+1 agree (next major version as 20
0 (no opinion)
-1 disagree (keep 4.20 as the next version, give a reason)

As this is a lazy consensus vote any -1 should be accompanied with a reason.

[1] https://lists.apache.org/thread/lh45w55c3jmhm7w2w0xgdvlw78pd4p87

--
Daan

[VOTE] next version 20 instead of 4.20

[Daan Hoogland]

LS,

This is a vote on dev@c.a.o with cc to users@c.a.o. If you want to be
counted please reply to dev@.

As discussed in [1] we are deciding to drop the 4 from our versioning
scheme. The result would be that the next major version will be 20
instead of 4.20, as it would be in a traditional upgrade. As 20 > 4
and the versions are processed numerically there are no technical
impediments.

+1 agree (next major version as 20
0 (no opinion)
-1 disagree (keep 4.20 as the next version, give a reason)

As this is a lazy consensus vote any -1 should be accompanied with a reason.

[1] https://lists.apache.org/thread/lh45w55c3jmhm7w2w0xgdvlw78pd4p87

-- 
Daan

Re: Secondary Storage VM not getting started

[Daan Hoogland]

On Mon, Feb 19, 2024 at 1:14 PM Kapil Bhuskute
 wrote:
>
> Hello Daan,
> What exactly did you mean by initiating the secondary storage?
> We have a secondary storage path and server name mentioned in the Cloudstack 
> management server wizard to add it, and that got added in the UI.
> It is a nfs export hosted on the same cloudstack server and is already 
> available with all required NFS permissions(rw,no_root_squash,sync).
> Is there any manual step required to initiate it?

No you shouldn't have to. Is the storage initiated with the templates
needed? You can check the path under /mnt/data/template/tmpl/ to see
if there are templates there. You can also check to see if the
templates are marked as ready?

>
> Kapil Bhuskute
>
>
> -Original Message-
> From: Daan Hoogland 
> Sent: Monday, February 19, 2024 1:55 PM
> To: users@cloudstack.apache.org
> Subject: Re: Secondary Storage VM not getting started
>
>CAUTION: This Email is from an EXTERNAL source. Ensure you trust this 
> sender before clicking on any links or attachments.
>
> Kapil,
> did you initiate your secondary storage (at 
> kvm01.p01.ops.sjc01.qualys.com:/mnt/data)?
> and did you export the storage for it from the nfs server?
> The error says there is a problem there.
>
> On Mon, Feb 19, 2024 at 7:35 AM Kapil Bhuskute  
> wrote:
> >
> > The secondary storage VM is not able to get deployed in CloudStack 4.19 
> > with below errors.
> >
> > Feb 16 13:25:08 qcs01 java[417597]: INFO  [o.a.c.e.o.VolumeOrchestrator] 
> > (secstorage-1:ctx-adb3bb9a ctx-2cb81e1f) (logid:67e774fb) Adding disk 
> > object [ROOT-6258] to VM [VM instance {"id":6258,"instanceName"
> > :"s-6258-VM","type":"SecondaryStorageVm","uuid":"a9520deb-ca26-4a6f-bc
> > 40-871841d05c28"}] Feb 16 13:25:11 qcs01 java[417597]: ERROR
> > [o.a.c.e.o.VolumeOrchestrator] (Work-Job-Executor-2:ctx-511f3201
> > job-9178/job-13001 ctx-8a4381d2) (logid:cbcf72ec) Unable to create volume 
> > [{"name":"ROOT-6258","uui d":"8444daf7-4145-4a40-8789-c623c5a5ad7c"}] due 
> > to [com.cloud.utils.exception.CloudRuntimeException: 
> > org.libvirt.LibvirtException: internal error: Child process (/usr/bin/mount 
> > -o nodev,nosuid,noexec kvm01.
> > p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222
> > /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) unexpected exit status 32:
> > mount.nfs: mounting
> > kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222
> > failed, reason given by server: No such file or directory Feb 16
> > 13:25:11 qcs01 java[417597]:
> > com.cloud.exception.StorageUnavailableException: Resource
> > [StoragePool:5] is unreachable: Unable to create volume
> > [{"name":"ROOT-6258","uuid":"8444daf7-4145-4a40-8789-c62
> > 3c5a5ad7c"}] due to [com.cloud.utils.exception.CloudRuntimeException:
> > org.libvirt.LibvirtException: internal error: Child process
> > (/usr/bin/mount -o nodev,nosuid,noexec
> > kvm01.p01.ops.sjc01.qualys.com:/mnt/d
> > ata/template/tmpl/1/222 /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) 
> > unexpected exit status 32: mount.nfs: mounting 
> > kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222 failed, reason 
> > given by server:
> > No such file or directory
> > Feb 16 13:25:41 qcs01 java[417597]: ERROR
> > [o.a.c.e.o.VolumeOrchestrator] (Work-Job-Executor-8:ctx-5417b759 
> > job-9178/job-13003 ctx-f6230d28) (logid:cbcf72ec) Unable to create volume 
> > [{"name":"ROOT-6258","uui d":"8444daf7-4145-4a40-8789-c623c5a5ad7c"}] due 
> > to [com.cloud.utils.exception.CloudRuntimeException: 
> > org.libvirt.LibvirtException: internal error: Child process (/usr/bin/mount 
> > -o nodev,nosuid,noexec kvm01.
> > p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222
> > /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) unexpected exit status 32:
> > mount.nfs: mounting
> > kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222
> > failed, reason given by server: No such file or directory Feb 16
> > 13:25:41 qcs01 java[417597]:
> > com.cloud.exception.StorageUnavailableException: Resource
> > [StoragePool:5] is unreachable: Unable to create volume
> > [{"name":"ROOT-6258","uuid":"8444daf7-4145-4a40-8789-c62
> > 3c5a5ad7c"}] due to [com.cloud.utils.exception.CloudRuntimeException:
> > org.libvirt.LibvirtException: internal error: Child process
> > (/usr/bin/mount -o nodev,nosuid,noexec
> > kvm01.p01.ops.sjc01.qualys.com:/mnt/d
> > ata/template/tmpl/1/222 /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) 
> > unexpected exit status 32: mount.nfs: mounting 
> > kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222 failed, reason 
> > given by server:
> > No such file or directory
> >
> > Regards,
> > Kapil Bhuskute
>
>
>
> --
> Daan



-- 
Daan

RE: Secondary Storage VM not getting started

[Kapil Bhuskute]

Hello Daan, 
What exactly did you mean by initiating the secondary storage?
We have a secondary storage path and server name mentioned in the Cloudstack 
management server wizard to add it, and that got added in the UI. 
It is a nfs export hosted on the same cloudstack server and is already 
available with all required NFS permissions(rw,no_root_squash,sync).
Is there any manual step required to initiate it?

Kapil Bhuskute 


-Original Message-
From: Daan Hoogland  
Sent: Monday, February 19, 2024 1:55 PM
To: users@cloudstack.apache.org
Subject: Re: Secondary Storage VM not getting started

   CAUTION: This Email is from an EXTERNAL source. Ensure you trust this 
sender before clicking on any links or attachments.  

Kapil,
did you initiate your secondary storage (at 
kvm01.p01.ops.sjc01.qualys.com:/mnt/data)?
and did you export the storage for it from the nfs server?
The error says there is a problem there.

On Mon, Feb 19, 2024 at 7:35 AM Kapil Bhuskute  
wrote:
>
> The secondary storage VM is not able to get deployed in CloudStack 4.19 with 
> below errors.
>
> Feb 16 13:25:08 qcs01 java[417597]: INFO  [o.a.c.e.o.VolumeOrchestrator] 
> (secstorage-1:ctx-adb3bb9a ctx-2cb81e1f) (logid:67e774fb) Adding disk object 
> [ROOT-6258] to VM [VM instance {"id":6258,"instanceName"
> :"s-6258-VM","type":"SecondaryStorageVm","uuid":"a9520deb-ca26-4a6f-bc
> 40-871841d05c28"}] Feb 16 13:25:11 qcs01 java[417597]: ERROR 
> [o.a.c.e.o.VolumeOrchestrator] (Work-Job-Executor-2:ctx-511f3201 
> job-9178/job-13001 ctx-8a4381d2) (logid:cbcf72ec) Unable to create volume 
> [{"name":"ROOT-6258","uui d":"8444daf7-4145-4a40-8789-c623c5a5ad7c"}] due to 
> [com.cloud.utils.exception.CloudRuntimeException: 
> org.libvirt.LibvirtException: internal error: Child process (/usr/bin/mount 
> -o nodev,nosuid,noexec kvm01.
> p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222 
> /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) unexpected exit status 32: 
> mount.nfs: mounting 
> kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222
> failed, reason given by server: No such file or directory Feb 16 
> 13:25:11 qcs01 java[417597]: 
> com.cloud.exception.StorageUnavailableException: Resource 
> [StoragePool:5] is unreachable: Unable to create volume 
> [{"name":"ROOT-6258","uuid":"8444daf7-4145-4a40-8789-c62
> 3c5a5ad7c"}] due to [com.cloud.utils.exception.CloudRuntimeException: 
> org.libvirt.LibvirtException: internal error: Child process 
> (/usr/bin/mount -o nodev,nosuid,noexec 
> kvm01.p01.ops.sjc01.qualys.com:/mnt/d
> ata/template/tmpl/1/222 /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) unexpected 
> exit status 32: mount.nfs: mounting 
> kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222 failed, reason 
> given by server:
> No such file or directory
> Feb 16 13:25:41 qcs01 java[417597]: ERROR 
> [o.a.c.e.o.VolumeOrchestrator] (Work-Job-Executor-8:ctx-5417b759 
> job-9178/job-13003 ctx-f6230d28) (logid:cbcf72ec) Unable to create volume 
> [{"name":"ROOT-6258","uui d":"8444daf7-4145-4a40-8789-c623c5a5ad7c"}] due to 
> [com.cloud.utils.exception.CloudRuntimeException: 
> org.libvirt.LibvirtException: internal error: Child process (/usr/bin/mount 
> -o nodev,nosuid,noexec kvm01.
> p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222 
> /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) unexpected exit status 32: 
> mount.nfs: mounting 
> kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222
> failed, reason given by server: No such file or directory Feb 16 
> 13:25:41 qcs01 java[417597]: 
> com.cloud.exception.StorageUnavailableException: Resource 
> [StoragePool:5] is unreachable: Unable to create volume 
> [{"name":"ROOT-6258","uuid":"8444daf7-4145-4a40-8789-c62
> 3c5a5ad7c"}] due to [com.cloud.utils.exception.CloudRuntimeException: 
> org.libvirt.LibvirtException: internal error: Child process 
> (/usr/bin/mount -o nodev,nosuid,noexec 
> kvm01.p01.ops.sjc01.qualys.com:/mnt/d
> ata/template/tmpl/1/222 /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) unexpected 
> exit status 32: mount.nfs: mounting 
> kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222 failed, reason 
> given by server:
> No such file or directory
>
> Regards,
> Kapil Bhuskute



--
Daan

Re: CS 4.19.0.0 - KVM Reboot Loop

[Wei ZHOU]

Hi,

Can you add a line in agent.properties and retry ?

reboot.host.and.alert.management.on.heartbeat.timeout=false

-Wei



On Mon, 19 Feb 2024 at 12:14, W. Verleger - proIO GmbH 
wrote:

> Hi,
>
> We are using a 3 node KVM/CS 4.19.0.0 cluster with Linstor storage.
> Since CS 4.19.0.0 we are encountering a reboot loop of our hosts. They
> keep rebooting.
>
> HA is disabled (globally and cluster wide).
>
> We are getting the following log entries in the cloudstack-agent log:
>
> Feb 19 11:53:05 pc-kvm-2 java[6617]: WARN  [kvm.resource.KVMHAMonitor]
> (Thread-1:) (logid:) Write heartbeat for pool
> [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 2 of 5.
> Feb 19 11:58:58 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
> (Thread-1:) (logid:) Write heartbeat for pool
> [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 3 of 5.
> Feb 19 12:00:08 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
> (Thread-1:) (logid:) Write heartbeat for pool
> [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 4 of 5.
> Feb 19 12:01:08 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
> (Thread-1:) (logid:) Write heartbeat for pool
> [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 5 of 5.
> Feb 19 12:01:08 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor]
> (Thread-1:) (logid:) Write heartbeat for pool
> [71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; stopping
> cloudstack-agent.
> Feb 19 12:02:08 pc-kvm-2 heartbeat: kvmspheartbeat.sh will reboot system
> because it was unable to write the heartbeat to the storage.
>
> Any idea why kvm heartbeat is still active?
>
>
> Best regards,
>
> Wilken
>
>
> - proIO GmbH -
> Geschäftsführer: Swen Brüseke
> Sitz der Gesellschaft: Frankfurt am Main
>
> USt-IdNr. DE 267 075 918
> Registergericht: Frankfurt am Main - HRB 86239
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
> erhalten haben,
> informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
> Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind
> nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this e-mail in
> error) please notify
> the sender immediately and destroy this e-mail.
> Any unauthorized copying, disclosure or distribution of the material in
> this e-mail is strictly forbidden.
>
>

CS 4.19.0.0 - KVM Reboot Loop

[W. Verleger - proIO GmbH]

Hi,
 
We are using a 3 node KVM/CS 4.19.0.0 cluster with Linstor storage.
Since CS 4.19.0.0 we are encountering a reboot loop of our hosts. They keep 
rebooting.
 
HA is disabled (globally and cluster wide).
 
We are getting the following log entries in the cloudstack-agent log:
 
Feb 19 11:53:05 pc-kvm-2 java[6617]: WARN  [kvm.resource.KVMHAMonitor] 
(Thread-1:) (logid:) Write heartbeat for pool 
[71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 2 of 5.
Feb 19 11:58:58 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor] 
(Thread-1:) (logid:) Write heartbeat for pool 
[71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 3 of 5.
Feb 19 12:00:08 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor] 
(Thread-1:) (logid:) Write heartbeat for pool 
[71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 4 of 5.
Feb 19 12:01:08 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor] 
(Thread-1:) (logid:) Write heartbeat for pool 
[71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; try: 5 of 5.
Feb 19 12:01:08 pc-kvm-2 java[9465]: WARN  [kvm.resource.KVMHAMonitor] 
(Thread-1:) (logid:) Write heartbeat for pool 
[71c272d3-b180-4b18-a0fc-cfc1dc5b86c9] failed: Down; stopping cloudstack-agent.
Feb 19 12:02:08 pc-kvm-2 heartbeat: kvmspheartbeat.sh will reboot system 
because it was unable to write the heartbeat to the storage.
 
Any idea why kvm heartbeat is still active?
 
 
Best regards,
 
Wilken


- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, 
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet. 

This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail in error) 
please notify 
the sender immediately and destroy this e-mail.  
Any unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden. 

Re: CPU Core Consumption High

[Jithin Raju]

Hi Bharat,

The VM’s CPU and Memory capacity won’t be released by cloudstack instantly 
after a stop. It is reserved for starting them upto 
‘capacity.skipcounting.hours’. You could reduce this value in the global 
settings.

-Jithin

From: Bharat Bhushan Saini 
Date: Monday, 19 February 2024 at 4:18 PM
To: users@cloudstack.apache.org 
Subject: Re: CPU Core Consumption High
Hi Wei,

Sure I will do that. Thanks for the suggestion.

Thanks and Regards,
Bharat Saini

[signature_527882427]

From: Wei ZHOU 
Date: Monday, 19 February 2024 at 3:37 PM
To: users@cloudstack.apache.org 
Subject: Re: CPU Core Consumption High
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hi,

Can you perform the same steps again ? If the result is same, you can
create an issue on github: https://github.com/apache/cloudstack/issues/new


-Wei



On Mon, 19 Feb 2024 at 10:30, Bharat Bhushan Saini
 wrote:

> Hi Wei,
>
>
>
> First I did poweroff from inside the vm the it is going off but the status
> show that it is running then I do turned off from the UI as well then
> status shows in UI stopped
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_615347824]
>
>
>
> *From: *Wei ZHOU 
> *Date: *Monday, 19 February 2024 at 2:45 PM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CPU Core Consumption High
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
> Hi,
>
> Did you poweroff from inside the VM or on cloudstack UI ?
>
> -Wei
>
> On Mon, 19 Feb 2024 at 09:53, Bharat Bhushan Saini
>  wrote:
>
> > Hi Wei/Darren,
> >
> >
> >
> > The issue was again trigged after the enable the
> resource.count.running.vms.only
> > option.
> > I shut down all the vm’s but the resource utilization is same as before
> > when vm’s are running.
> >
> >
> >
> > Thanks and Regards,
> >
> > Bharat Saini
> >
> >
> >
> > [image: signature_2781584380]
> >
> >
> >
> > *From: *Wei ZHOU 
> > *Date: *Tuesday, 13 February 2024 at 12:59 AM
> > *To: *users@cloudstack.apache.org 
> > *Subject: *Re: CPU Core Consumption High
> >
> > EXTERNAL EMAIL: Please verify the sender email address before taking any
> > action, replying, clicking any link or opening any attachment.
> >
> >
> > +1.
> >
> > The setting was introduced in 4.14 by my PR
> > https://github.com/apache/cloudstack/pull/3760
> > However, to keep backwards compatibility, the default value was set to
> > false, which does not make sense IMHO.
> >
> > -Wei
> >
> > 在 2024年2月12日星期一，Darren Cole  写道：
> >
> > > This caught me before as well.
> > > By default resource.count.running.vms.only is set to false, so
> resources
> > > are counted for all VMs.
> > > On clusters I run I set this to true so that only running VMs are
> counted
> > > for resource use.
> > >
> > > I have not tested 4.19 yet, but assume the setting stayed the same.
> > > There are also some similar/related settings to determine how running
> > > resources are counted.
> > > Some of these are specific what is backing the VMs.
> > > ie KVM, Xen, etc.
> > >
> > > Darren
> > > --
> > > This e-mail is confidential. Any distribution, use or copying of this
> > > e-mail or the information it contains other than by the intended
> > recipient
> > > is forbidden. If you are not the intended recipient, please advise the
> > > sender (by return e-mail or otherwise) immediately and delete this
> > e-mail.
> > >
> > >
> > > From: "Bharat Bhushan Saini" 
> > > To: "users" 
> > > Sent: Sunday, February 11, 2024 11:14:58 PM
> > > Subject: CPU Core Consumption High
> > >
> > >
> > >
> > > Hi All,
> > >
> > >
> > >
> > > I am facing an issue regarding the core consumption by the cloudstack.
> I
> > > started 2 vm with 6 cores and it takes 18 cores but when I poweroff the
> > vm
> > > the cores remains same in the dashboard.
> > >
> > >
> > >
> > >
> > > Thanks and Regards,
> > >
> > > Bharat Saini
> > >
> > >
> > >
> > >
> > >
> > >
> > > --- Disclaimer: --
> > > This message and its contents are intended solely for the designated
> > > addressee and are proprietary to Kloudspot. The information in this
> email
> > > is meant exclusively for Kloudspot business use. Any use by individuals
> > > other than the addressee constitutes misuse and an infringement of
> > > Kloudspot's proprietary rights. If you are not the intended recipient,
> > > please return this email to the sender. Kloudspot cannot guarantee the
> > > security or error-free transmission of e-mail communications.
> Information
> > > could be intercepted, corrupted, lost, destroyed, arrive late or
> > > incomplete, or contain viruses. Therefore, Kloudspot shall not be
> liable
> > > for any issues arising from the transmission of this email.
> > >
> >
> > --- Disclaimer: --
> > This message and 

Re: CPU Core Consumption High

[Bharat Bhushan Saini]

Hi Wei,

Sure I will do that. Thanks for the suggestion.

Thanks and Regards,
Bharat Saini

[signature_527882427]

From: Wei ZHOU 
Date: Monday, 19 February 2024 at 3:37 PM
To: users@cloudstack.apache.org 
Subject: Re: CPU Core Consumption High
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hi,

Can you perform the same steps again ? If the result is same, you can
create an issue on github: https://github.com/apache/cloudstack/issues/new


-Wei



On Mon, 19 Feb 2024 at 10:30, Bharat Bhushan Saini
 wrote:

> Hi Wei,
>
>
>
> First I did poweroff from inside the vm the it is going off but the status
> show that it is running then I do turned off from the UI as well then
> status shows in UI stopped
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_615347824]
>
>
>
> *From: *Wei ZHOU 
> *Date: *Monday, 19 February 2024 at 2:45 PM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CPU Core Consumption High
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
> Hi,
>
> Did you poweroff from inside the VM or on cloudstack UI ?
>
> -Wei
>
> On Mon, 19 Feb 2024 at 09:53, Bharat Bhushan Saini
>  wrote:
>
> > Hi Wei/Darren,
> >
> >
> >
> > The issue was again trigged after the enable the
> resource.count.running.vms.only
> > option.
> > I shut down all the vm’s but the resource utilization is same as before
> > when vm’s are running.
> >
> >
> >
> > Thanks and Regards,
> >
> > Bharat Saini
> >
> >
> >
> > [image: signature_2781584380]
> >
> >
> >
> > *From: *Wei ZHOU 
> > *Date: *Tuesday, 13 February 2024 at 12:59 AM
> > *To: *users@cloudstack.apache.org 
> > *Subject: *Re: CPU Core Consumption High
> >
> > EXTERNAL EMAIL: Please verify the sender email address before taking any
> > action, replying, clicking any link or opening any attachment.
> >
> >
> > +1.
> >
> > The setting was introduced in 4.14 by my PR
> > https://github.com/apache/cloudstack/pull/3760
> > However, to keep backwards compatibility, the default value was set to
> > false, which does not make sense IMHO.
> >
> > -Wei
> >
> > 在 2024年2月12日星期一，Darren Cole  写道：
> >
> > > This caught me before as well.
> > > By default resource.count.running.vms.only is set to false, so
> resources
> > > are counted for all VMs.
> > > On clusters I run I set this to true so that only running VMs are
> counted
> > > for resource use.
> > >
> > > I have not tested 4.19 yet, but assume the setting stayed the same.
> > > There are also some similar/related settings to determine how running
> > > resources are counted.
> > > Some of these are specific what is backing the VMs.
> > > ie KVM, Xen, etc.
> > >
> > > Darren
> > > --
> > > This e-mail is confidential. Any distribution, use or copying of this
> > > e-mail or the information it contains other than by the intended
> > recipient
> > > is forbidden. If you are not the intended recipient, please advise the
> > > sender (by return e-mail or otherwise) immediately and delete this
> > e-mail.
> > >
> > >
> > > From: "Bharat Bhushan Saini" 
> > > To: "users" 
> > > Sent: Sunday, February 11, 2024 11:14:58 PM
> > > Subject: CPU Core Consumption High
> > >
> > >
> > >
> > > Hi All,
> > >
> > >
> > >
> > > I am facing an issue regarding the core consumption by the cloudstack.
> I
> > > started 2 vm with 6 cores and it takes 18 cores but when I poweroff the
> > vm
> > > the cores remains same in the dashboard.
> > >
> > >
> > >
> > >
> > > Thanks and Regards,
> > >
> > > Bharat Saini
> > >
> > >
> > >
> > >
> > >
> > >
> > > --- Disclaimer: --
> > > This message and its contents are intended solely for the designated
> > > addressee and are proprietary to Kloudspot. The information in this
> email
> > > is meant exclusively for Kloudspot business use. Any use by individuals
> > > other than the addressee constitutes misuse and an infringement of
> > > Kloudspot's proprietary rights. If you are not the intended recipient,
> > > please return this email to the sender. Kloudspot cannot guarantee the
> > > security or error-free transmission of e-mail communications.
> Information
> > > could be intercepted, corrupted, lost, destroyed, arrive late or
> > > incomplete, or contain viruses. Therefore, Kloudspot shall not be
> liable
> > > for any issues arising from the transmission of this email.
> > >
> >
> > --- Disclaimer: --
> > This message and its contents are intended solely for the designated
> > addressee and are proprietary to Kloudspot. The information in this email
> > is meant exclusively for Kloudspot business use. Any use by individuals
> > other than the addressee constitutes misuse and an infringement of
> > Kloudspot's proprietary rights. If you are not the intended recipient,
> > please return this 

readyForShutdown api call every second

[me]

Hi all,

 

CS 4.19.0 upgrade from 4.18.1

 

I observe that my UI is doing the following api call every second:

/client/api/?command=readyForShutdown=json

 

Is this expected? I found this api docu:

https://cloudstack.apache.org/api/apidocs-4.19/apis/readyForShutdown.html

 

But I do not really understand it. I already restarted cloudstack-management
service on the management server.

 

Any idea what triggers that api call?

 

Regards,

Swen

Community Events this Week

[Ivet Petrova]

Hi all,

I am writing to remind that the CloudStack community has two upcoming events 
this week:
- CloudStack and Ceph Day Netherlands on Feb 22nd - event is sold out, but if 
someone still wants to attend, please ping me on email to add you to the list.
Event 
agenda:https://www.eventbrite.nl/e/cloudstack-and-ceph-day-netherlands-2024-tickets-700177167757

- CloudStack India User Group on Feb 23rd - we still collect registrations 
here: https://www.meetup.com/india-cloudstack-user-group/events/298324389/
Event agenda:https://cloudstack.apache.org/blog/india-user-group-2024/


Both events are in-person and they will not be live streamed, so I encourage 
you all to register and come meet the community live!

Best regards,


 

Re: CPU Core Consumption High

[Wei ZHOU]

Hi,

Can you perform the same steps again ? If the result is same, you can
create an issue on github: https://github.com/apache/cloudstack/issues/new


-Wei



On Mon, 19 Feb 2024 at 10:30, Bharat Bhushan Saini
 wrote:

> Hi Wei,
>
>
>
> First I did poweroff from inside the vm the it is going off but the status
> show that it is running then I do turned off from the UI as well then
> status shows in UI stopped
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_615347824]
>
>
>
> *From: *Wei ZHOU 
> *Date: *Monday, 19 February 2024 at 2:45 PM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CPU Core Consumption High
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
> Hi,
>
> Did you poweroff from inside the VM or on cloudstack UI ?
>
> -Wei
>
> On Mon, 19 Feb 2024 at 09:53, Bharat Bhushan Saini
>  wrote:
>
> > Hi Wei/Darren,
> >
> >
> >
> > The issue was again trigged after the enable the
> resource.count.running.vms.only
> > option.
> > I shut down all the vm’s but the resource utilization is same as before
> > when vm’s are running.
> >
> >
> >
> > Thanks and Regards,
> >
> > Bharat Saini
> >
> >
> >
> > [image: signature_2781584380]
> >
> >
> >
> > *From: *Wei ZHOU 
> > *Date: *Tuesday, 13 February 2024 at 12:59 AM
> > *To: *users@cloudstack.apache.org 
> > *Subject: *Re: CPU Core Consumption High
> >
> > EXTERNAL EMAIL: Please verify the sender email address before taking any
> > action, replying, clicking any link or opening any attachment.
> >
> >
> > +1.
> >
> > The setting was introduced in 4.14 by my PR
> > https://github.com/apache/cloudstack/pull/3760
> > However, to keep backwards compatibility, the default value was set to
> > false, which does not make sense IMHO.
> >
> > -Wei
> >
> > 在 2024年2月12日星期一，Darren Cole  写道：
> >
> > > This caught me before as well.
> > > By default resource.count.running.vms.only is set to false, so
> resources
> > > are counted for all VMs.
> > > On clusters I run I set this to true so that only running VMs are
> counted
> > > for resource use.
> > >
> > > I have not tested 4.19 yet, but assume the setting stayed the same.
> > > There are also some similar/related settings to determine how running
> > > resources are counted.
> > > Some of these are specific what is backing the VMs.
> > > ie KVM, Xen, etc.
> > >
> > > Darren
> > > --
> > > This e-mail is confidential. Any distribution, use or copying of this
> > > e-mail or the information it contains other than by the intended
> > recipient
> > > is forbidden. If you are not the intended recipient, please advise the
> > > sender (by return e-mail or otherwise) immediately and delete this
> > e-mail.
> > >
> > >
> > > From: "Bharat Bhushan Saini" 
> > > To: "users" 
> > > Sent: Sunday, February 11, 2024 11:14:58 PM
> > > Subject: CPU Core Consumption High
> > >
> > >
> > >
> > > Hi All,
> > >
> > >
> > >
> > > I am facing an issue regarding the core consumption by the cloudstack.
> I
> > > started 2 vm with 6 cores and it takes 18 cores but when I poweroff the
> > vm
> > > the cores remains same in the dashboard.
> > >
> > >
> > >
> > >
> > > Thanks and Regards,
> > >
> > > Bharat Saini
> > >
> > >
> > >
> > >
> > >
> > >
> > > --- Disclaimer: --
> > > This message and its contents are intended solely for the designated
> > > addressee and are proprietary to Kloudspot. The information in this
> email
> > > is meant exclusively for Kloudspot business use. Any use by individuals
> > > other than the addressee constitutes misuse and an infringement of
> > > Kloudspot's proprietary rights. If you are not the intended recipient,
> > > please return this email to the sender. Kloudspot cannot guarantee the
> > > security or error-free transmission of e-mail communications.
> Information
> > > could be intercepted, corrupted, lost, destroyed, arrive late or
> > > incomplete, or contain viruses. Therefore, Kloudspot shall not be
> liable
> > > for any issues arising from the transmission of this email.
> > >
> >
> > --- Disclaimer: --
> > This message and its contents are intended solely for the designated
> > addressee and are proprietary to Kloudspot. The information in this email
> > is meant exclusively for Kloudspot business use. Any use by individuals
> > other than the addressee constitutes misuse and an infringement of
> > Kloudspot's proprietary rights. If you are not the intended recipient,
> > please return this email to the sender. Kloudspot cannot guarantee the
> > security or error-free transmission of e-mail communications. Information
> > could be intercepted, corrupted, lost, destroyed, arrive late or
> > incomplete, or contain viruses. Therefore, Kloudspot shall not be liable
> > for any issues arising from the transmission of this email.
> >
>
> --- Disclaimer: 

Re: CPU Core Consumption High

[Bharat Bhushan Saini]

Hi Wei,

First I did poweroff from inside the vm the it is going off but the status show 
that it is running then I do turned off from the UI as well then status shows 
in UI stopped

Thanks and Regards,
Bharat Saini

[signature_615347824]

From: Wei ZHOU 
Date: Monday, 19 February 2024 at 2:45 PM
To: users@cloudstack.apache.org 
Subject: Re: CPU Core Consumption High
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hi,

Did you poweroff from inside the VM or on cloudstack UI ?

-Wei

On Mon, 19 Feb 2024 at 09:53, Bharat Bhushan Saini
 wrote:

> Hi Wei/Darren,
>
>
>
> The issue was again trigged after the enable the 
> resource.count.running.vms.only
> option.
> I shut down all the vm’s but the resource utilization is same as before
> when vm’s are running.
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_2781584380]
>
>
>
> *From: *Wei ZHOU 
> *Date: *Tuesday, 13 February 2024 at 12:59 AM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CPU Core Consumption High
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
> +1.
>
> The setting was introduced in 4.14 by my PR
> https://github.com/apache/cloudstack/pull/3760
> However, to keep backwards compatibility, the default value was set to
> false, which does not make sense IMHO.
>
> -Wei
>
> 在 2024年2月12日星期一，Darren Cole  写道：
>
> > This caught me before as well.
> > By default resource.count.running.vms.only is set to false, so resources
> > are counted for all VMs.
> > On clusters I run I set this to true so that only running VMs are counted
> > for resource use.
> >
> > I have not tested 4.19 yet, but assume the setting stayed the same.
> > There are also some similar/related settings to determine how running
> > resources are counted.
> > Some of these are specific what is backing the VMs.
> > ie KVM, Xen, etc.
> >
> > Darren
> > --
> > This e-mail is confidential. Any distribution, use or copying of this
> > e-mail or the information it contains other than by the intended
> recipient
> > is forbidden. If you are not the intended recipient, please advise the
> > sender (by return e-mail or otherwise) immediately and delete this
> e-mail.
> >
> >
> > From: "Bharat Bhushan Saini" 
> > To: "users" 
> > Sent: Sunday, February 11, 2024 11:14:58 PM
> > Subject: CPU Core Consumption High
> >
> >
> >
> > Hi All,
> >
> >
> >
> > I am facing an issue regarding the core consumption by the cloudstack. I
> > started 2 vm with 6 cores and it takes 18 cores but when I poweroff the
> vm
> > the cores remains same in the dashboard.
> >
> >
> >
> >
> > Thanks and Regards,
> >
> > Bharat Saini
> >
> >
> >
> >
> >
> >
> > --- Disclaimer: --
> > This message and its contents are intended solely for the designated
> > addressee and are proprietary to Kloudspot. The information in this email
> > is meant exclusively for Kloudspot business use. Any use by individuals
> > other than the addressee constitutes misuse and an infringement of
> > Kloudspot's proprietary rights. If you are not the intended recipient,
> > please return this email to the sender. Kloudspot cannot guarantee the
> > security or error-free transmission of e-mail communications. Information
> > could be intercepted, corrupted, lost, destroyed, arrive late or
> > incomplete, or contain viruses. Therefore, Kloudspot shall not be liable
> > for any issues arising from the transmission of this email.
> >
>
> --- Disclaimer: --
> This message and its contents are intended solely for the designated
> addressee and are proprietary to Kloudspot. The information in this email
> is meant exclusively for Kloudspot business use. Any use by individuals
> other than the addressee constitutes misuse and an infringement of
> Kloudspot's proprietary rights. If you are not the intended recipient,
> please return this email to the sender. Kloudspot cannot guarantee the
> security or error-free transmission of e-mail communications. Information
> could be intercepted, corrupted, lost, destroyed, arrive late or
> incomplete, or contain viruses. Therefore, Kloudspot shall not be liable
> for any issues arising from the transmission of this email.
>

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be 

Re: CPU Core Consumption High

[Wei ZHOU]

Hi,

Did you poweroff from inside the VM or on cloudstack UI ?

-Wei

On Mon, 19 Feb 2024 at 09:53, Bharat Bhushan Saini
 wrote:

> Hi Wei/Darren,
>
>
>
> The issue was again trigged after the enable the 
> resource.count.running.vms.only
> option.
> I shut down all the vm’s but the resource utilization is same as before
> when vm’s are running.
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_2781584380]
>
>
>
> *From: *Wei ZHOU 
> *Date: *Tuesday, 13 February 2024 at 12:59 AM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CPU Core Consumption High
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
> +1.
>
> The setting was introduced in 4.14 by my PR
> https://github.com/apache/cloudstack/pull/3760
> However, to keep backwards compatibility, the default value was set to
> false, which does not make sense IMHO.
>
> -Wei
>
> 在 2024年2月12日星期一，Darren Cole  写道：
>
> > This caught me before as well.
> > By default resource.count.running.vms.only is set to false, so resources
> > are counted for all VMs.
> > On clusters I run I set this to true so that only running VMs are counted
> > for resource use.
> >
> > I have not tested 4.19 yet, but assume the setting stayed the same.
> > There are also some similar/related settings to determine how running
> > resources are counted.
> > Some of these are specific what is backing the VMs.
> > ie KVM, Xen, etc.
> >
> > Darren
> > --
> > This e-mail is confidential. Any distribution, use or copying of this
> > e-mail or the information it contains other than by the intended
> recipient
> > is forbidden. If you are not the intended recipient, please advise the
> > sender (by return e-mail or otherwise) immediately and delete this
> e-mail.
> >
> >
> > From: "Bharat Bhushan Saini" 
> > To: "users" 
> > Sent: Sunday, February 11, 2024 11:14:58 PM
> > Subject: CPU Core Consumption High
> >
> >
> >
> > Hi All,
> >
> >
> >
> > I am facing an issue regarding the core consumption by the cloudstack. I
> > started 2 vm with 6 cores and it takes 18 cores but when I poweroff the
> vm
> > the cores remains same in the dashboard.
> >
> >
> >
> >
> > Thanks and Regards,
> >
> > Bharat Saini
> >
> >
> >
> >
> >
> >
> > --- Disclaimer: --
> > This message and its contents are intended solely for the designated
> > addressee and are proprietary to Kloudspot. The information in this email
> > is meant exclusively for Kloudspot business use. Any use by individuals
> > other than the addressee constitutes misuse and an infringement of
> > Kloudspot's proprietary rights. If you are not the intended recipient,
> > please return this email to the sender. Kloudspot cannot guarantee the
> > security or error-free transmission of e-mail communications. Information
> > could be intercepted, corrupted, lost, destroyed, arrive late or
> > incomplete, or contain viruses. Therefore, Kloudspot shall not be liable
> > for any issues arising from the transmission of this email.
> >
>
> --- Disclaimer: --
> This message and its contents are intended solely for the designated
> addressee and are proprietary to Kloudspot. The information in this email
> is meant exclusively for Kloudspot business use. Any use by individuals
> other than the addressee constitutes misuse and an infringement of
> Kloudspot's proprietary rights. If you are not the intended recipient,
> please return this email to the sender. Kloudspot cannot guarantee the
> security or error-free transmission of e-mail communications. Information
> could be intercepted, corrupted, lost, destroyed, arrive late or
> incomplete, or contain viruses. Therefore, Kloudspot shall not be liable
> for any issues arising from the transmission of this email.
>

CS 4.19.0.0 - UI Session Timeout

[W. Verleger - proIO GmbH]

Hi guys,
 
I was wondering if the default session timeout for the UI has been changed 
since CS 4.19.0.0?
In CS 4.18 I've configured the session timeout variable in "server.properties" 
to:

# Max inactivity time in minutes for the session
session.timeout=60
 
But it seems to have no effect anymore. I will no longer get logged off anymore 
at all.
Is there a new variable?
 
Thank you!
 
Best regards,
 
Wilken


- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, 
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet. 

This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail in error) 
please notify 
the sender immediately and destroy this e-mail.  
Any unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden. 

Re: CPU Core Consumption High

[Bharat Bhushan Saini]

Hi Wei/Darren,

The issue was again trigged after the enable the 
resource.count.running.vms.only option.
I shut down all the vm’s but the resource utilization is same as before when 
vm’s are running.

Thanks and Regards,
Bharat Saini

[signature_2781584380]

From: Wei ZHOU 
Date: Tuesday, 13 February 2024 at 12:59 AM
To: users@cloudstack.apache.org 
Subject: Re: CPU Core Consumption High
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


+1.

The setting was introduced in 4.14 by my PR
https://github.com/apache/cloudstack/pull/3760
However, to keep backwards compatibility, the default value was set to
false, which does not make sense IMHO.

-Wei

在 2024年2月12日星期一，Darren Cole  写道：

> This caught me before as well.
> By default resource.count.running.vms.only is set to false, so resources
> are counted for all VMs.
> On clusters I run I set this to true so that only running VMs are counted
> for resource use.
>
> I have not tested 4.19 yet, but assume the setting stayed the same.
> There are also some similar/related settings to determine how running
> resources are counted.
> Some of these are specific what is backing the VMs.
> ie KVM, Xen, etc.
>
> Darren
> --
> This e-mail is confidential. Any distribution, use or copying of this
> e-mail or the information it contains other than by the intended recipient
> is forbidden. If you are not the intended recipient, please advise the
> sender (by return e-mail or otherwise) immediately and delete this e-mail.
>
>
> From: "Bharat Bhushan Saini" 
> To: "users" 
> Sent: Sunday, February 11, 2024 11:14:58 PM
> Subject: CPU Core Consumption High
>
>
>
> Hi All,
>
>
>
> I am facing an issue regarding the core consumption by the cloudstack. I
> started 2 vm with 6 cores and it takes 18 cores but when I poweroff the vm
> the cores remains same in the dashboard.
>
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
>
>
>
> --- Disclaimer: --
> This message and its contents are intended solely for the designated
> addressee and are proprietary to Kloudspot. The information in this email
> is meant exclusively for Kloudspot business use. Any use by individuals
> other than the addressee constitutes misuse and an infringement of
> Kloudspot's proprietary rights. If you are not the intended recipient,
> please return this email to the sender. Kloudspot cannot guarantee the
> security or error-free transmission of e-mail communications. Information
> could be intercepted, corrupted, lost, destroyed, arrive late or
> incomplete, or contain viruses. Therefore, Kloudspot shall not be liable
> for any issues arising from the transmission of this email.
>

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. Therefore, Kloudspot 
shall not be liable for any issues arising from the transmission of this email.

Re: Secondary Storage VM not getting started

[Daan Hoogland]

Kapil,
did you initiate your secondary storage (at
kvm01.p01.ops.sjc01.qualys.com:/mnt/data)?
and did you export the storage for it from the nfs server?
The error says there is a problem there.

On Mon, Feb 19, 2024 at 7:35 AM Kapil Bhuskute
 wrote:
>
> The secondary storage VM is not able to get deployed in CloudStack 4.19 with 
> below errors.
>
> Feb 16 13:25:08 qcs01 java[417597]: INFO  [o.a.c.e.o.VolumeOrchestrator] 
> (secstorage-1:ctx-adb3bb9a ctx-2cb81e1f) (logid:67e774fb) Adding disk object 
> [ROOT-6258] to VM [VM instance {"id":6258,"instanceName"
> :"s-6258-VM","type":"SecondaryStorageVm","uuid":"a9520deb-ca26-4a6f-bc40-871841d05c28"}]
> Feb 16 13:25:11 qcs01 java[417597]: ERROR [o.a.c.e.o.VolumeOrchestrator] 
> (Work-Job-Executor-2:ctx-511f3201 job-9178/job-13001 ctx-8a4381d2) 
> (logid:cbcf72ec) Unable to create volume [{"name":"ROOT-6258","uui
> d":"8444daf7-4145-4a40-8789-c623c5a5ad7c"}] due to 
> [com.cloud.utils.exception.CloudRuntimeException: 
> org.libvirt.LibvirtException: internal error: Child process (/usr/bin/mount 
> -o nodev,nosuid,noexec kvm01.
> p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222 
> /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) unexpected exit status 32: 
> mount.nfs: mounting 
> kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222
> failed, reason given by server: No such file or directory
> Feb 16 13:25:11 qcs01 java[417597]: 
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:5] is 
> unreachable: Unable to create volume 
> [{"name":"ROOT-6258","uuid":"8444daf7-4145-4a40-8789-c62
> 3c5a5ad7c"}] due to [com.cloud.utils.exception.CloudRuntimeException: 
> org.libvirt.LibvirtException: internal error: Child process (/usr/bin/mount 
> -o nodev,nosuid,noexec kvm01.p01.ops.sjc01.qualys.com:/mnt/d
> ata/template/tmpl/1/222 /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) unexpected 
> exit status 32: mount.nfs: mounting 
> kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222 failed, reason 
> given by server:
> No such file or directory
> Feb 16 13:25:41 qcs01 java[417597]: ERROR [o.a.c.e.o.VolumeOrchestrator] 
> (Work-Job-Executor-8:ctx-5417b759 job-9178/job-13003 ctx-f6230d28) 
> (logid:cbcf72ec) Unable to create volume [{"name":"ROOT-6258","uui
> d":"8444daf7-4145-4a40-8789-c623c5a5ad7c"}] due to 
> [com.cloud.utils.exception.CloudRuntimeException: 
> org.libvirt.LibvirtException: internal error: Child process (/usr/bin/mount 
> -o nodev,nosuid,noexec kvm01.
> p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222 
> /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) unexpected exit status 32: 
> mount.nfs: mounting 
> kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222
> failed, reason given by server: No such file or directory
> Feb 16 13:25:41 qcs01 java[417597]: 
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:5] is 
> unreachable: Unable to create volume 
> [{"name":"ROOT-6258","uuid":"8444daf7-4145-4a40-8789-c62
> 3c5a5ad7c"}] due to [com.cloud.utils.exception.CloudRuntimeException: 
> org.libvirt.LibvirtException: internal error: Child process (/usr/bin/mount 
> -o nodev,nosuid,noexec kvm01.p01.ops.sjc01.qualys.com:/mnt/d
> ata/template/tmpl/1/222 /mnt/63da2d8b-fe6a-36ab-93c5-49867865f5b7) unexpected 
> exit status 32: mount.nfs: mounting 
> kvm01.p01.ops.sjc01.qualys.com:/mnt/data/template/tmpl/1/222 failed, reason 
> given by server:
> No such file or directory
>
> Regards,
> Kapil Bhuskute



-- 
Daan