Alarm displaying wrong NTP address when using IPV6
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Kristine Bujold |
Bug Description
Brief Description
-----------------
When setting NTP servers with IPv6, the alarm text doesn't display the full address.
server fd00:4888:
server fd00:4888:
The second address is not actually responding to ntp queries, so the system raises an alarm correctly. However the alarm doesn't display the full address.
fm alarm-list
-------
Alarm ID Reason Text Entity ID Severity Time Stamp
-------
100.114 NTP address fd00:4888:2000: is not a valid or a reachable NTP server. host=controller
4888:2000: .401532
100.114 NTP address fd00:4888:2000: is not a valid or a reachable NTP server. host=controller
4888:2000: .365423
-------
Severity
--------
Minor - display issue
Steps to Reproduce
------------------
- Configure NTP addresses with IPv6
- Specify one address that is not responding, so an alarm is raised
Expected Behavior
------------------
The alarm should display the full IPv6 address
Actual Behavior
----------------
The alarm doesn't display the full IPv6 address. See above.
Reproducibility
---------------
Reproducible
System Configuration
-------
Any
Branch/Pull Time/Commit
-------
Any recent stx load
Last Pass
---------
This never passed
Timestamp/Logs
--------------
Not required. Issue is easily reproducible.
Test Activity
-------------
IPv6 testing
Changed in starlingx: | |
assignee: | nobody → Kristine Bujold (kbujold) |
status: | New → In Progress |
tags: | added: stx.config |
Changed in starlingx: | |
status: | In Progress → Fix Released |
Marking as stx.3.0 - minor issue, but would improve the usability/accuracy for IPv6 configs