Bug 1999602 - Status of storageSystem is "Conditions: Available, VendorCsvReady, VendorSystemPresent" instead of "Succeeded"
Summary: Status of storageSystem is "Conditions: Available, VendorCsvReady, VendorSyst...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-operator
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Nitin Goyal
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-31 12:11 UTC by Shay Rozen
Modified: 2023-08-09 17:00 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-09-24 09:04:55 UTC
Embargoed:


Attachments (Terms of Use)
Image of storageSystem status (6.90 KB, image/png)
2021-08-31 12:11 UTC, Shay Rozen
no flags Details

Description Shay Rozen 2021-08-31 12:11:33 UTC
Created attachment 1819348 [details]
Image of storageSystem status

Description of problem (please be detailed as possible and provide log
snippests):
After ODF installation and creation of storageSystem status is "Conditions: Available, VendorCsvReady, VendorSystemPresent" instead of "Succeeded"


Version of all relevant components (if applicable):
ODF 4.9.0-118.ci (4.9.0-117.ci it worked)
OCP 4.9.0-0.nightly-2021-08-30-232019

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Customer will be confused of the status.

Is there any workaround available to the best of your knowledge?
No

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1

Can this issue reproducible?
yes

Can this issue reproduce from the UI?
Only

If this is a regression, please provide more details to justify this:
Yes. Previous version worked.

Steps to Reproduce:
1. Install OCP 4.9 and ODF 4.9.0-118.ci 
2. Create storageSystem.



Actual results:
Status of storageSystem is "Conditions: Available, VendorCsvReady, VendorSystemPresent"

Expected results:
Status should be "Succeeded"

Additional info:

Comment 5 Elad 2021-09-19 10:17:44 UTC
Hi Afreen, 

I agree that "Conditions: Available, VendorCsvReady, VendorSystemPresent" could be unclear to the users. 
As this is coming from the backend, I am changing the component and re-opening.

Comment 6 Shay Rozen 2021-09-19 10:30:10 UTC
I think that UI can recognize that the status is "Conditions: Available, VendorCsvReady, VendorSystemPresent" and replace it for UI representation with something more clearer and friendly to the customer.

Comment 7 Nitin Goyal 2021-09-20 07:58:32 UTC
Hi Elad,

We (DEV) have made a decision to deprecate the PHASE from the API in favour of https://github.com/kubernetes/community/blame/master/contributors/devel/sig-architecture/api-conventions.md#L433-L445

I am linking you to a discussion that happened on the GChat https://chat.google.com/room/AAAAvAcM88o/1ZFbr-e3IMA.

We really do not have any plan to introduce it back.


Note You need to log in before you can comment on or make changes to this bug.