100.114 alarm "NTP cannot reach external time source; syncing with peer controller only " raised when other external NTP servers are available
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Gustavo Dobro |
Bug Description
Brief Description
-----------------
In DX system, create patch-strategy and apply it. After patch applied, remove the patch and delete patch-strategy successfully, 100.114 alarm "NTP cannot reach external time source; syncing with peer controller only" raised.
Severity
--------
Major
Steps to Reproduce
------------------
create patch-strategy
apply it
After patch applied, remove the patch
delete patch-strategy
check alarm-list
TC-name: functional/
Expected Behavior
------------------
no 100.114 alamr
Actual Behavior
----------------
100.114 alarm raised
Reproducibility
---------------
Reproducible
System Configuration
-------
Two node system
Lab-name: WP_13-14
Branch/Pull Time/Commit
-------
2020-07-25_00-00-00
Last Pass
---------
no known
Timestamp/Logs
--------------
[2020-07-27 03:45:25,776] 314 DEBUG MainThread ssh.send :: Send 'sw-manager --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://[abcd:204:
[2020-07-27 03:45:27,774] 314 DEBUG MainThread ssh.send :: Send 'fm --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://[abcd:204:
[2020-07-27 03:45:28,901] 436 DEBUG MainThread ssh.expect :: Output:
+------
| UUID | Alarm ID | Reason Text | Entity ID | Severity | Time Stamp |
+------
| 1329c819-
+------
[sysadmin@
+------
| Alarm ID | Reason Text | Entity ID | Severity | Time Stamp |
+------
| 100.114 | NTP cannot reach external time source; syncing with peer controller only | host=controller
+------
# Following output indicates there are 3 external ntp servers in green available; however the peer controller in yellow was selected to be the ntp server, causing above alarm to be raised.
controller-1:~$ sudo ntpq -pn
Password:
remote refid st t when poll reach delay offset jitter
=======
*abcd:204::2
+64:ff9b::4246:ac11
+64:ff9b::a29f:c87b
+64:ff9b::d8e8:844d
controller-1:~$
Test Activity
-------------
Sanity
tags: | added: stx.config |
Changed in starlingx: | |
importance: | Undecided → Medium |
status: | New → Triaged |
tags: | added: stx.5.0 |
Changed in starlingx: | |
assignee: | Les Bowness (lbowness) → Gustavo Dobro (mgdobro) |
It might be a coincidence that this alarm happened to be raised during/after a patch test.
The issue is a peer controller could be selected as NTP server, while other external NTP servers are available, causing an alarm to be raised.