[
https://issues.apache.org/jira/browse/NIFI-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
olivier brobecker resolved NIFI-14298.
--------------------------------------
Fix Version/s: 2.2.0
Resolution: Not A Bug
wrong nifi configuration, only the metadata were saved in the database but not
the flow definitions
> [ dockerized nifi-registry ] cannot import flow when rebooting image
> --------------------------------------------------------------------
>
> Key: NIFI-14298
> URL: https://issues.apache.org/jira/browse/NIFI-14298
> Project: Apache NiFi
> Issue Type: Bug
> Components: Docker, NiFi Registry
> Affects Versions: 2.2.0
> Environment: kubernetes
> Reporter: olivier brobecker
> Priority: Major
> Fix For: 2.2.0
>
> Attachments: image-2025-02-27-12-02-45-154.png,
> image-2025-02-27-12-05-22-085.png
>
>
>
> When using nifi-registry on a kubernetes environment (openshift) using a
> customized docker hub image of nifi registry:
> * added jdbc driver to image in order to use postgresql database
> * update group and user writes in order to be compatible with openshift
> I've created the application using a deployment.
> Application start correctly and is working fine ( import / commit version /
> export ) from a nifi point of view.
> Everything works fine until the pod containing the nifi-registry application
> restart.
> After the pod restart, we cannot import previously versionned data flows.
> when trying to import a data flow :
> !image-2025-02-27-12-02-45-154.png!
> inside the logs of nifi-registry
>
> {code:java}
> 2025-02-21 12:00:07,675 INFO [NiFi Registry Web Server-31]
> o.a.n.r.w.m.IllegalStateExceptionMapper java.lang.IllegalStateException: No
> serialized content found for snapshot with flow identifier
> efb1c8ad-d9f5-47ee-8d25-d77d0b3c926a and version 1. Returning Conflict
> response. {code}
> If we try to search the flow id efb1c8ad-d9f5-47ee-8d25-d77d0b3c926a using
> the nifi-registry UI, it does exist:
>
> !image-2025-02-27-12-05-22-085.png!
> In order to reproduce the issue:
> * create nifi-registry using deployment in k8s
> * create a new flow
> * version it into nifi-registry
> * killl the pod for the deployment to recreate one
> * try to import the previously versionned flow
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
