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

no such file error on removing a podman machine never started #13834

Closed
benoitf opened this issue Apr 12, 2022 · 0 comments · Fixed by #13836
Closed

no such file error on removing a podman machine never started #13834

benoitf opened this issue Apr 12, 2022 · 0 comments · Fixed by #13836
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

@benoitf
Copy link
Contributor

benoitf commented Apr 12, 2022

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

/kind bug

Description

Create a podman machine and then remove it without starting it

Steps to reproduce the issue:

  1. podman machine init my-test

  2. podman machine rm my-test

Describe the results you received:


The following files will be deleted:

/Users/benoitf/.ssh/my-test
/Users/benoitf/.ssh/my-test.pub
/Users/benoitf/.config/containers/podman/machine/qemu/my-test.ign
/Users/benoitf/.local/share/containers/podman/machine/qemu/my-test_fedora-coreos-35.20220305.dev.0-qemu.x86_64.qcow2
/Users/benoitf/.local/share/containers/podman/machine/my-test/podman.sock
/Users/benoitf/.config/containers/podman/machine/qemu/my-test.json


Are you sure you want to continue? [y/N] y
ERRO[0002] remove /Users/benoitf/.local/share/containers/podman/machine/my-test/podman.sock: no such file or directory

Describe the results you expected:
No error ERRO[0002] remove /Users/benoitf/.local/share/containers/podman/machine/my-test/podman.sock: no such file or directory

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

main branch / 81b9646ceba05b2780d8c8210d60df4eaf6a3bdf 

Output of podman info --debug:

(paste your output here)

Package info (e.g. output of rpm -q podman or apt list podman):

(paste your output here)

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)

Yes/No

Additional environment details (AWS, VirtualBox, physical, etc.):

@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Apr 12, 2022
flouthoc added a commit to flouthoc/podman that referenced this issue Apr 12, 2022
Certain paths like `../containers/podman/machine/my-test/podman.sock`
do not exist when machine is not started, so removing a machine before
starting it will result in ENOENT which we should ignore cause these
paths do not exists

Closes: containers#13834

[NO TESTS NEEDED]
[NO NEW TESTS NEEDED]

Signed-off-by: Aditya R <arajan@redhat.com>
flouthoc added a commit to flouthoc/podman that referenced this issue Apr 12, 2022
Certain paths like `../containers/podman/machine/my-test/podman.sock`
do not exist when machine is not started, so removing a machine before
starting it will result in ENOENT which we should ignore cause these
paths do not exists

Closes: containers#13834

[NO TESTS NEEDED]
[NO NEW TESTS NEEDED]

Signed-off-by: Aditya R <arajan@redhat.com>
gbraad pushed a commit to gbraad-redhat/podman that referenced this issue Jul 13, 2022
Certain paths like `../containers/podman/machine/my-test/podman.sock`
do not exist when machine is not started, so removing a machine before
starting it will result in ENOENT which we should ignore cause these
paths do not exists

Closes: containers#13834

[NO TESTS NEEDED]
[NO NEW TESTS NEEDED]

Signed-off-by: Aditya R <arajan@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 20, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 20, 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