Using `icingacli-businessprocess` causes exception in `ipl-sql`

[TheSyscall]

Describe the bug

Using icingacli-businessprocess with monitoring and icingadb seems to cause
an exception in ipl-sql in the service details page of the monitoring module.

To Reproduce

1. have BOTH icingadb and monitoring enabled.
2. create a businessprocess
3. use icingacli-businessprocess to create a dummy service
4. visit the service details page

Expected behavior

Display the service details page.

Screenshots

Exception

Too few arguments to function ipl\Sql\Connection::select(), 0 passed in /usr/share/icingaweb2/modules/businessprocess/library/Businessprocess/State/MonitoringState.php on line 76 and exactly 1 expected

#0 /usr/share/icingaweb2/modules/businessprocess/library/Businessprocess/State/MonitoringState.php(76): ipl\Sql\Connection->select()
#1 /usr/share/icingaweb2/modules/businessprocess/library/Businessprocess/State/MonitoringState.php(41): Icinga\Module\Businessprocess\State\MonitoringState->reallyRetrieveStatesFromBackend()
#2 /usr/share/icingaweb2/modules/businessprocess/library/Businessprocess/State/MonitoringState.php(32): Icinga\Module\Businessprocess\State\MonitoringState->retrieveStatesFromBackend()
#3 /usr/share/icingaweb2/modules/businessprocess/library/Businessprocess/ProvidedHook/Monitoring/DetailviewExtension.php(98): Icinga\Module\Businessprocess\State\MonitoringState::apply()
#4 /usr/share/icingaweb2/modules/monitoring/library/Monitoring/Web/Controller/MonitoredObjectController.php(99): Icinga\Module\Businessprocess\ProvidedHook\Monitoring\DetailviewExtension->getHtmlForObject()
#5 /usr/share/icingaweb2/modules/monitoring/application/controllers/ServiceController.php(72): Icinga\Module\Monitoring\Web\Controller\MonitoredObjectController->showAction()
#6 /usr/share/icinga-php/vendor/vendor/icinga/zf1/library/Zend/Controller/Action.php(528): Icinga\Module\Monitoring\Controllers\ServiceController->showAction()
#7 /usr/share/php/Icinga/Web/Controller/Dispatcher.php(78): Zend_Controller_Action->dispatch()
#8 /usr/share/icinga-php/vendor/vendor/icinga/zf1/library/Zend/Controller/Front.php(954): Icinga\Web\Controller\Dispatcher->dispatch()
#9 /usr/share/php/Icinga/Application/Web.php(296): Zend_Controller_Front->dispatch()
#10 /usr/share/php/Icinga/Application/webrouter.php(107): Icinga\Application\Web->dispatch()
#11 /usr/share/icingaweb2/public/index.php(4): require_once(String)
#12 {main}

Your Environment

• Icinga Web 2 version and modules (System - About): 2.13.0
• icinga/icinga-php-library: 0.19.0
• icinga/icinga-php-thirdparty: 0.15.0
• icinga/icinga-php-legacy: 1.0.4
• Web browser used: firefox
• Icinga 2 version used (icinga2 --version): r2.15.2
• PHP version used (php --version): 8.4.19
• Server operating system and version: fedora 42

Additional context

Add any other context about the problem here.

[sukhwinder33445]

I still cannot reproduce the bug with the given information here and as discussed offline. Could you please explain in detail how I can reproduce it? You must also mention the director, as it plays a main role in this issue.
Please mention which objects are created by the director and also add the business process config file and object config.

[sukhwinder33445]

I was able to reproduce the bug with the help of @TheSyscall and have optimized the steps:

1. Create a new service:

apply Service "bp-test" {
  check_command = "icingacli-businessprocess"

  vars.icingacli_businessprocess_config = "test"
  vars.icingacli_businessprocess_process = "root"

  assign where host.name == "dummy-0"
}

2. Use the following business process config:

### Business Process Config File ###
#
# Title           : 
# Description     : 
# Owner           : icingaadmin
# AddToMenu       : yes
# Backend         : 
# Statetype       : soft
#
###################################

root = docker-master;Hoststatus
display 1;root;root

3. Make sure the monitoring and icingadb modules are enabled.
4. Open the service detail view in the monitoring module (icingaweb2/monitoring/service/show?host=dummy-0&service=bp-test).