| minimal | holmanb: here's an example that creates a XML file to define the VM and then creates it using virsh | 00:03 |
|---|---|---|
| holmanb | minimal did you send the example? | 06:29 |
| holmanb | I don't see it | 06:30 |
| ani | falcojr please see my comment in https://github.com/canonical/cloud-init/pull/4474 . | 06:41 |
| -ubottu:#cloud-init- Pull 4474 in canonical/cloud-init "net: allow dhcp6 configuration from generate_fallback_configuration()" [Merged] | 06:41 | |
| ani | Please unrevert this. | 06:41 |
| ani | We are also testing this internally again and the QE folks will come back with the result. | 06:41 |
| holmanb | ani: as I read it, the docs you quote support falcojr's statement | 11:30 |
| holmanb | ani: "For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config | 11:31 |
| holmanb | allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration | 11:31 |
| holmanb | completes successfully." | 11:31 |
| holmanb | Therefore, in order for the overall network configuration to succeed in an IPv6 network, may-fail=true MUST be set on NMSettingIP4Config. | 11:33 |
| holmanb | The ipv4 and ipv6 docs use the same example, but presumably it is also true that in an IPv4-only network, may-fail=true MUST be set on NMSettingIP6Config. | 11:38 |
| holmanb | ani: The implementation you proposed uses may-fail=false for both NMSettingIP4Config and NMSettingIP6Config, meaning that BOTH ipv4 and ipv6 must succeed for the overall network configuration to succeed - this is incorrect since cloud-init is expected to run in environments where either ipv4 or ipv6 is available. Obviously ipv6-only support is lacking by default, however this change breaks ipv4 support, hence it was reverted. | 11:45 |
| ani | holmanb OK I was misreading the doc. my apologies. I do not underastand how our QE gave a green flag to this change after testing. I am checking. Meanwhile can you please re-open https://github.com/canonical/cloud-init/issues/4439 ? | 13:11 |
| -ubottu:#cloud-init- Issue 4439 in canonical/cloud-init "[enhancement]: Modify net.generate_fallback_config() to configure IPv6 DHCP as well" [Closed] | 13:11 | |
| holmanb | ani: just reopened | 14:38 |
| holmanb | ani: This was caught because we're prepping for 24.4 release and this commit got flagged for broader review because of the risk that change. | 14:39 |
| holmanb | ani: I suspect that NetworkManager would either fail or not complete, blocking boot. Honestly I haven't tested myself, but it should be a trivial thing to do. | 14:43 |
| minimal | holmanb: strange, I thought I posted it. Anyway: https://gist.github.com/cjihrig/a0f0e3c058b4d9dcf9ca1f771916fa28 | 17:45 |
| === esv_ is now known as esv | ||
| holmanb | minimal: nice, thanks | 21:03 |
| holmanb | minimal: just saw this, was already working on a doc | 21:04 |
| holmanb | is there some advantage to not using virt-install? | 21:05 |
| holmanb | minimal: https://github.com/canonical/cloud-init/commit/d8bce5885ba032a10a9f23ad8ece9dd4f9599b9e | 21:05 |
| -ubottu:#cloud-init- Commit d8bce58 in canonical/cloud-init "docs: Add instructions to run libvirt with (#4578)" | 21:05 | |
| holmanb | Oh hey ubottu, nice to see you o/ | 21:06 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!