Hi,
Using icingacli vspheredb check vm doesn't work on vms that are in a vapp. It returns the following:
[UNKNOWN] Icinga\Module\Vspheredb\Monitoring\Rule\MonitoringRuleSet::loadOptionalForUuid(): Argument #1 ($uuid) must be of type string, null given, called in /usr/share/icingaweb2/modules/vspheredb/library/Vspheredb/Monitoring/Rule/InheritedSettings.php on line 32
Doing so via the gui (/vspheredb/vm/monitoring) does the same:
Moving the vm outside of the vapp and then trying again makes it work again:
It sounds like this should have been fixed in #379, but I'm getting this with the 1.8.0 version in vsphere 8.0.3 and 7.0.3.
I noticed that when adding a new vcenter, it doesn't show a path for vms that are in vapps
While there is no path, the Monitoring check doesn't work. The path is however present once I move the vm outside of the vapp and appears to still be present after moving it back inside the vapp. Even after moving it back, the check still works.
Screenshot after moving it ouside the vapp:
Screenshot after moving it back in:
The logs show the following when adding a new vcenter (version 7.0.3):
Logs when adding a new vcenter (version 8.0.3):

Hi,
Using
icingacli vspheredb check vmdoesn't work on vms that are in a vapp. It returns the following:[UNKNOWN] Icinga\Module\Vspheredb\Monitoring\Rule\MonitoringRuleSet::loadOptionalForUuid(): Argument #1 ($uuid) must be of type string, null given, called in /usr/share/icingaweb2/modules/vspheredb/library/Vspheredb/Monitoring/Rule/InheritedSettings.php on line 32Doing so via the gui (/vspheredb/vm/monitoring) does the same:
Moving the vm outside of the vapp and then trying again makes it work again:
It sounds like this should have been fixed in #379, but I'm getting this with the 1.8.0 version in vsphere 8.0.3 and 7.0.3.
I noticed that when adding a new vcenter, it doesn't show a path for vms that are in vapps
While there is no path, the Monitoring check doesn't work. The path is however present once I move the vm outside of the vapp and appears to still be present after moving it back inside the vapp. Even after moving it back, the check still works.
Screenshot after moving it ouside the vapp:
Screenshot after moving it back in:
The logs show the following when adding a new vcenter (version 7.0.3):
Logs when adding a new vcenter (version 8.0.3):