CSIT setup.sh for modeling/etsicatalog pulls images from Nexus3 by name only, therefore reverting to "latest" by default. While this is not a massive risk in case of etsicatalog (which only has master branch jobs - even though that is questionable in itself), it is still a bad practice that should be improved to reduce unambiguity.

The most complete solution to avoid any potential issues related to this is to move the CSITs under the project repository as described in https://wiki.onap.org/display/DW/Moving+CSIT+to+project+repositories.

If this is too big effort to consider, a more lightweight future-proof solution to identify the version of the tested etsicatalog image would be to use the snapshot_version variable value in etsicatalog/version.properties (currently this would yield 1.0.10-SNAPSHOT, which matches the version generated by https://jenkins.onap.org/view/modeling/job/modeling-etsicatalog-master-docker-java-version-shell-daily ... curiously though that job also generates 1.0.10-STAGING - is there some particular reason for that?)