Thanks Daan - enjoy your weekend; nonetheless would be great if our PMCs can
participate in next week(s), (praying) before the end of the month.
Regards.
From: Daan Hoogland
Sent: Friday, July 10, 2020 23:08
To: dev
Cc: users@cloudstack.apache.org ;
I appreciate the response, but I'm not sure where you are going.
My secondary and primary storage are mounts from a NetApp filer. Both the
CentOS (CloudStack Management) and the ESXi hosts can read/write to the
secondary volume. I don't understand why cloudstack is setting the ownership
and
sorry Rohit, I have not given this any attention at all. Hopefully over the
weekend...
On Fri, Jul 10, 2020 at 5:28 PM Rohit Yadav
wrote:
> Bump - kindly participate.
>
> We require lazy concensus with at least three PMC +1s to go forward.
> Thanks.
>
> Regards,
> Rohit Yadav
>
>
Bump - kindly participate.
We require lazy concensus with at least three PMC +1s to go forward. Thanks.
Regards,
Rohit Yadav
From: Rohit Yadav
Sent: Wednesday, July 1, 2020 10:21:19 AM
To: d...@cloudstack.apache.org ;
users@cloudstack.apache.org
Subject:
Hello
If you check your NFS configuration you will see that somewhere you have :
/etc/idmapd.conf "nobody"
Regards,
Cristian
-Original Message-
From: Corey, Mike
Sent: Friday, July 10, 2020 7:01 PM
To: users@cloudstack.apache.org
Subject: RE: Initial SystemVM Creation
The system VM folder is being created as owner & permissions nobody:nobody. I
have to believe that is NOT SUPPOSED to be the case.
Because the directory /var/cloudstack/mnt/VM/345050029058.4f87a734 is locked
down, no other steps in the systemvm creation can continue.
I need help figuring out
Just try to execute the command manually, copy the system.iso from source
to the destination. I had a similar issue but is was caused by the NFS
permissions.
On Wed, 8 Jul 2020, 21:44 Corey, Mike, wrote:
> Gone over the installation now twice (reverted to snapshot of CentOS VM)
> and still
