dohertj2/lmxopcua
1
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases Wiki Activity

Redundancy interop runbook uses deleted types and wrong standard NodeId #716

New Issue
Open
opened 2026-10-13 12:17:39 -04:00 by dohertj2 · 0 comments
dohertj2 commented 2026-10-13 12:17:39 -04:00
Owner
Copy Link
Copy Source

Finding

The current GA G9 checklist in #615 links docs/plans/phase-6-3-redundancy-interop-plan.md, but the executable instructions still use deleted ClusterNode.RedundancyRole, PeerHttpProbeLoop and PeerUaProbeLoop; expect historical 255/100 service-level bands; and read i=2271 as ServerUriArray.

Source audit at main 6f067429: docs/Redundancy.md describes oldest-Up election, current health tiers and actual ServerArray discovery; local SDK standard constants identify i=2271 as ServerCapabilities.LocaleIdArray, true ServerUriArray as i=11314, ServerArray as i=2254. This is a source/constant audit, not a live client pass.

Required correction

  • Reconcile executable setup, expected levels, timing and diagnostics with current source; clearly mark historical material.
  • Correct the standard variable identifiers and distinguish ServerArray discovery from the separate ServerRedundancy.ServerUriArray conformance gate.
  • Retain unmet standard metadata and production-client cutover gates; do not turn absent ServerUriArray into a passing ServerArray substitute.
  • Review source references and commands; no runtime change, deployment, lab-client claim or acceptance relaxation.

Parent #615 remains open. The standard metadata gap is tracked separately.

## Finding The current GA G9 checklist in #615 links docs/plans/phase-6-3-redundancy-interop-plan.md, but the executable instructions still use deleted ClusterNode.RedundancyRole, PeerHttpProbeLoop and PeerUaProbeLoop; expect historical 255/100 service-level bands; and read i=2271 as ServerUriArray. Source audit at main 6f067429: docs/Redundancy.md describes oldest-Up election, current health tiers and actual ServerArray discovery; local SDK standard constants identify i=2271 as ServerCapabilities.LocaleIdArray, true ServerUriArray as i=11314, ServerArray as i=2254. This is a source/constant audit, not a live client pass. ## Required correction - Reconcile executable setup, expected levels, timing and diagnostics with current source; clearly mark historical material. - Correct the standard variable identifiers and distinguish ServerArray discovery from the separate ServerRedundancy.ServerUriArray conformance gate. - Retain unmet standard metadata and production-client cutover gates; do not turn absent ServerUriArray into a passing ServerArray substitute. - Review source references and commands; no runtime change, deployment, lab-client claim or acceptance relaxation. Parent #615 remains open. The standard metadata gap is tracked separately.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
auto-managed
queue management
 cross-driver
queue management
 driver/abcip
queue management
 driver/ablegacy
queue management
 driver/focas
queue management
 driver/mqtt
MQTT / Sparkplug B broker-subscribe driver
 driver/opcuaclient
queue management
 driver/s7
queue management
 driver/twincat
queue management
 phase/1
queue management
 phase/2
queue management
 phase/3
queue management
 phase/4
queue management
 phase/5
queue management
 phase/6
queue management
 queue/blocked
queue management
 queue/done
queue management
 queue/failed
queue management
 queue/in-progress
queue management
 queue/queued
queue management
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dohertj2 (dohertj2)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/lmxopcua#716
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?