MAAS

  1. Bug #1817484
  2. Comment #21

Comment 21 for bug 1817484

Revision history for this message
Alexander Litvinov (alitvinov) wrote :

Tested in identical scenario as #19 (maas 2.5.1 with patches)

Out of 4 times - 3 times failover worked fine.
In the last case on of the regions didn't have their API sockets present
Here is the regiond log from the node where that happened (unfortunately is not debug=true enabled)

http://paste.ubuntu.com/p/QncM3Ybkxc/

root@maas-rack3:/var/lib/heartbeat/trace_ra/dns# pgrep -af regiond
997 /bin/sh -c exec /usr/sbin/regiond 2>&1 | tee -a $LOGFILE
1003 /usr/bin/python3 /usr/sbin/regiond
1004 tee -a /var/log/maas/regiond.log
1775 /usr/bin/python3 /usr/sbin/regiond
1783 /usr/bin/python3 /usr/sbin/regiond
1784 /usr/bin/python3 /usr/sbin/regiond
1788 /usr/bin/python3 /usr/sbin/regiond

root@maas-rack3:/var/lib/heartbeat/trace_ra/dns# ss -tulpan 'sport = 5240'
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port
udp UNCONN 0 0 *:5240 *:* users:(("rackd",pid=1066,fd=20))