Fix network unit for Ysul
Closed, WontfixPublic
Actions

Assigned To

Authored By

	dereckson
	Nov 10 2022, 00:43

Description

Some issues when applying roles/core/network to Ysul:

c4c5fe43 has introduced an unknown variable ipv6_gateway in ipv6.sls
IP aliases are ignored: ifconfig_igb0_alias0="212.83.187.132 netmask 255.255.255.255" should be added to /etc/rc.conf.d/netif/ipv4_igb0
/etc/rc.conf.d/routing must be created to provision /etc/rc.conf.d/routing/ipv6 and /etc/rc.conf.d/routing/managed, but /etc/rc.conf.d was a file before, not a directory
drake tunnel needs to use same IP on router-001 and Ysul, so let's pick 163.172.49.16

/etc/rc.conf.d/routing

#   -------------------------------------------------------------
#   Network — rc configuration
#   - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
#   Project:        Nasqueron
#   License:        Trivial work, not eligible to copyright
#   Source file:    roles/core/network/files/routing.rc
#   -------------------------------------------------------------
#
#   <auto-generated>
#       This file is managed by our rOPS SaltStack repository.
#
#       Changes to this file may cause incorrect behavior
#       and will be lost if the state is redeployed.
#   </auto-generated>

defaultrouter="163.172.49.1"

ipv6_defaultrouter="2001:470:1f12:9e1::1"

Related Objects

Mentioned Here: rOPSc4c5fe43bfca: Simplify network configuration

Event Timeline

dereckson triaged this task as High priority.Nov 10 2022, 00:43

dereckson created this task.

dereckson moved this task from Backlog to Bug and issues on the Salt board.

Drake tunnel is actually OK if we update Salt configuration on router-001:

$ cd /srv/salt
$ git pull
...
$ sudo salt-call --local saltutil.sync_all
...
$ sudo salt-call --local node.resolve_gre_tunnels
local:
    |_
      ----------
      description:
          drake_to_ysul
      dst:
          172.27.27.33
      icann_dst:
          212.83.187.132
      icann_src:
          51.255.124.8
      interface:
          gre0
      netmask:
          255.255.255.0
      src:
          172.27.27.252
...

During WindRiver reprovisioning, the network unit behaved correctly.

As Ysul is in decommissinong, no validation can be done there.

Marking as won't fix, as I'm not sure the IPFO scenario has been validated.

Fix network unit for YsulClosed, WontfixPublicActions

Description

Related Objects

Event Timeline

Fix network unit for Ysul
Closed, WontfixPublic
Actions