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

OCPBUGS-28248: Downstream Sync 2024-02-01 #882

Merged
merged 120 commits into from
Feb 13, 2024

Conversation

zeeke
Copy link
Contributor

@zeeke zeeke commented Feb 1, 2024

Clean merge, no conflicts.

Aligned field SriovNetworkNodeState.Status.Interfaces.Vfs.VdpaType

Refs:

vasrem and others added 30 commits December 27, 2023 12:56
This commit changes the behavior of the webhook when deleting the
default SriovNetworkNodePolicy and SriovOperatorConfig. This change is
needed so that we can smoothly uninstall Helm releases that have the
webhooks enabled.

Without this change, when running `helm uninstall`, it fails because the
webhook doesn't allow deletion of such resources mentioned above.

Since these Webhook Configurations resources are deployed via the
controller itself and not Helm, it's much more difficult to handle the
lifecycle of them via Helm in the current state. Instead, it's easier to
send a warning that these resources should not be deleted.

Signed-off-by: Vasilis Remmas <vremmas@nvidia.com>
Signed-off-by: Vasilis Remmas <vremmas@nvidia.com>
Signed-off-by: Sebastian Sch <sebassch@gmail.com>
like openstack and openshift add interfaces and mocks for better unit test

Signed-off-by: Sebastian Sch <sebassch@gmail.com>
for example MLX special mstconfig wrapper and create mock for unit tests

Signed-off-by: Sebastian Sch <sebassch@gmail.com>
…kage

create also interfaces for everything so we can have better unit tests coverage

Signed-off-by: Sebastian Sch <sebassch@gmail.com>
…onfig-delete-behavior

Change behavior when deleting default SriovNetworkNodePolicy and SriovOperatorConfig
Update chart README.md to reflect webhook changes
Update Helm chart kubeVersion check
…aces

Signed-off-by: Sebastian Sch <sebassch@gmail.com>
Signed-off-by: Sebastian Sch <sebassch@gmail.com>
go-get-tool is not available in the Makefile

Signed-off-by: Yury Kulazhenkov <ykulazhenkov@nvidia.com>
Use go-install-tool instead of go-get-tool for gomock
When interface(pf) is externally managed, we need to avoid
resetting firmware configurations.

- use store manager to get latest pf config from host so we can reliably
  determine if interface is externally managed if it does not appear in
  spec
- when interface appears in spec, block both sriov and link type
  firmware configurations if interface is externally managed
- skip pfs that are externally managed

Signed-off-by: adrianc <adrianc@nvidia.com>
Signed-off-by: adrianc <adrianc@nvidia.com>
Signed-off-by: Yury Kulazhenkov <ykulazhenkov@nvidia.com>
This field should be used to report information about type of the VDPA
device that is configured for VF.
Empty string means that there is no VDPA device.

Valid values are: `virtio`, `vhost` (same as in `SriovNetworkNodePolicySpec`)

Signed-off-by: Yury Kulazhenkov <ykulazhenkov@nvidia.com>
…ing-design

add design doc for switchdev mode refactoring
Refactoring in [1] left the openstackContext uninitialized.

[1] k8snetworkplumbingwg/sriov-network-operator#553

Signed-off-by: Andrea Panattoni <apanatto@redhat.com>
@zeeke
Copy link
Contributor Author

zeeke commented Feb 2, 2024

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 2, 2024
ykulazhenkov and others added 14 commits February 2, 2024 19:53
Signed-off-by: Yury Kulazhenkov <ykulazhenkov@nvidia.com>
- Move Manager creation and initialization to each controller test
- Move creation of k8s objs that are not common for all controllers
  to each controller test
- Use ordered containers to only setup manager once per controller test
- remove the usage of context.TODO() from tests

Signed-off-by: adrianc <adrianc@nvidia.com>
e2e: Fix `Debug logging should be visible in multus pod` flake
- move log level handling earlier in reconcile flow
- add log msg when reconicle has completed successfully

Signed-off-by: adrianc <adrianc@nvidia.com>
…operator-config

minor improvements in sriovOpeatorConfig controller
Signed-off-by: Andrea Panattoni <apanatto@redhat.com>
The configmap is created by the operator but never deleted.
Set OwnerReference to SriovOperatorConfig default CR to ensure
its deletion.

Signed-off-by: adrianc <adrianc@nvidia.com>
Set OwnerReference to sriov-device-plugin configmap
openstack: Fix `nil` HostManager in `openstackContext`
@zeeke
Copy link
Contributor Author

zeeke commented Feb 8, 2024

@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 Feb 8, 2024
Copy link
Contributor

openshift-ci bot commented Feb 8, 2024

@zeeke: all tests passed!

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.

@wizhaoredhat
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 13, 2024
Copy link
Contributor

openshift-ci bot commented Feb 13, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wizhaoredhat, zeeke

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 Feb 13, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 842a9f1 into openshift:master Feb 13, 2024
10 checks passed
@openshift-ci-robot
Copy link
Contributor

@zeeke: Jira Issue OCPBUGS-28248: All pull requests linked via external trackers have merged:

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

In response to this:

Clean merge, no conflicts.

Aligned field SriovNetworkNodeState.Status.Interfaces.Vfs.VdpaType

Refs:

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

[ART PR BUILD NOTIFIER]

This PR has been included in build sriov-network-operator-container-v4.16.0-202402140210.p0.g842a9f1.assembly.stream.el9 for distgit sriov-network-operator.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build sriov-network-config-daemon-container-v4.16.0-202402140210.p0.g842a9f1.assembly.stream.el9 for distgit sriov-network-config-daemon.
All builds following this will include this PR.

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