-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.20
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
masterOnly 0 is under [global] section for all our reference configs. That is a per-port option and doesn't belong there. Need to ignore it for clockType selection to preserve backwards compatability
Version-Release number of selected component (if applicable):
4.20
How reproducible:
100% as GM
Steps to Reproduce:
1. Configure system as GM 2. specify masterOnly 0 in the ptpconfig 3.
Actual results:
clockType is detected as GM
Expected results:
clockType is detected as BC
Additional info:
This is a workaround for the invalid reference configs, to avoid breaking systems when config refactoring is backported.