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.

Sign up for GitHub

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

Jump to bottom

podman inspect ctr is broken after network disconnect #9234

Closed
Luap99 opened this issue Feb 4, 2021 · 0 comments · Fixed by #9235
Closed

podman inspect ctr is broken after network disconnect #9234

Luap99 opened this issue Feb 4, 2021 · 0 comments · Fixed by #9235
Assignees
@Luap99
Labels
In Progress This issue is actively being worked by the assignee, please do not work on this at this time. kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@Luap99
Copy link
Member

Luap99 commented Feb 4, 2021

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

After running network disconnect on a container podman inspect fails with Error: network inspection mismatch: asked to join 1 CNI network(s) [foo-a], but have information on 2 network(s): internal libpod error

Steps to reproduce the issue:

  1. podman run --name test --network foo-a -d alpine sleep 1000

  2. podman network connect foo-b test

  3. podman network disconnect foo-b test

  4. podman inspect test

Describe the results you received:

Error: network inspection mismatch: asked to join 1 CNI network(s) [foo-a], but have information on 2 network(s): internal libpod error

Describe the results you expected:
inspect should work
@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Feb 4, 2021
@Luap99 Luap99 self-assigned this Feb 4, 2021
@Luap99 Luap99 added the In Progress This issue is actively being worked by the assignee, please do not work on this at this time. label Feb 4, 2021
Luap99 pushed a commit to Luap99/libpod that referenced this issue Feb 4, 2021
Fix podman network disconnect wrong NetworkStatus number
5c6ab30 
The allocated `tmpNetworkStatus` must be allocated with the length 0.
Otherwise append would add new elements to the end of the slice and
not at the beginning of the allocated memory.

This caused inspect to fail since the number of networks did not
matched the number of network statuses.

Fixes containers#9234

Signed-off-by: Paul Holzinger <[email protected]>
@Luap99 Luap99 mentioned this issue Feb 4, 2021
Merged
mheon pushed a commit to mheon/libpod that referenced this issue Feb 5, 2021
@mheon
Fix podman network disconnect wrong NetworkStatus number
951879c 
The allocated `tmpNetworkStatus` must be allocated with the length 0.
Otherwise append would add new elements to the end of the slice and
not at the beginning of the allocated memory.

This caused inspect to fail since the number of networks did not
matched the number of network statuses.

Fixes containers#9234

Signed-off-by: Paul Holzinger <[email protected]>
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 22, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Luap99 Luap99

Labels
In Progress This issue is actively being worked by the assignee, please do not work on this at this time. kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix podman network disconnect wrong NetworkStatus number Luap99/libpod
2 participants
@openshift-ci-robot @Luap99