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 1912409: Fix flow schema deployment #920

Conversation

alexanderConstantinescu
Copy link
Contributor

PR: #880 added a deployment stanza for a specific kubernetes feature, but only did that for openshift-sdn and not for ovn-kubernetes, moreover it added it in the wrong place independently of the network plugin being deployed.

I have no idea how this works and if the sequence of deployment is important or not for this stuff, so @tkashem could you please advise?

/assign @danwinship

PR: openshift#880 added a
deployment stanza for a specific kubernetes feature, but only did that for
openshift-sdn and not for ovn-kubernetes, moreover it added it in the wrong
place independently of the network plugin being deployed

Signed-off-by: Alexander Constantinescu <aconstan@redhat.com>
Copy link
Contributor

@danwinship danwinship left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

feature documentation is https://kubernetes.io/docs/concepts/cluster-administration/flow-control/

It looks like this is supposed to say "requests made by the given ServiceAccounts have system priority", which I believe is the highest priority level. OK. I agree that both the controller and the node service accounts should be high priority for both openshift-sdn and ovn-kubernetes.

metadata:
name: openshift-ovn-kubernetes
annotations:
include.release.openshift.io/self-managed-high-availability: "true"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This annotation only makes sense for things in manifests/ (so should be removed both here and from the sdn one)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK, will change.

@tkashem
Copy link
Contributor

tkashem commented Dec 16, 2020

  • the sdn flowschema is in manifests folder and the ovn flowschema is in bindata. Is it possible to have both in bindata?

  • if this is part of the operator reconciliation logic, i wonder what happens if I disable the priority & fairness feature on my cluster. access to the flowschema resource will result in an error from the apiserver. should the operator logic be resilient to handle such error?

@tkashem
Copy link
Contributor

tkashem commented Dec 16, 2020

/assign @deads2k

@alexanderConstantinescu
Copy link
Contributor Author

  • the sdn flowschema is in manifests folder and the ovn flowschema is in bindata. Is it possible to have both in bindata?

No, I just moved the sdn flowschema to bindata, so that is not a concern. My question was: does this resource need to be created with the deployment of the CNO, or can it wait until the deployment of the network plugin?

@tkashem
Copy link
Contributor

tkashem commented Dec 16, 2020

My question was: does this resource need to be created with the deployment of the CNO, or can it wait until the deployment of the network plugin?

I can't speak to the operator logic, but as far as the kube-apiserver and p&f are concerned, there is no dependency. A flowschema object can be created even though the specified user/service account do not exist yet.

@openshift-merge-robot
Copy link
Contributor

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

Test name Commit Details Rerun command
ci/prow/e2e-aws-ovn-windows-custom-vxlan 37be290 link /test e2e-aws-ovn-windows-custom-vxlan
ci/prow/e2e-aws-ovn-windows 37be290 link /test e2e-aws-ovn-windows
ci/prow/e2e-ovn-step-registry 37be290 link /test e2e-ovn-step-registry
ci/prow/e2e-ovn-hybrid-step-registry 37be290 link /test e2e-ovn-hybrid-step-registry
ci/prow/e2e-ovn-ipsec-step-registry 37be290 link /test e2e-ovn-ipsec-step-registry
ci/prow/e2e-aws-sdn-multi 37be290 link /test e2e-aws-sdn-multi
ci/prow/e2e-azure-ovn 37be290 link /test e2e-azure-ovn
ci/prow/e2e-openstack-ovn 37be290 link /test e2e-openstack-ovn
ci/prow/e2e-vsphere-ovn 37be290 link /test e2e-vsphere-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.

@danwinship
Copy link
Contributor

/lgtm
/retest

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 20, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alexanderConstantinescu, danwinship

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 the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 20, 2020
@openshift-bot
Copy link
Contributor

/retest

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

14 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.

12 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.

@alexanderConstantinescu
Copy link
Contributor Author

/hold

Not sure why it's been re-running all jobs when all required ones have already passed. Also not sure why I need a valid bug for getting this stuff in on master.

@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 Jan 4, 2021
@alexanderConstantinescu
Copy link
Contributor Author

/retitle Bug 1912409: Fix flow schema deployment

@openshift-ci-robot openshift-ci-robot changed the title Fix flow schema deployment Bug 1912409: Fix flow schema deployment Jan 4, 2021
@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/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Jan 4, 2021
@openshift-ci-robot
Copy link
Contributor

@alexanderConstantinescu: This pull request references Bugzilla bug 1912409, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.7.0) matches configured target release for branch (4.7.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1912409: Fix flow schema deployment

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.

@alexanderConstantinescu
Copy link
Contributor Author

/hold cancel

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

/retest

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 4, 2021

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

Test name Commit Details Rerun command
ci/prow/e2e-azure-ovn 37be290 link /test e2e-azure-ovn
ci/prow/e2e-aws-ovn-windows 37be290 link /test e2e-aws-ovn-windows
ci/prow/e2e-aws-ovn-windows-custom-vxlan 37be290 link /test e2e-aws-ovn-windows-custom-vxlan
ci/prow/e2e-ovn-ipsec-step-registry 37be290 link /test e2e-ovn-ipsec-step-registry

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 7c12be8 into openshift:master Jan 4, 2021
@openshift-ci-robot
Copy link
Contributor

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

Bugzilla bug 1912409 has been moved to the MODIFIED state.

In response to this:

Bug 1912409: Fix flow schema deployment

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.

@@ -0,0 +1,37 @@
apiVersion: flowcontrol.apiserver.k8s.io/v1alpha1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this must not use v1alpha1. v1alpha1 is subject to going away. Please switch to v1beta1 asap.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, I will file a PR momentarily for that. Thanks for letting us now

Copy link
Contributor

@tkashem tkashem Jan 7, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alexanderConstantinescu based on the discussion with @sttts we should leave the version to v1alpha1 for 4.7. We should set the version to v1beta1 in 4.8.
Please see https://bugzilla.redhat.com/show_bug.cgi?id=1913399#c1

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

8 participants