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

Skupper CLI is not throwing an error when a former (working) podman endpoint is no longer available #1219

Closed
fgiorgetti opened this issue Aug 25, 2023 · 0 comments · Fixed by #1222
Assignees
Labels
bug Something isn't working

Comments

@fgiorgetti
Copy link
Member

When the podman endpoint is not defined (stored with an empty value), which forces skupper to use the default endpoint,
then the default endpoint becomes unavailable, an invalid (nil) client is returned an no error is displayed, causing the problem
to show up later in the process.

@fgiorgetti fgiorgetti self-assigned this Aug 25, 2023
@fgiorgetti fgiorgetti added the bug Something isn't working label Aug 25, 2023
fgiorgetti added a commit to fgiorgetti/skupper that referenced this issue Aug 25, 2023
fgiorgetti added a commit to fgiorgetti/skupper that referenced this issue Nov 3, 2023
fgiorgetti added a commit to fgiorgetti/skupper that referenced this issue Nov 9, 2023
fgiorgetti added a commit that referenced this issue Nov 13, 2023
nluaces pushed a commit that referenced this issue Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant