Skip to content
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

[release-4.13] OCPBUGS-15476: Add release version annotation to whereabouts-reconciler #1853

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #1851

/assign jcaamano

CNO uses it to track whether updates to the daemonset have been done or
not. If not set, CNO won't set the overall operator version to the
target upgrade and the upgrade won't complete.

Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-15282 has been cloned as Jira Issue OCPBUGS-15476. Will retitle bug to link to clone.
/retitle [release-4.13] OCPBUGS-15476: Add release version annotation to whereabouts-reconciler

In response to this:

This is an automated cherry-pick of #1851

/assign jcaamano

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/test-infra repository.

@openshift-ci openshift-ci bot changed the title [release-4.13] OCPBUGS-15282: Add release version annotation to whereabouts-reconciler [release-4.13] OCPBUGS-15476: Add release version annotation to whereabouts-reconciler Jun 27, 2023
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 27, 2023
@openshift-ci-robot
Copy link
Contributor

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

  • expected dependent Jira Issue OCPBUGS-15282 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is MODIFIED instead

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 an automated cherry-pick of #1851

/assign jcaamano

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/test-infra repository.

@openshift-ci openshift-ci bot requested review from dcbw and dougbtv June 27, 2023 17:11
@dougbtv
Copy link
Member

dougbtv commented Jun 27, 2023

/approve

@dougbtv
Copy link
Member

dougbtv commented Jun 27, 2023

/lgtm

@dougbtv
Copy link
Member

dougbtv commented Jun 27, 2023

/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 Jun 27, 2023
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 27, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 27, 2023

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

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 Jun 27, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 27, 2023

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

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

@dougbtv
Copy link
Member

dougbtv commented Jun 27, 2023

/retest ci/prow/e2e-gcp-ovn

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 27, 2023

@dougbtv: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test e2e-aws-ovn-network-migration
  • /test e2e-aws-ovn-windows
  • /test e2e-aws-sdn-multi
  • /test e2e-aws-sdn-network-migration-rollback
  • /test e2e-aws-sdn-network-reverse-migration
  • /test e2e-gcp-ovn
  • /test e2e-gcp-sdn
  • /test e2e-metal-ipi-ovn-ipv6
  • /test e2e-vsphere-ovn-windows
  • /test images
  • /test lint
  • /test unit
  • /test verify

The following commands are available to trigger optional jobs:

  • /test e2e-aws-ovn-serial
  • /test e2e-aws-ovn-single-node
  • /test e2e-aws-sdn-upgrade
  • /test e2e-azure-ovn
  • /test e2e-azure-ovn-dualstack
  • /test e2e-gcp-ovn-upgrade
  • /test e2e-hypershift-ovn
  • /test e2e-metal-ipi-ovn-ipv6-ipsec
  • /test e2e-network-mtu-migration-ovn-ipv4
  • /test e2e-network-mtu-migration-ovn-ipv6
  • /test e2e-network-mtu-migration-sdn-ipv4
  • /test e2e-openstack-kuryr
  • /test e2e-openstack-ovn
  • /test e2e-openstack-sdn
  • /test e2e-ovn-hybrid-step-registry
  • /test e2e-ovn-ipsec-step-registry
  • /test e2e-ovn-step-registry
  • /test e2e-vsphere-ovn
  • /test e2e-vsphere-ovn-dualstack

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-aws-ovn-network-migration
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-aws-ovn-serial
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-aws-ovn-single-node
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-aws-ovn-windows
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-aws-sdn-multi
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-aws-sdn-network-migration-rollback
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-aws-sdn-network-reverse-migration
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-aws-sdn-upgrade
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-azure-ovn
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-gcp-ovn
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-gcp-ovn-upgrade
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-gcp-sdn
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-hypershift-ovn
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-metal-ipi-ovn-ipv6
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-metal-ipi-ovn-ipv6-ipsec
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-network-mtu-migration-ovn-ipv4
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-network-mtu-migration-ovn-ipv6
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-network-mtu-migration-sdn-ipv4
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-openstack-ovn
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-openstack-sdn
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-ovn-hybrid-step-registry
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-ovn-ipsec-step-registry
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-ovn-step-registry
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-vsphere-ovn
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-vsphere-ovn-dualstack
  • pull-ci-openshift-cluster-network-operator-release-4.13-e2e-vsphere-ovn-windows
  • pull-ci-openshift-cluster-network-operator-release-4.13-images
  • pull-ci-openshift-cluster-network-operator-release-4.13-lint
  • pull-ci-openshift-cluster-network-operator-release-4.13-unit
  • pull-ci-openshift-cluster-network-operator-release-4.13-verify

In response to this:

/retest ci/prow/e2e-gcp-ovn

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/test-infra repository.

@jcaamano
Copy link
Contributor

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 28, 2023

@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-hypershift-ovn cbe9fc9 link false /test e2e-hypershift-ovn
ci/prow/e2e-aws-ovn-serial cbe9fc9 link false /test e2e-aws-ovn-serial
ci/prow/e2e-network-mtu-migration-ovn-ipv6 cbe9fc9 link false /test e2e-network-mtu-migration-ovn-ipv6
ci/prow/e2e-gcp-ovn-upgrade cbe9fc9 link false /test e2e-gcp-ovn-upgrade
ci/prow/e2e-metal-ipi-ovn-ipv6-ipsec cbe9fc9 link false /test e2e-metal-ipi-ovn-ipv6-ipsec

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/test-infra repository. I understand the commands that are listed here.

@rbbratta
Copy link
Contributor

/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 Jun 28, 2023
@jcaamano
Copy link
Contributor

/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 Jun 30, 2023
@openshift-ci-robot
Copy link
Contributor

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

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.13.z) matches configured target version for branch (4.13.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-15282 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-15282 targets the "4.14.0" version, which is one of the valid target versions: 4.14.0
  • bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

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 kubernetes/test-infra 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 Jun 30, 2023
@jcaamano
Copy link
Contributor

/cherry-pick release-4.12

@openshift-cherrypick-robot
Copy link
Author

@jcaamano: once the present PR merges, I will cherry-pick it on top of release-4.12 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.12

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/test-infra repository.

@openshift-merge-robot openshift-merge-robot merged commit 618d519 into openshift:release-4.13 Jun 30, 2023
26 of 31 checks passed
@openshift-ci-robot
Copy link
Contributor

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

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

In response to this:

This is an automated cherry-pick of #1851

/assign jcaamano

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/test-infra repository.

@openshift-cherrypick-robot
Copy link
Author

@jcaamano: new pull request created: #1856

In response to this:

/cherry-pick release-4.12

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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/severity-critical Referenced Jira bug's severity is critical 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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet