Noble verification:
1- install landscape client on a machine that is running Noble, the proposed
version of landscape-client and has at least one interface in the DOWN state
(or with no IP address).
root@build-noble:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
30: eth0@if31: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UP group default qlen 1000
link/ether 00:16:3e:49:cc:65 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 10.30.157.234/24 metric 100 brd 10.30.157.255 scope global dynamic eth0
valid_lft 3262sec preferred_lft 3262sec
inet6 fe80::216:3eff:fe49:cc65/64 scope link
valid_lft forever preferred_lft forever
32: eth2@if33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UP group default qlen 1000
link/ether 00:16:3e:6a:d5:70 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::216:3eff:fe6a:d570/64 scope link
valid_lft forever preferred_lft forever
34: eth6@if35: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UP group default qlen 1000
link/ether 00:16:3e:24:90:15 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 192.168.126.134/24 metric 100 brd 192.168.126.255 scope global dynamic
eth6
valid_lft 3265sec preferred_lft 3265sec
inet6 fe80::216:3eff:fe24:9015/64 scope link
valid_lft forever preferred_lft forever
root@build-noble:~# apt list landscape-client
Listing... Done
landscape-client/noble-proposed,now 24.02-0ubuntu5.2 amd64 [installed]
N: There are 2 additional versions. Please use the '-a' switch to see them.
root@build-noble:~# cat /etc/os-release | grep VERSION
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
In this case eth2 is an interface with no IP address, but a valid MAC
address.
2- Running landscape-api get-computers --with-network --json we get the
following output section for the network devices of the machine I am testing on
(full output truncated for readability):
...
"network_devices": [
{
"interface": "eth0",
"ip_address": "10.30.157.234",
"mac_address": "00:16:3e:49:cc:65",
"broadcast_address": "10.30.157.255",
"netmask": "255.255.255.0",
"speed": 10000,
"duplex": true
},
{
"interface": "eth2",
"ip_address": "0.0.0.0",
"mac_address": "00:16:3e:6a:d5:70",
"broadcast_address": "0.0.0.0",
"netmask": "0.0.0.0",
"speed": 10000,
"duplex": true
},
{
"interface": "eth6",
"ip_address": "192.168.126.134",
"mac_address": "00:16:3e:24:90:15",
"broadcast_address": "192.168.126.255",
"netmask": "255.255.255.0",
"speed": 10000,
"duplex": true
}
]
...
As we can see all three interface show up including eth2 with the correct
placeholders used for an interface with no IP address.
** Tags removed: verification-needed-focal verification-needed-jammy
verification-needed-noble
** Tags added: verification-done-focal verification-done-jammy
verification-done-noble
--
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
