OCPBUGS-28928: Bump openshift/api to get updated docs for UnservableInFutureVersions

[gcs278]

Bump openshift/api to get updated docs for UnservableInFutureVersions which updates oc explain route.status.ingress.conditions.type.

  go get github.com/openshift/api@93d6bda14341f1d18319774367829c3278c171e7
  go mod tidy
  go mod vendor
  make update

This is a 4.15 backported API: openshift/api#1751

[openshift-ci-robot]

@gcs278: This pull request references Jira Issue OCPBUGS-28928, which is valid.

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 POST, 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-26498 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-26498 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
• bug has dependents

Requesting review from QA contact:
/cc @ShudiLi

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Bump openshift/api to get updated docs for UnservableInFutureVersions which updates oc explain route.status.ingress.conditions.type.

 go get github.com/openshift/api@93d6bda14341f1d18319774367829c3278c171e7
 go mod tidy
 go mod vendor
 make update

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.

[ShudiLi]

/label qe-approved

tested it with 4.15.0-0.test-2024-05-31-031732-ci-ln-jchbdg2-latest, tested the go version of the openshift-apiserver and some CRDs

1.
% go version -m openshift-apiserver | grep github.com/openshift/api
        dep     github.com/openshift/api        v0.0.0-20240522145529-93d6bda14341
        dep     github.com/openshift/apiserver-library-go       v0.0.0-20230503174907-d9b2bf6185e9

2.
% oc get crd cloudprivateipconfigs.cloud.network.openshift.io -oyaml -o=jsonpath="{.spec..metadata}"
{"properties":{"name":{"anyOf":[{"format":"ipv4"},{"pattern":"^[0-9a-f]{4}(\\.[0-9a-f]{4}){7}$"}],"type":"string"}},"type":"object"}%

3.
% oc get crd clusterversions.config.openshift.io
NAME                                  CREATED AT
clusterversions.config.openshift.io   2024-05-31T03:52:03Z

4.
% oc get crd clusterversions.config.openshift.io -oyaml | grep -E "release.openshift.io|CloudCredential|x-kubernetes-list"
    include.release.openshift.io/self-managed-high-availability: "true"
    include.release.openshift.io/single-node-developer: "true"
    release.openshift.io/feature-set: Default
                      - CloudCredential
                    x-kubernetes-list-type: atomic
                x-kubernetes-list-map-keys:
                x-kubernetes-list-type: map
                      x-kubernetes-list-type: set
                x-kubernetes-list-type: atomic
                      - CloudCredential
                    x-kubernetes-list-type: atomic
                      - CloudCredential
                    x-kubernetes-list-type: atomic
                      x-kubernetes-list-map-keys:
                      x-kubernetes-list-type: map
                          x-kubernetes-list-type: set
                            x-kubernetes-list-type: atomic
                      x-kubernetes-list-map-keys:
                      x-kubernetes-list-type: map
                x-kubernetes-list-type: atomic
                x-kubernetes-list-map-keys:
                x-kubernetes-list-type: map
                    x-kubernetes-list-type: set

[openshift-ci]

@ShudiLi: Can not set label cherry-pick-approved: Must be member in one of these teams: []

Details

In response to this:

/label cherry-pick-approved

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.

[ShudiLi]

/retest-required

[openshift-ci]

@gcs278: all tests passed!

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.

[frobware]

/lgtm

[tkashem]

/approve
/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: frobware, gcs278, tkashem

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:

• OWNERS [tkashem]

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

[ShudiLi]

/label cherry-pick-approved

[openshift-ci]

@ShudiLi: Can not set label cherry-pick-approved: Must be member in one of these teams: []

Details

In response to this:

/label cherry-pick-approved

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.

[lihongan]

/label cherry-pick-approved

[openshift-ci]

@lihongan: Can not set label cherry-pick-approved: Must be member in one of these teams: []

Details

In response to this:

/label cherry-pick-approved

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.

[xingxingxia]

/label cherry-pick-approved

[openshift-ci-robot]

@gcs278: Jira Issue OCPBUGS-28928: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

• openshift/cluster-ingress-operator#1014 is open

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

Details

In response to this:

Bump openshift/api to get updated docs for UnservableInFutureVersions which updates oc explain route.status.ingress.conditions.type.

 go get github.com/openshift/api@93d6bda14341f1d18319774367829c3278c171e7
 go mod tidy
 go mod vendor
 make update

This is a 4.15 backported API: openshift/api#1751

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]

This PR has been included in build ose-openshift-apiserver-container-v4.15.0-202406120336.p0.gebb067d.assembly.stream.el9 for distgit ose-openshift-apiserver.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.15.0-0.nightly-2024-06-12-223752