[
https://issues.apache.org/jira/browse/NIFI-15299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18043957#comment-18043957
]
David Handermann commented on NIFI-15299:
-----------------------------------------
I also tried reproducing the issue with ListenHTTP referencing
StandardSSLContextService. After stopping NiFi, removing a keystore file, and
starting again, I observed that the StandardSSLContextService was invalid and
could not be disabled and failed with the following message:
{noformat}
StandardControllerServiceNode[service=SSLContextService[id=04bc42e1-019b-1000-e617-c45517911a86],
name=StandardSSLContextService, active=true] cannot be disabled because it is
referenced by 1 components that are currently running:
[04bdf0e8-019b-1000-9a5e-6d599ccb8664]
{noformat}
However, after stopping ListenHTTP, I was able to disable the
StandardSSLContextService. Although that provides a workaround, it should not
be required, and the command to stop referencing components should work. I plan
to take a closer look at the issue and potential solutions.
> 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)
