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

Bug OCPBUGS-24304: GM clock state stays locked when 1PPS lost #244

Merged
merged 1 commit into from
Dec 4, 2023

Conversation

jzding
Copy link
Contributor

@jzding jzding commented Dec 1, 2023

Fixed the following issues:
When an event is received with an iface not found in the stored in-memory data, the whole Data is re-created before adding DataDetails for this event and DataDetails for other ifaces are wiped out. As a result, there is only one iface event data is stored in-memory at any given time and the GM State calculation is only based on this one iface instead of multiple ifaces.

Another issue is the event data for dpll is stored using iface alias, while event data for gnss is stored using iface name, resulting same interface having multiple entries in in-memory data.

@openshift-ci openshift-ci bot requested review from fepan and s1061123 December 1, 2023 13:46
@jzding jzding force-pushed the demo-fix branch 2 times, most recently from 1d4ac79 to 5834c13 Compare December 1, 2023 13:55
@jzding jzding changed the title Fix event handling Bug OCPBUGS-24304: Fix event handling Dec 1, 2023
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Dec 1, 2023
@openshift-ci-robot
Copy link
Contributor

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.15.0) matches configured target version for branch (4.15.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (bblock@redhat.com), skipping review request.

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

In response to this:

Fixed the following issues:
When an event is received with an iface not found in the stored in-memory data, the whole Data is re-created before adding DataDetails for this event and DataDetails for other ifaces are wiped out. As a result, there is only one iface event data is stored in-memory at any given time and the GM State calculation is only based on this one iface instead of multiple ifaces.

Another issue is the event data for dpll is stored using iface alias, while event data for gnss is stored using iface name, resulting same interface having multiple entries in in-memory data.

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/test-infra repository.

@jzding jzding changed the title Bug OCPBUGS-24304: Fix event handling Bug OCPBUGS-24304: GM clock state stays locked when 1PPS lost Dec 1, 2023
@jzding jzding force-pushed the demo-fix branch 3 times, most recently from 518c2d4 to ba5e752 Compare December 1, 2023 17:11
Fixed the following issues:
When an event is received with an iface not found in the stored
in-memory data, the whole Data is re-created before adding DataDetails
for this event and DataDetails for other ifaces are wiped out. As a
result, there is only one iface event data is stored in-memory at any
given time and the GM State calculation is only based on this one iface
instead of multiple ifaces.

Another issue is the event data for dpll is stored using iface alias,
while event data for gnss is stored using iface name, resulting same
interface having multiple entries in in-memory data.

Signed-off-by: Jack Ding <jackding@gmail.com>
Copy link
Contributor

openshift-ci bot commented Dec 1, 2023

@jzding: 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/test-infra repository. I understand the commands that are listed here.

Copy link
Contributor

@aneeshkp aneeshkp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 4, 2023
Copy link
Contributor

openshift-ci bot commented Dec 4, 2023

[APPROVALNOTIFIER] This PR is APPROVED

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

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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 4, 2023
@openshift-merge-bot openshift-merge-bot bot merged commit 9bba8cb into openshift:master Dec 4, 2023
5 checks passed
@openshift-ci-robot
Copy link
Contributor

@jzding: Jira Issue OCPBUGS-24304: All pull requests linked via external trackers have merged:

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

In response to this:

Fixed the following issues:
When an event is received with an iface not found in the stored in-memory data, the whole Data is re-created before adding DataDetails for this event and DataDetails for other ifaces are wiped out. As a result, there is only one iface event data is stored in-memory at any given time and the GM State calculation is only based on this one iface instead of multiple ifaces.

Another issue is the event data for dpll is stored using iface alias, while event data for gnss is stored using iface name, resulting same interface having multiple entries in in-memory data.

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/test-infra repository.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-linuxptp-daemon-container-v4.15.0-202312041611.p0.g9bba8cb.assembly.stream for distgit linuxptp-daemon.
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. 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.

None yet

4 participants