Description of problem: This environment had been very stable for several months then instance creations were failing/slow/retrying. Upon investigation we found that ovn-controller had crashed and was in a defunct state on the system(s). The ovn_controller container was still running but no logging; we don't believe any instances could be created after the fault. crash from /var/log/messages Aug 17 01:01:30 HOSTNAME setroubleshoot[35520]: SELinux is preventing (coredump) from remount access on the filesystem . For complete SELinux messages run: sealert -l 603f49ff-3068-4629-b399-b92abd7963d9 Aug 17 01:01:30 HOSTNAME platform-python[35520]: SELinux is preventing (coredump) from remount access on the filesystem .#012#012***** Plugin catchall (100. confidence) suggests **************************#012#012If you believe that (coredump) should be allowed remount access on the filesystem by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c '(coredump)' --raw | audit2allow -M my-coredump#012# semodule -X 300 -i my-coredump.pp#012 Aug 17 01:01:30 HOSTNAME systemd-coredump[35517]: Process 775194 (ovn-controller) of user 0 dumped core.#012#012Stack trace of thread 8:#012#0 0x000055fa865f5aa1 n/a (/usr/bin/ovn-controller) Version-Release number of selected component (if applicable): ovn2.13-20.12.0-85.el8fdp.x86_64 How reproducible: unknown - ovn-controller running for several months without issues. Steps to Reproduce: 1. unknown 2. 3. Additional info: Will provide additional details in privates comments
Closing this issue. It's been a couple of years, plus this is reported against a version of OVN that is now old and unsupported.