[VAL-107] Testcases fail to pull the latest docker images if they are already present on the system Created: 22/Apr/20 Updated: 23/Apr/20 Resolved: 23/Apr/20 |
|
| Status: | Done |
| Project: | Validation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Medium |
| Reporter: | Alexandru Avadanii | Assignee: | Alexandru Avadanii |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
bluval/blucon only execute a `docker run` without an explicit `docker pull`, so if the images with the desired tags already exist on the system, they are used as-is without pulling the latest upstream tag. This currently leads to failing bluval jobs, since the image present on the hosts in the Enea lab are there before some security tests were marked as non-critical. |
| Comments |
| Comment by Alexandru Avadanii [ 23/Apr/20 ] |
|
A new job parameter called PULL has been added to validation/bluval jobs and it has been set to 'yes' by default for IEC validation jobs, since those run only on static slaves where stale image tags are expected. Last night's CI runs worked fine and the latest images have been pulled before executing the testcases, so this can be considered fixed (provided the new parameter is leveraged where needed). |