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

'scw run' and 'scw exec -w' should exit if server state changed to 'stopped' #229

Closed
moul opened this issue Nov 3, 2015 · 0 comments
Closed

'scw run' and 'scw exec -w' should exit if server state changed to 'stopped' #229

moul opened this issue Nov 3, 2015 · 0 comments
Assignees
@QuentinPerez
Labels
enhancement

Comments

@moul
Copy link
Contributor

moul commented Nov 3, 2015

Sometimes, the server won't boot up from start to finish, i.e: if there are no spot left for this kind of instance, scw run and scw exec -w are polling the API to get the current state, the expected behavior is an exit 1 as soon as the server state is 'stopped' from the API point of view
@moul moul mentioned this issue Nov 25, 2015
Closed
@QuentinPerez QuentinPerez mentioned this issue Nov 25, 2015
Merged
@moul moul closed this as completed in #240 Nov 26, 2015
@moul moul removed the in progress label Nov 26, 2015
clement-gilbert pushed a commit to clement-gilbert/scaleway-cli that referenced this issue Mar 3, 2022
@kindermoumoute
fix: update sdk config (scaleway#229)
3dca78f 
* deps: update go modules and vendor
* fix: update SDK config methods
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@QuentinPerez QuentinPerez

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@moul @QuentinPerez