Disabling autopilot (was: member not found)

[John Lenton]

Quoting myself:

On 30 October 2015 at 07:20, John Lenton <john.lenton at canonical.com> wrote:
>
> those docs don't mention it, but it can be disabled via 'snappy
> config' also, e.g.
>
> echo 'config: {ubuntu-core: {autopilot: off}}' | sudo snappy config
> ubuntu-core - | grep autopilot
>
> we need to circle back and rename autopilot to autoupdate (I think?),
> and fix the docs. I've created
> https://github.com/ubuntu-core/snappy/issues/37 because I couldn't
> find it.

that issue is now addressed in master, with a rename of autopilot to
autoupdate and (hopefully) improved documentation, which you've
noticed, but that is not released yet.

On 4 November 2015 at 14:36, Gábor Paller <gaborpaller at gmail.com> wrote:
> I have dug into this autopilot issue more because I would like to make sure
> that my system is operational when I make a demo.
>
> There is a document on github where the feature is called autoupdate.
>
> https://github.com/ubuntu-core/snappy/blob/master/docs/autoupdate.md
>
> Of course, the example there does not work. It does not work either when I
> update the key-value to "autopilot: false" instead of "autoupdate: off". I
> made this change because if I query the ubuntu-core configuration, the
> answer is:
> root at localhost:~# snappy config ubuntu-core | grep autopilot
>     autopilot: true
>
> Unfortunately so far I have not been able to produce a yaml file which is
> accepted by snappy config. Any idea, how to do this?
>
> Regards,
> Gabor
>
> On Mon, Nov 2, 2015 at 12:20 PM, Gábor Paller <gaborpaller at gmail.com> wrote:
>>
>> 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).
>
>