Dears,

I have the following Bugs that crashed my VM, I reported it to RH, they didn't answer, and banned my developer account, the Bug is when you disable the network on RHEL with OSP 14 installed all in one, it crashes the system, I had a 12GB RAM, with 8 CPUs on the VM, and I found out that this crash report pissed off someone in RH, because they called me, and said what do you want from me!!, what I need is a Simple reply, is this a bug or not.

here is the problem:

[root@localhost network-scripts]# systemctl status network -l ? network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2019-01-19 03:47:01 EST; 21s ago Docs: man:systemd-sysv-generator(8) Process: 86319 ExecStop=/etc/rc.d/init.d/network stop (code=exited, status=0/SUCCESS) Process: 86591 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE) Tasks: 0

Jan 19 03:47:01 localhost.localdomain dhclient[86963]: Please report for this software via the Red Hat Bugzilla site: Jan 19 03:47:01 localhost.localdomain dhclient[86963]: http://bugzilla.redhat.com Jan 19 03:47:01 localhost.localdomain dhclient[86963]: ution. Jan 19 03:47:01 localhost.localdomain dhclient[86963]: exiting. Jan 19 03:47:01 localhost.localdomain network[86591]: failed. Jan 19 03:47:01 localhost.localdomain network[86591]: [FAILED] Jan 19 03:47:01 localhost.localdomain systemd[1]: network.service: control process exited, code=exited status=1 Jan 19 03:47:01 localhost.localdomain systemd[1]: Failed to start LSB: Bring up/down networking. Jan 19 03:47:01 localhost.localdomain systemd[1]: Unit network.service entered failed state. Jan 19 03:47:01 localhost.localdomain systemd[1]: network.service failed. [root@localhost network-scripts]#

[root@localhost log]# Message from syslogd@localhost at Jan 23 02:23:31 ... kernel:NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [ovsdb-server:10088]

[root@amer network-scripts]# Message from syslogd@amer at Jan 27 12:46:38 ... kernel:NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [nova-api:102738]

Message from syslogd@amer at Jan 27 19:26:19 ... kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 26s! [swapper/5:0]

Message from syslogd@amer at Jan 27 19:26:19 ... kernel:NMI watchdog: BUG: soft lockup - CPU#1 stuck for 27s! [dmeventd:71548]

Message from syslogd@amer at Jan 27 19:27:30 ... kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [6_scheduler:64928]

Message from syslogd@amer at Jan 27 19:31:25 ... kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [ksoftirqd/5:34]

Message from syslogd@amer at Jan 27 19:32:42 ... kernel:NMI watchdog: BUG: soft lockup - CPU#3 stuck for 33s! [swift-object-up:11358]

Message from syslogd@amer at Jan 27 19:33:55 ... kernel:NMI watchdog: BUG: soft lockup - CPU#3 stuck for 24s! [dmeventd:71548]

Message from syslogd@amer at Jan 27 19:34:25 ... kernel:NMI watchdog: BUG: soft lockup - CPU#2 stuck for 65s! [kworker/2:0:59993]

Message from syslogd@amer at Jan 27 19:37:50 ... kernel:NMI watchdog: BUG: soft lockup - CPU#2 stuck for 24s! [kworker/u256:3:8447]

Message from syslogd@amer at Jan 27 19:37:50 ... kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [ksoftirqd/5:34]

Message from syslogd@amer at Jan 27 19:37:51 ... kernel:NMI watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [systemd:11968]

The CPU has been disabled by the guest operating system. Power off or reset the virtual machine.

snapshots attached [image: Red Hat Enterprise Linux 7 64-bit (2)-2019-01-28-03-57-27.png] [image: Red Hat Enterprise Linux 7 64-bit (2)-2019-01-28-04-26-41.png] [image: working solution.JPG] the last snapshot is from a successful installation of OSP 14 that specifically says that Kernel is not compatible with Firmware (Bios).

I didn't test on Debian flavors but I think it's the same, the problem is with RabbitMQ heart beats, when the server is disconnected it times out causing this problem of kernel loop.

Thanks and Best regards Amer