You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After investigating this intermittent issue, there is a race condition in the test between Docker and Test execution. As part of the test it update the FF Config to add a new namespace, that file is mounted into the FireFly container in Docker. After adding a new namespace it will call the /spi/v1/reset API for FF to restart with that new config. If the volume mount hasn't picked up that new configuration then it will not start the new namespace and thus the test will fail when checking for the status of that namespace as such:
restclient.go:109: 2024-07-22T17:01:05.89518895Z: ==> GET /namespaces/e2e_65737b8a1b-C/status map[]: null
restclient.go:109: 2024-07-22T17:01:10.89563318Z: ==> GET /namespaces/e2e_65737b8a1b-C/status map[]: null
restclient.go:109: 2024-07-22T17:01:15.896077617Z: ==> GET /namespaces/e2e_65737b8a1b-C/status map[]: null
restclient.go:109: 2024-07-22T17:01:20.900465937Z: ==> GET /namespaces/e2e_65737b8a1b-C/status map[]: null
restclient.go:109: 2024-07-22T17:01:25.904224656Z: ==> GET /namespaces/e2e_65737b8a1b-C/status map[]: null
restclient.go:109: 2024-07-22T17:01:30.905116092Z: ==> GET /namespaces/e2e_65737b8a1b-C/status map[]: null
restclient.go:109: 2024-07-22T17:01:35.909481946Z: ==> GET /namespaces/e2e_65737b8a1b-C/status map[]: null
restclient.go:109: 2024-07-22T17:01:40.910588275Z: ==> GET /namespaces/e2e_65737b8a1b-C/status map[]: null
restclient.go:109: 2024-07-22T17:01:45.911013176Z: ==> GET /namespaces/e2e_65737b8a1b-C/status map[]: null
restclient.go:109: 2024-07-22T17:01:50.911431512Z: ==> GET /namespaces/e2e_65737b8a1b-C/status map[]: null
restclient.go:109: 2024-07-22T17:01:55.913719974Z: ==> GET /namespaces/e2e_65737b8a1b-C/status map[]: null
restclient.go:109: 2024-07-22T17:02:00.918162459Z: ==> GET /namespaces/e2e_65737b8a1b-C/status map[]: null
e2e.go:71:
Error Trace: /home/runner/work/firefly/firefly/test/e2e/e2e.go:71
/home/runner/work/firefly/firefly/test/e2e/multiparty/multi_tenancy.go:117
Error: Received unexpected error:
Get "http://127.0.0.1:5001/api/v1/namespaces/e2e_65737b8a1b-C/status": dial tcp 127.0.0.1:5001: connect: connection refused
The text was updated successfully, but these errors were encountered:
Have hit this again multiple times, I think the ideal fix would be to use the reload config watcher instead of calling this reset and for the test to wait for things to spin back up... We had deprecated this reset API a while back
There is an intermittent test failure such as this one https://github.com/hyperledger/firefly/actions/runs/10045043332/job/27761545128?pr=1544
After investigating this intermittent issue, there is a race condition in the test between Docker and Test execution. As part of the test it update the FF Config to add a new namespace, that file is mounted into the FireFly container in Docker. After adding a new namespace it will call the
/spi/v1/reset
API for FF to restart with that new config. If the volume mount hasn't picked up that new configuration then it will not start the new namespace and thus the test will fail when checking for the status of that namespace as such:The text was updated successfully, but these errors were encountered: