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

Bug 1955418: manifests: Shift FlowSchema to level 50 #582

Merged

Conversation

wking
Copy link
Member

@wking wking commented Apr 30, 2021

(like #581, but against the correct release-4.7, instead of #581's master)

This moves us behind the Kube API-server, like some other FlowSchema:

$ oc adm release extract --to manifests quay.io/openshift-release-dev/ocp-release:4.7.9-x86_64
$ ls manifests/*kube-apiserver*deployment*
manifests/0000_20_kube-apiserver-operator_06_deployment.yaml
$ grep -4r FlowSchema manifests | grep apiVersion | sort
manifests/0000_12_etcd-operator_10_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
manifests/0000_20_kube-apiserver-operator_08_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
manifests/0000_20_kube-apiserver-operator_08_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
manifests/0000_30_openshift-apiserver-operator_09_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
manifests/0000_30_openshift-apiserver-operator_09_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
manifests/0000_30_openshift-apiserver-operator_09_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
manifests/0000_50_cluster-authentication-operator_09_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
manifests/0000_50_cluster-authentication-operator_09_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
manifests/0000_50_cluster-authentication-operator_09_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
manifests/0000_50_cluster-authentication-operator_09_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
manifests/0000_50_cluster-openshift-controller-manager-operator_10_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1

That fixes a 4.7 v1alpha1 manifest vs. 4.8 v1beta1-only API-server on 4.8 -> 4.7 rollbacks.

We could also bump to v1beta1 like master/4.8's 7f76a91 (#516), but I don't think we need to, and as you can see in the grep there are lots of other v1alpha1 FlowSchema in 4.7, so I'm leaving that off for now.

This moves us behind the Kube API-server, like some other FlowSchema:

  $ oc adm release extract --to manifests quay.io/openshift-release-dev/ocp-release:4.7.9-x86_64
  $ ls manifests/*kube-apiserver*deployment*
  manifests/0000_20_kube-apiserver-operator_06_deployment.yaml
  $ grep -4r FlowSchema manifests | grep apiVersion | sort
  manifests/0000_12_etcd-operator_10_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
  manifests/0000_20_kube-apiserver-operator_08_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
  manifests/0000_20_kube-apiserver-operator_08_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
  manifests/0000_30_openshift-apiserver-operator_09_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
  manifests/0000_30_openshift-apiserver-operator_09_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
  manifests/0000_30_openshift-apiserver-operator_09_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
  manifests/0000_50_cluster-authentication-operator_09_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
  manifests/0000_50_cluster-authentication-operator_09_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
  manifests/0000_50_cluster-authentication-operator_09_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
  manifests/0000_50_cluster-authentication-operator_09_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
  manifests/0000_50_cluster-openshift-controller-manager-operator_10_flowschema.yaml-apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1

That fixes a 4.7 v1alpha1 manifest vs. 4.8 v1beta1-only API-server on
4.8 -> 4.7 rollbacks [1].

We could also bump to v1beta1 like master/4.8's 7f76a91 (switch to
v1beta1 for the p&f APIs, 2021-01-06, openshift#516), but I don't think we need
to, and as you can see in the grep there are lots of other v1alpha1
FlowSchema in 4.7, so I'm leaving that off for now.

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1955414
@openshift-ci-robot openshift-ci-robot added bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Apr 30, 2021
@openshift-ci-robot
Copy link

@wking: This pull request references Bugzilla bug 1955418, which is invalid:

  • expected dependent Bugzilla bug 1955414 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1955418: manifests: Shift FlowSchema to level 50

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.

@hexfusion
Copy link
Contributor

/lgtm
/approve

/retest

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hexfusion, wking

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-robot openshift-ci-robot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Apr 30, 2021
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

18 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

8 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci-robot
Copy link

@openshift-bot: This pull request references Bugzilla bug 1955418, which is invalid:

  • expected dependent Bugzilla bug 1955414 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

@wking
Copy link
Member Author

wking commented May 1, 2021

/hold

Enough of the CI jobs have passed for this to merge, once QE verifies that 4.8->4.8 rollbacks are working and the patch-manager approves the cherry-pick. No need to keep retesting while we wait on those.

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 1, 2021
@wking
Copy link
Member Author

wking commented May 24, 2021

/bugzilla refresh

@openshift-ci openshift-ci bot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels May 24, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 24, 2021

@wking: This pull request references Bugzilla bug 1955418, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.7.z) matches configured target release for branch (4.7.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1955414 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 1955414 targets the "4.8.0" release, which is one of the valid target releases: 4.8.0
  • bug has dependents

Requesting review from QA contact:
/cc @geliu2016

In response to this:

/bugzilla 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
Copy link
Contributor

openshift-ci bot commented May 24, 2021

@openshift-ci[bot]: GitHub didn't allow me to request PR reviews from the following users: geliu2016.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

@wking: This pull request references Bugzilla bug 1955418, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.7.z) matches configured target release for branch (4.7.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1955414 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 1955414 targets the "4.8.0" release, which is one of the valid target releases: 4.8.0
  • bug has dependents

Requesting review from QA contact:
/cc @geliu2016

In response to this:

/bugzilla 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.

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.

@hexfusion
Copy link
Contributor

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 27, 2021
@hexfusion
Copy link
Contributor

/skip

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@hexfusion
Copy link
Contributor

hexfusion commented May 27, 2021

/override ci/prow/e2e-gcp-five-control-plane-replicas

not supported in 4.7 failure was interrupt after 2m

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 27, 2021

@hexfusion: Overrode contexts on behalf of hexfusion: ci/prow/e2e-gcp-five-control-plane-replicas

In response to this:

/override ci/prow/e2e-gcp-five-control-plane-replicas

not supported in 4.7

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.

@sdodson sdodson added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label May 27, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 27, 2021

@wking: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-aws-disruptive-ovn b570e4b link /test e2e-aws-disruptive-ovn

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.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit afb5e8d into openshift:release-4.7 May 28, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 28, 2021

@wking: All pull requests linked via external trackers have merged:

Bugzilla bug 1955418 has been moved to the MODIFIED state.

In response to this:

Bug 1955418: manifests: Shift FlowSchema to level 50

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.

@wking wking deleted the flow-schema-for-rollbacks branch May 28, 2021 02:53
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. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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

6 participants