Tests for Zesty Zapus

[benjaoming]

Summary

Since 16.10, systemd has been both for system and user sessions (startup applications etc). No more upstart.

We've fixed #440 and as of now, released it in ka-lite-proposed

I think we should test our installers for 17.04 already, so we know if we're good.

@radinamatic - would you be able to do this?

[radinamatic]

Tested on Ubuntu 16.10, with installer ka-lite-bundle_0.17.0-0ubuntu2_all.deb

However, server is not starting at reboot:

Tried checking kalite.service as suggested in #5423:

[benjaoming]

@radinamatic I'll get 16.10 running on a virtualbox and see what that's about.

[benjaoming]

Seems everything is fine with the latest 0.17.0-0ubuntu3 - which incidentally also contained a systemd fix, see #443

[radinamatic]

I tried again on Ubuntu 16.10 (latest with all the updates), with installer ka-lite-bundle_0.17.0-0ubuntu3_all.deb, but the server is still not starting at reboot.

Am I missing something @benjaoming?

[benjaoming]

@radinamatic sorry I didn't properly explain. #440 is still open and that part is still broken. There's more explanation in that issue.

You can still start ka-lite with both sudo service ka-lite start and sudo systemctl start ka-lite.service

[radinamatic]

Starting it from terminal is not a problem, even simple kalite start works:

Maybe I'm not getting the real purpose of having a system service... 🤔
My understanding was that the main benefit was so KA Lite could run from boot/startup, but if that's not working because of the broken stuff you investigated in #440, then we should amend the wording of the install configuration, because it is misleading:

Here it states that the service is started automatically, and that's not the case atm, at least on 16.10.

[benjaoming]

@radinamatic I can't work with the differences caused by systemd and explain them to users. Luckily, service ka-lite is still functional on systemd 15.04+ systems afaik.

🤔 My understanding was that the main benefit was so KA Lite could run from boot/startup, but if that's not working because of the broken stuff you investigated in #440, then we should amend the wording of the install configuration, because it is misleading:

I'll fix the startup script and leave the texts unchanged ;)

The purpose of having a system service, is so things get started and stopped when the system boots and shuts down.

[radinamatic]

The purpose of having a system service, is so things get started and stopped when the system boots and shuts down.

Ok, so I wasn't so far off base after all... 😛

I'll fix the startup script and leave the texts unchanged ;)

If the startup script is fixed, no need to change the text! 😉