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

Update Centos Stream 9 version to a stable version #924

Merged
merged 1 commit into from
Dec 8, 2022

Conversation

Barakmor1
Copy link
Member

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]

@kubevirt-bot kubevirt-bot added the dco-signoff: yes Indicates the PR's author has DCO signed all their commits. label Dec 8, 2022
@Barakmor1
Copy link
Member Author

/test check-provision-k8s-1.26

@oshoval
Copy link
Contributor

oshoval commented Dec 8, 2022

Nice, do you have please a specific issue to link about it ?
Please update commit message itself with the error as well

@jean-edouard
Copy link
Contributor

jean-edouard commented Dec 8, 2022

Is this the latest stable version? Where do we find those numbers online? Thank you!
Edit: looks like it matches CentOS-Stream-Container-Base-9 versions in https://cloud.centos.org/centos/9-stream/x86_64/images/
In that case, why don't we use 20221206.0?

@Barakmor1
Copy link
Member Author

Is this the latest stable version? Where do we find those numbers online? Thank you! Edit: looks like it matches CentOS-Stream-Container-Base-9 versions in https://cloud.centos.org/centos/9-stream/x86_64/images/ In that case, why don't we use 20221206.0?

Because it didn't work :\
this is the latest one that did work locally

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]>
@jean-edouard
Copy link
Contributor

Is this the latest stable version? Where do we find those numbers online? Thank you! Edit: looks like it matches CentOS-Stream-Container-Base-9 versions in https://cloud.centos.org/centos/9-stream/x86_64/images/ In that case, why don't we use 20221206.0?

Because it didn't work :\ this is the latest one that did work locally

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!

@Barakmor1
Copy link
Member Author

Is this the latest stable version? Where do we find those numbers online? Thank you! Edit: looks like it matches CentOS-Stream-Container-Base-9 versions in https://cloud.centos.org/centos/9-stream/x86_64/images/ In that case, why don't we use 20221206.0?

Because it didn't work :\ this is the latest one that did work locally

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 ,
i got
Job for crio.service failed because the control process exited with error code. error
after running
systemctl enable --now crio

also tried the resolution in :
https://access.redhat.com/solutions/5009091
And it didn't work for me

@Barakmor1 Barakmor1 force-pushed the update_centos9_version branch from e4d601f to 173ee40 Compare December 8, 2022 14:44
@jean-edouard
Copy link
Contributor

Is this the latest stable version? Where do we find those numbers online? Thank you! Edit: looks like it matches CentOS-Stream-Container-Base-9 versions in https://cloud.centos.org/centos/9-stream/x86_64/images/ In that case, why don't we use 20221206.0?

Because it didn't work :\ this is the latest one that did work locally

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 , i got Job for crio.service failed because the control process exited with error code. error after running systemctl enable --now crio

also tried the resolution in : https://access.redhat.com/solutions/5009091 And it didn't work for me

Ok, thank you, please file a Bugzilla issue for it.
/approve

@kubevirt-bot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 8, 2022
@Barakmor1
Copy link
Member Author

/test check-provision-k8s-1.26

@Barakmor1
Copy link
Member Author

/hold
Let's wait for the lane to finish

@kubevirt-bot kubevirt-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 8, 2022
@oshoval
Copy link
Contributor

oshoval commented Dec 8, 2022

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

@oshoval
Copy link
Contributor

oshoval commented Dec 8, 2022

@kubevirt-bot
Copy link
Contributor

@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:

It blocks publish
https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/logs/publish-kubevirtci/1600820546306576384

/cc @brianmcarey FYI

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.

Copy link
Member

@brianmcarey brianmcarey left a comment

Choose a reason for hiding this comment

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

/lgtm

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Dec 8, 2022
@brianmcarey
Copy link
Member

/override check-up-kind-1.23-vgpu

This lane looks to be broken and not related to this change.
#925

@kubevirt-bot
Copy link
Contributor

@brianmcarey: Overrode contexts on behalf of brianmcarey: check-up-kind-1.23-vgpu

In response to this:

/override check-up-kind-1.23-vgpu

This lane looks to be broken and not related to this change.
#925

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.

@brianmcarey
Copy link
Member

@kubevirt-bot kubevirt-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 8, 2022
@kubevirt-bot kubevirt-bot merged commit dc4fc70 into kubevirt:main Dec 8, 2022
kubevirt-bot added a commit to kubevirt-bot/kubevirt that referenced this pull request Dec 9, 2022
[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]>
zhangzhangzf pushed a commit to zhangzhangzf/kubevirt that referenced this pull request Dec 10, 2022
[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]>
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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. size/XS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants