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

OCPBUGS-31868: Wait for monitor resources cleanup #28758

Closed
wants to merge 1 commit into from
Closed

OCPBUGS-31868: Wait for monitor resources cleanup #28758

wants to merge 1 commit into from

Conversation

jluhrsen
Copy link
Contributor

No description provided.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 30, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 30, 2024 •
edited by openshift-ci bot

@jluhrsen: This pull request references trt-1538 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 story to target the "4.15.z" version, but no target version was set.

In 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.

@jluhrsen
Copy link
Contributor Author

/hold

for testing purposes

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 30, 2024
@jluhrsen jluhrsen changed the title trt-1538: Wait for monitor resources cleanup OCPBUGS-23957: Wait for monitor resources cleanup Apr 30, 2024
@openshift-ci-robot openshift-ci-robot added the jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. label Apr 30, 2024
@openshift-ci-robot
Copy link

@jluhrsen: This pull request references Jira Issue OCPBUGS-23957, which is invalid:

  • expected the bug to target either version "4.15." or "openshift-4.15.", but it targets "4.16.0" instead
  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
  • expected Jira Issue OCPBUGS-23957 to depend on a bug targeting a version in 4.16.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

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 openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Apr 30, 2024
@openshift-ci openshift-ci bot requested review from csrwng and spadgett April 30, 2024 21:13
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Apr 30, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jluhrsen
Once this PR has been reviewed and has the lgtm label, please assign bparees for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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

@jluhrsen
Copy link
Contributor Author

/test e2e-azure-ovn-upgrade

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Apr 30, 2024

@jluhrsen: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test e2e-aws-jenkins
  • /test e2e-aws-ovn-fips
  • /test e2e-aws-ovn-image-registry
  • /test e2e-aws-ovn-serial
  • /test e2e-gcp-ovn
  • /test e2e-gcp-ovn-builds
  • /test e2e-gcp-ovn-image-ecosystem
  • /test e2e-gcp-ovn-upgrade
  • /test e2e-metal-ipi-ovn-ipv6
  • /test images
  • /test lint
  • /test unit
  • /test verify
  • /test verify-deps

The following commands are available to trigger optional jobs:

  • /test e2e-agnostic-ovn-cmd
  • /test e2e-aws
  • /test e2e-aws-csi
  • /test e2e-aws-disruptive
  • /test e2e-aws-etcd-recovery
  • /test e2e-aws-multitenant
  • /test e2e-aws-ovn
  • /test e2e-aws-ovn-cgroupsv2
  • /test e2e-aws-ovn-etcd-scaling
  • /test e2e-aws-ovn-kubevirt
  • /test e2e-aws-ovn-single-node
  • /test e2e-aws-ovn-single-node-serial
  • /test e2e-aws-ovn-single-node-upgrade
  • /test e2e-aws-ovn-upgrade
  • /test e2e-aws-ovn-upi
  • /test e2e-aws-proxy
  • /test e2e-azure
  • /test e2e-azure-ovn-etcd-scaling
  • /test e2e-baremetalds-kubevirt
  • /test e2e-gcp-csi
  • /test e2e-gcp-disruptive
  • /test e2e-gcp-fips-serial
  • /test e2e-gcp-ovn-etcd-scaling
  • /test e2e-gcp-ovn-rt-upgrade
  • /test e2e-gcp-ovn-techpreview
  • /test e2e-gcp-ovn-techpreview-serial
  • /test e2e-metal-ipi-ovn-dualstack
  • /test e2e-metal-ipi-sdn
  • /test e2e-metal-ipi-serial
  • /test e2e-metal-ipi-serial-ovn-ipv6
  • /test e2e-metal-ipi-virtualmedia
  • /test e2e-openstack-ovn
  • /test e2e-openstack-serial
  • /test e2e-vsphere
  • /test e2e-vsphere-ovn-etcd-scaling

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

  • pull-ci-openshift-origin-release-4.15-e2e-agnostic-ovn-cmd
  • pull-ci-openshift-origin-release-4.15-e2e-aws-csi
  • pull-ci-openshift-origin-release-4.15-e2e-aws-etcd-recovery
  • pull-ci-openshift-origin-release-4.15-e2e-aws-ovn-cgroupsv2
  • pull-ci-openshift-origin-release-4.15-e2e-aws-ovn-fips
  • pull-ci-openshift-origin-release-4.15-e2e-aws-ovn-serial
  • pull-ci-openshift-origin-release-4.15-e2e-aws-ovn-single-node
  • pull-ci-openshift-origin-release-4.15-e2e-aws-ovn-single-node-serial
  • pull-ci-openshift-origin-release-4.15-e2e-aws-ovn-single-node-upgrade
  • pull-ci-openshift-origin-release-4.15-e2e-aws-ovn-upgrade
  • pull-ci-openshift-origin-release-4.15-e2e-gcp-csi
  • pull-ci-openshift-origin-release-4.15-e2e-gcp-ovn
  • pull-ci-openshift-origin-release-4.15-e2e-gcp-ovn-rt-upgrade
  • pull-ci-openshift-origin-release-4.15-e2e-gcp-ovn-upgrade
  • pull-ci-openshift-origin-release-4.15-e2e-metal-ipi-ovn-ipv6
  • pull-ci-openshift-origin-release-4.15-e2e-metal-ipi-sdn
  • pull-ci-openshift-origin-release-4.15-e2e-openstack-ovn
  • pull-ci-openshift-origin-release-4.15-images
  • pull-ci-openshift-origin-release-4.15-lint
  • pull-ci-openshift-origin-release-4.15-unit
  • pull-ci-openshift-origin-release-4.15-verify
  • pull-ci-openshift-origin-release-4.15-verify-deps

In response to this:

/test e2e-azure-ovn-upgrade

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/test-infra repository.

@jluhrsen jluhrsen changed the title OCPBUGS-23957: Wait for monitor resources cleanup OCPBUGS-31868: Wait for monitor resources cleanup Apr 30, 2024
@openshift-ci-robot openshift-ci-robot removed the jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. label Apr 30, 2024
@openshift-ci-robot
Copy link

@jluhrsen: This pull request references Jira Issue OCPBUGS-31868, which is invalid:

  • expected the bug to target either version "4.15." or "openshift-4.15.", but it targets "4.16.0" instead
  • expected Jira Issue OCPBUGS-31868 to depend on a bug targeting a version in 4.16.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

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
Copy link
Contributor

openshift-ci bot commented May 1, 2024

@jluhrsen: The following tests 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-metal-ipi-ovn-ipv6 c101b4b link true /test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-metal-ipi-sdn c101b4b link false /test e2e-metal-ipi-sdn
ci/prow/e2e-aws-ovn-single-node-upgrade c101b4b link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-etcd-recovery c101b4b link false /test e2e-aws-etcd-recovery
ci/prow/e2e-openstack-ovn c101b4b link false /test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-single-node c101b4b link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-single-node-serial c101b4b link false /test e2e-aws-ovn-single-node-serial

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/test-infra repository. I understand the commands that are listed here.

@jluhrsen
Copy link
Contributor Author

jluhrsen commented May 1, 2024

wanted this on a different local branch. it's here now

@jluhrsen jluhrsen closed this May 1, 2024
@openshift-ci-robot
Copy link

@jluhrsen: This pull request references Jira Issue OCPBUGS-31868. The bug has been updated to no longer refer to the pull request using the external bug tracker.

In 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@csrwng csrwng Awaiting requested review from csrwng

@spadgett spadgett Awaiting requested review from spadgett

Assignees
No one assigned
Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@jluhrsen @openshift-ci-robot @neisw