<html><body><div>Ok, I will try to disable selinux and deploy one more compute node. I just stumbled across another issue, not sure if it is related. The instance seems to be deployed just fine but now I looked on the console and neither cirros nor centos 7 seem to be booting up correctly. <br></div><div><br data-mce-bogus="1"></div><div>on cirros i see an error:<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div><pre class="logs"><pre class="logs">[ 0.846019] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---<br><br>and on centos7:<br><br>error: not a correct XFS inode.<br><br>I tried to create with ephemeral and volume.<br><br>Cheers,<br>Oliver<br></pre></pre></div><div>Am 19. Oktober 2020 um 16:09 schrieb Alex Schultz <aschultz@redhat.com>:<br><br><div><blockquote type="cite"><div class="msg-quote"><div class="_stretch"><span class="body-text-content">On Mon, Oct 19, 2020 at 7:59 AM Oliver Weinmann <oliver.weinmann@me.com> wrote:<br><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">First of all thanks a lot for the quick reply.</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">I just checked and it seems that the package is really not available for centos8 from the upstream repo:</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite"><a href="https://centos.pkgs.org/8/centos-appstream-x86_64/podman-1.6.4-15.module_el8.2.0+465+f9348e8f.x86_64.rpm.html" data-mce-href="https://centos.pkgs.org/8/centos-appstream-x86_64/podman-1.6.4-15.module_el8.2.0+465+f9348e8f.x86_64.rpm.html">https://centos.pkgs.org/8/centos-appstream-x86_64/podman-1.6.4-15.module_el8.2.0+465+f9348e8f.x86_64.rpm.html</a><br data-mce-bogus="1"></blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">When you say it should be available via rdo, does this mean I have to add or use a different repo when deploying undercloud / overcloud? I have followed the tripleo guide to deploy it:</blockquote><br>I thought we shipped it, maybe we don't because we run with selinux<br>disabled so it doesn't show up in CI.<br><br><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite"><a href="https://docs.openstack.org/tripleo-docs/latest/" data-mce-href="https://docs.openstack.org/tripleo-docs/latest/">https://docs.openstack.org/tripleo-docs/latest/</a><br data-mce-bogus="1"></blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">And is there a way to disable selinux on all overcloud nodes by default? I guess it is the default to disable it?</blockquote><br>Set the following in an environment file as part of the deployment:<br><br>parameter_defaults:<br> SELinuxMode: permissive<br><br><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">Cheers,</blockquote><blockquote class="quoted-plain-text" type="cite">Oliver</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">Am 19. Oktober 2020 um 15:29 schrieb Alex Schultz <aschultz@redhat.com>:</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">On Mon, Oct 19, 2020 at 7:09 AM Oliver Weinmann <oliver.weinmann@me.com> wrote:</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">Hi all,</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">I have successfully deployed the overcloud many many times, but this time I have a strange behaviour. Whenever I try to launch an instance it fails. I checked the logs on the compute node and saw this error:</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">Failed to build and run instance: libvirt.libvirtError: internal error: process exited while connecting to monitor: libvirt: error : cannot execute binary /usr/libexec/qemu-kvm: Permission denied</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">googling led me to the solution to disable selinux:</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">setenforce 0</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">I have not made this change persistent yet, as I would like to know why I'm facing this issue right now. What is actually the default for the overcloud nodes SeLinux? Enforcing, permissive or disabled? I build the ipa and overcloud image myself as I had to include drivers. Is this maybe the reason why SeLinux is now enabled, but is actually disabled when using the default ipa images?</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">From a TripleO perspective, we do not officially support selinux</blockquote><blockquote class="quoted-plain-text" type="cite">enabled when running with CentOS. In theory it should work, however</blockquote><blockquote class="quoted-plain-text" type="cite">it is very dependent on versions. I think you're likely running into</blockquote><blockquote class="quoted-plain-text" type="cite">an issue with the correct version of podman which is likely causing</blockquote><blockquote class="quoted-plain-text" type="cite">this. We've had some issues as of late which require a very specific</blockquote><blockquote class="quoted-plain-text" type="cite">version of podman in order to work correctly with nova compute when</blockquote><blockquote class="quoted-plain-text" type="cite">running with selinux enabled. You need 1.6.4-15 or higher which I</blockquote><blockquote class="quoted-plain-text" type="cite">don't think is available with centos8. It should be available via</blockquote><blockquote class="quoted-plain-text" type="cite">RDO.</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">Related: <a href="https://review.opendev.org/#/c/736173/" data-mce-href="https://review.opendev.org/#/c/736173/">https://review.opendev.org/#/c/736173/</a><br data-mce-bogus="1"></blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">Thanks and Best Regards,</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">Oliver</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><br><br></span></div></div></blockquote></div></div></body></html>