(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/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-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-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. 2020-10-30T18:12:25+00:00 Markus Schade markus.schade@hetzner.com 2020-10-30T18:12:25+00:00 urn:sha1:0f8be879073148f1d67094df9ec895a873caa0d7 Fixes erroneous string/int comparison introduced in 1431c8a metadata['instance-id'] is an integer but the value read from smbios is a string. The comparision would cause TypeError. 2020-10-29T14:45:47+00:00 Markus Schade markus.schade@hetzner.com 2020-10-29T14:45:47+00:00 urn:sha1:1431c8a1bddaabf85e1bbb32bf316a3aef20036e Hetzner Cloud also provides the instance ID in SMBIOS information. Use it to locally check_instance_id and to compared with instance_id from metadata service. LP: #1885527 2020-10-16T15:54:38+00:00 Johnson Shi Johnson.Shi@microsoft.com 2020-10-16T15:54:38+00:00 urn:sha1:8766784f4b1d1f9f6a9094e1268e4accb811ea7f DataSourceAzure previously writes the preprovisioning reported ready marker file before it goes through the report ready workflow. On certain VM instances, the marker file is successfully written but then reporting ready fails. Upon rare VM reboots by the platform, cloud-init sees that the report ready marker file already exists. The existence of this marker file tells cloud-init not to report ready again (because it mistakenly assumes that it already reported ready in preprovisioning). In this scenario, cloud-init instead erroneously takes the reprovisioning workflow instead of reporting ready again. 2020-10-15T19:39:09+00:00 Adrian Vladu avladu@cloudbasesolutions.com 2020-10-15T19:39:09+00:00 urn:sha1:d76d6e6749315634efe0494501270740e8fef206 Consider valid product names as valid chassis asset tags when detecting OpenStack platform before crawling for OpenStack metadata. As `ds-identify` tool uses product name as valid chassis asset tags, let's replicate the behaviour in the OpenStack platform detection too. This change should be backwards compatible and a temporary fix for the current limitations on the OpenStack platform detection. LP: #1895976 2020-10-13T19:42:54+00:00 Anh Vo anhvo@microsoft.com 2020-10-13T19:42:54+00:00 urn:sha1:8ec8c3fc63a59b85888a0b52356b784314a1d4cc