[11:03] stickupkid, achilleasa_: Small one - https://github.com/juju/juju/pull/12661 [11:05] stickupkid, achilleasa_: Also, need help with a design choice. We currently sort addresses with scope as the first priority, then IPv4 over v6 with host-names after that. [11:06] that makes sense... what's the issue going forward? [11:06] Should secondary IP addresses come before or after host-names. I think after. [11:28] is there a way to categorise this, or is it just a slice [11:28] seems like we lose information during this process [11:29] Slice. See https://github.com/juju/juju/blob/develop/core/network/address.go#L215 [11:30] booo [11:31] wait, why is the sort order on the MachineAddress [11:31] ? [11:31] that's an implementation detail of the consumer, not the provider [11:32] here you could have sortOrder take a machine address https://github.com/juju/juju/blob/develop/core/network/address.go#L798-L799 [11:32] machine address should be a struct of data, not dictate how you represent it [11:33] anyway [11:33] secondary addresses if put at the end of the slice wouldn't in theory change the ordering of existing expectations? [12:49] Hey team, I am trying to add a new unit to a model which is assosciated with OpenStack cluster. But everytime I try to add the unit it throws error [12:49] cannot record provisioning info for "juju-55f8ad-9-lxd [12:49] -42": cannot set link-layer device addresses of machine "9/lxd/42": invalid address "172.16.68.239/24": DeviceName [12:49] "eth0" on machine "9/lxd/42" not found [12:51] 172.16.68.0/24 is the default subnet used (but its not associated with any space) and hence the space is 'undefined' [12:52] Can any one please help here === aluria_ is now known as aluria [16:42] achilleasa_, https://github.com/juju/bundlechanges/pull/91 [17:47] achilleasa_, this handles talking to older controllers https://github.com/juju/bundlechanges/pull/92