@coutoPL are we there yet? ™ 
1 Like
Did you approve @Dzuming’s PR? 
1 Like
All done this morning! We are good to go 
1 Like
@mgopathi01 ROR 1.69.0 with the change is released
@coutoPL Thank you for new release version .
just quick update :
I deployed new version but users were not able to login and in kibana logs i could see error “Unhandled error from Elasticsearch, status: 400, error: {“error”:“no handler found for uri [/_readonlyrest/metadata/user] and method [GET]”}”.After rollback issue got resolved.
I will perform few more checks and get back to you with additional details.
Hi @mgopathi01
This endpoint /_readonlyrest/metadata/user is a part of the internal API added in ROR ES 1.69.0. It’s used by ROR KBN.
You should upgrade ROR in the Elasticsearch cluster to 1.69.0 first. Then you should upgrade ROR KBN to 1.69.0.
Do you confirm you did it like that?
Because it looks like you could upgrade ROR KBN first, without upgrading ROR ES.
Hello @coutoPL ,Thank you for clarification.
No i didn’t upgrade the ReadonlyREST plugin in Elasticsearch First.I was under assumption that final build would be similar to beshultd/kibana-readonlyrest-dev:7.17.24-ror-1.69.0-pre4 which didn’t require Elasticsearch ROR upgrade.
Will proceed to upgrade Elasticsearch ReadonlyREST plugin.
We always recommend having the ROR plugin versions aligned.
And upgrade the ROR ES first.
Please, let me know if you experience any problem after full upgrade.
1 Like