I think the issue cannot be classified as blocker as it's specific to just UI,
a user may still use the API for the specific case where offering has root
disk. There are some other issues reported like this as well.
RC3 may not be strictly necessary but I'm willing to cut it, but let's do it on
I hate to bring bad news, but I found an issue caused by PR #5085 [1].
The issue affects only VM deployment via UI when using an offering that has
root disk size.
I've just opened PR #5150 [2]; tested it and this fixes the issue.
Sorry for the inconvenience but this might require a third round. Wh
Dear All,
I’d like to put myself forward as the release manager for 4.16.0.0 and my
colleagues Suresh Anaparti and Rohit Yadav as the co-RMs.
For 4.16.0.0 my colleague Suresh will assist me during the process for
reviewing/testing/merging the PRs, others will be welcome to support as well.
I p
+1
Did some manual tests with RC2 packages deploying a new environment.
(Advanced zone with 2x XCP-ng 8.2 hosts, 2x NFS storage pools)
* VM - deploy, stop-start, reset, migrate, expunge
* Volumes - attach, detach, migrate
* Templates - register, delete
* Network - restart, cleanu
Maybe Rocky is a good replacement for CentOS. We will see. We dont
have so much choices. For me its important to support the Commercial
RHEL one besides the Community.
Thanks and
Cheers,
Sven Vogel
Apache CloudStack PMC member
On Wednesday, 06/23/2021 at 06:40 David Jumani wrote:
+1
I t
The voting window has finished, the vote now remains open until we've lazy
consensus (min. 3 +1/binding and no -1s/vetos). Thanks to all those who have
tested and voted, kindly continue testing/voting.
I'll add mine based on automated smoketests results and manually testing
template registratio
+1
The following upgrades has been tested and passed successfully:
Upgrade from 4.11.3:
Xen 7.1
VMWare: 60u2
KVM CentOS7
Upgrade from 4.13.1:
Xen 7.2
XCP-NG 7.4
VMWare 65u2
KVM CentOS7
Upgrade from 4.14.1:
Xen 7.4
XCP-NG 8.1
KVM CentOS8
Upgrade from 4.15.0:
Xen 8.1
VMWare 67u3
KVM CentOS7
KVM C
Hi Rohit,
+1 from our side, too.
All our reported issues from rc1 are solved in rc2 and our tests (mostly VMware
related) passed successful.
Many thanks for great support and hard work.
Regards,
Michael
Geschäftsführung: Mirko Kruse, André Walter
Sitz und Amtsgericht: Dresden, HRB 21356
This
+1 (binding)
We’ve done upgrade tests from major previous versions and number of smoketests
executions. Also some manual verification was done around lifecycle operations
for: VMs, Volumes, Networks, Infrastructure and others.
Thanks,
Bobby.
From: Rohit Yadav
Date: Monday, 21 June 2021, 15:23
A thing that I briefly touched somewhere upstairs ^^^ - for each
traffic
type you have defined - you need to define a traffic label - my
deduction
capabilities make me believe you are using KVM, so you need to set
your KVM
traffic label for all your network traf
10 matches
Mail list logo
