This repository was archived by the owner on Apr 17, 2023. It is now read-only.
background: mark failed scans as re-schedulable #1671
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After a security scanning iteration, some tags might not be in a :scan_done state. This is possible in situtations like: - Clair was unavailable for some time because of a hiccup. - There's an actual bug on the security scanning. In these cases, we will check in the end of the iteration whether all tags have been marked as scan. If this is not the case, then we will log a warning and mark the failed tags as :scan_none (so in the next iteration they can be picked up and hopefully be scanned properly this time). See SUSE#1649 Signed-off-by: Miquel Sabaté Solà <msabate@suse.com>
vitoravelino
approved these changes
Feb 8, 2018
|
Nice |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After a security scanning iteration, some tags might not be in a
:scan_done state. This is possible in situtations like:
In these cases, we will check in the end of the iteration whether all
tags have been marked as scan. If this is not the case, then we will log
a warning and mark the failed tags as :scan_none (so in the next
iteration they can be picked up and hopefully be scanned properly this
time).
See #1649
Signed-off-by: Miquel Sabaté Solà msabate@suse.com