OCPBUGS-49622: Fix leaderelection settings

[LalatenduMohanty]

This is a manual backport of openshift/operator-framework-operator-controller#249
to fix leaderelection settings

[openshift-ci-robot]

@LalatenduMohanty: This pull request references Jira Issue OCPBUGS-48765, which is invalid:

• expected the bug to target either version "4.18." or "openshift-4.18.", but it targets "4.19.0" instead
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead
• 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.
• expected Jira Issue OCPBUGS-48765 to depend on a bug targeting a version in 4.19.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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.

[tmshort]

The commit really shoudn't be a <drop> commit, but have the original PR number, or a <carry>. But to be blunt, since we don't use the bumper for these release branches, it doesn't really matter that much.

[openshift-ci-robot]

@LalatenduMohanty: No Jira issue with key 0OCPBUGS-49622 exists in the tracker at https://issues.redhat.com/.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

In response to this:

This is a manual backport of openshift/operator-framework-operator-controller#249
to fix leaderelection settings

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]

@LalatenduMohanty: The referenced Jira(s) [0OCPBUGS-49622] could not be located, all automatically applied jira labels will be removed.

In response to this:

This is a manual backport of openshift/operator-framework-operator-controller#249
to fix leaderelection settings

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]

@LalatenduMohanty: This pull request references Jira Issue OCPBUGS-49622, 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.
• expected Jira Issue OCPBUGS-49622 to depend on a bug targeting a version in 4.19.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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:

This is a manual backport of openshift/operator-framework-operator-controller#249
to fix leaderelection settings

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.

[LalatenduMohanty]

/jira refresh

[openshift-ci-robot]

@LalatenduMohanty: This pull request references Jira Issue OCPBUGS-49622, which is invalid:

• expected Jira Issue OCPBUGS-49622 to depend on a bug targeting a version in 4.19.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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.

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.

[LalatenduMohanty]

/jira refresh

[openshift-ci-robot]

@LalatenduMohanty: This pull request references Jira Issue OCPBUGS-49622, 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.18.0) matches configured target version for branch (4.18.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-48765 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-48765 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request.

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.

[joelanford]

/lgtm
/approve
/label backport-risk-assessed

[LalatenduMohanty]

operator-controller PR openshift/operator-framework-operator-controller#251

[camilamacedo86]

/test okd-scos-e2e-aws-ovn

[camilamacedo86]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, joelanford, LalatenduMohanty

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:

• DOWNSTREAM_OWNERS [joelanford]

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

[bandrade]

/label cherry-pick-approved

[openshift-ci-robot]

@LalatenduMohanty: An error was encountered updating to the MODIFIED state for bug OCPBUGS-49622 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message.

Error marking step #34662361 finished: root cause: Tried to update an entity that does not exist.: request failed. Please analyze the request body for more details. Status code: 400:

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

In response to this:

This is a manual backport of openshift/operator-framework-operator-controller#249
to fix leaderelection settings

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

[ART PR BUILD NOTIFIER]

Distgit: ose-olm-catalogd
This PR has been included in build ose-olm-catalogd-container-v4.18.0-202501301814.p0.g37a1fb5.assembly.stream.el9.
All builds following this will include this PR.