I ran into same issue. I'm setting up an ovirt module that has the sudoer file for ovirt 3.3.2. Are you using filebucket with puppet? If so, try restoring. - Trey On Jan 31, 2014 1:15 PM, "Matt Warren" <mwarren@hnw.com> wrote:

I'm putting vdsm on a host that is also managed by puppet. I'm tracing some of my troubles to the fact that puppet stepped on some sudoers config done by vdsm.

Is it possible to re-run the setup scripts for vdsm to regenerate the sudoers changes? _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On 01/31/2014 08:15 PM, Matt Warren wrote:

I'm putting vdsm on a host that is also managed by puppet. I'm tracing some of my troubles to the fact that puppet stepped on some sudoers config done by vdsm.

Is it possible to re-run the setup scripts for vdsm to regenerate the sudoers changes? _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

you can move the host to maint and chose re-install. maybe remove vdsm from the node for it setup to re-occur.