Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

LOG-6838: use stable channel for COO #62517

Merged
merged 1 commit into from
Mar 7, 2025
Merged

LOG-6838: use stable channel for COO #62517

merged 1 commit into from
Mar 7, 2025
+9 −9

Conversation

QiaolingTang
Copy link
Contributor

Fix below failure:

Try 29/30: cluster-observability-operator is not deployed yet. Checking again in 30 seconds
Try 30/30: can't get the cluster-observability-operator yet. Checking again in 30 seconds
Try 30/30: cluster-observability-operator is not deployed yet. Checking again in 30 seconds
error: resource name may not be empty
Error: Failed to deploy cluster-observability-operator

Assert that the 'cluster-observability-operator' packagemanifest belongs to 'redhat-operators' catalog

cluster-observability-operator                        Production Operators   35m
cluster-observability-operator                        Red Hat Operators      64m
CSV  YAML
error: resource name may not be empty
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:84","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2025-02-25T21:52:46Z"}
error: failed to execute wrapped command: exit status 1

/cc @anpingli @kabirbhartiRH

@QiaolingTang
use stable channel for COO
Loading
Loading status checks…
283e94d
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 7, 2025
@openshift-ci openshift-ci bot requested review from anpingli and kabirbhartiRH March 7, 2025 06:13
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 7, 2025 •
edited by openshift-ci bot
Loading

@QiaolingTang: This pull request references LOG-6838 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.19.0" version, but no target version was set.

In response to this:

Fix below failure:

Try 29/30: cluster-observability-operator is not deployed yet. Checking again in 30 seconds
Try 30/30: can't get the cluster-observability-operator yet. Checking again in 30 seconds
Try 30/30: cluster-observability-operator is not deployed yet. Checking again in 30 seconds
error: resource name may not be empty
Error: Failed to deploy cluster-observability-operator

Assert that the 'cluster-observability-operator' packagemanifest belongs to 'redhat-operators' catalog

cluster-observability-operator                        Production Operators   35m
cluster-observability-operator                        Red Hat Operators      64m
CSV  YAML
error: resource name may not be empty
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:84","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2025-02-25T21:52:46Z"}
error: failed to execute wrapped command: exit status 1

/cc @anpingli @kabirbhartiRH

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.

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@QiaolingTang: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
periodic-ci-openshift-openshift-tests-private-release-4.16-amd64-stable-openshift-logging-6.1-gcp-ipi-proxy-oidc-amd-f7-logging N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.18-amd64-nightly-openshift-logging-6.1-gcp-ipi-fips-f7-logging N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.16-amd64-stable-openshift-logging-6.0-gcp-ipi-proxy-oidc-amd-f7-logging N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-openshift-logging-6.0-gcp-ipi-sdn-fips-f14-logging N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.15-multi-stable-openshift-logging-6.1-azure-ipi-oidc-mixarch-f14-logging N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.17-multi-stable-openshift-logging-6.0-aws-ipi-proxy-sts-mixarch-f7-logging N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.15-multi-stable-openshift-logging-6.0-azure-ipi-oidc-mixarch-f14-logging N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.17-multi-stable-openshift-logging-6.1-aws-ipi-proxy-sts-mixarch-f7-logging N/A periodic Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.17-multi-stable-openshift-logging-6.2-aws-ipi-arm-f7-logging N/A periodic Ci-operator config changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@QiaolingTang
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-openshift-logging-6.0-gcp-ipi-sdn-fips-f14-logging

@openshift-ci-robot
Copy link
Contributor

@QiaolingTang: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@QiaolingTang
Copy link
Contributor Author

/pj-rehearse ack

@openshift-ci-robot
Copy link
Contributor

@QiaolingTang: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Mar 7, 2025
anpingli
anpingli reviewed Mar 7, 2025
View reviewed changes
Copy link
Contributor

@anpingli anpingli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 7, 2025
@QiaolingTang
Copy link
Contributor Author

/assign @liangxia

@liangxia
Copy link
Member

liangxia commented Mar 7, 2025

/approve

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Mar 7, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anpingli, liangxia, QiaolingTang

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 7, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 84d3f04 into openshift:master Mar 7, 2025
13 of 14 checks passed
@QiaolingTang QiaolingTang deleted the use_stable_channel branch March 7, 2025 08:38
shajmakh pushed a commit to shajmakh/release that referenced this pull request Mar 7, 2025
@QiaolingTang @shajmakh
use stable channel for COO (openshift#62517)
11ca3b8
shajmakh pushed a commit to shajmakh/release that referenced this pull request Mar 7, 2025
@QiaolingTang @shajmakh
use stable channel for COO (openshift#62517)
8f74880
shajmakh pushed a commit to shajmakh/release that referenced this pull request Mar 7, 2025
@QiaolingTang @shajmakh
use stable channel for COO (openshift#62517)
267b449
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@anpingli anpingli

@kabirbhartiRH kabirbhartiRH

Assignees

@liangxia liangxia

@anpingli anpingli

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
4 participants
@QiaolingTang @openshift-ci-robot @liangxia @anpingli