-
Bug
-
Resolution: Unresolved
-
Normal
-
1.2.3
-
None
-
False
-
-
False
-
-
Description of problem:
Deploying a new RHDH instance that's configured with this appConfig will result in a failure to start the catalog plugin due to a MigrationLocked error. This in turn prevents RHDH from starting.
Simplifying the config as seen in this commit will allow the RHDH instance to start. Once RHDH starts for the first time, the complete config can be re-applied and RHDH will start normally with the desired catalog config.
I don't know if this issue is specifically linked to using the GitHub catalog integration on first boot, or if it's a combination of plugins causing it.
Prerequisites (if any, like setup, operators/versions):
Remove any existing RHDH instance and PVC/PVs before attempting to reproduce. This error occurs only on the first boot of a new RHDH instance.
Steps to Reproduce
- Create a new OpenShift 4.16 cluster
- Deploy RHDH using the Operator or Helm, being sure to use this config
Actual results:
RHDH crash loops, since it cannot progress beyond the catalog plugin startup.
Expected results:
RHDH starts successfully and imports catalog entries from GitHub.
Reproducibility (Always/Intermittent/Only Once):
Always, on a brand new RHDH instance. The issue does not occur if you start RHDH once without the GitHub catalog integration, then restart it with the integration.
Build Details:
RHDH Version: 1.2.3
Backstage Version: 1.26.5
Upstream: janus-idp/backstage-showcase 1.2.x @ d65fdb35
Midstream: gitlab.cee.redhat.com/rhidp/rhdh rhdh-1.2-rhel-9 @ 797d7405
Build Time: 2024-08-22T19:44:13Z
Additional info (Such as Logs, Screenshots, etc):
- relates to
-
RHDHBUGS-1738 Spike: Investigate why migration table is already locked
-
- New
-