Hi Andreas, Thank you for looking into this!
To answer your questions/concerns: a) These changes only apply for the API and will not result in any change for the UI. I actually also had to confirm that upstream (https://github.com/canonical/landscape-client/pull/241#issuecomment-2139980751). Also I think such an issue with the UI should be reported and fixed in a different LP bug report (in case there isn't already one) since it would be already affecting users with multiple active interfaces. b) I had though about this as well while working on this patch and I am still open to modifying it upstream and re-doing the SRU. The initial reason if I remember correctly on why I decided not to, was to avoid changing the output format of the API since it might break some user tools that were developed with this order in mind (blindly iterating over each entry in the json without checking the name). As for why I used 0.0.0.0 specifically is because of this :"A host may use 0.0.0.0 as its own source address in IP when it has not yet been assigned an address, such as when sending the initial DHCPDISCOVER packet when using DHCP."[1]. Let me know what you think and how I should proceed. Thank you again for reviewing this patch! [1] https://en.wikipedia.org/wiki/0.0.0.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052834 Title: Incomplete network info showing in both web and API :: landscape- server 23.03 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape/+bug/2052834/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
