[release-4.21] OCPBUGS-71242: remove duplicated events before processing lease intervals

[openshift-cherrypick-robot]

This is an automated cherry-pick of #30639

/assign jianlinliu

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-66065 has been cloned as Jira Issue OCPBUGS-71242. Will retitle bug to link to clone.
/retitle [release-4.21] OCPBUGS-71242: remove duplicated events before processing lease intervals

Details

In response to this:

This is an automated cherry-pick of #30639

/assign jianlinliu

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign dennisperiquet 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:

• OWNERS

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

[openshift-ci-robot]

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

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

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.

Details

In response to this:

This is an automated cherry-pick of #30639

/assign jianlinliu

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.

[jianlinliu]

/jira refresh

[openshift-ci-robot]

@jianlinliu: This pull request references Jira Issue OCPBUGS-71242, 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.21.0) matches configured target version for branch (4.21.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-66065 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-66065 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
• bug has dependents

Details

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.

[jianlinliu]

@dgoodwin can you help override ci/prow/okd-scos-images ?

[dgoodwin]

/override ci/prow/okd-scos-images

I'm also working on a PR to disable this as a required job.

[openshift-ci]

@dgoodwin: Overrode contexts on behalf of dgoodwin: ci/prow/okd-scos-images

Details

In response to this:

/override ci/prow/okd-scos-images

I'm also working on a PR to disable this as a required job.

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-ci]

@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/okd-scos-images	0231f79	link	true	/test okd-scos-images

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.

[jianlinliu]

I'm also working on a PR to disable this as a required job.

Nice.

@dgoodwin Do you mind to approve and label backport-risk-assessed this PR ?

[dgoodwin]

This one is not actively regressed in 4.21 though it does still happen here and there, and the change is a little risky, lets hold off to make sure no problems surface in the tests in 4.22 in the coming week(s).