Comment 5 for bug 1851043

I have tested a host-swact and it looks like after a swact the ntpq looses its reachability statuses.

Controller-0:
     remote refid st t when poll reach delay offset jitter
==============================================================================
+face::3
                 107.242.40.132 3 u 588 1024 377 0.089 1.210 0.265
+64:ff9b::3627:1740
                 192.99.2.172 3 u 409 1024 377 15.674 -0.118 0.758
*64:ff9b::c063:2ac
                 213.251.128.249 2 u 795 1024 377 15.055 0.259 1.224
+64:ff9b::a29f:c801
                 10.14.8.68 3 u 657 1024 377 18.819 0.097 0.937

After the swact

     remote refid st t when poll reach delay offset jitter
==============================================================================
 face::3
                 127.0.0.1 12 u 586 1024 7 0.065 1.160 0.034
 64:ff9b::3627:1740
                 192.99.2.172 3 u 611 1024 7 14.417 0.016 0.439
 64:ff9b::c063:2ac
                 213.251.128.249 2 u 677 1024 3 15.656 0.239 0.070
 64:ff9b::a29f:c801
                 10.14.8.68 3 u 613 1024 7 18.327 0.247 0.351

Controller-1:

     remote refid st t when poll reach delay offset jitter
==============================================================================
+face::2
                 143.161.167.89 3 u 428 1024 377 0.104 -1.132 0.255
+64:ff9b::cdce:4607
                 206.108.0.131 2 u 342 1024 377 43.230 -0.699 0.425
*64:ff9b::23b7:39a9
                 206.108.0.131 2 u 483 1024 377 10.450 1.795 0.385
+64:ff9b::9538:2f3c
                 206.108.0.132 2 u 123 1024 377 14.716 1.211 0.879

After swact

     remote refid st t when poll reach delay offset jitter
==============================================================================
 face::2
                 127.0.0.1 12 u 27 64 1 0.154 -1.134 0.000
 64:ff9b::cdce:4607
                 206.108.0.131 2 u 27 64 1 43.220 -0.894 0.000
 64:ff9b::23b7:39a9
                 206.108.0.131 2 u 29 64 1 10.626 1.972 0.000
 64:ff9b::9538:2f3c
                 206.108.0.132 2 u 29 64 1 15.316 0.934 0.000

from daemon.log on controller-1

2019-11-20T17:42:58.000 controller-0 ntpd[100062]: info Deleting interface #16 eno1, 2620:10a:a001:a103::1218#123, interface stats: received=422, sent=422, dropped=0, active_time=71038 secs
2019-11-20T17:42:58.000 controller-0 ntpd[100062]: info 64:ff9b::a29f:c801 interface 2620:10a:a001:a103::1218 -> (none)
2019-11-20T17:42:58.000 controller-0 ntpd[100062]: info 64:ff9b::c063:2ac interface 2620:10a:a001:a103::1218 -> (none)
2019-11-20T17:42:58.000 controller-0 ntpd[100062]: info 64:ff9b::3627:1740 interface 2620:10a:a001:a103::1218 -> (none)
2019-11-20T17:42:58.000 controller-0 ntpd[100062]: info Deleting interface #14 vlan116, feed:beef::1#123, interface stats: received=0, sent=0, dropped=0, active_time=71038 secs
2019-11-20T17:42:58.000 controller-0 ntpd[100062]: info Deleting interface #4 ens801f0, 192.168.202.1#123, interface stats: received=0, sent=0, dropped=0, active_time=71038 secs
2019-11-20T17:43:06.000 controller-0 ntpd[100062]: info Deleting interface #17 vlan115, face::4#123, interface stats: received=105, sent=115, dropped=0, active_time=70977 secs
2019-11-20T17:43:06.000 controller-0 ntpd[100062]: info face::3 interface face::4 -> (none)
2019-11-20T17:43:08.000 controller-0 ntpd[100062]: info 0.0.0.0 0618 08 no_sys_peer
2019-11-20T17:43:20.000 controller-0 ntpd[100062]: info Deleting interface #12 vlan115, face::1#123, interface stats: received=1, sent=3, dropped=0, active_time=71060 secs
2019-11-20T17:43:20.000 controller-0 ntpd[100062]: info face::3 interface face::1 -> (none)