DigitalOcean provider playbook: doctl compute image create step is not skipped & image creation always fails
Absynth723 opened this issue · 1 comments
I'm trying to set up Forem with the DigitalOcean provider playbook and keep hitting a wall on the "doctl compute image create" step.
I can see that the correct custom image has been created in the first run of the playbook (it's visible with "doctl compute image list" via CLI, and I can see it in the web-based UI at DO), but the playbook keeps insisting on re-creating it (and subsequently times out). Every time I run it, a new image with the same name (at the time of writing, fcos-36.20220806.3.0) is created at my DO custom image store.
Also, the sequence of things looks a little odd to me:
TASK [Create FCOS image] **********************************************************************************************************************************************
changed: [forem]
TASK [Skip doctl compute image create step if image already exists] ***************************************************************************************************
skipping: [forem]
Shouldn't the "Skip" task be executed before the "Create Image" task?
I suspect this might be an issue in my doctl setup and/or in the DO API, because the ansible playbook seems to see different images than a command-line "doctl" execution. I'm investigating this locally.