Red Hat Bugzilla – Bug 1314464
automatic (re)initialization fails if skyringd restarts
Last modified: 2016-08-03 10:30:15 EDT
Description of problem:
When skyringd is restarted it doesn't (re)start the accept node process for those nodes for which it was not finished when skyringd is stopped.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Click on 'Accept' button for some un-managed node
2. Before the node is completely accepted and initialized restart skyringd service
Node is not re-initialized after skyringd starts again.
Node initialization is (re)started after skyringd starts again.
skyringd will not restart any of the tasks which not completed. Ideal case is that USM should go through the list of tasks which are not 'completed' and mark it as failed. Its up to the user to redo the things which are not completed/failed.
So what is the state of task after the restart of skyring? is it failed or still going on?
(In reply to Nishanth Thomas from comment #2)
> skyringd will not restart any of the tasks which not completed. Ideal case
> is that USM should go through the list of tasks which are not 'completed'
> and mark it as failed. Its up to the user to redo the things which are not
> So what is the state of task after the restart of skyring? is it failed or
> still going on?
Still going on, they have "status": 0 in db.
When skyringd is restarted at that time re-initialization gets triggered for nodes which is initializing state