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

SCAP checks failing after upstream changes #2269

Open
ehashman opened this issue Apr 6, 2020 · 7 comments
Open

SCAP checks failing after upstream changes #2269

ehashman opened this issue Apr 6, 2020 · 7 comments
Labels
kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@ehashman
Copy link
Contributor

ehashman commented Apr 6, 2020

I think we just need to update the benchmarks to avoid these warnings: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/periodic-ci-azure-vmimage-validate-osa311-latest/200#1:build-log.txt%3A269
@ehashman
Copy link
Contributor Author

ehashman commented Apr 6, 2020

/kind test-flake
/assign

@openshift-ci-robot openshift-ci-robot added the kind/test-flake Categorizes issue or PR as related to test flakes. label Apr 6, 2020
This was referenced Apr 13, 2020
Closed
Merged
@ehashman
Copy link
Contributor Author

Submitted https://bugzilla.redhat.com/show_bug.cgi?id=1823576 -- we have two rules failing and I don't think they should be.

@ehashman
Copy link
Contributor Author

ehashman commented May 5, 2020

Fixed in version: scap-security-guide-0.1.49-5.el7

@ehashman
Copy link
Contributor Author

ehashman commented May 5, 2020

0:0.1.46-11.el7 is still the one available in our builds. I'll wait until the correct version of the scanner rules are available.

@ehashman ehashman mentioned this issue May 5, 2020
Closed
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 3, 2020
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 2, 2020
@ehashman
Copy link
Contributor Author

ehashman commented Sep 3, 2020

/lifecycle frozen
/remove-lifecycle rotten

@openshift-ci-robot openshift-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Sep 3, 2020
@ehashman ehashman removed their assignment Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Revert "HACK: Disable false negatives for now" ehashman/openshift-azure
3 participants
@openshift-bot @ehashman @openshift-ci-robot