Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-30877

GNSS Offset between UBlox and constellations takes more than 1CPU

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • 4.15.0
    • 4.14.0, 4.14.z
    • Networking / ptp
    • None
    • No
    • CNF RAN Sprint 250, CNF RAN Sprint 251, CNF Ran Sprint 252
    • 3
    • False
    • Hide

      None

      Show
      None
    • Hide
      3/14: Backport to 4.15
      2/29: PR under review
      2/22: development and testing in progress for updated changes - forecast next week for PR
      Show
      3/14: Backport to 4.15 2/29: PR under review 2/22: development and testing in progress for updated changes - forecast next week for PR

      This is a clone of issue OCPBUGS-17422. The following is the description of the original issue:
      —
      Description of problem:

      GNSS offset is required  along wth DPLL and ts2phc offsets to report the GM state as Locked . Current implmentation of reading GNSS offset via ublox tool client call takes more than 1CPU .In fact any call via ublox tool takes more than 1CPU. OCP 4.14 has now dropped any calls to ublox and uses direct GSPD calls to read the gps fix status. This only solves one problem of getting GPS status without ublox call  , But offset reading still needs Ublox cli execution via deaemon, hence the  reporting of offset is not implmented in 4.14 for now.

      Version-Release number of selected component (if applicable):

       

      How reproducible:

       

      Steps to Reproduce:

      1.
2.
3.

      Actual results:

       

      Expected results:

       

      Additional info:

       

              josricha@redhat.com Joseph Richard
              openshift-crt-jira-prow OpenShift Prow Bot
              Hen Shay Hassid Hen Shay Hassid
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: