-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
digital_ocean_v2.py doesn't restore snapshot #22724
Comments
Here is the output with the modification I made: |
@TY2U I suspect we just haven't implemented this kind of functionality yet, but i'm sure it can be done. ping @techhat and @wesleylancel |
I was looking into getting the snapshot functionality added soon |
Yay! Thank you for the awesomeness everyone =) |
@dmyerscough are you close to getting snapshot integration working? I can take a stab if you want. |
@TY2U @Pravka @dmyerscough Did #26824 fix the issue of getting snapshots working in digital ocean? |
Works for me; salt-cloud creates droplet from a snap and uses the right ssh key. I'd still prefer for salt-cloud to be aware that private_networking is enabled and give you the option of using that to provision, but I'll be opening a separate issue for that. |
@Pravka Yeah, a separate issue for the private_networking option would be great. Since this is confirmed to be working, I am going to go a head a close this. If there are any other troubles here, let us know and we can re-open. Thanks everyone! |
Hey,
I'm wondering if someone can help me figure this out.
I made a snapshot of a server and I am trying to restore it via the digital_ocean_v2.py but it's not working properly.
The name of the snapshot in the example is server.example.com
Debug output of command:
salt-cloud -p server.example.com server.example.com
https://gist.github.com/ty2u/f48557e6c4bd56723f25
server.example.com profile:
salt --versions-report
If I modify the digital_ocean_v2.py script to use the image id number instead of the name it will actually launch the server but still seems to display errors. I did this by replacing lines 226-229:
with
Furthermore, the ssh key is not valid, I think when the server has a different IP address sometimes.
The text was updated successfully, but these errors were encountered: