Conversation
The fulfillment service runs database migrations automatically when it starts, so a separate pre-upgrade Job is unnecessary. Remove the `db-migrate.yaml` hook template, the `dbMigrate` values and schema entries, all per-environment overrides, the `--set dbMigrate.enabled=false` flags from CI workflows, and the related documentation. Assisted-by: Cursor Signed-off-by: Juan Hernandez <juan.hernandez@redhat.com>
|
@jhernand: This pull request explicitly references no jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jhernand The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: osac-project/coderabbit/.coderabbit.yaml Review profile: ASSERTIVE Plan: Enterprise Run ID: 📒 Files selected for processing (10)
💤 Files with no reviewable changes (10)
WalkthroughThis PR removes the Helm ChangesHelm dbMigrate removal
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 11✅ Passed checks (11 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@jhernand: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
/retest |
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
🏗️ CI Triage: Root cause: The osac-operator pod failed to pull its image from ghcr.io due to a registry rate limit (pull QPS exceeded). Explanation: During the boot step's refresh phase, the script waits for the OSAC deployments to roll out. The osac-operator deployment failed to start because its pod encountered an ImagePullBackOff error. The specific error from the container runtime was 'ErrImagePull: pull QPS exceeded', indicating that GitHub Container Registry (ghcr.io) rate-limited the image pull request. This is a transient infrastructure issue unrelated to the PR's code changes. Evidence: [ Suggestion: Retrigger the job. If the issue persists, wait a while for the ghcr.io rate limit to reset before retesting. Prow job | Build For deeper investigation, use the |
|
/retest |
Summary
db-migratepre-upgrade Helm hook. The fulfillment service runsdatabase migrations automatically when it starts, so a separate Job is
unnecessary.
documentation.
Test plan
kustomize-build-all.shpasses.helm templaterenders without errors for all value files.Summary by CodeRabbit
Refactor
Documentation