[
https://issues.apache.org/jira/browse/NIFI-15299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18043660#comment-18043660
]
Mark Bean commented on NIFI-15299:
----------------------------------
I confirmed this is still an issue in 2.7.0 RC4. The Controller Service is able
to be disabled properly _only if_ it does not have any referencing components.
If it does have a referencing component, it generates an exception during the
disable process and remains in the Invalid (but actually Enabled) state where
modification of properties is not possible. Also, the referencing component is
in an invalid state. I used ListenHTTP as the referencing component.
> Controller Service state cannot be changed under certain conditions
> -------------------------------------------------------------------
>
> Key: NIFI-15299
> URL: https://issues.apache.org/jira/browse/NIFI-15299
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Mark Bean
> Priority: Major
>
> When a controller service was previously in an Enabled state, and NiFi is
> restarted with the controller service now in an Invalid state, the service
> cannot be disabled in order to correct the validation error.
> To reproduce:
> * Create StandardRestrictedSSLContextService with all valid properties
> * Enable the service
> * Stop NiFi
> * (Re)move the keystore and/or truststore file(s)
> * Start NiFi
> Observe: the controller service is has validation errors and is reported to
> be in an Invalid state. However, the service can not be edited. Disabling the
> service is not an option.
> The only remedy is to replace the controller service (and update all
> referencing components to the new service.)
> Proper behavior should allow the service to be disabled (and/or it should be
> automatically entered into a disabled state on startup if validation fails.)
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
