CSO status is true if we edit CSI secret with wrong user #1146
Labels
Customer Impact: Localized high impact
(3) Reduction of function. Significant impact to workload.
Customer Probability: Medium
(3) Issue occurs in normal path but specific limited timing window, or other mitigating factor
Found In: 2.12.0
For Bug issues to identify what release level issue was found in 2.12.0
Severity: 2
Indicates that the issue is critical and must be addressed before milestone.
Type: Bug
Indicates issue is an undesired behavior, usually caused by code error.
Describe the bug
When we edit secret with wrong user and then check cso status then it is shown as true and there is no event for same
How to Reproduce?
Please list the steps to help development teams reproduce the behavior
Expected behavior
CSO status should be false if username is wrong as improvement so that it will be easy to detect and won't cause any issue during volume creation or CSI upgrade or there should be event generated for the same
logs :
The text was updated successfully, but these errors were encountered: