[mgmt-vrf]: Fix mgmt VRF configuration failure by rminnikanti · Pull Request #25332 · sonic-net/sonic-buildimage

rminnikanti · 2026-02-03T18:39:01Z

Why I did it

Adding mgmt vrf is failing on latest 202511 images after trixie update. Older versions of iproute2 package on bookworm (6.1.0-3) has /etc/iproute2/rt_tables.d directory because of which ifupdown2_vrf_map.conf generated by ifupdown2 in this directory always succeeded.

New version of iproute2 (6.15.0-1) in trixie doesn't have /etc/iproute2 directory, because of which vrf map conf generation failing, in-turn resulting in mgmt VRF creation failure.

Work item tracking

Microsoft ADO (number only):

How I did it

Fix is to ensure /etc/iproute2/rt_tables.d directory present before generating ifupdown2_vrf_map.conf in ifupdown2 vrf addon.

How to verify it

Create mgmt VRF and observe the failure without the fix.

sudo config vrf add mgmt

show mgmt-vrf

ManagementVRF : Enabled

Management VRF interfaces in Linux:
Device "mgmt" does not exist.

Which release branch to backport (provide reason below if selected)

Tested branch (Please provide the tested image version)

202511

Description for the changelog

Fixed mgmt VRF addition failure after trixie upgrade

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

Older versions of iproute2 package created /etc/iproute2/rt_tables.d directory because of which ifupdown2_vrf_map.conf generation succeeded. New version of iproute2 (6.15.0-1) in trixie doesn't create /etc/iproute2, because of this vrf map conf generation failing, inturn resulting in mgmt VRF creation failure Fix is to ensure /etc/iproute2/rt_tables.d directory present before generating ifupdown2_vrf_map.conf Signed-off-by: Ravi Minnikanti <rminnikanti@marvell.com>

mssonicbld · 2026-02-03T18:39:10Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-03T18:39:23Z

Azure Pipelines successfully started running 1 pipeline(s).

vivekrnv · 2026-02-03T19:45:59Z

@rminnikanti, Is this an upstream commit? If not, it is worth upstreaming it to ifupdown2 IMO

mssonicbld · 2026-02-04T06:07:10Z

/azp run Azure.sonic-buildimage

rminnikanti · 2026-02-04T06:08:19Z

@rminnikanti, Is this an upstream commit? If not, it is worth upstreaming it to ifupdown2 IMO

@vivekrnv, thanks for the review. I see that this change is not present in upstream. Sure, I will upstream it.

azure-pipelines · 2026-02-04T06:09:31Z

Azure Pipelines successfully started running 1 pipeline(s).

rminnikanti · 2026-02-04T10:17:31Z

@rminnikanti, Is this an upstream commit? If not, it is worth upstreaming it to ifupdown2 IMO

@vivekrnv, thanks for the review. I see that this change is not present in upstream. Sure, I will upstream it.

Created:
CumulusNetworks/ifupdown2#348

mssonicbld · 2026-02-05T06:12:18Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-05T06:12:31Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-02-07T12:48:14Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-07T12:48:26Z

Azure Pipelines successfully started running 1 pipeline(s).

vivekrnv · 2026-02-10T19:07:36Z

@rminnikanti , Please re-trigger the CI

mssonicbld · 2026-02-10T19:48:34Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-10T19:48:46Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-02-12T17:23:50Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-12T17:24:08Z

Azure Pipelines successfully started running 1 pipeline(s).

rminnikanti · 2026-02-14T04:22:12Z

@saiarcot895 can this be merged?

ronan-nexthop · 2026-02-17T03:11:16Z

Can a user with write-permission please approve this

mssonicbld · 2026-02-19T01:02:58Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-19T01:03:10Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-02-19T11:30:26Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-19T11:30:37Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-02-23T09:09:31Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-23T09:09:43Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-02-24T01:17:56Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-24T01:18:06Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-02-26T04:54:22Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-26T04:54:33Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-02-27T00:35:27Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-27T00:35:38Z

Azure Pipelines successfully started running 1 pipeline(s).

Older versions of iproute2 package created /etc/iproute2/rt_tables.d directory because of which ifupdown2_vrf_map.conf generation succeeded. New version of iproute2 (6.15.0-1) in trixie doesn't create /etc/iproute2, because of this vrf map conf generation failing, inturn resulting in mgmt VRF creation failure Fix is to ensure /etc/iproute2/rt_tables.d directory present before generating ifupdown2_vrf_map.conf Signed-off-by: Ravi Minnikanti <rminnikanti@marvell.com> Co-authored-by: Lihua Yuan <lihuay@users.noreply.github.com> Signed-off-by: Feng Pan <fenpan@microsoft.com>

mssonicbld · 2026-03-09T18:14:23Z

Cherry-pick PR to 202511: #25978

Older versions of iproute2 package created /etc/iproute2/rt_tables.d directory because of which ifupdown2_vrf_map.conf generation succeeded. New version of iproute2 (6.15.0-1) in trixie doesn't create /etc/iproute2, because of this vrf map conf generation failing, inturn resulting in mgmt VRF creation failure Fix is to ensure /etc/iproute2/rt_tables.d directory present before generating ifupdown2_vrf_map.conf Signed-off-by: Ravi Minnikanti <rminnikanti@marvell.com> Co-authored-by: Lihua Yuan <lihuay@users.noreply.github.com>

vivekrnv added the Trixie label Feb 3, 2026

vivekrnv approved these changes Feb 3, 2026

View reviewed changes

vivekrnv requested a review from saiarcot895 February 3, 2026 19:42

vivekrnv added the Request for 202511 Branch label Feb 3, 2026

Merge branch 'master' into fix_vrf

386787e

saiarcot895 approved these changes Feb 4, 2026

View reviewed changes

Merge branch 'master' into fix_vrf

2a51fc8

Merge branch 'master' into fix_vrf

5915df3

Merge branch 'master' into fix_vrf

6104f0e

Merge branch 'master' into fix_vrf

b2d784c

Merge branch 'master' into fix_vrf

b712392

Merge branch 'master' into fix_vrf

f1fa72f

Merge branch 'master' into fix_vrf

d80e235

Merge branch 'master' into fix_vrf

e2f6d16

Merge branch 'master' into fix_vrf

a3de978

Merge branch 'master' into fix_vrf

961115d

lihuay approved these changes Feb 27, 2026

View reviewed changes

lihuay merged commit 359fea4 into sonic-net:master Feb 27, 2026
7 of 15 checks passed

vmittal-msft added the Approved for 202511 Branch label Mar 9, 2026

mssonicbld mentioned this pull request Mar 9, 2026

[action] [PR:25332] [mgmt-vrf]: Fix mgmt VRF configuration failure #25978

Merged

7 tasks

mssonicbld added the Created PR to 202511 Branch label Mar 9, 2026

PriyanshTratiya added the Included in 202511 Branch label Mar 13, 2026

Conversation

rminnikanti commented Feb 3, 2026

Why I did it

Work item tracking

How I did it

How to verify it

Which release branch to backport (provide reason below if selected)

Tested branch (Please provide the tested image version)

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

Uh oh!

mssonicbld commented Feb 3, 2026

Uh oh!

azure-pipelines Bot commented Feb 3, 2026

Uh oh!

vivekrnv commented Feb 3, 2026

Uh oh!

mssonicbld commented Feb 4, 2026

Uh oh!

rminnikanti commented Feb 4, 2026

Uh oh!

azure-pipelines Bot commented Feb 4, 2026

Uh oh!

rminnikanti commented Feb 4, 2026

Uh oh!

mssonicbld commented Feb 5, 2026

Uh oh!

azure-pipelines Bot commented Feb 5, 2026

Uh oh!

mssonicbld commented Feb 7, 2026

Uh oh!

azure-pipelines Bot commented Feb 7, 2026

Uh oh!

vivekrnv commented Feb 10, 2026

Uh oh!

mssonicbld commented Feb 10, 2026

Uh oh!

azure-pipelines Bot commented Feb 10, 2026

Uh oh!

mssonicbld commented Feb 12, 2026

Uh oh!

azure-pipelines Bot commented Feb 12, 2026

Uh oh!

rminnikanti commented Feb 14, 2026

Uh oh!

ronan-nexthop commented Feb 17, 2026

Uh oh!

mssonicbld commented Feb 19, 2026

Uh oh!

azure-pipelines Bot commented Feb 19, 2026

Uh oh!

mssonicbld commented Feb 19, 2026

Uh oh!

azure-pipelines Bot commented Feb 19, 2026

Uh oh!

mssonicbld commented Feb 23, 2026

Uh oh!

azure-pipelines Bot commented Feb 23, 2026

Uh oh!

mssonicbld commented Feb 24, 2026

Uh oh!

azure-pipelines Bot commented Feb 24, 2026

Uh oh!

mssonicbld commented Feb 26, 2026

Uh oh!

azure-pipelines Bot commented Feb 26, 2026

Uh oh!

mssonicbld commented Feb 27, 2026

Uh oh!

azure-pipelines Bot commented Feb 27, 2026

Uh oh!

Uh oh!

mssonicbld commented Mar 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone