jammy verification:
1- install landscape client on a machine that is running jammy, the proposed
version of landscape-client and has at least one interface in the DOWN state
(or with no IP address).
root@jammy-lds:~# apt list landscape-client
Listing... Done
landscape-client/jammy-proposed,now 23.02-0ubuntu1~22.04.4 amd64 [installed]
N: There are 2 additional versions. Please use the '-a' switch to see them.
root@jammy-lds:~# cat /etc/os-release | grep VERSION
VERSION_ID="22.04"
VERSION="22.04.5 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
root@jammy-lds:~# 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
36: eth0@if37: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UP group default qlen 1000
link/ether 00:16:3e:7a:c5:b2 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 10.30.157.143/24 metric 100 brd 10.30.157.255 scope global dynamic eth0
valid_lft 2395sec preferred_lft 2395sec
inet6 fe80::216:3eff:fe7a:c5b2/64 scope link
valid_lft forever preferred_lft forever
38: eth1@if39: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UP group default qlen 1000
link/ether 00:16:3e:f1:ad:c5 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 192.168.126.246/24 metric 100 brd 192.168.126.255 scope global dynamic
eth1
valid_lft 2274sec preferred_lft 2274sec
inet6 fe80::216:3eff:fef1:adc5/64 scope link
valid_lft forever preferred_lft forever
40: eth2@if41: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UP group default qlen 1000
link/ether 00:16:3e:20:78:4d brd ff:ff:ff:ff:ff:ff link-netnsid 0
In this case eth2 is the interface with no IP 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.143",
"mac_address": "00:16:3e:7a:c5:b2",
"broadcast_address": "10.30.157.255",
"netmask": "255.255.255.0",
"speed": 10000,
"duplex": true
},
{
"interface": "eth1",
"ip_address": "192.168.126.246",
"mac_address": "00:16:3e:f1:ad:c5",
"broadcast_address": "192.168.126.255",
"netmask": "255.255.255.0",
"speed": 10000,
"duplex": true
},
{
"interface": "eth2",
"ip_address": "0.0.0.0",
"mac_address": "00:16:3e:20:78:4d",
"broadcast_address": "0.0.0.0",
"netmask": "0.0.0.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 the IP address.
--
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
