+1
Did basic tests and the integration tests with Linstor as primary storage.
On Tue, Feb 11, 2025 at 3:25 PM Daan Hoogland wrote:
> Hi All,
>
> I've created a 4.19.2.0 release candidate, with the following
> artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/clo
I just noticed another mistake. I am closing this vote and will start a 3rd
one soon.
On Tue, Feb 11, 2025 at 3:28 PM Daan Hoogland wrote:
> please not that I forgot to update the commit-id, this should be
> f05fa27bfd843c6fea7b4a2d9e5c62ee21d57019
>
> Hi All,
>
> I've created a 4.19.2.0 release
Hi All,
I've created a 4.19.2.0 release candidate, with the following
artifacts up for a vote:
Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.19.2.0-RC20250212T1722
Commit: 7f0eed39419b6076eed8db39a8cd3be326a49a2d
Source release (checksums and signatures are available at
daviftorres opened a new pull request, #479:
URL: https://github.com/apache/cloudstack-documentation/pull/479
On Ubuntu 24.04 LTS I found the described issue with the forwarding traffic
back and fourth from guests system VMs and the physical interfaces attached to
the bridges.
--
Hi all,
So far I tested the GitHub branch link exists and the full commit sha is
correct.
Next I checked the source release and the shasum 512 was correct.
Printed some details about the signature
Signature made Thu 13 Feb 2025 02:22:26 AEST
gpg:using RSA key 256ABDFB8D89EDE0754
ccheline closed pull request #26: Fixed example code replacement of space
URL: https://github.com/apache/cloudstack-docs/pull/26
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
