network-get returns mac-addresses instead of being more agnostic to a L2 type

Bug #1864070 reported by Dmitrii Shcherbakov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

Currently mac addresses are returned by network-get, however this is specific to Ethernet while other L2 types could be used (infiniband has GUIDs, tun interface don't have any hardware address).

Maybe we should call it something like hardware-address which would be more generic.

juju run --unit percona-cluster/0 'network-get cluster'
bind-addresses:
- macaddress: 02:f3:f8:4e:26:ba
  interfacename: ens5
  addresses:
  - hostname: ""
    address: 172.31.10.139
    cidr: 172.31.0.0/20
  - hostname: ""
    address: 172.31.10.139
    cidr: 172.31.0.0/20
- macaddress: 36:87:3d:0c:73:9a
  interfacename: fan-252
  addresses:
  - hostname: ""
    address: 252.10.139.1
    cidr: 252.0.0.0/12
egress-subnets:
- 172.31.10.139/32
ingress-addresses:
- 172.31.10.139
- 172.31.10.139
- 252.10.139.1

Tim Penhey (thumper)
Changed in juju:
status: New → Triaged
importance: Undecided → Medium
tags: added: db-schema network network-get
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: Medium → Low
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.