I'd really like to help, but I'm confused. You say that you are not looking for a solution for the errors, so what exactly is it you are asking for?
In case it's just the vCSA deployment, please provide some details, about the steps you took, and the issue you are facing.
like the correct way to virtualized or gotchas or something like that that can check and compare with my vESXi's or something in the config to compare in the physical ESXi host or something to check it up to see my fault.
Solutions will emerge eventually but I need to just to stick to the config to get it up and running to be able to create the vsan node and everything for VAN to work nested since this is just the top of a bunch of things to test on top of it.
thanks for your kind response.
The main 'gotcha' I have noted from nested vSAN labs (and specifically when adding/creating Disk-Groups) is not providing sufficient memory to the hosts to do so.
I did notice as well in 7.0 vs previous versions that it is way stricter on this - in older versions you might get away with the bare minimum (provided the DGs are tiny) but in 7.0 if providing the same amount of available memory run into either not being able to create DGs or have them drop off or fail to mount on boot etc.:
I noticed that when I gave nested ESXi servers only 8 GB of ram, they would boot but vSAN would not work. When I gave them 10GB, it started working. The disk-groups where very small but vSAN does consume memory obviously as Bob stated.
In reality, to actually host a couple of small VM's on those nested vSAN nodes, I had to give them 12GB of RAM.