Fix schedule_all_controllers to skip INVALID controllers when enabling #400
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When enabling controller services, NiFi server correctly skips INVALID controllers (those that cannot be enabled due to validation errors). The client was incorrectly waiting for ALL controllers to reach ENABLED state, causing a 30-second timeout when any controller was INVALID.
Now the polling logic only waits for VALID controllers when enabling. When disabling, all controllers are still checked since any controller can be disabled regardless of validation status.
Adds test for mixed VALID/INVALID controller scenario.