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

remote: pod start empty pod: error without message #22989

Closed
edsantiago opened this issue Jun 12, 2024 · 0 comments · Fixed by #23080
Closed

remote: pod start empty pod: error without message #22989

edsantiago opened this issue Jun 12, 2024 · 0 comments · Fixed by #23080
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. remote Problem is in podman-remote

Comments

@edsantiago
Copy link
Collaborator 

$ bin/podman-remote pod create --infra=false --name=foo
a0cb944bf836e95ca0a83f98e1af151879552ac4fc424e29031c5f214227bdf6

$ bin/podman-remote pod start foo
Error:

(That's it. Just "Error colon space").

The expected error message (from podman-local) is:

Error: no containers in pod a0cb944bf836e95ca0a83f98e1af151879552ac4fc424e29031c5f214227bdf6 have no dependencies, cannot start pod: no such container
@edsantiago edsantiago added kind/bug Categorizes issue or PR as related to a bug. remote Problem is in podman-remote labels Jun 12, 2024
@edsantiago edsantiago mentioned this issue Jun 21, 2024
Merged
@Luap99 Luap99 self-assigned this Jun 24, 2024
@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 Jun 24, 2024
Luap99 added a commit to Luap99/libpod that referenced this issue Jun 24, 2024
@Luap99
libpod API: return proper error status code for pod start
4c48946 
When we failed to do anything we should return 500, the 409 code has a
special meaing to the client as it uses a different error format. As
such the remote client was not able to unmarshal the error correctly and
just returned an empty string.

Fixes containers#22989

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
@Luap99 Luap99 mentioned this issue Jun 24, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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. remote Problem is in podman-remote
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

libpod API: fix two pod remote error messages Luap99/libpod
2 participants
@edsantiago @Luap99