Cloudstack VXLAN at the Host Re: EVPN VXLANY hosts communicate to VXLANX hosts Do we need Traditional Vlans

2025-01-10 Thread Chi vediamo
Forgot to add Wido The Isolation should start, and should happen at the HOST running KVM, No VLANS needed at the Host, neither at the Leafs. But seems isolation is not happening! using cloudstack 4.20, maybe is a detail missing on my side. What Cloudstac documentation mean with "On the Spine ro

Re: A possible bug in instance start for end users when a host is deleted

2025-01-10 Thread Nux
Good call, Daan, I remember this bug getting fixed a while ago, seems to show up like a bad penny. On 2025-01-10 12:38, Daan wrote: Eric, Do you have the means to test a PR? if so, please have a look at [10175](https://github.com/apache/cloudstack/pull/10175/) On 2025/01/10 08:54:30 Daan H

Re: A possible bug in instance start for end users when a host is deleted

2025-01-10 Thread Daan
Eric, Do you have the means to test a PR? if so, please have a look at [10175](https://github.com/apache/cloudstack/pull/10175/) On 2025/01/10 08:54:30 Daan Hoogland wrote: > Makes sense Eric, I'll reapply this old PR on 4.19 > > On Fri, Jan 10, 2025 at 9:31 AM Eric Green wrote: > > > I don’t

Re: Secondary Storage Snapshot Priority

2025-01-10 Thread Granwille Strauss
Hi Guys Any feedback on how CM determines the next available storage location for a snapshot? Or are we meant to manually re-balance secondary storage when this happens? On 1/7/25 12:24, Granwille Strauss wrote: Good Day, Compliments of the season! I have a quick question I would like to

Webhook Body/Content Blank

2025-01-10 Thread Granwille Strauss
Good Day, I am testing out webhook integration with our local chat server (RocketChat), I have successfully configured a global hook, upon running some test to trigger events, I can confirm that hook reaches my sever without any issues. However, the JSON content does not display accordingly a

Re: A possible bug in instance start for end users when a host is deleted

2025-01-10 Thread Daan Hoogland
Makes sense Eric, I'll reapply this old PR on 4.19 On Fri, Jan 10, 2025 at 9:31 AM Eric Green wrote: > I don’t know that it’s acceptable as a known bug for 4.19 unless the > workaround that I did for my cluster (whack last_host_id in the database if > it points at removed hosts) is documented. >

Re: A possible bug in instance start for end users when a host is deleted

2025-01-10 Thread Eric Green
I don’t know that it’s acceptable as a known bug for 4.19 unless the workaround that I did for my cluster (whack last_host_id in the database if it points at removed hosts) is documented. But honestly, any bug that requires manually whacking things in the database as a workaround probably need

Re: [DISCUSS]to disable the agent property setting `reboot.host.and.alert.management.on.heartbeat.timeout` by default

2025-01-10 Thread Daan Hoogland
your proposal seems sensible for the most part Slavka, There is just one concern I have with this Such behaviour can create several problems. If the primary storage is > temporarily not accessible, all hosts could reboot. VMs become dysfunctional if their storage has been inaccessible and become

Re: A possible bug in instance start for end users when a host is deleted

2025-01-10 Thread Daan Hoogland
Wei, Eric, This sounds like we must reapply for 4.19, and make sure it doesn't get pulled forward. The 4.20 code for this class has been heavily refactorred. We could also accept this as a known bug for 4.19? On Fri, Jan 10, 2025 at 8:47 AM Eric Green wrote: > Thanks, Wei. The log definitely s