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

OCPBUGS-45308: PTP holdover time should be kept for 4 hours #379

Merged

Conversation

aneeshkp
Copy link
Contributor

@aneeshkp aneeshkp commented Dec 10, 2024

Enhancements to Logging and Clock Class Announcements for T-GM State Management

This PR introduces structured logging that includes the state tree, providing users with detailed insights into the relationships between all components involved in the Time Grandmaster (T-GM) state decision process. By exposing state transitions and dependencies, this enhancement simplifies troubleshooting and improves the overall observability of T-GM behavior.

Additionally, this PR removes the use of ClockClass 140 (OutOfSpec) and implements the following improvements:

  • Announces ClockClass 6 during the LOCKED state.
  • Announces ClockClass 7 during the HOLDOVER state until one of the following conditions is met:
    • The holdover duration times out.
    • The inSpecOffset threshold is reached.

These changes enhance state accuracy and ensure consistent clock class announcements.

@openshift-ci openshift-ci bot requested review from dougbtv and SchSeba December 10, 2024 14:55
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 10, 2024
This commit disables SA and SV messages to reduce unnecessare computing
load on ts2phc. The amount of these two messages can increase
uncontrollably with the number of visible satellites, and they don't
provide any useful information for the timing solution.

Signed-off-by: Vitaly Grinberg <[email protected]>
This commit reduces the number of NMEA messages going to the log and
through the `ts2phc` to the essential two message types: GNRMC and
GNGGA.

Signed-off-by: Vitaly Grinberg <[email protected]>
@aneeshkp aneeshkp force-pushed the case-fix-clockclass branch from f4897e2 to 8b016a1 Compare December 11, 2024 16:40
Signed-off-by: Aneesh Puttur <[email protected]>
@aneeshkp aneeshkp force-pushed the case-fix-clockclass branch from 8b016a1 to d1bf196 Compare December 11, 2024 16:49
Copy link
Contributor

openshift-ci bot commented Dec 11, 2024

@aneeshkp: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@aneeshkp aneeshkp changed the title Add debug tree for states and minor fixes OCPBUGS-45308: PTP holdover time should be kept for 4 hours Dec 12, 2024
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Dec 12, 2024
@openshift-ci-robot
Copy link
Contributor

@aneeshkp: This pull request references Jira Issue OCPBUGS-45308, which is invalid:

  • expected the bug to target the "4.14.z" version, but no target version was set
  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-45308 to depend on a bug targeting a version in 4.15.0, 4.15.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This PR introduces structured logging to include the state tree, enabling users to better understand the relationships between all components involved in the T-GM state decision process. By providing detailed insights into state transitions and dependencies, this enhancement aims to simplify troubleshooting .

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@vitus133
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@vitus133: This pull request references Jira Issue OCPBUGS-45308, which is invalid:

  • expected the bug to target the "4.14.z" version, but no target version was set
  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@vitus133
Copy link
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Dec 24, 2024
@openshift-ci-robot
Copy link
Contributor

@vitus133: This pull request references Jira Issue OCPBUGS-45308, which is valid. The bug has been moved to the POST state.

9 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-47520 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent bug Jira Issue OCPBUGS-47520 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-47520 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
  • dependent Jira Issue OCPBUGS-47520 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@vitus133
Copy link
Contributor

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Dec 24, 2024
@hhassid
Copy link

hhassid commented Dec 24, 2024

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Dec 24, 2024
@vitus133
Copy link
Contributor

vitus133 commented Jan 2, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 2, 2025
Copy link
Contributor

openshift-ci bot commented Jan 2, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aneeshkp, vitus133

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 0982992 into openshift:release-4.14 Jan 2, 2025
6 checks passed
@openshift-ci-robot
Copy link
Contributor

@aneeshkp: Jira Issue OCPBUGS-45308: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-45308 has been moved to the MODIFIED state.

In response to this:

Enhancements to Logging and Clock Class Announcements for T-GM State Management

This PR introduces structured logging that includes the state tree, providing users with detailed insights into the relationships between all components involved in the Time Grandmaster (T-GM) state decision process. By exposing state transitions and dependencies, this enhancement simplifies troubleshooting and improves the overall observability of T-GM behavior.

Additionally, this PR removes the use of ClockClass 140 (OutOfSpec) and implements the following improvements:

  • Announces ClockClass 6 during the LOCKED state.
  • Announces ClockClass 7 during the HOLDOVER state until one of the following conditions is met:
  • The holdover duration times out.
  • The inSpecOffset threshold is reached.

These changes enhance state accuracy and ensure consistent clock class announcements.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: linuxptp-daemon
This PR has been included in build ose-linuxptp-daemon-container-v4.14.0-202501021036.p0.g0982992.assembly.stream.el9.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.