search

openshift / cluster-kube-apiserver-operator

The kube-apiserver operator installs and maintains the kube-apiserver on a cluster
Apache License 2.0
74 stars 159 forks source link

OCPBUGS-34800: Update APIRemovedInNextReleaseInUse for kube 1.30 / ocp 4.17 #1697

Closed sanchezl closed 5 months ago

sanchezl commented 5 months ago

APIRemovedInNextReleaseInUse: 1.30 -> 1.31 APIRemovedInNextEUSReleaseInUse: 1.3[01] -> 1.31

tkashem commented 5 months ago

/lgtm

openshift-ci-robot commented 5 months ago

@sanchezl: This pull request references Jira Issue OCPBUGS-34800, which is invalid:

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](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1697): >APIRemovedInNextReleaseInUse: 1.30 -> 1.31 >APIRemovedInNextEUSReleaseInUse: 1.3[01] -> 1.31 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-kube-apiserver-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
sanchezl commented 5 months ago

/jira refresh

openshift-ci-robot commented 5 months ago

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

3 validation(s) were run on this bug * bug is open, matching expected state (open) * bug target version (4.17.0) matches configured target version for branch (4.17.0) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact: /cc @wangke19

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1697#issuecomment-2145216105): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-kube-apiserver-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
sanchezl commented 5 months ago

/cherry-pick release-4.17

openshift-cherrypick-robot commented 5 months ago

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

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1697#issuecomment-2145219558): >/cherry-pick release-4.17 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
openshift-ci[bot] commented 5 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sanchezl, tkashem

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: - ~~[OWNERS](https://github.com/openshift/cluster-kube-apiserver-operator/blob/master/OWNERS)~~ [sanchezl,tkashem] 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 commented 5 months ago

/retest-required

Remaining retests: 0 against base HEAD 09258494e5c99595825898f90cedb46d7b3964b4 and 2 for PR HEAD 32549a4d1ffd5247ba05583987f61ccdccdc326f in total

sanchezl commented 5 months ago

/retest-required

sanchezl commented 5 months ago

/retest-required

p0lyn0mial commented 5 months ago

/retest-required

openshift-ci[bot] commented 5 months ago

@sanchezl: 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 32549a4d1ffd5247ba05583987f61ccdccdc326f link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-operator-disruptive-single-node 32549a4d1ffd5247ba05583987f61ccdccdc326f link false /test e2e-aws-operator-disruptive-single-node
ci/prow/e2e-metal-single-node-live-iso 32549a4d1ffd5247ba05583987f61ccdccdc326f link false /test e2e-metal-single-node-live-iso
ci/prow/e2e-gcp-operator-single-node 32549a4d1ffd5247ba05583987f61ccdccdc326f link false /test e2e-gcp-operator-single-node
ci/prow/k8s-e2e-gcp-serial 32549a4d1ffd5247ba05583987f61ccdccdc326f link false /test k8s-e2e-gcp-serial

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
p0lyn0mial commented 5 months ago

it looks like ci/prow/e2e-gcp-operator and ci/prow/e2e-aws-ovn-upgrade keeps failing on ipi-deprovision-deprovision which seems to be failing on Filestores: error retrieving filestore instances: googleapi: Error 403: Cloud Filestore API has not been used in project XXXXXXXXXXXXXXXXXXXXXXXX before or it is disabled

p0lyn0mial commented 5 months ago

t looks like ci/prow/e2e-gcp-operator and ci/prow/e2e-aws-ovn-upgrade keeps failing on ipi-deprovision-deprovision which seems to be failing on Filestores: error retrieving filestore instances: googleapi: Error 403: Cloud Filestore API has not been used in project XXXXXXXXXXXXXXXXXXXXXXXX before or it is disabled

xref: https://github.com/openshift/installer/pull/7251

p0lyn0mial commented 5 months ago

/retest-required

tkashem commented 5 months ago

/label acknowledge-critical-fixes-only

openshift-ci-robot commented 5 months ago

@sanchezl: Jira Issue OCPBUGS-34800: All pull requests linked via external trackers have merged:

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

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1697): >APIRemovedInNextReleaseInUse: 1.30 -> 1.31 >APIRemovedInNextEUSReleaseInUse: 1.3[01] -> 1.31 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-kube-apiserver-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-cherrypick-robot commented 5 months ago

@sanchezl: new pull request created: #1698

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1697#issuecomment-2145219558): >/cherry-pick release-4.17 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
openshift-bot commented 5 months ago

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-kube-apiserver-operator-container-v4.17.0-202406052200.p0.gc700fe8.assembly.stream.el9 for distgit ose-cluster-kube-apiserver-operator. All builds following this will include this PR.