Comment 7 for bug 1935961

thanks for comments rabi it makes sense - i did wonder why swift was still enabled here (and failing the job). I wasnt sure if we needed to special case those deploy steps to not execute the failing task, or just not use that service template at all in the deployment (i.e. remove swift completely) which is what we need to do here.

that probably answers why this isn't happening for wallaby-master (at least haven't found examples yet). There is likely handling for that already in the master upgrade_tasks?