Jan
Jan
We got the same issue and the workaround from @mgaruccio works for us.
I stumbled across this issue now too. With vSphere 6.5 it was working, on another vCenter with 7.0.3 it occurs. Ansible version 2.9.9 Collection version 2.5.0
> ... Keep in mind it doesn't work well when changing those settings back and forth. Once the database is initialized it will somehow rebel against changes and output weird...
Just in case, it looks like the only way to get authentication running is to delete and recreate the volume until now, e.g. #232