miniboot: fix incorrect vlan interface applied for default route
This commit fixes a but where the ip route add default is referencing
the management device name instead of the interface name (containing
vlan tag).
The issue is only seen when the OAM network is on a VLAN and
is a separate network (requires nexthop_gateway setting in
install values).
The fix is to apply the root on the vlan interface, not the top-level
network device interface.
Test Plan
PASS:
- Verify installation on system with OAM network on separate VLAN using
nexthop_gateway
- Verify installation on system with vlan but no nexthop_gateway
Reviewed: https:/ /review. opendev. org/c/starlingx /metal/ +/879068 /opendev. org/starlingx/ metal/commit/ 5bd181cdcfa7702 73112d411b412a9 645035a54c
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 5bd181cdcfa7702 73112d411b412a9 645035a54c
Author: Kyle MacLeod <email address hidden>
Date: Thu Mar 30 13:21:40 2023 -0400
miniboot: fix incorrect vlan interface applied for default route
This commit fixes a but where the ip route add default is referencing
the management device name instead of the interface name (containing
vlan tag).
The issue is only seen when the OAM network is on a VLAN and
is a separate network (requires nexthop_gateway setting in
install values).
The fix is to apply the root on the vlan interface, not the top-level
network device interface.
Test Plan gateway
PASS:
- Verify installation on system with OAM network on separate VLAN using
nexthop_
- Verify installation on system with vlan but no nexthop_gateway
Closes-Bug: 2013372 21435f23859e6d2 28e6ab95a8c
Change-Id: Ic3febbd0cb77dd
Signed-off-by: Kyle MacLeod <email address hidden>