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

focas-sim fixture image on 10.100.0.35 is stale #651

New Issue
Closed
opened 2026-10-08 18:51:43 -04:00 by dohertj2 · 1 comment
dohertj2 commented 2026-10-08 18:51:43 -04:00
Owner
Copy Link
Copy Source

Found during the b640 FOCAS live run. The deployed focas-sim image on 10.100.0.35 is dated 2026-08-19. WireBackendTests Timers_populate_via_wire_backend and Identity_axes_and_dynamic_populate_via_wire_backend fail on master against it but pass against the vendored mock. Rebuild/redeploy the fixture (lmxopcua-fix sync + rebuild). Also: the container publishes no port; the tests reached it via ssh -L to the container IP (127.0.0.1:28193 -> 172.26.0.2:8193), so consider publishing 8193.

Found during the b640 FOCAS live run. The deployed focas-sim image on 10.100.0.35 is dated 2026-08-19. WireBackendTests Timers_populate_via_wire_backend and Identity_axes_and_dynamic_populate_via_wire_backend fail on master against it but pass against the vendored mock. Rebuild/redeploy the fixture (lmxopcua-fix sync + rebuild). Also: the container publishes no port; the tests reached it via ssh -L to the container IP (127.0.0.1:28193 -> 172.26.0.2:8193), so consider publishing 8193.
dohertj2 added the driver/focas label 2026-10-08 18:51:43 -04:00
dohertj2 commented 2026-10-08 20:50:24 -04:00
Author
Owner
Copy Link
Copy Source

Root cause was not staleness: otopcua-focas-sim on 10.100.0.35 belongs to ignitionoee (its provision-oee-focas.sh docker rm -fs and recreates it, unpublished, with its own mock whose timer encoding is big-endian). Fixed on master (7dd64b8c): an OtOpcUa-owned stack otopcua-focas-fixture at /opt/otopcua-focas (8193 published, project: lmxopcua label); FOCAS integration tests default to 10.100.0.35:8193. Deployed + live gate PASS: FOCAS.IntegrationTests 14/14 incl. the two previously failing WireBackendTests; ignitionoee's otopcua-focas-sim verified untouched (same container Id/Created). Docs: infra/README.md, docs/v2/dev-environment.md.

Root cause was not staleness: `otopcua-focas-sim` on 10.100.0.35 belongs to ignitionoee (its provision-oee-focas.sh `docker rm -f`s and recreates it, unpublished, with its own mock whose timer encoding is big-endian). Fixed on master (`7dd64b8c`): an OtOpcUa-owned stack `otopcua-focas-fixture` at `/opt/otopcua-focas` (8193 published, `project: lmxopcua` label); FOCAS integration tests default to `10.100.0.35:8193`. **Deployed + live gate PASS**: FOCAS.IntegrationTests 14/14 incl. the two previously failing WireBackendTests; ignitionoee's `otopcua-focas-sim` verified untouched (same container Id/Created). Docs: infra/README.md, docs/v2/dev-environment.md.
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 driver/focas
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#651
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?