Networks of type physical managed do not expose state about lxd HOT 2 OPEN

Whilst I agree this is a bug, I am not entirely sure what we should return here for this endpoint.

The problem is that for physical networks, the parent interface can disappear from the host if used by an physical NIC, and so most of the info will not be retrievable, or worse only retrievable when the instance isn't running (and the parent interface has been released back to the host).

But when the physical parent is being used as an OVN uplink it might be quite useful to see the counters of data flowing through it.

@edlerd would it be acceptable to sometimes return 404 on this endpoint if the parent interface is missing, either because its not been configured on the host or if its passed into a running instance?

from lxd.

@edlerd would it be acceptable to sometimes return 404 on this endpoint if the parent interface is missing, either because its not been configured on the host or if its passed into a running instance?

Yes, we can sometimes have a 404. Can we improve the error message?

Motivation: Reading your explanation, I understand in the OVN case, we want to display the state info for physical managed networks. The UI will show the error message in the other case. But the current error message doesn't make clear, as your explanation above does. I think it is misleading:

I think it is the same issue on the command line:

root@latest-edge:~# lxc network info abc
Error: Network interface "abc" not found

where abc exists:

root@latest-edge:~# lxc network show abc
name: abc
description: ""
type: physical
managed: true
status: Created
config:
  parent: eth0
  volatile.last_state.created: "false"
used_by: []
locations:
- none

from lxd.