Hide Forgot
Description of problem: If the node initialization fail, there's possibility to run it again. However it always fails. Version-Release number of selected component (if applicable): rhscon-core-0.0.8-10.el7.x86_64 rhscon-ui-0.0.19-1.el7.noarch rhscon-ceph-0.0.6-10.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Accept the node on UI 2. Stop salt-minion and systemd-skynetd services on the node before the initialization is completed 3. Start those services again and trigger re-initialization of the node Actual results: The initialization task fails with Unable to add details of node: <node_hostname> to DB. error: Node with id: <some_id> already exists Expected results: Node re-initialization task is finished successfully Additional info:
Require a setup to reproduce this issue
(In reply to Nishanth Thomas from comment #2) > Require a setup to reproduce this issue I was not able to reproduce it on the new build: rhscon-ui-0.0.29-1.el7scon.noarch rhscon-ceph-0.0.13-1.el7scon.x86_64 rhscon-core-0.0.16-1.el7scon.x86_64
All the changes which is discussed in this bug are fixed successfully. https://review.gerrithub.io/#/c/264225/
Tested on: rhscon-ui-0.0.48-1.el7scon.noarch rhscon-core-selinux-0.0.34-1.el7scon.noarch rhscon-ceph-0.0.33-1.el7scon.x86_64 rhscon-core-0.0.34-1.el7scon.x86_64