Disabling autopilot (was: member not found)

[Gábor Paller]

I thought I would move this discussion to a new thread.

I looked after a proposal to disable the autopilot with snappy config but I
did not find such a mail.

Meanwhile, I experimented more with the commands on the page that Leo
proposed.
https://github.com/ubuntu-core/snappy/blob/master/docs/autopilot.md

When I say:
systemctl disable snappy-autopilot.timer
it does remove the autopilot symlink from the
/etc/systemd/system/multi-user.target.wants directory.

Before:
root at localhost:/etc/systemd/system/multi-user.target.wants# ls
cgmanager.service
rsyslog.service
cgproxy.service
snappy-autopilot.timer
cloud-config.service
ssh.service
cloud-final.service
ubuntu-snappy.boot-ok.service
cloud-init-local.service
ubuntu-snappy.firstboot.service
cloud-init.service
ubuntu-snappy.grub-migrate.service
cron.service
ubuntu-snappy.run-hooks.service
pppd-dns.service
webdm_snappyd_0.9.4.service
remote-fs.target

After:
root at localhost:/etc/systemd/system/multi-user.target.wants# ls
cgmanager.service         remote-fs.target
cgproxy.service
rsyslog.service
cloud-config.service
ssh.service
cloud-final.service
ubuntu-snappy.boot-ok.service
cloud-init-local.service
ubuntu-snappy.firstboot.service
cloud-init.service
ubuntu-snappy.grub-migrate.service
cron.service
ubuntu-snappy.run-hooks.service
pppd-dns.service          webdm_snappyd_0.9.4.service

However, reboot somehow recreates the link.
After reboot:
root at localhost:/etc/systemd/system/multi-user.target.wants#
ls
cgmanager.service
rsyslog.service
cgproxy.service
snappy-autopilot.timer
cloud-config.service
ssh.service
cloud-final.service
ubuntu-snappy.boot-ok.service
cloud-init-local.service
ubuntu-snappy.firstboot.service
cloud-init.service
ubuntu-snappy.grub-migrate.service
cron.service
ubuntu-snappy.run-hooks.service
pppd-dns.service
webdm_snappyd_0.9.4.service
remote-fs.target

Can this be the BeagleBone's SD card filesystem?

Regards,
Gabor

John Lenton wrote:
so, first off, if you're seeing that message then autopilot is still
enabled.

However, doing the stop (and especially the disable) means it's going
to be disabled at the next boot. Maybe after doing this you played
with “snappy config”? I remember telling you about using snappy config
to enable/disable this, so that could be it. Anyway, if snappy config
doesn't effectively disable it, it's a bug, please let us know (with
steps-to-reproduce, given I've just tried to reproduce what you
described and got nowhere).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snappy-devel/attachments/20151102/53beb848/attachment.html>