Segfault Upgrade Icinga 2.13.7 -> 2.14.0

Describe the bug

Icinga 2 crashes immediatly after start/restart.

After upgrading Icinga 2 from 2.13.7 to 2.14.0 the configuration master ran into a segfault.

To Reproduce

Unknown. First occurence of the error after deploying new configuration -> a reload of the service.

Expected behavior

Icinga 2 should not crash.

Your Environment

Include as many relevant details about the environment you experienced the problem in

• Version used (icinga2 --version): 2.14.0
• Operating System and version: RHEL 8.8
• Enabled features (icinga2 feature list):
  • api;
  • checker;
  • icingadb;
  • ido-mysql;
  • influxdb2;
  • mainlog;
  • notification
• Icinga Web 2 version and modules (System - About): 2.11.4
  • cube 1.3.0
  • director 1.10.2
  • grafana 1.4.3
  • icingadb 1.0.2
  • idoreports 0.10.0
  • incubator 0.20.0
  • jira 1.3.0
  • monitoring 2.11.4
  • nagvis 1.1.1
  • pdfexport 0.10.2
  • vspheredb 1.7.1
  • x509 1.2.1

Additional context

Worth mentioning:

Aug 23 11:04:42 **** systemd[1]: Started Icinga host/service/network monitoring system.
Aug 23 11:04:45 **** systemd[1]: icinga2.service: Main process exited, code=exited, status=139/n/a
Aug 23 11:04:45 **** systemd[1]: icinga2.service: Failed with result 'exit-code'.
Aug 23 11:06:47 **** systemd[1]: Starting Icinga host/service/network monitoring system...

As well as the segfault itself.

Aug 23 11:06:58 **** icinga2[22890]: [2023-08-23 11:06:58 +0200] information/cli: Closing console log.
Aug 23 11:06:58 **** systemd[1]: Started Icinga host/service/network monitoring system.
Aug 23 11:07:00 **** kernel: icinga2[23000]: segfault at 1b0 ip 0000000000f6146c sp 00007f401f74b1c0 error 4 in icinga2[400000+ebe000]
Aug 23 11:07:00 **** kernel: Code: 00 48 89 43 10 48 c7 43 18 00 00 00 00 0f ae f0 f0 48 83 45 00 01 e8 83 37 a6 ff f0 48 83 45 00 01 0f b6 44 24 0c 48 8b 0c 24 <4c> 8b a1 b0 01 00 00 4c 8d a9 b8 01 00 00 88 44 24 28 48 8b 84 24
Aug 23 11:07:01 **** systemd[1]: icinga2.service: Main process exited, code=exited, status=139/n/a

We've attempted to produce a core dump, but were not able to. Due to the fact that the system is in production the environment was downgraded to 2.13.8.

No source file, test, or reproducible configuration is named. Start by comparing the 2.13.7/2.14.0 startup and reload behavior on RHEL 8.8 using the reported systemd and kernel logs; done means the service starts and reloads without a segfault, with a regression test or reproducible diagnosis if available.