Skip to content

Conversation

@ibihim
Copy link
Contributor

@ibihim ibihim commented May 15, 2025

What

Add a test to verify that the annotation is set properly.

Why

To protect the feature.

Note

Will work once PR is merged.

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

openshift-ci-robot commented May 15, 2025

@ibihim: This pull request references CNTRLPLANE-179 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.20.0" version, but no target version was set.

Details

In response to this:

What

Add a test to verify that the annotation is set properly.

Why

To protect the feature.

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

openshift-ci-robot commented May 15, 2025

@ibihim: This pull request references CNTRLPLANE-179 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.20.0" version, but no target version was set.

Details

In response to this:

What

Add a test to verify that the annotation is set properly.

Why

To protect the feature.

Note

Will work once PR is merged.

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 review from deads2k and liouk May 15, 2025 12:58
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 15, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details 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

@ibihim
Copy link
Contributor Author

ibihim commented May 16, 2025

/retest-required

1 similar comment
@ibihim
Copy link
Contributor Author

ibihim commented May 19, 2025

/retest-required

@ibihim
Copy link
Contributor Author

ibihim commented May 21, 2025

/retest-required

3 similar comments
@ibihim
Copy link
Contributor Author

ibihim commented May 22, 2025

/retest-required

@ibihim
Copy link
Contributor Author

ibihim commented May 26, 2025

/retest-required

@ibihim
Copy link
Contributor Author

ibihim commented May 27, 2025

/retest-required

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 26, 2025
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 25, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 3, 2025
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

Details

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

openshift-trt bot commented Oct 3, 2025

Job Failure Risk Analysis for sha: a25a7e1

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-aws-disruptive High
[sig-node] node-lifecycle detects unexpected not ready node
This test has passed 99.81% of 5670 runs on release 4.20 [Overall] in the last week.

Open Bugs
node-lifecycle detects unexpected not ready node failing on azure serial and upgrade jobs
---
[sig-arch][Late] operators should not create watch channels very often
This test has passed 99.72% of 5443 runs on release 4.20 [Overall] in the last week.

Open Bugs
operators should not create watch channels very often regression
operators should not create watch channels very often regression
ResilientWatchCacheInitialization (Re)enablement - operator watch counts from component readiness
---
[bz-Etcd] clusteroperator/etcd should not change condition/Available
This test has passed 99.79% of 5670 runs on release 4.20 [Overall] in the last week.
---
[sig-architecture] platform pods in ns/openshift-machine-api should not exit an excessive amount of times
This test has passed 99.98% of 5589 runs on release 4.20 [Overall] in the last week.
---
Showing 4 of 6 test results
pull-ci-openshift-origin-main-e2e-aws-ovn-etcd-scaling High
[sig-network] can collect network.openshift.io/disruption-actor=poller,network.openshift.io/disruption-target=pod-to-service poller pod logs
This test has passed 99.73% of 5557 runs on release 4.20 [Overall] in the last week.
---
[sig-network] can collect network.openshift.io/disruption-actor=poller,network.openshift.io/disruption-target=host-to-pod poller pod logs
This test has passed 99.75% of 5557 runs on release 4.20 [Overall] in the last week.
---
[sig-network] can collect network.openshift.io/disruption-actor=poller,network.openshift.io/disruption-target=host-to-host poller pod logs
This test has passed 99.75% of 5557 runs on release 4.20 [Overall] in the last week.
---
[sig-network] can collect network.openshift.io/disruption-actor=poller,network.openshift.io/disruption-target=pod-to-host poller pod logs
This test has passed 99.75% of 5557 runs on release 4.20 [Overall] in the last week.
---
Showing 4 of 7 test results
pull-ci-openshift-origin-main-e2e-gcp-disruptive High
[sig-arch][Late] operators should not create watch channels very often
This test has passed 99.72% of 5443 runs on release 4.20 [Overall] in the last week.

Open Bugs
operators should not create watch channels very often regression
operators should not create watch channels very often regression
ResilientWatchCacheInitialization (Re)enablement - operator watch counts from component readiness
---
[sig-architecture] platform pods in ns/openshift-etcd should not exit an excessive amount of times
This test has passed 99.98% of 5589 runs on release 4.20 [Overall] in the last week.
pull-ci-openshift-origin-main-e2e-gcp-ovn-etcd-scaling Low
[bz-Cloud Compute] clusteroperator/control-plane-machine-set should not change condition/Degraded
This test has passed 0.00% of 1 runs on release 4.20 [Architecture:amd64 FeatureSet:default Installer:ipi JobTier:rare Network:ovn NetworkStack:ipv4 Owner:eng Platform:gcp SecurityMode:default Topology:ha Upgrade:none] in the last week.
pull-ci-openshift-origin-main-e2e-vsphere-ovn-etcd-scaling High
[sig-api-machinery] disruption/cache-openshift-api apiserver/openshift-apiserver connection/new should be available throughout the test
This test has passed 99.59% of 4863 runs on release 4.20 [Overall] in the last week.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 18, 2025

@ibihim: 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-aws-ovn-single-node-serial a25a7e1 link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-proxy a25a7e1 link false /test e2e-aws-proxy
ci/prow/e2e-azure-ovn-upgrade a25a7e1 link false /test e2e-azure-ovn-upgrade
ci/prow/e2e-metal-ipi-virtualmedia a25a7e1 link false /test e2e-metal-ipi-virtualmedia
ci/prow/e2e-metal-ipi-ovn-dualstack a25a7e1 link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-azure-ovn-etcd-scaling a25a7e1 link false /test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-gcp-ovn-etcd-scaling a25a7e1 link false /test e2e-gcp-ovn-etcd-scaling
ci/prow/e2e-aws-ovn-kube-apiserver-rollout a25a7e1 link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-single-node a25a7e1 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-openstack-ovn a25a7e1 link false /test e2e-openstack-ovn
ci/prow/e2e-openstack-serial a25a7e1 link false /test e2e-openstack-serial
ci/prow/4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback a25a7e1 link false /test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback
ci/prow/e2e-aws-ovn a25a7e1 link false /test e2e-aws-ovn
ci/prow/e2e-aws-ovn-serial-publicnet a25a7e1 link false /test e2e-aws-ovn-serial-publicnet
ci/prow/e2e-gcp-fips-serial a25a7e1 link false /test e2e-gcp-fips-serial
ci/prow/e2e-azure a25a7e1 link false /test e2e-azure
ci/prow/e2e-gcp-disruptive a25a7e1 link false /test e2e-gcp-disruptive
ci/prow/e2e-metal-ipi-ovn a25a7e1 link false /test e2e-metal-ipi-ovn
ci/prow/e2e-aws-ovn-cgroupsv2 a25a7e1 link false /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-disruptive a25a7e1 link false /test e2e-aws-disruptive
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 a25a7e1 link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-hypershift-conformance a25a7e1 link false /test e2e-hypershift-conformance
ci/prow/e2e-vsphere-ovn-etcd-scaling a25a7e1 link false /test e2e-vsphere-ovn-etcd-scaling
ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway a25a7e1 link false /test e2e-metal-ipi-ovn-dualstack-local-gateway
ci/prow/okd-e2e-gcp a25a7e1 link false /test okd-e2e-gcp
ci/prow/okd-scos-e2e-aws-ovn a25a7e1 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-single-node-upgrade a25a7e1 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws a25a7e1 link false /test e2e-aws
ci/prow/e2e-aws-ovn-etcd-scaling a25a7e1 link false /test e2e-aws-ovn-etcd-scaling
ci/prow/e2e-gcp-csi a25a7e1 link true /test e2e-gcp-csi
ci/prow/e2e-aws-csi a25a7e1 link true /test e2e-aws-csi
ci/prow/go-verify-deps a25a7e1 link true /test go-verify-deps
ci/prow/e2e-aws-ovn-microshift-serial a25a7e1 link true /test e2e-aws-ovn-microshift-serial
ci/prow/e2e-aws-ovn-microshift a25a7e1 link true /test e2e-aws-ovn-microshift
ci/prow/e2e-metal-ipi-ovn-ipv6 a25a7e1 link true /test e2e-metal-ipi-ovn-ipv6

Full PR test history. Your PR dashboard.

Details

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/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants