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

Add a port-NAT opc-plc fixture so the #806 NAT browse tests run in CI #813

New Issue
Closed
opened 2026-11-10 21:39:42 -05:00 by dohertj2 · 1 comment
dohertj2 commented 2026-11-10 21:39:42 -05:00
Owner
Copy Link
Copy Source

#806 added NatPublishedEndpointBrowseTests (Fixture=opc-plc-nat, skipped unless OPCUA_NAT_ENDPOINT is set). They were verified against a local OrbStack container: opc-plc:2.14.10 --hostname otopcua-806-nat-parity -p 32781:50000 --autoaccept --ut (advertises opc.tcp://otopcua-806-nat-parity:50000, unresolvable from the client).

Add an equivalent compose fixture on the docker host (10.100.0.35) with a private hostname and a published port different from the internal one (carry the project=lmxopcua label), document it in infra/README.md, and set OPCUA_NAT_ENDPOINT in CI. Optional: OPCUA_NAT_SERVER_CERT_TRUSTED=1 with the fixture cert in the browser trust store turns the security case positive.

#806 added NatPublishedEndpointBrowseTests (Fixture=opc-plc-nat, skipped unless OPCUA_NAT_ENDPOINT is set). They were verified against a local OrbStack container: `opc-plc:2.14.10 --hostname otopcua-806-nat-parity -p 32781:50000 --autoaccept --ut` (advertises opc.tcp://otopcua-806-nat-parity:50000, unresolvable from the client). Add an equivalent compose fixture on the docker host (10.100.0.35) with a private hostname and a published port different from the internal one (carry the project=lmxopcua label), document it in infra/README.md, and set OPCUA_NAT_ENDPOINT in CI. Optional: OPCUA_NAT_SERVER_CERT_TRUSTED=1 with the fixture cert in the browser trust store turns the security case positive.
dohertj2 added the type:infrapriority:p3 labels 2026-11-10 21:39:42 -05:00
dohertj2 commented 2026-11-11 00:49:02 -05:00
Author
Owner
Copy Link
Copy Source

Done on master (ac1b3355, 27302314). Port-NAT opc-plc fixture under tests/Drivers/ZB.MOM.WW.OtOpcUa.Driver.OpcUaClient.IntegrationTests/Docker/nat/, deployed as /opt/otopcua-opcuaclient-nat on 10.100.0.35 → opc.tcp://10.100.0.35:50010 (internal 50000), advertising otopcua-opc-plc-nat-private.invalid via --ph, project: lmxopcua label. CI: integration-fixtures.sh starts a throwaway container and exports OPCUA_NAT_ENDPOINT; v2-e2e points at the shared stack. Documented in infra/README.md and scripts/ci/README.md. NAT tests 3/3 live, 0 skipped; the secure case was made positive once with the cert trusted. Follow-ups: #817, #818, #816.

Done on master (ac1b3355, 27302314). Port-NAT opc-plc fixture under `tests/Drivers/ZB.MOM.WW.OtOpcUa.Driver.OpcUaClient.IntegrationTests/Docker/nat/`, deployed as `/opt/otopcua-opcuaclient-nat` on 10.100.0.35 → `opc.tcp://10.100.0.35:50010` (internal 50000), advertising `otopcua-opc-plc-nat-private.invalid` via `--ph`, `project: lmxopcua` label. CI: `integration-fixtures.sh` starts a throwaway container and exports `OPCUA_NAT_ENDPOINT`; v2-e2e points at the shared stack. Documented in infra/README.md and scripts/ci/README.md. NAT tests 3/3 live, 0 skipped; the secure case was made positive once with the cert trusted. Follow-ups: #817, #818, #816.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
auto-managed
queue management
 blocked
Blocked by dependency or external hold
 cross-driver
queue management
 cross-repo
Needs coordinated change in another family repo (wire contract etc.)
 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
 migrated
Migrated from a markdown backlog (2026-11 standardization)
 phase/1
queue management
 phase/2
queue management
 phase/3
queue management
 phase/4
queue management
 phase/5
queue management
 phase/6
queue management
 priority:p0
Must-have / blocking
 priority:p1
High priority
 priority:p2
Normal priority
 priority:p3
Low priority / nice to have
 queue/blocked
queue management
 queue/done
queue management
 queue/failed
queue management
 queue/in-progress
queue management
 queue/queued
queue management
 type:bug
Defect in shipped behaviour
 type:debt
Technical debt / hygiene
 type:deploy-gate
Rollout/deploy/migration step not yet done on an environment
 type:docs
Documentation work
 type:feature
Feature implementation
 type:followup
Follow-up deferred from a plan, PR or gate
 type:infra
Infrastructure and scaffolding
 type:review-finding
Unfixed finding from an architecture/code review
 type:test
Test work
No Label priority:p3 type:infra
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#813
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?