Hi,
We've found the problem.
One of the step on the playbook changed the permission of one of the path in script /usr/share/perl5/PVE/Report.pm
This caused to pveproxy to fail to start because it could not access that folder.
Resetting it to the correct permission solved the problem and permitted to pveproxy to start.
Maybe it could be good to put this cause is some page for troubleshooting, it was strange error and didn't give all the correct logs at the beginning.
Regards
Red
