Hello Andreas. Thank you for looking into this SRU! To answer your questions/concerns: a) You are correct, this has already been mentioned by the landscape team as a none concern with the current architecture.
b) The vast majority of my testing was actually done using the old landscape server with 0 changes done to it! The server and the API will continue to work as expected, with the only different being that on old landscape-server deployments the extra network information will be part of the "--with-networks" API call instead of being only included in the new API call "--with-all-networks" implemented in the new landscape-server version. The changes done to landscape-server were done very late on after after getting feedback that it would be better to separate the behavior into a different API call. The patch itself was developed and tested using the old landscape-server. c1) The data returned by "--with-networks" will NOT change if the user upgrades to the new landscape-server and this was the reason for updating landscape-server. Having said so, users who remain on the old landscape-server will see that there are extra interfaces that will be returned by the "--with-networks" API call, however the format of the message is the exact same as before (even the order in which the parameters are printed), the only difference would be the values of the extra interfaces: For example, these interfaces will show their IP address, broadcast_address and netmask as 0.0.0.0 instead of a valid value. The MAC address will also be the actual MAC address of the interface since interfaces with no MAC address are ignored. For a more detailed example, Comment #26 #27 and #28 where I did the verification for focal, jammy and noble respectively shows how the response would look like for an interface that is not active, compared to the other active ones. This is also how the output will look like on the new landscape-server when using the new "--with-all-networks" call. c2) Using a new API call on an old version of landscape-server will result in an error being returned by the API client, but will not result in a crash of landscape-server. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
