/srv/irclogs.ubuntu.com/2021/12/06/#cloud-init.txt

=== esv_ is now known as esv
minimalblackboxsw: following on from the IPv6 chat last Friday, eni.py always adds an entry for "lo" with ipv4, wondering how to "signal" in the network metadata whether (a) an IPv4 loopback, or (b) an IPv6 one, or (c) both entries should be setup10:30
falcojrblackboxsw: looking for quick review to unblock CI: https://github.com/canonical/cloud-init/pull/113416:05
ubottuPull 1134 in canonical/cloud-init "docs: pin mistune dependency" [Open]16:05
blackboxswlanded 1134. Also thanks for the Ubuntu Jammy review  upload success: [ubuntu/jammy-proposed] cloud-init 21.4-25-g039c40f9-0ubuntu1~22.04.1 (Accepted)17:18
blackboxswso tip of cloud-init from Friday will be in cloudimages soon.17:18
blackboxswholmanb: is the meta-schema branch good for final review?17:20
holmanb@blackboxsw: assuming tests pass, yes :)17:22
holmanbaaaaaaand tests did not pass17:25
holmanb*grumble grumble* 17:26
minimalblackboxsw: hi, not sure if you noticed my IM from earlier today17:26
minimalblackboxsw: following on from the IPv6 chat last Friday, eni.py always adds an entry for "lo" with ipv4, wondering how to "signal" in the network metadata whether (a) an IPv4 loopback, or (b) an IPv6 one, or (c) both entries should be setup17:27
blackboxswminimal: hrm good question. Need to think on that a bit.17:30
minimalyeah, its a general network-config YAML issue rather than eni-specific17:32
minimalmight also need "smarts", e.g. if any IPv6 address is defined for any device in network-config then should the ipv6 ::1 lo also be brought up, likewise for any ipv4 address in the YAML17:33
* holmanb pushes fix for failed xenial test and crosses fingers17:35
holmanb@blackboxsw - good for final review18:05
blackboxswholmanb: landed meta-schema validation. thanks for the work on that22:27
holmanb@blackboxsw: woot! thank you!22:31

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!