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.

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

[release-4.13] OCPBUGS-35380: Improved debugging of API listing errors #304

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #303

/assign JoelSpeed

@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-35338 has been cloned as Jira Issue OCPBUGS-35380. Will retitle bug to link to clone.
/retitle [release-4.13] OCPBUGS-35380: Improved debugging of API listing errors

In response to this:

This is an automated cherry-pick of #303

/assign JoelSpeed

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 openshift-ci bot changed the title [release-4.13] OCPBUGS-35338: Improved debugging of API listing errors [release-4.13] OCPBUGS-35380: Improved debugging of API listing errors Jun 12, 2024
@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jun 12, 2024
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 12, 2024
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-35380, which is invalid:

  • expected dependent Jira Issue OCPBUGS-35338 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #303

/assign JoelSpeed

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.

@JoelSpeed
Copy link
Contributor

/retest

@JoelSpeed
Copy link
Contributor

/approve
/lgtm
/label backport-risk-assessed
/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 13, 2024
@openshift-ci-robot
Copy link

@JoelSpeed: This pull request references Jira Issue OCPBUGS-35380, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.13.z) matches configured target version for branch (4.13.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-35338 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-35338 targets the "4.14.z" version, which is one of the valid target versions: 4.14.0, 4.14.z
  • bug has dependents

Requesting review from QA contact:
/cc @sunzhaohua2

In response to this:

/approve
/lgtm
/label backport-risk-assessed
/jira refresh

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 openshift-ci bot requested a review from sunzhaohua2 June 13, 2024 07:42
@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jun 13, 2024
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 13, 2024
Copy link
Contributor

openshift-ci bot commented Jun 13, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

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 Jun 13, 2024
@JoelSpeed
Copy link
Contributor

/retest

@JoelSpeed
Copy link
Contributor

/override ci/prow/e2e-aws-operator

I can see there's another race condition in one of the pre-submit cases, since we aren't adjusting those in this PR, I'll override for now and raise a separate bug to fix this other race condition

Copy link
Contributor

openshift-ci bot commented Jun 13, 2024

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/e2e-aws-operator

In response to this:

/override ci/prow/e2e-aws-operator

I can see there's another race condition in one of the pre-submit cases, since we aren't adjusting those in this PR, I'll override for now and raise a separate bug to fix this other race condition

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 kubernetes-sigs/prow repository.

Copy link
Contributor

openshift-ci bot commented Jun 13, 2024

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-operator 94a4206 link true /test e2e-aws-operator

Full PR test history. Your PR dashboard.

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

@JoelSpeed
Copy link
Contributor

/test ?

Copy link
Contributor

openshift-ci bot commented Jun 13, 2024

@JoelSpeed: The following commands are available to trigger required jobs:

  • /test e2e-aws-operator
  • /test e2e-aws-ovn
  • /test e2e-aws-ovn-etcd-scaling
  • /test e2e-aws-ovn-serial
  • /test e2e-aws-ovn-upgrade
  • /test fmt
  • /test generate
  • /test images
  • /test lint
  • /test periodics-images
  • /test unit
  • /test vendor
  • /test vet

The following commands are available to trigger optional jobs:

  • /test e2e-aws-periodic-pre
  • /test e2e-azure-operator
  • /test e2e-azure-ovn-etcd-scaling
  • /test e2e-gcp-operator
  • /test e2e-gcp-ovn-etcd-scaling
  • /test e2e-vsphere-ovn-etcd-scaling

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-cluster-control-plane-machine-set-operator-release-4.13-e2e-aws-operator
  • pull-ci-openshift-cluster-control-plane-machine-set-operator-release-4.13-e2e-aws-ovn
  • pull-ci-openshift-cluster-control-plane-machine-set-operator-release-4.13-e2e-aws-ovn-etcd-scaling
  • pull-ci-openshift-cluster-control-plane-machine-set-operator-release-4.13-e2e-aws-ovn-serial
  • pull-ci-openshift-cluster-control-plane-machine-set-operator-release-4.13-e2e-aws-ovn-upgrade
  • pull-ci-openshift-cluster-control-plane-machine-set-operator-release-4.13-fmt
  • pull-ci-openshift-cluster-control-plane-machine-set-operator-release-4.13-generate
  • pull-ci-openshift-cluster-control-plane-machine-set-operator-release-4.13-images
  • pull-ci-openshift-cluster-control-plane-machine-set-operator-release-4.13-lint
  • pull-ci-openshift-cluster-control-plane-machine-set-operator-release-4.13-periodics-images
  • pull-ci-openshift-cluster-control-plane-machine-set-operator-release-4.13-unit
  • pull-ci-openshift-cluster-control-plane-machine-set-operator-release-4.13-vendor
  • pull-ci-openshift-cluster-control-plane-machine-set-operator-release-4.13-vet

In response to this:

/test ?

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 kubernetes-sigs/prow repository.

@JoelSpeed JoelSpeed added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 13, 2024
@JoelSpeed
Copy link
Contributor

/cherry-pick release-4.12

@openshift-cherrypick-robot
Copy link
Author

@JoelSpeed: once the present PR merges, I will cherry-pick it on top of release-4.12 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.12

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 kubernetes-sigs/prow repository.

@openshift-merge-bot openshift-merge-bot bot merged commit c9d5fa3 into openshift:release-4.13 Jun 13, 2024
14 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-35380: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-35380 has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #303

/assign JoelSpeed

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-cherrypick-robot
Copy link
Author

@JoelSpeed: new pull request created: #306

In response to this:

/cherry-pick release-4.12

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 kubernetes-sigs/prow repository.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-control-plane-machine-set-operator-container-v4.13.0-202406131508.p0.gc9d5fa3.assembly.stream.el8 for distgit ose-cluster-control-plane-machine-set-operator.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants