-
Bug
-
Resolution: Unresolved
-
Major
-
4.14.z, 4.15.z, 4.17.z, 4.16.z, 4.18
This is a clone of issue OCPBUGS-48398. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-48343. The following is the description of the original issue:
—
I introduced this misleading formatting quirk when synchronizing the source-crs and cluster-compare reference which hides the proper syntax for the e810 `pins` section.
Old version:
pins: $e810_pins
# "$iface_master":
# "U.FL2": "0 2"
# "U.FL1": "0 1"
# "SMA2": "0 2"
# "SMA1": "0 1"
Current version:
pins:
e810_pins: {}
# "(?<iface_timeTx1>[[:alnum:]]+)":
# "U.FL2": "0 2"
# "U.FL1": "0 1"
# "SMA2": "0 2"
# "SMA1": "2 1"
# "(?<iface_timeTx2>[[:alnum:]]+)":
# "U.FL2": "0 2"
# "U.FL1": "0 1"
# "SMA2": "0 2"
# "SMA1": "1 1"
What it should probably be:
pins: "$iface_timeTx1": "U.FL2": "0 2" "U.FL1": "0 1" "SMA2": "0 2" "SMA1": "2 1" "$iface_timeTx2": "U.FL2": "0 2" "U.FL1": "0 1" "SMA2": "0 2" "SMA1": "1 1"
The cluster-compare template should of course allow any valid interface name, and any values for any of the pins.
- blocks
-
-
- New
-
- clones
-
-
- Verified
-
- is blocked by
-
-
- Verified
-
- is cloned by
-
-
- New
-
- links to
-
RHEA-2024:139529
OpenShift Container Platform 4.17.1 CNF vRAN extras update
- mentioned on
