Upgrade Assistant: Internal Server Error

Elastic Stack Kibana
1

Hello everyone,

after upgrading to 7.11.1 (coming from 7.5.0) I notice that the "Upgrade Assistant" reports an Internal Server Error:

image
image1309×518 33.2 KB

I tried starting kibana with logging.verbose: true but can't seem to see any "useful" information:

GET /api/upgrade_assistant/status

Error: Internal Server Error
    at HapiResponseAdapter.toError (/usr/share/kibana/src/core/server/http/router/response_adapter.js:121:19)
    at HapiResponseAdapter.toHapiResponse (/usr/share/kibana/src/core/server/http/router/response_adapter.js:75:19)
    at HapiResponseAdapter.handle (/usr/share/kibana/src/core/server/http/router/response_adapter.js:70:17)
    at Router.handle (/usr/share/kibana/src/core/server/http/router/router.js:164:34)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at handler (/usr/share/kibana/src/core/server/http/router/router.js:124:50)
    at module.exports.internals.Manager.execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/toolkit.js:45:28)
    at Object.internals.handler (/usr/share/kibana/node_modules/@hapi/hapi/lib/handler.js:46:20)
    at exports.execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/handler.js:31:20)
    at Request._lifecycle (/usr/share/kibana/node_modules/@hapi/hapi/lib/request.js:312:32)
    at Request._execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/request.js:221:9)

The request appears to return a

{"statusCode":500,"error":"Internal Server Error","message":"Cannot read property 'level' of undefined"}

Thanks for input.

2

Hi @adsr,

It looks like a bug to me. I've created The Upgrade Assistant shows Internal Server · Issue #93408 · elastic/kibana · GitHub for the team to track a fix. Would you mind following in there and adding any additional context I might have missed when creating the issue?

Thank you!

3

Hi @afharo,
thanks for your input. I will gladly do so!

I guess this here can be closed then.

BR

1 Like
5

Hi @adsr! I've responded to the GitHub issue asking for additional information. I do not know your GH handle so I was not able to tag you. Can you respond there when you get a chance? Thanks!