Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

No labels!

There aren’t any labels for this repository quite yet.

Architecture: ppc64le
Architecture: ppc64le
Architecture: s390
Architecture: s390
Architecture: x86_64
Architecture: x86_64
Component: API
Component: API
Component: Automation
Component: Automation
Customer Impact: Global
Customer Impact: Global
(4) Cluster-wide impact. FS corruption, global unmount, loss of quorum, ...
Customer Impact: Localized high impact
Customer Impact: Localized high impact
(3) Reduction of function. Significant impact to workload.
Customer Impact: Localized low impact
Customer Impact: Localized low impact
(2) Temporary / limited perf impact, unnecessary failovers, issues occur while in degraded state
Customer Impact: Minor
Customer Impact: Minor
(1) misleading msgs, operational oddities not affecting workload. Failure of non critical services
Customer Probability: Can't Happen
Customer Probability: Can't Happen
0) Problem is only hit w multiple failures or pathological use of operations rare in production env
Customer Probability: High
Customer Probability: High
(5) Issue occurs in normal main path, IO load within expected norms, no failure triggers or oddities
Customer Probability: Low
Customer Probability: Low
Low (1) Issue only occurs during failure condition - disk, server, network, test assert, ...
Customer Probability: Medium
Customer Probability: Medium
(3) Issue occurs in normal path but specific limited timing window, or other mitigating factor
Environment: IBM Spectrum Archive
Environment: IBM Spectrum Archive
Environment: IBM Spectrum Discover
Environment: IBM Spectrum Discover
Environment: IBM Spectrum LSF
Environment: IBM Spectrum LSF
Environment: IBM Spectrum Scale
Environment: IBM Spectrum Scale
Environment: Red Hat OpenShift
Environment: Red Hat OpenShift
Epic
Epic
good first issue
good first issue
Good for newcomers
MDD
MDD
A Miniature Design Document
Phase: Automation
Phase: Automation
Issues found during automation test run
Phase: Build
Phase: Build
Issue found during build process
Phase: Development
Phase: Development
Issue was discovered through development
Phase: Field
Phase: Field
Issue was discovered in customer environment
Phase: Test
Phase: Test
Issue was discovered through Test
Severity: 1
Severity: 1
Indicates that the issue breaks function unilaterally.
Severity: 2
Severity: 2
Indicates that the issue is critical and must be addressed before milestone.
Severity: 3
Severity: 3
Indicates the the issue is on the priority list for next milestone.
Severity: 4
Severity: 4
Indicates low priority issue.