<div dir="ltr">Thanks Michal, if reinstalling the engine, (which also had SELinux disabled at install), would the best way be to backup the engine and then restore just the ovirt config?<div><br></div><div>Cheers,</div><div><br></div><div>Cam</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 11, 2016 at 2:14 PM, Michal Skrivanek <span dir="ltr"><<a href="mailto:michal.skrivanek@redhat.com" target="_blank">michal.skrivanek@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On 11 May 2016, at 15:02, Cam Mac <<a href="mailto:iucounu@gmail.com">iucounu@gmail.com</a>> wrote:<br>
><br>
> Hi,<br>
><br>
> In the oVirt guide, it says that "SELinux is being used by default on oVirt Node", but then goes on to say that if you have problems you should set it to permissive mode. I have had a few things fail due to being blocked by SELinux on a node I later enabled SELinux on, as it was off at install time. The other node which has had SELinux on from the start and so far has not had any oVirt operations blocked. I am guessing that the oVirt install process creates the necessary rules to allow vdsm to run under SELinux. So if you want to set SELinux to enforcing after installation, is there a script to do this, or is it better to just reinstall the node or engine, rather than trying to work out the individual exceptions?<br>
<br>
</span>For oVirt node it’s easier to reinstall it, it doesn’t persist much and it’s the easies way how to get the labelling right<br>
<br>
Thanks,<br>
michal<br>
<br>
><br>
> Thanks,<br>
><br>
> Cam<br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
<br>
</blockquote></div><br></div>