<div dir="ltr"><div><div><div><div><div>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.<br><br></div>There is a document on github where the feature is called autoupdate.<br><br><a href="https://github.com/ubuntu-core/snappy/blob/master/docs/autoupdate.md">https://github.com/ubuntu-core/snappy/blob/master/docs/autoupdate.md</a><br><br></div>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:<br>root@localhost:~# snappy config ubuntu-core | grep autopilot                    <br>    autopilot: true      <br><br></div>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?<br><br></div>Regards,<br></div>Gabor<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 2, 2015 at 12:20 PM, Gábor Paller <span dir="ltr"><<a href="mailto:gaborpaller@gmail.com" target="_blank">gaborpaller@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>I thought I would move this discussion to a new thread.<br><br></div><div>I looked after a proposal to disable the autopilot with snappy config but I did not find such a mail.<br><br></div><div>Meanwhile, I experimented more with the commands on the page that Leo proposed.<br><a href="https://github.com/ubuntu-core/snappy/blob/master/docs/autopilot.md" target="_blank">https://github.com/ubuntu-core/snappy/blob/master/docs/autopilot.md</a><br><br></div><div>When I say:<br>systemctl disable snappy-autopilot.timer<br></div><div>it does remove the autopilot symlink from the /etc/systemd/system/multi-user.target.wants directory.<br><br></div><div>Before:<br>root@localhost:/etc/systemd/system/multi-user.target.wants# ls<br>cgmanager.service         rsyslog.service                                       <br>cgproxy.service           snappy-autopilot.timer                                <br>cloud-config.service      ssh.service                                           <br>cloud-final.service       ubuntu-snappy.boot-ok.service                         <br>cloud-init-local.service  ubuntu-snappy.firstboot.service                       <br>cloud-init.service        ubuntu-snappy.grub-migrate.service                    <br>cron.service              ubuntu-snappy.run-hooks.service                       <br>pppd-dns.service          webdm_snappyd_0.9.4.service                           <br>remote-fs.target          <br><br></div><div>After:<br>root@localhost:/etc/systemd/system/multi-user.target.wants# ls<br>cgmanager.service         remote-fs.target<br>cgproxy.service           rsyslog.service                                       <br>cloud-config.service      ssh.service                                           <br>cloud-final.service       ubuntu-snappy.boot-ok.service                         <br>cloud-init-local.service  ubuntu-snappy.firstboot.service                       <br>cloud-init.service        ubuntu-snappy.grub-migrate.service                    <br>cron.service              ubuntu-snappy.run-hooks.service                       <br>pppd-dns.service          webdm_snappyd_0.9.4.service     <br><br></div><div>However, reboot somehow recreates the link.<br></div><div>After reboot:<br>root@localhost:/etc/systemd/system/multi-user.target.wants# ls                  <br>cgmanager.service         rsyslog.service                                       <br>cgproxy.service           snappy-autopilot.timer                                <br>cloud-config.service      ssh.service                                           <br>cloud-final.service       ubuntu-snappy.boot-ok.service                         <br>cloud-init-local.service  ubuntu-snappy.firstboot.service                       <br>cloud-init.service        ubuntu-snappy.grub-migrate.service                    <br>cron.service              ubuntu-snappy.run-hooks.service                       <br>pppd-dns.service          webdm_snappyd_0.9.4.service                           <br>remote-fs.target    <br><br></div><div>Can this be the BeagleBone's SD card filesystem?<br><br></div><div>Regards,<br></div><div>Gabor<br></div><div><br></div>John Lenton wrote:<br>so, first off, if you're seeing that message then autopilot is still enabled.<br>
<br>
However, doing the stop (and especially the disable) means it's going<br>
to be disabled at the next boot. Maybe after doing this you played<br>
with “<span>snappy</span> <span>config</span>”? I remember telling you about using <span>snappy</span> <span>config</span><br>
to enable/disable this, so that could be it. Anyway, if <span>snappy</span> <span>config</span><br>
doesn't effectively disable it, it's a bug, please let us know (with<br>
steps-to-reproduce, given I've just tried to reproduce what you<br>
described and got nowhere).<br></div>
</blockquote></div><br></div>