It is caused by the following (Vaadin internal) code:
The class OsgiVaadinResources is located in the vaadin-shared bundle. If the bundle is not yet started, the call will fail, leaving the bundles in a weird state.
With some Karaf Shell Kung Fu you can see the details of the problem:
There is a workaround mentioned in the issue, but also seems to be fixed in Vaadin 8.6.0 and higher versions.
This behavior happens intermittently when restarting OpenNMS.
health:check shows bundle 85 is waiting:
Bundles:
diag:
nothing exposing the service in question: