rebooting host does not start microstack

[jensni-ch]

I installed snap microstack as described here: https://ubuntu.com/tutorials/microstack-get-started#2-install-microstack
On a new intel system with latest LTS Ubuntu Server.
Everything runs fine after installation, but after rebooting, snap does not start all services.

At least the following services are not started:
snap.microstack.cinder-uwsgi.service
snap.microstack.glance-api.service
snap.microstack.keystone-uwsgi.service
snap.microstack.neutron-api.service
snap.microstack.neutron-ovn-metadata-agent.service
snap.microstack.nginx.service
snap.microstack.nova-api-metadata.service
snap.microstack.nova-api.service
snap.microstack.nova-compute.service
snap.microstack.nova-conductor.service
snap.microstack.nova-scheduler.service
snap.microstack.nova-spicehtml5proxy.service
snap.microstack.placement-uwsgi.service
snap.microstack.registry.service

$ systemctl status snap.microstack.cinder-uwsgi.service
snap.microstack.cinder-uwsgi.service - Service for snap application microstack.cinder-uwsgi
     Loaded: loaded (/etc/systemd/system/snap.microstack.cinder-uwsgi.service; disabled; vendor preset: enabled)
     Active: inactive (dead)

$ snap services
Service                                Startup   Current   Notes
lxd.activate                           enabled   inactive  -
lxd.daemon                             enabled   inactive  socket-activated
microstack.cinder-backup               disabled  inactive  -
microstack.cinder-scheduler            enabled   active    -
microstack.cinder-uwsgi                disabled  inactive  -
microstack.cinder-volume               disabled  inactive  -
microstack.cluster-uwsgi               enabled   active    -
microstack.external-bridge             enabled   inactive  -
microstack.filebeat                    disabled  inactive  -
microstack.glance-api                  disabled  inactive  -
microstack.horizon-uwsgi               enabled   active    -
microstack.iscsid                      disabled  inactive  -
microstack.keystone-uwsgi              disabled  inactive  -
microstack.libvirtd                    enabled   active    -
microstack.load-modules                enabled   inactive  -
microstack.memcached                   enabled   active    -
microstack.mysqld                      enabled   active    -
microstack.neutron-api                 disabled  inactive  -
microstack.neutron-ovn-metadata-agent  disabled  inactive  -
microstack.nginx                       disabled  inactive  -
microstack.nova-api                    disabled  inactive  -
microstack.nova-api-metadata           disabled  inactive  -
microstack.nova-compute                disabled  inactive  -
microstack.nova-conductor              disabled  inactive  -
microstack.nova-scheduler              disabled  inactive  -
microstack.nova-spicehtml5proxy        disabled  inactive  -
microstack.nrpe                        disabled  inactive  -
microstack.ovn-controller              enabled   active    -
microstack.ovn-northd                  enabled   active    -
microstack.ovn-ovsdb-server-nb         enabled   active    -
microstack.ovn-ovsdb-server-sb         enabled   active    -
microstack.ovs-vswitchd                enabled   active    -
microstack.ovsdb-server                enabled   active    -
microstack.placement-uwsgi             disabled  inactive  -
microstack.rabbitmq-server             enabled   active    -
microstack.registry                    disabled  inactive  -
microstack.setup-lvm-loopdev           disabled  inactive  -
microstack.target                      disabled  inactive  -
microstack.telegraf                    disabled  inactive  -
microstack.virtlogd                    enabled   active    -

I couldn't find an error in any snap warning, journalctl or dmesg.
Why are these services disabled after rebooting?

[jensni-ch]

Also reported this here: https://bugs.launchpad.net/microstack/+bug/1901827