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

podman pod inspect not working for more than one argument #15674

Closed
Luap99 opened this issue Sep 7, 2022 · 0 comments · Fixed by #15675
Closed

podman pod inspect not working for more than one argument #15674

Luap99 opened this issue Sep 7, 2022 · 0 comments · Fixed by #15675
Assignees
Labels
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 Sep 7, 2022

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

/kind bug

Description

The documentation states that podman pod inspect accepts one or more arguments (pod names or ids). This also matches the behavior of all other inspect commands. However in reality only the first argument is used and all extra arguments are silently ignored.

Steps to reproduce the issue:

  1. podman pod create --name p1

  2. podman pod create --name p2

  3. podman pod inspect p1 p2

Describe the results you received:
Inspect output for only the first pod p1

Describe the results you expected:
Inspect output for both pods.

Output of podman version:
latest main

@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Sep 7, 2022
@Luap99 Luap99 self-assigned this Sep 7, 2022
Luap99 added a commit to Luap99/libpod that referenced this issue Sep 7, 2022
Just like the other inspect commands `podman pod inspect p1 p2` should
return the json for both.

To correctly implement this we follow the contianer inspect logic, this
allows use to reuse the global inspect command.
Note: This may be breaking since we now return a json array of pods and
no longer a single pod.

Fixes containers#15674

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Luap99 added a commit to Luap99/libpod that referenced this issue Sep 7, 2022
Just like the other inspect commands `podman pod inspect p1 p2` should
return the json for both.

To correctly implement this we follow the container inspect logic, this
allows use to reuse the global inspect command.
Note: This may be breaking since we now return a json array of pods and
no longer a single pod.

Fixes containers#15674

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Luap99 added a commit to Luap99/libpod that referenced this issue Sep 8, 2022
Just like the other inspect commands `podman pod inspect p1 p2` should
return the json for both.

To correctly implement this we follow the container inspect logic, this
allows use to reuse the global inspect command.
Note: This may be breaking since we now return a json array of pods and
no longer a single pod.

Fixes containers#15674

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
@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 16, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 16, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
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
Development

Successfully merging a pull request may close this issue.

1 participant