NTP 100.14 alarm is not cleared
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Eric MacDonald |
Bug Description
Brief Description
-----------------
alarm 100.114 popped up during regression test suite run and it had not been cleared.
Severity
--------
Major
Steps to Reproduce
------------------
Expected Behaviour
------------------
All unexpected alarm should be cleared
Actual Behaviour
----------------
100.114 alarm not cleared
Reproducibility
---------------
Reproducible
rate: unknown
System Configuration
-------
Two node system
Low latency
Branch/Pull Time/Commit
-------
master as of as of 2019-01-15_20-18-00
Timestamp/Logs
--------------
[2019-01-17 12:16:19,350] 262 DEBUG MainThread ssh.send :: Send 'sudo ntpq -pn'
[2019-01-17 12:16:19,476] 387 DEBUG MainThread ssh.expect :: Output:
remote refid st t when poll reach delay offset jitter
=======
+192.168.204.4 144.217.65.183 3 u 12 64 377 0.111 1.903 0.156
+54.39.20.247 213.251.128.249 2 u 48 128 377 14.397 -0.533 0.201
*206.108.0.131 .PPS. 1 u 114 128 377 7.141 0.371 0.312
+149.56.121.16 213.251.128.249 2 u 51 128 377 14.227 -0.095 0.220
controller-0:~$
[2019-01-17 12:16:19,476] 262 DEBUG MainThread ssh.send :: Send 'echo $?'
[2019-01-17 12:16:19,580] 387 DEBUG MainThread ssh.expect :: Output:
0
controller-0:~$
[2019-01-17 12:16:19,580] 4006 INFO MainThread host_helper.
[2019-01-17 12:16:49,593] 423 DEBUG MainThread ssh.exec_cmd:: Executing command...
[2019-01-17 12:16:49,594] 262 DEBUG MainThread ssh.send :: Send 'fm --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://
[2019-01-17 12:16:51,152] 387 DEBUG MainThread ssh.expect :: Output:
+------
| UUID | Alarm ID | Reason Text | Entity ID | Severity | Time Stamp |
+------
| 92156e60-
+------
controller-0:~$
controller-1:~$ sudo ntpq -pn
Password:
remote refid st t when poll reach delay offset jitter
=======
+192.168.204.3 206.108.0.131 2 u 843 1024 333 0.077 -0.914 0.494
*144.217.65.183 152.2.133.52 2 u 827 1024 377 14.563 1.353 0.404
+144.217.181.221 5.56.147.93 2 u 825 1024 377 14.530 -0.798 1.446
+159.203.8.72 192.5.41.209 2 u 288 1024 377 7.659 -2.216 2.103
controller-1:~$
Changed in starlingx: | |
assignee: | nobody → Eric MacDonald (rocksolidmtce) |
importance: | Undecided → Medium |
tags: | added: stx.2019.05 stx.metal |
tags: |
added: stx.2.0 removed: stx.2019.05 |
Reviewed: https:/ /review. openstack. org/631888 /git.openstack. org/cgit/ openstack/ stx-integ/ commit/ ?id=abaff6b2752 5aaa91df53319f8 4004640f75e6a3
Committed: https:/
Submitter: Zuul
Branch: master
commit abaff6b27525aaa 91df53319f84004 640f75e6a3
Author: Eric MacDonald <email address hidden>
Date: Fri Jan 18 16:29:56 2019 -0500
Remove alarm query before clear in NTP plugin
Issue titled 'NTP 100.14 alarm is not cleared' exposed
an issue where the NTP plugin alarm clear operation is
circumvented when its pre-curser fm_api.get_fault call
returns None if the fm process is not running.
From the callers point of view the None return suggests
that the alarm to be cleared does not exist so the code
skips the call to clear.
This update works around this by simply issuing the
clear without the query.
Change-Id: Idcc05bb0e7e1aa 1082af1e8ecdcb1 a5463b19440
Closes-Bug: 1812440
Signed-off-by: Eric MacDonald <email address hidden>