Hi Li,
Can you post the stack trace of the faiure from the logs?
Regards,
Nicolas Vazquez
From: li jerry
Sent: Thursday, June 6, 2019 11:50 AM
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: Host's HA failed!
Hell All
We are trying to de
Yes snapshots are supposed to be in PS template copy.
On 6/6/19, 9:24 AM, "Yiping Zhang" wrote:
The nfs volume definitely allows root mount and have RW permissions, as we
already see the volume mounted and template staged on primary storage. The
volume is mounted as NFS3 datastore in vSp
The nfs volume definitely allows root mount and have RW permissions, as we
already see the volume mounted and template staged on primary storage. The
volume is mounted as NFS3 datastore in vSphere.
Volume snapshot is enabled, I can ask to have snapshot disabled to see if it
makes any different
Hell All
We are trying to deploy VMs as cloudstack management nodes over the compute
nodes, like hyper-converged infrastructure. But we found some issue with the HA
switch.
The test is based on CentOS 7.6 and CloudStack 4.11.2. The primary storage is
NFS.
We have enabled VM HA and Host HA, and
This option is 'vol options name_of_volume nosnapdir on' however if I recall it
right is supposed to work even with .snapshot directory visible
Can you find out all vol options on your netapp volume? I would be most
concerned about:
- NFS version - NFS v4 should be disabled
- security qtree mode
I did not try your fix but I will be trying to import image again soon and
see. My fix was to create directory in template/tmpl/2/209, then using th
UI I was able to remove the template.
Thanks again,
Jesse
On Wed, Jun 5, 2019 at 4:55 PM Nicolas Vazquez <
nicolas.vazq...@shapeblue.com> wrote:
To be fair, this fix is not a "fix" - it just allows "subtracting" CPU
flags for the vCPU from the base model presented, if the physical CPU
doesn't support it.
I spent some time yesterday googling - and it seems like a possible
kernel/qemu bug which is presented on just some CPU models.
Adam, I
On 6/5/19 7:56 PM, Rohit Yadav wrote:
> All,
>
> Bases on some conversation on a Github issue on moving to Python3 today, I
> would like to propose a PR after 4.13 is cut on deprecation of following
> hypervisors in the next major 4.14 release:
>
> - XenServer 6.2, 6.5 and older
> - VMware 5
Sounds like a good idea!
People can still stay on a older version of CS if needed for them.
We can't support older versions for ever.
Wido
On 6/5/19 7:56 PM, Rohit Yadav wrote:
> All,
>
> Bases on some conversation on a Github issue on moving to Python3 today, I
> would like to propose a PR a
