image last pull time updated by image scan though global option set not to do so about harbor HOT 7 OPEN

In the core.log I see

Mar  4 11:58:14 172.18.0.1 core[342063]: 2024-03-04T10:58:14Z [INFO] [/pkg/task/dao/execution.go:471]: scanned out 1 executions with outdate status, refresh status to db
Mar  4 11:58:14 172.18.0.1 core[342063]: 2024-03-04T10:58:14Z [INFO] [/pkg/task/dao/execution.go:512]: refresh outdate execution status done, 1 succeed, 0 failed

but no log line with [INFO] [/lib/config/userconfig.go:255]: skip_update_pull_time:true by that time.
Though core.log contains lots of these messages (as addressed in #19795).

from harbor.

You could set Retain Image last pull time On Scanning on system configuration since 2.8

from harbor.

see #17807

from harbor.

Sorry, have you read through my report?
I have clearly set the system configuration to retain the last image pull time on scanning. You need a screenshot?

harbor_sys02=> select * from properties where k = 'scanner_skip_update_pulltime';
id | k | v
----+------------------------------+------
39 | scanner_skip_update_pulltime | true
(1 row)

Thought that would be enough to prove I have set it. I even stated that I see [INFO] [/lib/config/userconfig.go:255]: skip_update_pull_time:true messages in the core.log, just not for the case where I have explicitly noted that the pull time got modified by a scanner pull.

from harbor.

@MinerYang or @stonezdj please reopen this issue or at least please explain to me what I am seeing different than you.

from harbor.

Reopening the issue as @alexanderdalloz mentioned he has enabled the option Retain Image last pull time On Scanning, yet in some cases the pull time is updated.

from harbor.

Hello,
We also see that, we currently have the PrismaCloud scanner configured that scans and pulls all images once a day for CVE scanning.
Is there any extra configuration that might be added so that the pull can be ignored? Like it's mentioned on the settings for Trivy, some other configuration, like account that is pulling, or even other settings.
This would help alot also in the definition of the cleanup policies for pull time, for example to delete images that are not pulled for x days.

Thanks!

from harbor.