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

GCE Error message with statestore #2082

Open
chrislovecnm opened this issue Mar 9, 2017 · 7 comments
Open

GCE Error message with statestore #2082

chrislovecnm opened this issue Mar 9, 2017 · 7 comments
Labels
area/gce lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
Google Cloud support (GCE) to GA

Comments

@chrislovecnm
Copy link
Contributor

state_store error message does not mention gs:// - consider customizing error message depending on cloud type
@caulagi
Copy link

caulagi commented Nov 10, 2017

I wanted to try and fix this issue. Can you help me get started? I am looking at pkg/apis/registry/statestore.go. Does this look correct? Are there examples of how this is done elsewhere? Thanks.

@chrislovecnm
Copy link
Contributor Author

This is a really old commit, and I am on my phone, so I cannot fully reasearch, but check here https://github.com/kubernetes/kops/pull/1049/files

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 8, 2018
@caulagi
Copy link

caulagi commented Feb 8, 2018

Will try to spend time this weekend.

@chrislovecnm
Copy link
Contributor Author

/remove-stale

@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 10, 2018
@chrislovecnm
Copy link
Contributor Author

/lifecycle frozen
/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Mar 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/gce lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
No open projects
Google Cloud support (GCE) to GA
  
To do
Milestone
No milestone
Development

No branches or pull requests
5 participants
@justinsb @caulagi @chrislovecnm @k8s-ci-robot @fejta-bot