Comment 7 for bug 1863667

@lweberru,

To complete the guide there is no mention that the "systemd" service snap.microstack.*.services are autogenerated from whats seems to be the snap install. This means that for you to enable the services and make them "autostart" it will have to be done manually by creating the service in "/etc/systemd/system/". I'm adding as an example cinder-scheduler and this was repeated for cinder-uwsgi as well. Once created the service just start the new services if some issues still arise just restart the whole service batch ( systemctl restart snap.microstack.* )

file: snap.microstack.cinder-scheduler.service

[Unit]
# Auto-generated, DO NOT EDIT
Description=Service for snap application microstack.cinder-scheduler
Requires=snap-microstack-196.mount
Wants=network.target
After=snap-microstack-196.mount network.target
X-Snappy=yes

[Service]
ExecStart=/usr/bin/snap run microstack.cinder-scheduler
SyslogIdentifier=microstack.cinder-scheduler
Restart=on-failure
WorkingDirectory=/var/snap/microstack/196
TimeoutStopSec=30
Type=simple

[Install]
WantedBy=multi-user.target

Regards
- MRBC