| === cpaelzer_ is now known as cpaelzer | ||
| kqkq95 | hi all ! | 10:01 |
|---|---|---|
| kqkq95 | I have a conflict between cloud-init and customization of the VMware guest operating system, at the first start, the network configuration + name of the VM is configured, cloud-init starts to configure while my system reboots because of VMware who has finished his configuration, someone has already encountered this problem? | 10:03 |
| kqkq95 | at the next start cloud-init repeats the actions .. | 10:04 |
| Odd_Bloke | blackboxsw: Still waiting on an answer to my flake8 Q from yesterday. (This is a semi-blocker for my work to add a conftest to tests/, which is the only reason I'm nagging you. :) | 14:15 |
| blackboxsw | The following changes have landed in master; found via git log --since 05-05-2020 https://paste.ubuntu.com/p/d2qR8pTZNY/ | 16:24 |
| AnhVoMSFT | @blackboxsw i think cloud-init doesn't really depend on the order of attached device since it's been using the device path (/dev/disk/...). I don't know if this is a new issue or if it has always been there. I can go back to older cloud-init version and check. Will file a bug | 18:46 |
| blackboxsw | thanks AnhVoMSFT | 19:10 |
| rharper | AnhVoMSFT: blackboxsw: if you configure more than one additional disk, and provide a disk_setup, fs_setup and mounts; the default merge behavior combines dictionaries, but lists are replaced, so both disks go through disk_setup; but only one gets config for fs_setup and mounts | 19:18 |
| rharper | https://paste.ubuntu.com/p/KbWYh2jkPw/ | 19:18 |
| rharper | AnhVoMSFT: unfortunately, they'll need to replicate the built-in config with the additional disks; https://paste.ubuntu.com/p/2wkyvD2zhj/ | 19:21 |
| rharper | if we changed mounts and fs_setup to also accept a dictionary; with the device-name or something to be an unique key; then, that would merge more cleanly by default https://paste.ubuntu.com/p/4fWT9tGD7T/ | 19:27 |
| rharper | blackboxsw: ^ | 19:27 |
| blackboxsw | reading back | 19:30 |
| AnhVoMSFT | oh i see - so disk_setup currently accepts dictionary but fs_setup and mounts accept lists, that's the issue | 19:33 |
| AnhVoMSFT | thanks for the clarification @rharper | 19:34 |
| blackboxsw | Odd_Bloke: sorry to miss that question about flake8. I have no objections to moving to flake8 from pyflakes. there was a flake8 dependency issue that a barely recall and I didn't have strong opinions about moving away from flake8 other than there were py3 dependency issues at the time for flake8 I believe. | 19:39 |
| blackboxsw | and rharper thanks, I have limited use of the cc_disk_setup module, and forgot how merging would affect additional disks. | 19:40 |
| blackboxsw | Odd_Bloke: falcojr finally responded on https://github.com/canonical/cloud-init/pull/367 I think your suggestions are solid on the approach | 19:42 |
| blackboxsw | just some questions on whether we can include feature_overrides.py module in tip to better document our expected behavior on downstream ubuntu/* releases. | 19:42 |
| rharper | AnhVoMSFT: if you want to file a bug with that issue, we can discuss and see how much effort to support fs_setup/mounts as dictionaries would be | 19:47 |
| rharper | bug 1879552 | 19:48 |
| ubot5 | bug 1879552 in cloud-init "Azure: cloud-init skips formatting the resource disk (ephemeral0) when there is additional data disks' configuration in user-data" [Undecided,New] https://launchpad.net/bugs/1879552 | 19:48 |
| rharper | good, you already did! | 19:48 |
| AnhVoMSFT | yep :) | 19:48 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!