Skip to content
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

Chronyd and PTP should cannot be enabled in the same node #522

Open
williamcaban opened this issue May 7, 2021 · 8 comments
Open

Chronyd and PTP should cannot be enabled in the same node #522

williamcaban opened this issue May 7, 2021 · 8 comments

Comments

@williamcaban
Copy link

williamcaban commented May 7, 2021

When using PTP Operator, it does contain the phy2sys which does time sync between PTP and the system. Having chronyd also active and doing clock sync, will be a conflict of two different processes (one with high time resolution other with regular time resolution) modifying the system clock. This affect workloads that rely on PTP and assume the system is also sync to PTP.

Remediation:

  • In the ZTP Policy generator, for the SNO DU and the RWN DU, make sure to disable chronyd systemd service on the nodes
@ijolliffe
Copy link
Contributor

@josephdrichard please have a look.

@yuvalk
Copy link
Member

yuvalk commented May 7, 2021

@williamcaban
Copy link
Author

Yes, like that and to make sure it is part of the ZTP policy generator

@vitus133
Copy link
Contributor

@serngawy
@imiller0
Could you guys please add it to the pipeline manifests? The need for patch is going to stay here for a while. As I understand it's not going to be handled by the PTP operator because there is a case where PTP benefits from NTP,

@serngawy
Copy link
Contributor

@imiller0
Copy link
Contributor

imiller0 commented May 13, 2021

Yes. This machine config CR is part of the DU profile that is applied to clusters deployed through our ZTP pipeline.

@imiller0
Copy link
Contributor

Yesterday I added a validation in the ZTP metrics pipeline which checks that the chronyd machine config (disables chronyd) is applied to the active SNO MCP.

@ijolliffe
Copy link
Contributor

Thanks all and @imiller0 for the updates - seems like we can close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants