Details
-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
3
-
False
-
None
-
False
-
Pipelines Sprint 244, Pipelines Sprint 245, Pipelines Sprint 246
Description
Story (Required)
As a QE trying to review failed CI pipeline runs I want review logs referenced from Slack notification but they are very often gone, even minutes after pipeline run finished.
Background (Required)
We only see messages like the one below after opening logs in OpenShift console or using `tkn pr logs`
STEP-RUN unable to retrieve container logs for cri-o://ebd0c7a32c8fc7dd6d84481c67bbf88b72c48828ae3e71794449eaf47b5bab5b STEP-UPDATE-RESULT unable to retrieve container logs for cri-o://35aa7105b5c7792ef10f58e1609f0ebf7ab5cdb4404d764cce34a9f7a1122e6c STEP-ENABLE-RETRIES unable to retrieve container logs for cri-o://ebca4d869c0f05c6a21f4eed6a7a9704d1a824dc40b893d17fae91529dec9584
Out of scope
test artifacts storage
Approach (Required)
<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>
Dependencies
<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>
Acceptance Criteria (Mandatory)
<Describe edge cases to consider when implementing the story and defining tests>
<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>
INVEST Checklist
Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated
Legend
Unknown
Verified
Unsatisfied
Done Checklist
- Code is completed, reviewed, documented and checked in
- Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
- Continuous Delivery pipeline(s) is able to proceed with new code included
- Customer facing documentation, API docs etc. are produced/updated, reviewed and published
- Acceptance criteria are met