Comment 3 for bug 1993652

To give some more context, FCE initializes vault, ceilometer, octavia, heat, cinder, designate, and keystone and waits for the deployment to idle in between each step. Then we run:

```
2022-10-19-16:30:19 fce.openstack INFO Starting step: openstack:glance_simplestreams_sync
2022-10-19-16:30:21 root DEBUG [localhost]: juju config -m foundations-maas:openstack glance-simplestreams-sync run=true
2022-10-19-16:30:22 root DEBUG [localhost]: juju status -m foundations-maas:openstack --format=yaml
2022-10-19-16:30:27 root DEBUG [localhost]: juju wait-for unit -m foundations-maas:openstack --timeout 3600s glance-simplestreams-sync/0 --query 'workload-status=="active"'
2022-10-19-17:30:27 root ERROR [localhost] Command failed: juju wait-for unit -m foundations-maas:openstack --timeout 3600s glance-simplestreams-sync/0 --query 'workload-status=="active"'
2022-10-19-17:30:27 root ERROR [localhost] STDOUT follows:
properties:
  workload-status: unknown

2022-10-19-17:30:27 root ERROR [localhost] STDERR follows:
Unit "glance-simplestreams-sync/0" is running
ERROR timed out waiting for "glance-simplestreams-sync/0" to reach goal state
```

Usually gss syncs all the images within an hour but on all the juju 3.0 runs it doesn't change its status.