Description
If the FeaturesService is unavailable during startup for some reason, after 5 minutes, you will get a TimeoutException from blueprint and the bundle goes into a failed state. If FeaturesService then becomes available, the features command bundle does not recover.
I think blueprint.graceperiod:=false is a good workaround to this. The user will see "FeaturesService service is unavailable" when issuing features commands rather than not being able to use them at all. Then when the feature is back the command operates normally.
There is a similar issue described in KARAF-1925.