Since 20th of January cds-resource-resolution test fails due to same error Tests results - Summary (onap.org)

Based on logs it looks like something creates cds-resource-resolution-mock-server resource few minutes before test is executed.

Logs from 27th January:

kubectl -n onap-tests logs cds-cds-mockserver-fd85cf599-w85pw
2022-01-27 01:52:20 5.11.2 INFO logger level is INFO, change using:

• 'ConfigurationProperties.logLevel(String level)' in Java code,
• '-logLevel' command line argument,
• 'mockserver.logLevel' JVM system property or,
• 'mockserver.logLevel' property value in 'mockserver.properties'
  2022-01-27 01:52:20 5.11.2 INFO 1080 started on port: 1080
  2022-01-27 01:52:58 5.11.2 INFO 1080 creating expectation:

Test logs:

2022-01-27 01:58:13,357 DEBUG 71:cds_resource_resolution.py(1) - CDS resource resolution initialization

...
2022-01-27 01:58:14,177 INFO 142:onap_service.py(1) - [None][Create Instance] response code: 500
2022-01-27 01:58:14,177 DEBUG 146:onap_service.py(1) - [None][Create Instance] response: n/a
2022-01-27 01:58:14,177 ERROR 157:onap_service.py(1) - [None][Create Instance] API returned and error: {}
2022-01-27 01:58:14,177 ERROR 233:onap_service.py(1) - [None][Create Instance] request failed: Code: 500. Info: Create Kubernetes Resources: Error creating kind: /v1, Kind=Service: Error in plugin Service plugin: Create Service error: Service "cds-regression-mockserver" is invalid: spec.ports[0].nodePort: Invalid value: 30726: provided port is already allocated

So based on logs we can see that pod was created 6 minutes before test was executed