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

AWS: empty snapshot names with USE_CLAIM_NAME=true #53

Open
mrtyler opened this issue Mar 22, 2018 · 1 comment
Open

AWS: empty snapshot names with USE_CLAIM_NAME=true #53

mrtyler opened this issue Mar 22, 2018 · 1 comment

Comments

@mrtyler
Copy link
Contributor

mrtyler commented Mar 22, 2018

I've been running k8s-snapshots for a few months in a kops-managed Kubernetes cluster on AWS.

I pulled the latest k8s-snapshots Docker image. I believe I went from the 2018-02-09 image c5da4196dfa7 to the 2018-02-18 image d4c54dea2402 (current latest build).

With the old version and USE_CLAIM_NAME=true, my Snapshot names looked as expected. With the new version, Snapshot names are empty. I believe the k8s-snapshots version change is the only thing that changed in my cluster between the desired behavior and the buggy behavior.

If I have it right, the two changes merged between the old version and the new version are #51 --
which looks to be Google Cloud-only -- and #50. @wadahiro do you think this could be related to your boto3 changes?

@mrtyler
Copy link
Contributor Author

mrtyler commented Mar 28, 2018

I reverted the changes from #50, rebuilt the Docker image, and deployed it to my cluster. Snapshot names have returned.

In case it is useful to anyone, my image -- built from d4af616 minus #50, or the equivalent of c66eedb -- is available at https://hub.docker.com/r/mrtyler/k8s-snapshots/.

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

No branches or pull requests

1 participant