Skip to content

[release-4.15] OCPBUGS-43268: Update network operator status for IPsec - #2530

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.15from
openshift-cherrypick-robot:cherry-pick-2360-to-release-4.15
Oct 15, 2024
Merged

[release-4.15] OCPBUGS-43268: Update network operator status for IPsec#2530
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.15from
openshift-cherrypick-robot:cherry-pick-2360-to-release-4.15

Conversation

@openshift-cherrypick-robot

@openshift-cherrypick-robot openshift-cherrypick-robot commented Oct 13, 2024

Copy link
Copy Markdown

This is an automated cherry-pick of #2360

/assign pperiyasamy

@pperiyasamy openshift-cherrypick-robot
Update network operator status for IPsec
d794d8f 
This commit updates network operator progressing condition for
rolling out IPsec daemonset for cluster. It reflects appropriate
status for network cluster operator which would make
openshift-install to exit gracefully after installing all of IPsec
components for the cluster.

Signed-off-by: Periyasamy Palanisamy <pepalani@redhat.com>
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Oct 13, 2024
Merged
@openshift-ci-robot

openshift-ci-robot commented Oct 13, 2024

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-32979 has been cloned as Jira Issue OCPBUGS-43268. Will retitle bug to link to clone.
/retitle [release-4.15] OCPBUGS-43268: Update network operator status for IPsec

Details

In response to this:

This is an automated cherry-pick of #2360

/assign pperiyasamy

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 changed the title [release-4.15] OCPBUGS-32979: Update network operator status for IPsec [release-4.15] OCPBUGS-43268: Update network operator status for IPsec Oct 13, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 13, 2024
@openshift-ci-robot

openshift-ci-robot commented Oct 13, 2024

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-43268, 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 #2360

/assign pperiyasamy

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 Oct 13, 2024
@openshift-ci
openshift-ci Bot requested review from dougbtv and trozet October 13, 2024 14:35
@pperiyasamy

pperiyasamy commented Oct 13, 2024

Copy link
Copy Markdown
Member

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Oct 13, 2024
@openshift-ci-robot

openshift-ci-robot commented Oct 13, 2024

Copy link
Copy Markdown
Contributor

@pperiyasamy: This pull request references Jira Issue OCPBUGS-43268, 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.15.z) matches configured target version for branch (4.15.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-32979 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-32979 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0, 4.16.z
  • bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

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.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Oct 13, 2024
@pperiyasamy

pperiyasamy commented Oct 14, 2024

Copy link
Copy Markdown
Member

/retest

@openshift-ci

openshift-ci Bot commented Oct 14, 2024

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: 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 d794d8f link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-aws-live-migration-sdn-ovn-rollback d794d8f link false /test e2e-aws-live-migration-sdn-ovn-rollback
ci/prow/security d794d8f link false /test security
ci/prow/e2e-aws-hypershift-ovn-kubevirt d794d8f link false /test e2e-aws-hypershift-ovn-kubevirt

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.

@jcaamano

jcaamano commented Oct 14, 2024

Copy link
Copy Markdown
Contributor

/lgtm
/approve
/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Oct 14, 2024
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Oct 14, 2024
@openshift-ci

openshift-ci Bot commented Oct 14, 2024

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcaamano, openshift-cherrypick-robot

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

The pull request process is described 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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 14, 2024
@huiran0826

huiran0826 commented Oct 15, 2024

Copy link
Copy Markdown

/label cherry-pick-approved

@openshift-ci openshift-ci Bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Oct 15, 2024
@openshift-merge-bot
openshift-merge-bot Bot merged commit 6af7942 into openshift:release-4.15 Oct 15, 2024
@openshift-ci-robot

openshift-ci-robot commented Oct 15, 2024

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-43268: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-43268 has been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #2360

/assign pperiyasamy

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

openshift-bot commented Oct 15, 2024

Copy link
Copy Markdown
Contributor

[ART PR BUILD NOTIFIER]

Distgit: cluster-network-operator
This PR has been included in build cluster-network-operator-container-v4.15.0-202410150905.p0.g6af7942.assembly.stream.el9.
All builds following this will include this PR.

@openshift-merge-robot

openshift-merge-robot commented Oct 15, 2024

Copy link
Copy Markdown
Contributor

Fix included in accepted release 4.15.0-0.nightly-2024-10-15-110258

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

Reviewers

@dougbtv dougbtv Awaiting requested review from dougbtv
@trozet trozet Awaiting requested review from trozet
@anuragthehatter anuragthehatter Awaiting requested review from anuragthehatter

Assignees

@mffiedler mffiedler

@rbbratta rbbratta

@eurijon eurijon

@pperiyasamy pperiyasamy

@anuragthehatter anuragthehatter

@huiran0826 huiran0826

@rlobillo rlobillo

@asood-rh asood-rh

@jechen0648 jechen0648

@qiowang721 qiowang721

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.