-
Notifications
You must be signed in to change notification settings - Fork 123
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
Update Centos Stream 9 version to a stable version #924
Conversation
/test check-provision-k8s-1.26 |
Nice, do you have please a specific issue to link about it ? |
Is this the latest stable version? Where do we find those numbers online? Thank you! |
Because it didn't work :\ |
cni's coredns and calico-kube-controllers getting: CreateContainerError with the following message: "runc create failed: unable to start container process: error during container init: write /proc/self/attr/keycreate: invalid argument" Signed-off-by: bmordeha <[email protected]>
Can you please elaborate? If there a problem with 20221206.0 we should file an issue, because it's likely to persist in future versions! |
Yes , also tried the resolution in : |
e4d601f
to
173ee40
Compare
Ok, thank you, please file a Bugzilla issue for it. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jean-edouard 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 |
/test check-provision-k8s-1.26 |
/hold |
Please include in the BZ also the current version and the problem, because the fact it works might be just temporary until a new containerd or some RPM is released |
The problem this PR solves blocks publish /cc @brianmcarey FYI If https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirtci/924/check-provision-k8s-1.26/1600864837548642304 |
@oshoval: GitHub didn't allow me to request PR reviews from the following users: FYI. Note that only kubevirt members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/override check-up-kind-1.23-vgpu This lane looks to be broken and not related to this change. |
@brianmcarey: Overrode contexts on behalf of brianmcarey: check-up-kind-1.23-vgpu In response to this:
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. |
/unhold check-provision-k8s-1.26 passed - https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirtci/924/check-provision-k8s-1.26/1600864837548642304 |
[dc4fc70 Update Centos Stream 9 version to a stable version](kubevirt/kubevirtci#924) [e0ace8c Revert "bump, cnao: k8s-1.2[4,5] to cnao v0.82.0](https://github.com/kubevirt/kubevirtci/pull/910)"](https://github.com/kubevirt/kubevirtci/pull/920) [bc9b6d2 Remove the 1.22 kubevirtci provider](kubevirt/kubevirtci#922) [c1432fc k8s-1.26: Update cni ipv6 diff file](kubevirt/kubevirtci#914) [921f43c SR-IOV providers: Bump SR-IOV CNI to v2.7.0](kubevirt/kubevirtci#913) [4eb880c vm based providers: Add single stack k8s-1.25 ipv6 lane](kubevirt/kubevirtci#912) [d73b264 bump, cnao: k8s-1.2[4,5] to cnao v0.82.0](kubevirt/kubevirtci#910) ```release-note NONE ``` Signed-off-by: kubevirt-bot <[email protected]>
[dc4fc70 Update Centos Stream 9 version to a stable version](kubevirt/kubevirtci#924) [e0ace8c Revert "bump, cnao: k8s-1.2[4,5] to cnao v0.82.0](https://github.com/kubevirt/kubevirtci/pull/910)"](https://github.com/kubevirt/kubevirtci/pull/920) [bc9b6d2 Remove the 1.22 kubevirtci provider](kubevirt/kubevirtci#922) [c1432fc k8s-1.26: Update cni ipv6 diff file](kubevirt/kubevirtci#914) [921f43c SR-IOV providers: Bump SR-IOV CNI to v2.7.0](kubevirt/kubevirtci#913) [4eb880c vm based providers: Add single stack k8s-1.25 ipv6 lane](kubevirt/kubevirtci#912) [d73b264 bump, cnao: k8s-1.2[4,5] to cnao v0.82.0](kubevirt/kubevirtci#910) ```release-note NONE ``` Signed-off-by: kubevirt-bot <[email protected]> Signed-off-by: zhangzhangzf <[email protected]>
Currently we have problem deploying the cni pods with the current centos 9 version:
https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirtci/914/check-provision-k8s-1.26/1600162586337218560
getting this error in the pod's status:
container create failed: time="2022-12-08T11:41:22Z" level=error msg="runc create failed: unable to start container process: error during container init: write /proc/self/attr/keycreate: invalid argument"
with this newer version the problem doesn't exist.
Signed-off-by: bmordeha [email protected]