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

Error: No such file or directory #69

Closed
diego-maravankin opened this issue Mar 17, 2021 · 6 comments · Fixed by #70
Closed

Error: No such file or directory #69

diego-maravankin opened this issue Mar 17, 2021 · 6 comments · Fixed by #70

Comments

@diego-maravankin
Copy link

Hi guys!
I am using kubie 0.13.3, but I cannot seem to get it working. When I try to swit to a new context, it fails with "no such file or directory".

$ kubie --version
kubie 0.13.3
$ kubie ctx
Error: No such file or directory (os error 2)

I went back to 0.13.2 and it works properly. If you let me know how to increase the log level, I can share more information.

@TyBrown
Copy link
Contributor

TyBrown commented Mar 17, 2021

Hi @diego-maravankin ... we've found the bug that I introduced in 0.13.3 (#67 (review) for more details if you're interested). The good news is that once you've run kubie once on 0.13.2, you should be able to upgrade to 0.13.3 with no problems, the bug only seems to occur on a fresh install, which is why I missed it while I was testing. I'm terribly sorry for the troubles. @sbstp has a fix already in #70.

@diego-maravankin
Copy link
Author

Hi @TyBrown! I just saw your response. I am using Ubuntu 20.04 amd64, I am using the precompiled binary.

I tried 0.13.3 after using 0.13.2, but still get the error. Let me know if you need me to do any further tests.

@sbstp
Copy link
Owner

sbstp commented Mar 17, 2021

To repair the bug with 0.13.2, you need to enter a context and then switch the namespace with kubie ns. After that 0.13.3 should work. But anyway I will publish 0.13.4 in a few minutes.

@diego-maravankin
Copy link
Author

That fixed it. Thanks @sbstp! I'll update to 0.13.4 when its available.

@sbstp sbstp closed this as completed in #70 Mar 17, 2021
@sbstp
Copy link
Owner

sbstp commented Mar 17, 2021

It's ready.

@rubensayshi
Copy link

hmm @sbstp this seems to be occuring for me with v0.16.0 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants