| 19 Feb 2025 |
 adamcstephens | do y'all see timeouts waiting for import snapshot with your upload jobs? | 22:33:47 |
 @hexa:lossy.network | adam asked if the room was broken 😄 so I joined | 22:33:50 |
 Arian | I don't see the messages on my laptop. Only on my phone. So maybe? | 22:34:24 |
| Arian | waddup | 22:34:31 |
| Arian | Oh my laptop is just laggy. | 22:34:40 |
| Arian | In reply to @adam:robins.wtf
do y'all see timeouts waiting for import snapshot with your upload jobs? It can happen very occasional. However the whole script is idempotent. Just rerun it and it should pick up where it left off | 22:35:08 |
| Arian | Sometimes Amazon has a bad day | 22:35:15 |
| Arian | I'm planning to move to coldsnap for snapshot uploads at some point. Which should make things more snappy | 22:35:29 |
| adamcstephens | i just noticed multiple failures today waiting on snapshot import. good to know it's fully idempotent | 22:37:10 |
| adamcstephens | maybe i'll wrap upload-ami in a loop to try a few times :) | 22:37:36 |
| adamcstephens | that or I open another PR to allow for extending the timeout | 22:38:34 |
| adamcstephens | how does the coldsnap path help? | 22:39:34 |
| Arian | coldsnap bypasses the vmimport service | 22:39:43 |
| Arian | which god knows what it’s written in | 22:39:47 |
| Arian | it just uploads blocks directly to EBS | 22:39:53 |
| Arian | image uploads take like 5 seconds with coldsnap | 22:40:27 |
| adamcstephens | that sounds better than the current path. the timeout it's hitting on import is 10 minutes | 22:40:52 |
| Arian | what region are you in?t | 22:42:34 |
| adamcstephens | us-east-2 | 22:43:31 |
| Arian | that timeout is set by AWS. usually AWS timeouts are pretty aligned with the normal behaviour of services | 22:43:37 |
| Arian | might be AWS is having a bad time | 22:43:38 |
| adamcstephens | the imports are completing, but only after the waiter times out :/ | 22:50:10 |
| 20 Feb 2025 |
| @hexa:lossy.network left the room. | 02:39:47 |
| adamcstephens | It took me longer to upload due to my internet connection, but once the snapshot is imported registering it as an AMI is almost instant. | 13:51:42 |
| adamcstephens | This route also seems to be more space efficient in Amazon's reading of the size. A snapshot using the current import-snapshot shows as the full size of the disk image used during build, but a coldsnap uploaded image shows the actual disk usage of the image. | 13:53:22 |
| adamcstephens | * It took me longer to upload due to my internet connection, but once the snapshot is uploaded, then registering it as an AMI is almost instant. | 13:54:27 |
| adamcstephens | hmm, but that snapshot doesn't seem to work for launching instances. likely i did something wrong :/ | 15:01:49 |
| adamcstephens | I'm extending the timeout for our use, since a snapshot is still imported even if the waiter times out. But re-running upload-ami will initiate another import-snapshot, ignoring the already imported one | 15:25:30 |
| 22 Feb 2025 |
| Arian | Oh you need to coldsnap over a raw image | 11:01:35 |
| Arian | You're probably coldsnapping the sparse VHD lol | 11:01:49 |
