[action] [PR:18841] Fix ntp synchronization issue for test_ntp

[mssonicbld]

Description of PR

The test initiates an NTP server on PTF, which has a pool of 4 network NTP servers and sets the local clock as the preferred option. However, the local server's clock (crystal oscillator) has poor accuracy, causing the PTF's NTP server to dynamically switch to other network NTP servers in the pool. As a result, when DUT uses the PTF NTP server as the clock, synchronization becomes difficult. To resolve the issue, remove the network NTP configuration from the pool.

Summary:
Fixes # (issue)

Type of change

• Bug fix
• Testbed and Framework(new/improvement)
• New Test case
• Skipped for non-supported platforms
• Test case improvement

Back port request

• 202205
• 202305
• 202311
• 202405
• 202411
• 202505

Approach

What is the motivation for this PR?

Fix ntp synchronization issue for test_ntp

How did you do it?

Just keep one ntp clock for the ptf ntp server

How did you verify/test it?

Run test_ntp.py

Any platform specific information?

Any

Supported testbed topology if it's a new test case?

Documentation

[mssonicbld]

Original PR: #18841

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wsycqyz]

Re-trigger the PR test

[yejianquan]

/azp run

[azure-pipelines]

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

[yejianquan]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[yejianquan]

Hi @JibinBao , could you check the test failure of cherry-picking to 202505 branch?

[JibinBao]

Hi @JibinBao , could you check the test failure of cherry-picking to 202505 branch?

I have seen the same error on other PRs. It looks like not related to my fix.
Let's re-run the checker.

[JibinBao]

/azpw run Azure.sonic-mgmt

[mssonicbld]

/AzurePipelines run Azure.sonic-mgmt

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[yejianquan]

Hi @JibinBao , could you check the test failure of cherry-picking to 202505 branch?

I have seen the same error on other PRs. It looks like not related to my fix. Let's re-run the checker.

Hi @JibinBao , multi-asic failures we can ignore, but on t0 and t1-lag, the ntp test is failing

[JibinBao]

hi @yejianquan ,
From the logs, I cannot see what is the root cause.However, it passed the checker on master branch, I am not sure whether it is the environmental issue. What is the difference for ntp server between master and 202505 branch?
Or let try re-run it multi times. Usually if it is a environmental issue, re-running it many times can pass the checker.

[JibinBao]

/azpw run Azure.sonic-mgmt

[mssonicbld]

/AzurePipelines run Azure.sonic-mgmt

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Verma-Anukul]

@JibinBao

Any update here

[yejianquan]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[yejianquan]

has been included in #19948