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

Cherry-picking error for 633db0ff0c9df375b62e3c70ed6cd6fe80d878bc #1269

Open
github-actions bot opened this issue Dec 12, 2024 · 0 comments
Open

Cherry-picking error for 633db0ff0c9df375b62e3c70ed6cd6fe80d878bc #1269

github-actions bot opened this issue Dec 12, 2024 · 0 comments
Assignees

Comments

@github-actions
Copy link
Contributor

gitstream tried to cherry-pick commit 633db0ff0c9df375b62e3c70ed6cd6fe80d878bc from https://github.com/kubernetes-sigs/kernel-module-management but was unable to do so.

Commit message:

Making ImagePullPolicy in NMC optional

Currently ImagePullPolicy has a kubebuilder instruction for default
value, which automatically makes it a required field. In previous
version, this field was optional, meaning: when upgrading KMM operator,
the upgrade will fail , since NMC object will be missing the required
field
This commit keep the default value, but makes this field optional, in
order to solve the upgrade issue

Please cherry-pick the commit manually.


Error:

could not cherry-pick: could not run a command 0 before committing: exit status 1

Upstream-Commit: 633db0ff0c9df375b62e3c70ed6cd6fe80d878bc

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

No branches or pull requests

1 participant