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

Need steps to collect driver's persistent logs #913

Open
Jainbrt opened this issue Feb 21, 2023 · 0 comments
Open

Need steps to collect driver's persistent logs #913

Jainbrt opened this issue Feb 21, 2023 · 0 comments
Labels
Customer Impact: Localized low impact (2) Temporary / limited perf impact, unnecessary failovers, issues occur while in degraded state Customer Probability: Medium (3) Issue occurs in normal path but specific limited timing window, or other mitigating factor Found In: 2.9.0 For Bug issues to identify what release level issue was found in 2.9.0 Severity: 3 Indicates the the issue is on the priority list for next milestone. Type: Bug Indicates issue is an undesired behavior, usually caused by code error.

Comments

@Jainbrt
Copy link
Member

Jainbrt commented Feb 21, 2023

Describe the bug

Need steps to collect driver's persistent logs

How to Reproduce?

Please list the steps to help development teams reproduce the behavior

  1. Install CSI driver with driver's persistent logs enabled

Logs would be generated at /host/var/adm/ras/scalecsilogs folder

Expected behavior

Need steps to collect driver's persistent logs
@Jainbrt Jainbrt added Type: Bug Indicates issue is an undesired behavior, usually caused by code error. Severity: 3 Indicates the the issue is on the priority list for next milestone. Customer Probability: Medium (3) Issue occurs in normal path but specific limited timing window, or other mitigating factor Customer Impact: Localized low impact (2) Temporary / limited perf impact, unnecessary failovers, issues occur while in degraded state Found In: 2.9.0 For Bug issues to identify what release level issue was found in 2.9.0 labels Feb 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Customer Impact: Localized low impact (2) Temporary / limited perf impact, unnecessary failovers, issues occur while in degraded state Customer Probability: Medium (3) Issue occurs in normal path but specific limited timing window, or other mitigating factor Found In: 2.9.0 For Bug issues to identify what release level issue was found in 2.9.0 Severity: 3 Indicates the the issue is on the priority list for next milestone. Type: Bug Indicates issue is an undesired behavior, usually caused by code error.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Jainbrt