fix: extract instance id and disk id from packer build and use them for cleanup in case of cancellation#6539
fix: extract instance id and disk id from packer build and use them for cleanup in case of cancellation#6539librarian wants to merge 5 commits into
Conversation
|
Note This is an automated comment that will be appended during run. Note All workloads for linux-x86_64-relwithdebinfo have completed. Tip Planned checks for linux-x86_64-relwithdebinfo. |
|
status: 🔴 GA scripts pytest result (artifact) GA scripts pytest report (artifact) GA scripts pytest report (s3) GA scripts pytest results (s3)
|
|
Note This is an automated comment that will be appended during run. Note All workloads for linux-x86_64-relwithdebinfo have completed. Tip Planned checks for linux-x86_64-relwithdebinfo. |
|
status: 🔴 GA scripts pytest result (artifact) GA scripts pytest report (artifact) GA scripts pytest report (s3) GA scripts pytest results (s3)
|
|
Note This is an automated comment that will be appended during run. Note All workloads for linux-x86_64-relwithdebinfo have completed. Tip Planned checks for linux-x86_64-relwithdebinfo. |
|
status: 🟢 GA scripts pytest result (artifact) GA scripts pytest report (artifact) GA scripts pytest report (s3) GA scripts pytest results (s3)
|
1 participant
Initial thought was to use always() to prevent packer build from interrupting and thus allowing it to cleanup after himself. But this is problematic and would require force-cancel to cancel workflow.
Now we parse logs that are provided by packer and catch instance ids and disk ids and run clean up action after.