Skip to content
This repository has been archived by the owner on Jan 27, 2023. It is now read-only.

max_days_since_fix policy parameter not triggering after updating to 1.1.0 from 0.9.1 #1395

Open
davidtseng opened this issue Dec 7, 2022 · 0 comments

Comments

@davidtseng
Copy link

Is this a request for help?:


Is this a BUG REPORT or a FEATURE REQUEST? (choose one):

Version of Anchore Engine and Anchore CLI if applicable:

Engine DB Version: 0.0.16
Engine Code Version: 1.1.0

What happened:

For the policy gate:
anchore-cli policy describe --gate=vulnerabilities --trigger package
+------------------------------------------------+------------------------------------------+----------+--------------+
| max_days_since_fix | If provided (only evaluated when | False | 30 |
| | fix_available option is also set to | | |
| | true), the fix first observed time must | | |
| | be older than days provided, to trigger. | | |
+------------------------------------------------+------------------------------------------+----------+--------------+
|

max_days_since_fix does not appear to trigger after updating anchore-engine to 1.1.0, it was working with 0.9.1. Currently our scans do not trigger with this parameter when they used to with the same policy.

Also max_days_since_creation does not seem to trigger in some limited tests.

What did you expect to happen:

max_days_since_fix parameter triggers as expected

Any relevant log output from /var/log/anchore:

What docker images are you using:

How to reproduce the issue:

Anything else we need to know:

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant