When running standalone on centos7 between Rocky and Stein or Stein and Train, the upgrade fails because docker is disabled.
2020-10-21 03:07:42 | 2020-10-21 03:07:42.221 317589 WARNING tripleoclient.v1.tripleo_upgrade.Upgrade [-] TASK [Online data migration for Cinder] ****************************************[00m
2020-10-21 03:07:42 | 2020-10-21 03:07:42.223 317589 WARNING tripleoclient.v1.tripleo_upgrade.Upgrade [-] fatal: [undercloud -> 192.168.24.1]: FAILED! => {"changed": true, "cmd": ["docker", "exec", "cinder_api", "cinder-manage", "db", "online_data_migrations"], "delta": "0:00:00.055891", "end": "2020-10-21 03:07:42.199657", "msg": "non-zero return code", "rc": 1, "start": "2020-10-21 03:07:42.143766", "stderr": "Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?", "stderr_lines": ["Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"], "stdout": "", "stdout_lines": []}[00m
This is standalone specific because we define the OS::TripleO::Services::Podman service in environments/standalone/standalone-tripleo.yaml but we use container_cli: docker via environments/docker-ha.yaml. We don't then disable the Podman service definition so both podman and docker are configured. During the upgrade, the podman service nukes docker so it breaks the upgrade.
While we could fix this by switch docker-ha.yaml to disable the Podman service, this might break actual deployments depending on environment file loading order (e.g. podman.yaml is defined prior to docker-ha.yaml). Since this only affects upstream standalone CI, we should probably just stop running the upgrade standalone jobs on centos7 and document this via this bug. We don't officially support this for end users and we no longer wish to continue to manage the centos7 upgrade jobs since they don't provide us necessary coverage anymore now that we have centos8 jobs starting in Train. The centos7 -> centos8 (or rhel) upgrade won't hit this because we completely remove packages via leapp so you cannot hit this situation normally.
Related fix proposed to branch: stable/train
Review: https:/