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

re-fixing DevicePlugin upgrade from v1.1 to v2 #968

Conversation

yevgeny-shnaidman
Copy link
Member

Unlike upstream, in downstream version ModuleLoader daemonset differs from DevicePlugin by present of the kernel version label, and not by role label.
This PR changes the identification of DevicePlugins during gathering all device plugin DS by checkig the absence of the kernel version label

Unlike upstream, in downstream version ModuleLoader daemonset differs
from DevicePlugin by present of the kernel version label, and not by
role label.
This PR changes the identification of DevicePlugins during gathering
all device plugin DS by checkig the absence of the kernel version label
Copy link

netlify bot commented Jan 16, 2024

Deploy Preview for openshift-kmm ready!

Name Link
🔨 Latest commit c7c1ca8
🔍 Latest deploy log https://app.netlify.com/sites/openshift-kmm/deploys/65a6fd56d42b3e00081b71a4
😎 Deploy Preview https://deploy-preview-968--openshift-kmm.netlify.app/
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@openshift-ci openshift-ci bot requested review from chr15p and ybettan January 16, 2024 22:04
@yevgeny-shnaidman
Copy link
Member Author

/assign @qbarrand

Copy link

openshift-ci bot commented Jan 16, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: yevgeny-shnaidman

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

@@ -176,7 +176,7 @@ func (dprh *devicePluginReconcilerHelper) getModuleDevicePluginDaemonSets(ctx co
devicePluginsList := make([]appsv1.DaemonSet, 0, len(dsList.Items))
// remove the older version module loader daemonsets
for _, ds := range dsList.Items {
if ds.GetLabels()[constants.DaemonSetRole] != constants.ModuleLoaderRoleLabelValue {
if _, ok := ds.GetLabels()[constants.KernelLabel]; !ok {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why do we have that diff in the labels of the DS between u/s and d/s?

Copy link
Contributor

Choose a reason for hiding this comment

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

Because we released upstream before we tested downstream. That is why now we wait for testing to be completed downstream before releasing upstream.
BTW this means that the 1.0 --> 1.1 upgrade was probably broken upstream.

Copy link
Member Author

Choose a reason for hiding this comment

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

we never tested upgrade in upstream, and i think that most upstream project never really test it

@qbarrand
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Jan 17, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 29d995b into rh-ecosystem-edge:main Jan 17, 2024
18 checks passed
@qbarrand
Copy link
Contributor

/cherry-pick release-2.0

@openshift-cherrypick-robot

@qbarrand: new pull request created: #969

In response to this:

/cherry-pick release-2.0

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants