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

Remove the secure boot checker pod #206

Merged

Conversation

SchSeba
Copy link
Collaborator

@SchSeba SchSeba commented Nov 21, 2021

This commit removes the pod that is created to validate if the node has
secure boot enable or not

Before this PR after every test running there are test pods in the sriov
operator namespace that does not get clean

@SchSeba SchSeba requested a review from fedepaol November 21, 2021 13:51
@SchSeba SchSeba force-pushed the fix_secureboot_validation branch from 7a4beea to 0a65935 Compare November 21, 2021 13:52
@mmirecki
Copy link
Contributor

/lgtm

Copy link
Collaborator

@Eoghan1232 Eoghan1232 left a comment

Choose a reason for hiding this comment

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

lgtm

@@ -308,5 +309,10 @@ func GetNodeSecureBootState(clients *testclient.ClientSet, nodeName, namespace s
return false, err
}

err = clients.Pods(namespace).Delete(context.Background(), runningPod.Name, metav1.DeleteOptions{GracePeriodSeconds: pointer.Int64Ptr(0)})
Copy link
Collaborator

Choose a reason for hiding this comment

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

should we use defer to delete the pod in case of early return ?

Copy link
Collaborator

Choose a reason for hiding this comment

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

@SchSeba WDYT ? :)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

sorry for the late response :)

@SchSeba SchSeba force-pushed the fix_secureboot_validation branch from 0a65935 to e835e8f Compare January 20, 2022 13:37
@github-actions
Copy link

Thanks for your PR,
To run vendors CIs use one of:

  • /test-all: To run all tests for all vendors.
  • /test-e2e-all: To run all E2E tests for all vendors.
  • /test-e2e-nvidia-all: To run all E2E tests for NVIDIA vendor.

To skip the vendors CIs use one of:

  • /skip-all: To skip all tests for all vendors.
  • /skip-e2e-all: To skip all E2E tests for all vendors.
  • /skip-e2e-nvidia-all: To skip all E2E tests for NVIDIA vendor.
    Best regards.

This commit removes the pod that is created to validate if the node has
secure boot enable or not

Before this PR after every test running there are test pods in the sriov
operator namespace that does not get clean

Signed-off-by: Sebastian Sch <[email protected]>
@SchSeba SchSeba force-pushed the fix_secureboot_validation branch from e835e8f to eb8654d Compare January 20, 2022 13:38
@github-actions
Copy link

Thanks for your PR,
To run vendors CIs use one of:

  • /test-all: To run all tests for all vendors.
  • /test-e2e-all: To run all E2E tests for all vendors.
  • /test-e2e-nvidia-all: To run all E2E tests for NVIDIA vendor.

To skip the vendors CIs use one of:

  • /skip-all: To skip all tests for all vendors.
  • /skip-e2e-all: To skip all E2E tests for all vendors.
  • /skip-e2e-nvidia-all: To skip all E2E tests for NVIDIA vendor.
    Best regards.

@adrianchiris adrianchiris merged commit 16174f6 into k8snetworkplumbingwg:master Jan 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants