Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Better error reporting for failed database setup #24

Open
abn opened this issue Jun 2, 2014 · 1 comment
Open

Better error reporting for failed database setup #24

abn opened this issue Jun 2, 2014 · 1 comment
Assignees
@gcmurphy
Labels
enhancement
Milestone
1.3.5

Comments

@abn
Copy link
Member

abn commented Jun 2, 2014

Currently, if the database setup fails, the rule does not report the root cause. An example message would be as shown below. We probably need to improve this a bit.

[WARNING] Rule 0: com.redhat.victims.VictimsRule failed with message:
Could not create a VictimsSQL instance.
@abn abn added the enhancement label Jun 2, 2014
@gcmurphy gcmurphy added this to the 1.3.5 milestone Jun 9, 2014
@seanf
Copy link
Contributor

seanf commented Jul 2, 2014

In addition, if victims-enforcer is configured not to fail the build in the case of metadata/fingerprint vulnerabilitiess, it probably shouldn't fail the build because of database problems either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gcmurphy gcmurphy

Labels
enhancement
Projects
None yet
Milestone
1.3.5
Development

No branches or pull requests
3 participants
@seanf @abn @gcmurphy