=== esv_ is now known as esv
[10:30] <minimal> blackboxsw: 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 setup
[16:05] <falcojr> blackboxsw: looking for quick review to unblock CI: https://github.com/canonical/cloud-init/pull/1134
[16:05] <ubottu> Pull 1134 in canonical/cloud-init "docs: pin mistune dependency" [Open]
[17:18] <blackboxsw> landed 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] <blackboxsw> so tip of cloud-init from Friday will be in cloudimages soon.
[17:20] <blackboxsw> holmanb: is the meta-schema branch good for final review?
[17:22] <holmanb> @blackboxsw: assuming tests pass, yes :)
[17:25] <holmanb> aaaaaaand tests did not pass
[17:26] <holmanb> *grumble grumble* 
[17:26] <minimal> blackboxsw: hi, not sure if you noticed my IM from earlier today
[17:27] <minimal> blackboxsw: 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 setup
[17:30] <blackboxsw> minimal: hrm good question. Need to think on that a bit.
[17:32] <minimal> yeah, its a general network-config YAML issue rather than eni-specific
[17:33] <minimal> might 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 YAML
[17:35]  * holmanb pushes fix for failed xenial test and crosses fingers
[18:05] <holmanb> @blackboxsw - good for final review
[22:27] <blackboxsw> holmanb: landed meta-schema validation. thanks for the work on that
[22:31] <holmanb> @blackboxsw: woot! thank you!