-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.16
-
Important
-
None
-
CNF RAN Sprint 264, CNF RAN Sprint 265
-
2
-
False
-
-
N/A
-
Release Note Not Required
-
Done
-
1/9: SLCM to verify the workaround, currently having issues with their test server
-
Description of problem:
4.16 ptp events SDK backward comparability issue:
Any ptp event v1 user app using the original ptp event SDK will not work with the 4.16 ptp operator after ptp faster event v2 backported even with V1 configuration.
The problem will happen during updates from 4.16.Z release with v1 only to 4.16.Z release with v1 and v2. The root cause is the original SDK for V1 is not comparable after ptp event v2 backport from 4.18 to 4.16
Version-Release number of selected component (if applicable):
How reproducible:
Ptp event v1 user app using the original ptp event SDK and try to communicate with the 4.16 ptp operator after ptp faster event v2 backported even with V1 configuration.
Steps to Reproduce:
1. Run a 4.16 ptp operator (has ptp event v2 backport) with ptp event V1 configuration 2. Deploy a ptp event user app usingoriginal ptp event SDK 3. Validate the communication between the user app and ptp operator.
Actual results:
SLCM user app observed unmarshall error during api getCurrentState.
Expected results:
No error
Additional info:
- links to
-
RHBA-2025:1124 OpenShift Container Platform 4.16.z bug fix update