Skip to content

OCPBUGS-55238: spyglass: hide disruption events for localhost #29710

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

vrutkovs
Copy link
Member

Don't display localhost-related disruptions on spyglass. These are still displayed on non-spyglass reports in case unexpected localhost disruption happens

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Apr 24, 2025
@openshift-ci-robot
Copy link

@vrutkovs: This pull request references Jira Issue OCPBUGS-55238, which is invalid:

  • expected the bug to target the "4.19.0" version, but no target version was set

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:

Don't display localhost-related disruptions on spyglass. These are still displayed on non-spyglass reports in case unexpected localhost disruption happens

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 24, 2025
@vrutkovs
Copy link
Member Author

/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 Apr 24, 2025
@openshift-ci-robot
Copy link

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @wangke19

In response to this:

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

Copy link
Contributor

openshift-ci bot commented Apr 24, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vrutkovs
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the 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

Copy link

openshift-trt bot commented May 2, 2025

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New Test Risks for sha: c900caa

Job Name New Test Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-serial Medium - "Find all of the input images from ocp/4.20 and tag them into the stable stream" is a new test, and was only seen in one job.
pull-ci-openshift-origin-main-e2e-aws-ovn-serial Medium - "Find all of the input images from ocp/4.20 and tag them into the stable-initial stream" is a new test, and was only seen in one job.

New tests seen in this PR at sha: c900caa

  • "Find all of the input images from ocp/4.20 and tag them into the stable stream" [Total: 1, Pass: 1, Fail: 0, Flake: 0]
  • "Find all of the input images from ocp/4.20 and tag them into the stable-initial stream" [Total: 1, Pass: 1, Fail: 0, Flake: 0]

Copy link
Contributor

openshift-ci bot commented May 15, 2025

@vrutkovs: 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-vsphere-ovn-dualstack-primaryv6 c900caa link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-aws-disruptive c900caa link false /test e2e-aws-disruptive
ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway c900caa link false /test e2e-metal-ipi-ovn-dualstack-local-gateway
ci/prow/4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback c900caa link false /test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback
ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview c900caa link false /test e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview
ci/prow/e2e-metal-ipi-ovn-ipv6 c900caa link true /test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-vsphere-ovn-etcd-scaling c900caa link false /test e2e-vsphere-ovn-etcd-scaling
ci/prow/okd-e2e-gcp c900caa link false /test okd-e2e-gcp
ci/prow/e2e-metal-ipi-virtualmedia c900caa link false /test e2e-metal-ipi-virtualmedia
ci/prow/e2e-aws-ovn-cgroupsv2 c900caa link false /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-gcp-fips-serial c900caa link false /test e2e-gcp-fips-serial
ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-techpreview c900caa link false /test e2e-metal-ipi-ovn-dualstack-bgp-techpreview
ci/prow/e2e-openstack-serial c900caa link false /test e2e-openstack-serial
ci/prow/e2e-gcp-ovn-etcd-scaling c900caa link false /test e2e-gcp-ovn-etcd-scaling
ci/prow/e2e-metal-ipi-serial c900caa link false /test e2e-metal-ipi-serial
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout c900caa link false /test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/okd-scos-e2e-aws-ovn c900caa link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-gcp-disruptive c900caa link false /test e2e-gcp-disruptive
ci/prow/e2e-aws-ovn-kube-apiserver-rollout c900caa link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-metal-ipi-ovn-dualstack c900caa link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-azure-ovn-etcd-scaling c900caa link false /test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-aws-ovn-single-node-upgrade c900caa link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-metal-ipi-serial-ovn-ipv6 c900caa link false /test e2e-metal-ipi-serial-ovn-ipv6
ci/prow/e2e-azure-ovn-upgrade c900caa link false /test e2e-azure-ovn-upgrade
ci/prow/e2e-metal-ipi-ovn c900caa link false /test e2e-metal-ipi-ovn
ci/prow/e2e-aws-ovn-single-node c900caa link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-etcd-scaling c900caa link false /test e2e-aws-ovn-etcd-scaling
ci/prow/e2e-aws-ovn-serial-2of2 c900caa link true /test e2e-aws-ovn-serial-2of2
ci/prow/e2e-aws-ovn-serial-1of2 c900caa link true /test e2e-aws-ovn-serial-1of2
ci/prow/e2e-aws-ovn-serial c900caa link true /test e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-serial-publicnet c900caa link true /test e2e-aws-ovn-serial-publicnet

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants