-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The NTP_SERVER configuration generated from the minigraph doesn't meet the new schema requirements. #17906
Labels
Triaged
this issue has been triaged
Comments
@fastiuk , please help fix this as the PR you raised seems to be the root cause of this issue. |
@fastiuk , I would say as soon as possible as this is a regression and impacting the community. |
This issue is present on both master and 202311 branch. |
Due date is Apr 12 |
WIP on that issue. Any way to move it to the "In progress" state, or there is no such thing on GitHub? |
12 tasks
qiluo-msft
pushed a commit
that referenced
this issue
May 15, 2024
fixes #17906 #### Why I did it To fix NTP config generation from the minigraph and save backward compatability #### How I did it Align `ntp.conf.j2` template to generate config out of empty `NTP_SERVER` DB configuration #### How to verify it Out of that NTP_SERVER configuration: ```json { "10.210.25.32": {}, "10.75.202.2": {} } ``` The next config in `ntp.conf` file should be produced: ``` server 10.210.25.32 restrict 10.210.25.32 kod limited nomodify notrap noquery nopeer server 10.75.202.2 restrict 10.75.202.2 kod limited nomodify notrap noquery nopeer ```
fastiuk
added a commit
to fastiuk/sonic-buildimage
that referenced
this issue
May 16, 2024
fixes sonic-net#17906 #### Why I did it To fix NTP config generation from the minigraph and save backward compatability #### How I did it Align `ntp.conf.j2` template to generate config out of empty `NTP_SERVER` DB configuration #### How to verify it Out of that NTP_SERVER configuration: ```json { "10.210.25.32": {}, "10.75.202.2": {} } ``` The next config in `ntp.conf` file should be produced: ``` server 10.210.25.32 restrict 10.210.25.32 kod limited nomodify notrap noquery nopeer server 10.75.202.2 restrict 10.75.202.2 kod limited nomodify notrap noquery nopeer ```
12 tasks
fastiuk
added a commit
to fastiuk/sonic-buildimage
that referenced
this issue
May 16, 2024
fixes sonic-net#17906 To fix NTP config generation from the minigraph and save backward compatability Align `ntp.conf.j2` template to generate config out of empty `NTP_SERVER` DB configuration Out of that NTP_SERVER configuration: ```json { "10.210.25.32": {}, "10.75.202.2": {} } ``` The next config in `ntp.conf` file should be produced: ``` server 10.210.25.32 restrict 10.210.25.32 kod limited nomodify notrap noquery nopeer server 10.75.202.2 restrict 10.75.202.2 kod limited nomodify notrap noquery nopeer ``` Signed-off-by: Yevhen Fastiuk <[email protected]>
yxieca
pushed a commit
that referenced
this issue
May 28, 2024
fixes #17906 To fix NTP config generation from the minigraph and save backward compatability Align `ntp.conf.j2` template to generate config out of empty `NTP_SERVER` DB configuration Out of that NTP_SERVER configuration: ```json { "10.210.25.32": {}, "10.75.202.2": {} } ``` The next config in `ntp.conf` file should be produced: ``` server 10.210.25.32 restrict 10.210.25.32 kod limited nomodify notrap noquery nopeer server 10.75.202.2 restrict 10.75.202.2 kod limited nomodify notrap noquery nopeer ``` Signed-off-by: Yevhen Fastiuk <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The
NTP_SERVER
configuration generated from the minigraph doesn't meet the new schema requirements.The issue is caused by the changes introduced in [NTP] Add NTP extended configuration PR. The PR updates the config DB schema and makes the NTP configuration generated from the minigraph incompatible.
Steps to reproduce the issue:
Describe the results you received:
The utility generates the NTP_SERVER configuration in the following format:
As a result, the NTP feature ignores this configuration, and the time synchronization doesn't work:
Describe the results you expected:
The NTP feature implementation expects to have an extended configuration in the format like this:
The YANG model for the configuration is defined here sonic-ntp.yang
Output of
show version
:Output of
show techsupport
:Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: