-
Sub-task
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
None
-
4
-
False
-
-
False
-
ToDo
-
0
-
0.000
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
Description of problem:
If the VSB or VSR controller errors, the status field on the CRs is not updated/included.
How reproducible:
100% on error
Steps to Reproduce:
1. Create an error for VSB/VSR such as multiple default classes
2. oc get vsb -n <appns> -oyaml
3. check that there is no status field
Actual results:
No status on CR
Expected results:
Status which includes conditions with the error