(mirror of https://github.com/marekm72/vyos-cloud-init.git) https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=20.4 2020-11-23T15:04:05+00:00 2020-11-23T15:04:05+00:00 aswinrajamannar 39812128+aswinrajamannar@users.noreply.github.com 2020-11-23T15:04:05+00:00 urn:sha1:a4d0feb050e32277a218e45bfb6a496d26ff46d0 Adds the ability to run the Azure preprovisioned VMs as NIC-less and then hot-attach them when assigned for reprovision. The NIC on the preprovisioned VM is hot-detached as soon as it reports ready and goes into wait for one or more interfaces to be hot-attached. Once they are attached, cloud-init gets the expected number of NICs (in case there are more than one) that will be attached from IMDS and waits until all of them are attached. After all the NICs are attached, reprovision proceeds as usual. 2020-11-19T18:38:27+00:00 Anh Vo anhvo@microsoft.com 2020-11-19T18:38:27+00:00 urn:sha1:73e704e3690611625e3cda060a7a6a81492af9d2 Pushing dmesg log to KVP to help troubleshoot VM boot issues 2020-11-19T05:35:46+00:00 Anh Vo anhvo@microsoft.com 2020-11-19T05:35:46+00:00 urn:sha1:eea754492f074e00b601cf77aa278e3623857c5a cc_set_password will only update the password for the default user if cfg['password'] is set. The existing code of datasource Azure will fail to update the default user's password because it does not set that metadata. If the default user doesn't exist in the image, the current code works fine because the password is set during user create and not in cc_set_password 2020-11-18T18:02:56+00:00 Johnson Shi Johnson.Shi@microsoft.com 2020-11-18T18:02:56+00:00 urn:sha1:6df0230b1201d6bed8661b19d8f3758797635377 Increase Azure Endpoint HTTP retries to handle occasional platform network blips. Introduce a common method http_with_retries in the azure.py helper, which will serve as the common HTTP request handler for all HTTP requests with the Azure endpoint. This method has builtin retries and reporting diagnostics logic. 2020-11-18T17:34:04+00:00 Johnson Shi Johnson.Shi@microsoft.com 2020-11-18T17:34:04+00:00 urn:sha1:d807df288f8cef29ca74f0b00c326b084e825782 On systems where the Azure datasource is a viable platform for crawling metadata, cloud-init occasionally encounters fatal irrecoverable errors during the crawling of the Azure datasource. When this happens, cloud-init crashes, and Azure VM provisioning would fail. However, instead of failing immediately, the user will continue seeing provisioning for a long time until it times out with "OS Provisioning Timed Out" message. In these situations, cloud-init should report failure to the Azure datasource endpoint indicating provisioning failure. The user will immediately see provisioning terminate, giving them a much better failure experience instead of pointlessly waiting for OS provisioning timeout. 2020-11-13T22:34:44+00:00 Daniel Watkins oddbloke@ubuntu.com 2020-11-13T22:34:44+00:00 urn:sha1:8a9ee02dce8485961b0eeb1930e637a88b03b0ad This is a new builtin variable that appeared in Ubuntu in 5.1~rc2-1ubuntu1 and started causing daily build failures. 2020-11-10T14:51:16+00:00 Scott Moser smoser@brickies.net 2020-11-10T14:51:16+00:00 urn:sha1:2730521fd566f855863c5ed049a1df26abcd0770 Largely speaking, ds-identify protects from this scenario being hit, but if DataSourceRbxCloud ran and there was no metadata disks found (LABEL=CLOUDMD), then it would stacktrace. The fix is just to clean up the get_md function a little bit, and the explicitly check for False as a return value in _get_data. 2020-11-04T19:51:16+00:00 Moustafa Moustafa momousta@microsoft.com 2020-11-04T19:51:16+00:00 urn:sha1:c86283f0d9fe8a2634dc3c47727e6218fdaf25e2 This allows the cloud-init log to be pushed multiple times during boot, with the latest lines being pushed each time. 2020-11-03T14:47:03+00:00 WebSpider WebSpider@users.noreply.github.com 2020-11-03T14:47:03+00:00 urn:sha1:7978feb3af5846a1a2ac489cde83febe975b046d * Include both Ubuntu-style cfg file, and Debian-style directory in ENI * Add WebSpider as contributor 2020-11-02T20:41:11+00:00 Scott Moser smoser@brickies.net 2020-11-02T20:41:11+00:00 urn:sha1:0af1ff1eaf593c325b4f53181a572110eb016c50 This just separates the reading of dmi values into its own file. Some things of note: * left import of util in dmi.py only for 'is_container' It'd be good if is_container was not in util. * just the use of 'util.is_x86' to dmi.py * open() is used directly rather than load_file.