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

Hi Swen, The KVMHAMonitor is initialised here even if you didn't enable the HA. If I may advise you to

Re: K8s Dashboard Not Found

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:

Re: K8s Dashboard Not Found

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

Re: K8s Dashboard Not Found

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

Re: K8s Dashboard Not Found

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”

Re: K8s Dashboard Not Found

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

Re: K8s Dashboard Not Found

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

Re: K8s Dashboard Not Found

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,

K8s Dashboard Not Found

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

Re: CPU Core Consumption High

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

Re: [VOTE] next version 20 instead of 4.20

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

ha checks on kvm hosts running even with ha disabled

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

Re: restrict Instance console access

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 -

Re: [VOTE] next version 20 instead of 4.20

+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

Re: Site-to-Site VPN to Opnsense

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

Re: restrict Instance console access

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

Re: Site-to-Site VPN to Opnsense

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

Re: Site-to-Site VPN to Opnsense

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

RE: [VOTE] next version 20 instead of 4.20

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

restrict Instance console access

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

Re: [VOTE] next version 20 instead of 4.20

+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

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

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

Re: [VOTE] next version 20 instead of 4.20

+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

RE: [VOTE] next version 20 instead of 4.20

+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

[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

Re: Secondary Storage VM not getting started

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

RE: Secondary Storage VM not getting started

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

Re: CS 4.19.0.0 - KVM Reboot Loop

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

CS 4.19.0.0 - KVM Reboot Loop

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

Re: CPU Core Consumption High

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

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

readyForShutdown api call every second

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

Community Events this Week

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

Re: CPU Core Consumption High

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

Re: CPU Core Consumption High

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

Re: CPU Core Consumption High

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

CS 4.19.0.0 - UI Session Timeout

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

Re: CPU Core Consumption High

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

Re: Secondary Storage VM not getting started

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