Page MenuHomeDevCentral

Fix IPv4 alias not applied on Ysul
ClosedPublic

Authored by yousra on Apr 24 2026, 09:36.
Tags
None
Referenced Files
F31861156: D4095.id10758.diff
Fri, Jun 5, 00:19
Unknown Object (File)
Wed, Jun 3, 18:40
Unknown Object (File)
Wed, Jun 3, 07:09
Unknown Object (File)
Tue, Jun 2, 23:16
Unknown Object (File)
Mon, Jun 1, 06:01
Unknown Object (File)
Fri, May 29, 03:13
Unknown Object (File)
Wed, May 27, 14:06
Unknown Object (File)
Tue, May 26, 20:22

Details

Summary

Ysul has two public IPv4 addresses:

  • 163.172.49.16
  • 212.83.187.132 as an alias, which is the canonical public IPv4 address

However, we noticed that the alias was not actually applied on the server after applying roles/core/network.

The pillar nodes.sls was correct, but the Jinja syntax used to read the aliases was wrong.

The template used interface.get("ipv4.aliases", []), which looks for a key literally named ipv4.aliases.

It should instead read the aliases with:

interface.ipv4.get("aliases", [])

After this change, the alias is correctly generated in /etc/rc.conf.d/netif/ipv4_public and aplied on the server.

Ref T2315

Test Plan
  • salt 'ysul' state.apply roles/core/network
  • Restart netif and routing
  • Verify that the alias 212.83.187.132 was applied on ysul

Diff Detail

Repository
rOPS Nasqueron Operations
Lint
Lint Skipped
Unit
No Test Coverage
Branch
alias-ysul-issue
Build Status
Buildable 6671
Build 6959: arc lint + arc unit

Event Timeline

yousra requested review of this revision.Apr 24 2026, 09:36
yousra created this revision.
This revision is now accepted and ready to land.Apr 24 2026, 13:00
This revision was automatically updated to reflect the committed changes.