Comment 8 for bug 1935961

> There is likely handling for that already in the master upgrade_tasks?

Don't think we've to handle it in upgrade_tasks as someone may want to enable swift in the undercloud intentionally (by enabling it in undercloud.conf).

If we use the defaults(not setting enable_swift=true explicitly in undercloud.conf) it would work fine and there would be no issue for upgrade (i.e enabled in v but disabled in w) . I think, we set it explicitly in CI[1], hence the issue.

[1] https://github.com/openstack/tripleo-quickstart-extras/blob/master/roles/extras-common/defaults/main.yml#L163-L168

Don't know how we automated it in the CI for mistral/zaqar etc.