[
https://issues.apache.org/jira/browse/NIFI-7084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17026963#comment-17026963
]
James Sevener commented on NIFI-7084:
-------------------------------------
Hey Andrew,
I redeployed my Docker stack using an updated image (1.11.0) So the flow.xml.gz
is still in the conf directory.
I have not tried it outside of docker, as that is where my current focus is.
The SSL context was created at the Process Group level, and the InvokeHTTP
Processor is referencing the SSL context service.
Also of note, I've upgraded from 1.9.2 to 1.10 this same way without issue,
however I can not downgrade from 1.10 to 1.9.2 without the same error.
> Upgrade from 1.10 to 1.11 fails
> -------------------------------
>
> Key: NIFI-7084
> URL: https://issues.apache.org/jira/browse/NIFI-7084
> Project: Apache NiFi
> Issue Type: Bug
> Components: Docker
> Affects Versions: 1.10.0, 1.11.0
> Environment: Docker version 19.03.2
> NiFi 1.10.0 and NiFi 1.11.0
> Reporter: James Sevener
> Priority: Major
> Attachments: nifi.1.11.stacktrace
>
>
> Spun up a fresh NiFi 1.10 instance and created an InvokeHTTP processor, then
> SSL context service. Then upgraded the instance from 1.10.0 to 1.11.0 and get
> the following error.
> Caused by: java.lang.IllegalStateException:
> org.apache.nifi.ssl.StandardRestrictedSSLContextService from
> org.apache.nifi:nifi-ssl-context-service-nar:1.10.0 is not known to this NiFi
> instance.
>
> Attached is the full stack trace from the error to the instance shutdown.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
