Cypress Tests Failing on Big Bang Cluster

Summary

Using the IB Cypress test image, the tests for my deployed BB applications do not run.

Steps to reproduce

1. Set values.bbtests.cypress.image to registry1.dso.mil/ironbank/big-bang/cypress:14.4.1
2. Run tests for a release on the cluster. I tried these two:
   1. helm test sonarqube -n bigbang
   2. helm test monitoring-grafana -n bigbang
3. Tests fail

What is the current bug behavior?

The test pod gets created but the actual Cypress tests are unable to start:

$ helm test sonarqube -n bigbang
NAME: sonarqube
LAST DEPLOYED: Fri Jun 27 13:55:03 2025
NAMESPACE: sonarqube
STATUS: deployed
REVISION: 1
TEST SUITE:     sonarqube-cypress-config
Last Started:   Fri Jun 27 14:04:15 2025
Last Completed: Fri Jun 27 14:04:15 2025
Phase:          Succeeded
TEST SUITE:     sonarqube-cypress-test
Last Started:   Fri Jun 27 14:04:15 2025
Last Completed: Fri Jun 27 14:04:30 2025
Phase:          Failed
Error: 1 error occurred:
        * pod sonarqube-cypress-test failed

What is the expected correct behavior?

Tests run.

Relevant logs and/or screenshots

--2025-06-27 14:04:27--  https://repo1.dso.mil/big-bang/product/packages/gluon/-/raw/master/common/commands.js
Resolving repo1.dso.mil (repo1.dso.mil)... 15.205.173.153
Connecting to repo1.dso.mil (repo1.dso.mil)|15.205.173.153|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4656 (4.5K) [text/plain]
Saving to: '/test/cypress/common/commands.js'
0K ....                                                  100% 3.08G=0s
2025-06-27 14:04:27 (3.08 GB/s) - '/test/cypress/common/commands.js' saved [4656/4656]
No version of Cypress is installed in: /.cache/Cypress/14.4.1/Cypress
Please reinstall Cypress by running: cypress install
----------
Cypress executable not found at: /.cache/Cypress/14.4.1/Cypress/Cypress
----------
Platform: linux-x64 (Ubuntu - 22.04)
Cypress Version: 14.4.1
no cypress logs found from the pod
no cypress screenshots found from the pod
no cypress videos found from the pod
OK

This is running in a BB 2.52.0 cluster.

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Tasks

• Bug has been identified and corrected within the container

Please read the Iron Bank Documentation for more info