-
Notifications
You must be signed in to change notification settings - Fork 37
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.
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
docs: mention fix for rekor and apiserver host resolution failures #2380
base: main
Are you sure you want to change the base?
docs: mention fix for rekor and apiserver host resolution failures #2380
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2380 +/- ##
==========================================
- Coverage 72.92% 67.87% -5.06%
==========================================
Files 89 101 +12
Lines 7783 8380 +597
==========================================
+ Hits 5676 5688 +12
- Misses 2107 2692 +585
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
/ok-to-test |
/lgtm |
Build PLR failed while running the
maybe a random quay.io issue? retesting /retest |
/retest |
README.md
Outdated
@@ -40,7 +40,7 @@ The `--debug` parameter enables debug logging. Setting `EC_DEBUG` environment | |||
variable can be set to prevent deletion of temporary `ec-work-*` directories so | |||
that the attestations, policy and data files can be examined. | |||
|
|||
When running acceptance tests you may experience issues with starting enough Docker containers to successfullyl complete testing. These issues may appear as repeated failures, such as seen below, and a failed acceptance test run: | |||
1. When running acceptance tests you may experience issues with starting enough Docker containers to successfullyl complete testing. These issues may appear as repeated failures, such as seen below, and a failed acceptance test run: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1. When running acceptance tests you may experience issues with starting enough Docker containers to successfullyl complete testing. These issues may appear as repeated failures, such as seen below, and a failed acceptance test run: | |
1. When running acceptance tests you may experience issues with starting enough Docker containers to successfully complete testing. These issues may appear as repeated failures, such as seen below, and a failed acceptance test run: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thanks!
Signed-off-by: Dheeraj<[email protected]>
d8c67f5
to
2f190b0
Compare
Failure is due to an out of date Task, rpms-signature-scan. Merging this. |
if you rebase with |
While running the acceptance tests, you might encounter an issue with host resolution for the calls to the apiserver and rekor. The fix is to include an entry for these 2 within your host file.
This PR adds this info to our troubleshooting guide.