fix(ci): pull-ci-redhat-developer-rhdh-main-e2e-osd-gcp-operator-nightly#4419
Conversation
|
/test e2e-osd-gcp-operator-nightly |
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
…oyment-not-starting-fix
|
/test e2e-osd-gcp-operator-nightly |
|
The container image build workflow finished with status: |
…/pull/redhat-developer_rhdh/4419/pull-ci-redhat-developer-rhdh-main-e2e-osd-gcp-operator-nightly/2034295666343153664/artifacts/e2e-osd-gcp-operator-nightly/redhat-developer-rhdh-osd-gcp-helm-nightly/artifacts/showcase-operator-rbac/pod_logs/backstage-rhdh-rbac-5cb7c87f4b-hxtsd_install-dynamic-plugins.log FIX is dont ask OSD-GCP to pull from ghcr.io during init, plus dont run tests that need those GHCR-only plugins on OSD-GCP. OCP cluster is unchanged it can still use the full catalog and GHCR where egress works Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
…oyment-not-starting-fix
|
The container image build workflow finished with status: |
|
/test e2e-osd-gcp-operator-nightly |
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
|
/test e2e-osd-gcp-operator-nightly |
…hat-developer_rhdh/4419/pull-ci-redhat-developer-rhdh-main-e2e-osd-gcp-operator-nightly/2034352921931419648/build-log.txt FIX: Run prepare_operator once for OSD-GCP; wait for operator controller ready and on osd-gcp, apply registry.redhat.io pull secret and link to operator workload SAs Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
|
/test e2e-ocp-helm |
|
/test e2e-osd-gcp-operator-nightly |
…24&job=pull-ci-redhat-developer-rhdh-main-e2e-osd-gcp-operator-nightly FIX Tighter OSD-GCP plugin strip and Dump init container logs on CrashLoopBackOff Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
|
/test e2e-osd-gcp-operator-nightly |
…hat-developer_rhdh/4419/pull-ci-redhat-developer-rhdh-main-e2e-osd-gcp-operator-nightly/2034445085407449088/build-log.txt Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
…erit}} in the catalog Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
|
/test e2e-osd-gcp-operator-nightly |
…828800&job=pull-ci-redhat-developer-rhdh-main-e2e-osd-gcp-operator-nightly Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
|
/test e2e-osd-gcp-operator-nightly |
|
/test e2e-osd-gcp-operator-nightly |
|
/test e2e-osd-gcp-operator-nightly |
…oyment-not-starting-fix
|
/test e2e-osd-gcp-operator-nightly |
|
/test e2e-osd-gcp-operator-nightly |
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
…oyment-not-starting-fix
…oyment-not-starting-fix
|
/test e2e-osd-gcp-operator-nightly |
|
/test e2e-osd-gcp-operator-nightly |
1 similar comment
|
/test e2e-osd-gcp-operator-nightly |
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
…oyment-not-starting-fix
|
/test e2e-osd-gcp-operator-nightly |
|
- Always write sanitized YAML to both dynamic-plugins.yaml and install-dynamic-plugins so the init subPath mount exists and matches. - Validate all ConfigMap data keys that look like plugin YAML for clean checks. - Read operator baseline from install-dynamic-plugins when dynamic-plugins.yaml is empty. - After setting PR init image, re-merge and poll until CM stays clean and init uses the PR image (stabilize loop). - Fail fast on CrashLoop only for pods owned by ReplicaSets with desired>0. Made-with: Cursor
|
@Fortune-Ndlovu: 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. |
1 participant
Description
fix(ci): avoid duplicate orchestrator plugins on OSD-GCP (operator e2e)
Strip orchestrator-related entries from merged dynamic-plugins values after
OSD-GCP merge so install-dynamic-plugins no longer hits InstallException
when merging with the catalog. Apply for operator and Helm OSD-GCP paths.
Keep orchestrator: null; drop redundant disabled plugin overrides in diff files.
Which issue(s) does this PR fix
PR acceptance criteria
Please make sure that the following steps are complete:
How to test changes / Special notes to the reviewer