> 7- Prior to this patch, the interfaces in the down state or with no IP
> addresses will not show up in the
> API response. However after this patch these interfaces will show up with an
> IP address, broadcast
> address and netmask of 0.0.0.0.
I have some questions about this change.
a) Won't this potentially pollute and overcrowd the landscape server
monitoring page? I vaguely remember cases where landscape-client was
installed on a system with multiple network interfaces and vlans (I
think it was an openstack neutron gateway), and the monitoring page
would just be HUGE, with empty graphs because some interfaces didn't
have an IP. [citation needed] Or is this change only affecting the API
call and its results?
b) Wouldn't it be better to, instead of faking the IP layer with
0.0.0.0, to have an indication that the interface is down, and have that
available in the API as a filter perhaps? This would have to be done in
a backwards compatible way, of course.
** Changed in: landscape-client (Ubuntu Noble)
Status: In Progress => Incomplete
** Changed in: landscape-client (Ubuntu Jammy)
Status: In Progress => Incomplete
** Changed in: landscape-client (Ubuntu Focal)
Status: In Progress => Incomplete
--
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
