OCPBUGS-77750: Auto-detect GNSS serial port by NIC

[vitus133]

Address the problem of randomly changing GNSS device names after host reboot. Use ts2phc configuration to determine the operation mode and the clock chain leading NIC. In the T-GM case, find the GNSS device by browsing the leading NIC SysFS structure. Add the discovered serial port address to ts2phc.conf.
The mechanism only works if ts2phc.nmea_serialport setting is omitted from the PTP profile. If the setting is present, it acts as before the change, leaving "Automatic" Vs. "Manual" setting decision to user.

Assisted by Cursor AI

[openshift-ci-robot]

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

• expected the bug to target either version "4.21." or "openshift-4.21.", but it targets "4.20.z" instead
• expected dependent Jira Issue OCPBUGS-77751 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead
• expected dependent Jira Issue OCPBUGS-77751 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

Details

In response to this:

Address the problem of randomly changing GNSS device names after host reboot. Use ts2phc configuration to determine the operation mode and the clock chain leading NIC. In the T-GM case, find the GNSS device by browsing the leading NIC SysFS structure. Add the discovered serial port address to ts2phc.conf.
The mechanism only works if ts2phc.nmea_serialport setting is omitted from the PTP profile. If the setting is present, it acts as before the change, leaving "Automatic" Vs. "Manual" setting decision to user.

Assisted by Cursor AI

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-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vitus133

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [vitus133]

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

[vitus133]

/jira refresh

[openshift-ci-robot]

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

• expected dependent Jira Issue OCPBUGS-77751 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead
• expected dependent Jira Issue OCPBUGS-77751 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

Details

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.

[openshift-ci]

@vitus133: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.