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

scw inspect doesn't work if "-" hyphen is present in name #531

Closed
alexellis opened this issue Dec 30, 2018 · 6 comments
Closed

scw inspect doesn't work if "-" hyphen is present in name #531

alexellis opened this issue Dec 30, 2018 · 6 comments
Labels

Comments

@alexellis
Copy link

I created an image named inlets-4a0817ff and scw inspect cannot find that server with any of the following:

scw inspect inlets-4a0817ff # doesn't work
scw inspect server:inlets-4a0817ff # doesn't work
scw inspect server"inlets-4a0817ff" # doesn't work

# renaming to inlets4a0817ff # allows the following to work
scw inspect inlets4a0817ff # works

It works on scw exec so I assume there might be an issue with the args-parsing code for scw inspect.

Please could someone look into this and get back to me?

@alexellis alexellis changed the title saw inspect doesn't work if "-" hyphen is present in name scw inspect doesn't work if "-" hyphen is present in name Dec 30, 2018
@alexellis
Copy link
Author

Might be related to #473 ?

@phhusson
Copy link

phhusson commented Jul 6, 2019

As mentioned in #473; rm ~/.scw-cache.db "fixes" the issue

@alexellis
Copy link
Author

This is not a fix, it is a manual and (unfortunately) impractical workaround

@QuentinBrosse
Copy link
Contributor

QuentinBrosse commented Sep 11, 2019

Hi @alexellis,

I can't reproduce the bug:

$ scw create --name="inlets-4a0817ff" ubuntu-bionic
11111111-1111-1111-1111-111111111111

$ scw start inlets-4a0817ff
inlets-4a0817ff

$ scw inspect inlets-4a0817ff
[{...}]

@Hades32
Copy link

Hades32 commented Oct 27, 2019

Can reproduce with the server name test-cluster:

$ scw version
Client version: v1.20
Go version (client): go1.13
Git commit (client):
OS/Arch (client): windows/386

The above workaround helped, but...

And it only happens when the said server name was used, removed and then a new server with the same name created. What probably explains why killing the cache helps...

@remyleone remyleone added the v1 label Apr 24, 2020
@remyleone
Copy link
Member

This issue is related to a legacy version of the CLI. We released a new version for the CLI that you can try out: https://github.com/scaleway/scaleway-cli/releases/tag/v2.0.0
If your issue is not resolved with this new version, feel free to open a new issue.

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

No branches or pull requests

5 participants