LifeCycle pattern dosn't work (for me at least)

Here's the problem:
I have LifeCycleNode implemented as component. The node has to received some data from a service to pass Configuration state. I bet you've already got the point. The configuration func is deadlocked. Because I can't return control to a component_container, cause configuration is not finished. I can't finish configuration, cause I've not received the data from the service (stiil awaiting). To receive response some of spins has to be called, but I can't do this, because my node will be double-registrated in that case. I cannot create another node (for client purpose) and destroy it after response is received, because any new node inside component derive name from parent. I cannot create sub-node, cause my node is derived from LifeCycleNode.
May be messed up a little bit, but it seems to me, that is is a bug.

The report concerns LifeCycleNode configuration, component_container registration, service responses, and spinning. Start by reproducing the configuration deadlock with a lifecycle component and inspect how node registration and service handling interact. Done means establishing whether the reported deadlock is a bug and documenting or testing a decided fix.