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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release/1.6] CRI: Fix no CNI info for pod sandbox on restart #7848

Merged
merged 1 commit into from Dec 20, 2022

Conversation

dcantah
Copy link
Member

@dcantah dcantah commented Dec 20, 2022

馃崚pick: 3ee6dd5

Due to when we were updating the pod sandboxes underlying container object, the pointer to the sandbox would have the right info, but the on-disk representation of the data was behind. This would cause the data returned from loading any sandboxes after a restart to have no CNI result or IP information for the pod.

This change does an additional update to the on-disk container info right after we invoke the CNI plugin so the metadata for the CNI result and other networking information is properly flushed to disk.

Due to when we were updating the pod sandboxes underlying container
object, the pointer to the sandbox would have the right info, but
the on-disk representation of the data was behind. This would cause
the data returned from loading any sandboxes after a restart to have
no CNI result or IP information for the pod.

This change does an additional update to the on-disk container info
right after we invoke the CNI plugin so the metadata for the CNI result
and other networking information is properly flushed to disk.

Signed-off-by: Danny Canter <danny@dcantah.dev>
(cherry picked from commit 3ee6dd5)
Signed-off-by: Danny Canter <danny@dcantah.dev>
@dcantah dcantah added area/cri Container Runtime Interface (CRI) cherry-picked/1.6.x PR commits are cherry-picked into release/1.6 branch labels Dec 20, 2022
@dmcgowan dmcgowan removed the cherry-picked/1.6.x PR commits are cherry-picked into release/1.6 branch label Dec 20, 2022
@dcantah
Copy link
Member Author

dcantah commented Dec 20, 2022

Oop, misused the cherry-picked label; thanks Derek!

@dmcgowan dmcgowan merged commit 686c3f3 into containerd:release/1.6 Dec 20, 2022
@mikebrow mikebrow added this to the 1.6.* milestone Dec 23, 2022
Mengkzhaoyun pushed a commit to open-beagle/containerd that referenced this pull request Jan 16, 2023
containerd 1.6.15

Welcome to the v1.6.15 release of containerd!

The fifteenth patch release for containerd 1.6 fixes an issue with CNI in the CRI plugin

* **Fix no CNI info for pod sandbox on restart in CRI plugin** ([#7848](containerd/containerd#7848))

See the changelog for complete list of changes

Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.

* Derek McGowan
* Akihiro Suda
* Danny Canter
* Kevin Parsons
* Samuel Karp
* Wei Fu
<details><summary>8 commits</summary>
<p>

* [release/1.6] Prepare release notes for v1.6.15 ([#7924](containerd/containerd#7924))
  * [`883899eae`](containerd/containerd@883899e) Prepare release notes for v1.6.15
* [release/1.6] CI: Pass GITHUB_TOKEN to containerd/project-checks ([#7919](containerd/containerd#7919))
  * [`b57367020`](containerd/containerd@b573670) CI: Pass GITHUB_TOKEN to containerd/project-checks
* [release/1.6] integration/images: switch away from Docker Hub to avoid rate limit ([#7900](containerd/containerd#7900))
  * [`0f4062c9b`](containerd/containerd@0f4062c) integration/images: switch away from Docker Hub to avoid rate limit
* [release/1.6] CRI: Fix no CNI info for pod sandbox on restart ([#7848](containerd/containerd#7848))
  * [`f16447e2d`](containerd/containerd@f16447e) CRI: Fix no CNI info for pod sandbox on restart
</p>
</details>

This release has no dependency changes

Previous release can be found at [v1.6.14](https://github.com/containerd/containerd/releases/tag/v1.6.14)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cri Container Runtime Interface (CRI) impact/changelog kind/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants