Comment 5 for bug 1901783

Even the segfault itself in syslog is not a guarantee of job failure. Happens for all node providers and happens on both ubuntu-focal and fedora-32 [1]:

2020-12-17T15:28:29.000-08:00 lvs[102392]: segfault at 800 ip 00007fa46b0b3860 sp 00007fff518238e8 error 4 in libc-2.31.so[7fa46af... SUCCESS ubuntu-focal rax-dfw
2020-12-17T15:18:20.000-08:00 lvs[150462]: segfault at 810 ip 00007f923e699a50 sp 00007ffda8a5ec38 error 4 in libc-2.31.so[7f923e5... SUCCESS fedora-32 rax-dfw
2020-12-17T14:35:05.000-08:00 lvs[156376]: segfault at 800 ip 00007f2ae51ac860 sp 00007ffd952947a8 error 4 in libc-2.31.so[7f2ae50... FAILURE ubuntu-focal rax-iad
2020-12-17T13:27:20.000-08:00 lvs[141354]: segfault at 800 ip 00007fb785c9b01e sp 00007ffedf1548f8 error 4 in libc-2.31.so[7fb785b... FAILURE fedora-32 ovh-bhs1
2020-12-17T11:47:10.000-08:00 lvs[125849]: segfault at 800 ip 00007fd9fe98c860 sp 00007ffdd7859fa8 error 4 in libc-2.31.so[7fd9fe8... FAILURE ubuntu-focal rax-dfw

[1] http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22lvs%5C%22%20AND%20message%3A%5C%22segfault%5C%22%20AND%20filename%3A%5C%22controller%2Flogs%2Fsyslog.txt%5C%22&from=7d