<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 5, 2016 at 9:31 AM, MikeB <span dir="ltr"><<a href="mailto:mabnhdev@gmail.com" target="_blank">mabnhdev@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 style="font-family:tahoma,sans-serif;font-size:small"><pre style="font-family:courier,"courier new",monospace;font-size:14px;white-space:pre-wrap;word-wrap:break-word;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">I posted this over a week ago and received no responses. I'd really like to get past this problem so that I no longer have to use ubuntu-device-flash to generate a working ubuntu-core. </pre></div></div></blockquote><div><br></div><div>Hi Mike,</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div style="font-family:tahoma,sans-serif;font-size:small"><pre style="font-family:courier,"courier new",monospace;font-size:14px;white-space:pre-wrap;word-wrap:break-word;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre style="font-family:courier,"courier new",monospace;font-size:14px;white-space:pre-wrap;word-wrap:break-word;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">I'm trying to generate a custom Ubuntu-Core OS for a network switch
whitebox from DNI. I'm building a custom kernel snap using the latest snapcraft, et. al. - I needed to patch a couple kernel files, but mostly the customization are config changes. The snap was built with confinement:strict, grade:devel</pre><pre style="font-family:courier,"courier new",monospace;font-size:14px;white-space:pre-wrap;word-wrap:break-word;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">I'm using ubuntu-image (Version 0.5+mvo10 Rev 17) to generate the image.</pre><pre style="font-family:courier,"courier new",monospace;font-size:14px;white-space:pre-wrap;word-wrap:break-word;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre style="font-family:courier,"courier new",monospace;font-size:14px;white-space:pre-wrap;word-wrap:break-word;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">I'm using the gadget from the latest rev of lp:~vorlon/snappy-hub/snappy-<wbr>systems.
The assertion file:
type: model
authority-id: TBD
series: 16
brand-id: TBD
model: canonical-pc-amd64
gadget: pc
kernel: deltanetworks-l9032nxb-kernel
architecture: amd64
timestamp: 2016-09-19T8:30:00-04:00
revision: 0
body-length: 0
</pre><pre style="font-family:courier,"courier new",monospace;font-size:14px;white-space:pre-wrap;word-wrap:break-word;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre style="font-family:courier,"courier new",monospace;font-size:14px;white-space:pre-wrap;word-wrap:break-word;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><div style="color:rgb(34,34,34);white-space:normal;font-family:tahoma,sans-serif;font-size:small">The first problem is that firstboot setup fails every time.</div><div style="color:rgb(34,34,34);white-space:normal;font-family:tahoma,sans-serif;font-size:small"><br></div><div style="color:rgb(34,34,34);white-space:normal;font-family:tahoma,sans-serif;font-size:small">I see this message in the syslog...</div><div style="color:rgb(34,34,34);white-space:normal;font-family:tahoma,sans-serif;font-size:small"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;white-space:normal"><font face="tahoma, sans-serif">error: cannot create state: state "/var/lib/snapd/state.json" already exists</font></div></pre><div><br></div><div><div>The second problem is much more annoying - a very long bootup time.</div><div><br></div><div>From 'Starting Initial cloud-init job (metadata service crawler)...' to getting a login prompt now takes about 260 seconds. This happens on every reboot.</div></div></div></div></blockquote><div><br></div><div>Typically if cloud-init did not obtain a local data source (a cdrom or disk with cloud-init data) then it will attempt to look for one on the net; think EC2 and other</div><div>clouds which host metadata services over the network.</div><div><br></div><div>This suggests that your image is not including any cloud-config in /var/lib/cloud/seed/nocloud-net/ </div><div><br></div><div>Getting a copy of /var/lib/cloud-init.log would be helpful, as well as confirming if you have any </div><div>data in the image under the nocloud-net seed directory.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div style="font-family:tahoma,sans-serif;font-size:small"><div><div><br></div><div>About 60 seconds is spent in 'Started Update resolvconf for networkd DNS.'</div><div><br></div><div>Another 80 seconds is spent "Calling '<a href="http://169.254.169.254/2009-04-04/meta-data/instance-id" target="_blank">http://169.254.169.254/2009-0<wbr>4-04/meta-data/instance-id</a>'"</div><div><br></div><div>Another 120 seconds is spent "Calling 'http:///latest/meta-data/inst<wbr>ance-id'" - that is the default gateway for the subnet, which, as far as I know, does not have an http server.</div><div><br></div><div>Any ideas on how I can get back to reasonable boot times?</div></div></div></div></blockquote><div><br></div><div>I suspect that once we figure out what's going on with your data source, these will go away.</div><div> </div><div>Ryan</div><div><br></div></div></div></div>