After upgrading 3scale from 2.11 to a newer version, system-mysql is not starting

Solution Verified - Updated -

Issue

After upgrading 3scale system-mysql POD is in CrashLoopBackOff status with log showing this error:

---> 17:07:58     Waiting for MySQL to start ...
2023-10-11T17:07:58.733701Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2023-10-11T17:07:59.413486Z 2 [ERROR] [MY-010520] [Server] Invalid (old?) table or database name 'lost+found'
2023-10-11T17:07:59.452911Z 0 [ERROR] [MY-010022] [Server] Failed to Populate DD tables.
2023-10-11T17:07:59.452947Z 0 [ERROR] [MY-010119] [Server] Aborting

Environment

  • Red Hat 3scale API Management
    • Upgrading from 2.11 or earlier On-Premises

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content