[
https://issues.apache.org/jira/browse/NIFI-7084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17027004#comment-17027004
]
Andrew M. Lim commented on NIFI-7084:
-------------------------------------
Hey [~jamessevener], thanks for getting back to me. I'm new to NiFi on Docker,
so appreciate your patience.
So I got 1.10.0 running on Docker and created the described bug scenario
(InvokeHTTP processor referencing a StandardRestrictedSSLContextService). But
can you clarify your steps for deploying your Docker stack using 1.11.0 with
your _flow.xml.gz_ still in the {{conf}} directory? I'm probably missing
something, but wouldn't you still have to copy your _flow.xml.gz_ from your
1.10.0 instance to your 1.11.0 instance? Thanks!
> 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)
