ElasticSearch problem after rolling back an upgrade

[Colin]

Hey there.

I would start with this advice:

@jacek.poreda

Search nodes are Stateful Set, so the state of your previous installation will be reused for the new one. Have you tried to stop search nodes, dropping persistence volumes for those nodes, and start with the new version? I haven’t experienced that issue, but I think it could happen if you have upgraded Elasticsearch and you are trying to reuse the same data directory.

@Jan_van_Veldhuizen

For some reason SQ came up with a default login prompt, no single sign-on. Also, it displayed messages about the need of getting a license to use an external database.
Then, I decided to rollback.

It sounds like your database configuration didn’t stick around. Can you share your docker-compse file?