Hi Gregoire,
For 4.9, no systemvmtemplate upgrade is necessary. Please re-perform your tests
without upgrading systemvmtemplate and let us know what failed and what steps
were performed, thanks.
Regards.
From: Grégoire Lamodière
Sent: Wednesday, September 13
Hi Sean,
Thanks, I think these issues were missed from the list since the list is
created using git log summary that have the CLOUDSTACK- prefix, I checked
the specific commits don't have the JIRA id in the git commit's summary.
However, this is not a blocker you may send a PR against the
Hi Rohit,
Thank your for your answer.
My tests were done without upgrading systemvmtemplates, and I have few more
results :
1/ It fails for both old (created on 4.9.2) and new (created on 4.9.3) VPC
2/ It fails for old (4.9.2) and new (4.9.3) instances
3/ As long as the virtual routeur (created
CloudStack Mgmt: CentOS Linux release 7.3.1611
Hypervisor: XenServer
-Original Message-
From: Rene Moser [mailto:m...@renemoser.net]
Sent: Tuesday, September 12, 2017 7:13 AM
To: users@cloudstack.apache.org
Subject: Quick 1 Question Survey
What Linux OS and release are you running below
Hi Gregoire,
Thanks for sharing, can you share:
- Your environment details, hypervisors, basic vs advance zone/networking,
storage (NFS vs local storage etc)
- What is your management server os? (centos6, 7, or ubuntu?)
- When you say your VPC failed in 4.9.3.0, what exactly works or does not
Cloud 1:
Cloudstack Management / Nodes = Centos 6.9 (CS 4.9)
KVM/XEN = KVM+CLVM
Cloud 2 / 3 / 4:
Cloudstack Management / Nodes = Ubuntu 14.04 (CS 4.9)
KVM/XEN = KVM+NFS+Local Storage (cloud 2/4)
On 12/09/2017 13:12, Rene Moser wrote:
What Linux OS and release are you running below your:
*
