(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=equuleus 2014-09-15T13:40:29+00:00 2014-09-15T13:40:29+00:00 Scott Moser smoser@ubuntu.com 2014-09-15T13:40:29+00:00 urn:sha1:6093b8b2733814b9265494c47f4268167c9491ab 2014-09-12T21:59:52+00:00 Scott Moser smoser@ubuntu.com 2014-09-12T21:59:52+00:00 urn:sha1:f5be74dc84aac7bb9a634e5518f5aac6ae80098a silently wait 5 seconds for networking to come up. We started seeing the message more now, as we are now blocking the networking from coming up until cloud-init-local is done. Previously that would have happened in parallel, and we were less likely to see that message. 2014-09-12T21:45:20+00:00 Scott Moser smoser@ubuntu.com 2014-09-12T21:45:20+00:00 urn:sha1:41a52ef99a9dddd3fef9bdc883dfca55770ef2a5 not sure why this was here. the intent must of have been to allow for a local datasource to continue booting and not annoyingly block waiting for network information (if ithere was no network information). However, that seems wrong. If the datasource wipes /etc/network/interfaces and there are no network interfaces then we're probably breaking that use case here. However we're fixing the other more common case. 2014-09-12T19:38:56+00:00 Scott Moser smoser@ubuntu.com 2014-09-12T19:38:56+00:00 urn:sha1:8eb2f6ea588775d3ddd55a62630cab310497190e 2014-09-12T17:03:44+00:00 Scott Moser smoser@ubuntu.com 2014-09-12T17:03:44+00:00 urn:sha1:b09b12bc0130b6787bfee0332addd055459b9629 This makes it so networking wont start to come up until after cloud-init-local has had a chance to search local datasources and set /etc/network/interfaces. The changes most likely need to still be done for systemd. LP: #1368861 2014-09-11T14:50:04+00:00 Scott Moser smoser@ubuntu.com 2014-09-11T14:50:04+00:00 urn:sha1:26c1cf9eeeb39e9bfcc1a37743679e5c76ab97b0 With the writing of cloud-init status, cloud-init-local needs to have /run mounted. The issue we were seeing was a race where: cloud-init-local creates /run/cloud-init /run is mounted cloud-init-local tries to link a file into /run/cloud-init that directory was no longer visisable as /run was mounted over the top. LP: #1353008 2013-09-17T16:34:25+00:00 Scott Moser smoser@ubuntu.com 2013-09-17T16:34:25+00:00 urn:sha1:266d12c5777d5fba97c374c33cb4f31d50e2d347 2013-03-26T19:40:29+00:00 Scott Moser smoser@ubuntu.com 2013-03-26T19:40:29+00:00 urn:sha1:be0041e7c7fd6ce5ffc1c9c54893b715bcab6358 In starting containers in lxc, I was seeing errors like: /proc/self/fd/9: 24: kill: No such process Which indicated the sleep pid had already died. I'm not sure how or why it was dead, but this just is less annoying in that case. 2013-03-04T19:28:34+00:00 Scott Moser smoser@ubuntu.com 2013-03-04T19:28:34+00:00 urn:sha1:bcf04395be323c60b013e531ef3bf32b722a780a 2013-03-04T14:56:24+00:00 Scott Moser smoser@ubuntu.com 2013-03-04T14:56:24+00:00 urn:sha1:1a3e0fa19b6c3224ea986141b37f74d5464b7c82 LP: #1015223