Red Hat Bugzilla – Bug 1262310
[RFE]: [SNAPSHOT]: snap_scheduler.py should have an unintialize option as well.
Last modified: 2018-04-07 14:52:41 EDT
Description of problem:
Currently there is no option to uninitialize snap_scheduler.py. This is required in case we want snap_scheduler to stop working on specific nodes, after initializing it for the cluster (for all the nodes in the trusted pool).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. initialize snap_scheduler.py on all the nodes in the cluster.
2. Now suppose we don't want it to run on specific nodes, so there should be an option to uninitialize it.
3.Disabling snap_scheduler.py will disable it on all the nodes. So a specific uninitialize option is required.
snap_scheculer.py uninitialize option is required.