Concerning the services being started and complaining about db tables not existing is because we actually ask pebble to be up and running (having all its services up) before we run the db_sync. (cf https://opendev.org/openstack/sunbeam-charms/src/commit/3de9342ed47460df61f5f13528080fe81c24cc69/ops-sunbeam/ops_sunbeam/charm.py#L653)
I think we can be smarter there and actually take into account if a database sync run has been executed or not.
I had started some implementation to try skipping service check at some point: https://review.opendev.org/c/openstack/sunbeam-charms/+/909657 this gives a rough idea, it's not complete
Concerning the services being started and complaining about db tables not existing is because we actually ask pebble to be up and running (having all its services up) before we run the db_sync. (cf https:/ /opendev. org/openstack/ sunbeam- charms/ src/commit/ 3de9342ed47460d f61f5f13528080f e81c24cc69/ ops-sunbeam/ ops_sunbeam/ charm.py# L653)
I think we can be smarter there and actually take into account if a database sync run has been executed or not.
I had started some implementation to try skipping service check at some point: https:/ /review. opendev. org/c/openstack /sunbeam- charms/ +/909657 this gives a rough idea, it's not complete