Bug 1783857

Summary: Mix use of "local storage operator" and "local volume operator" can confuse customer
Product: OpenShift Container Platform Reporter: Liang Xia <lxia>
Component: StorageAssignee: Jan Safranek <jsafrane>
Status: CLOSED ERRATA QA Contact: Liang Xia <lxia>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.4CC: aos-bugs, jsafrane, nagrawal
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-13 21:55:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Liang Xia 2019-12-16 05:35:21 UTC
Description of problem:
Both "local storage operator" and "local volume operator" are used, which can confuse customer.
We should consistently use "local storage operator".

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install local storage operator.
2. Check several pages for the installed local storage operator.

Actual results:
Some times "local storage operator" is used,
while some times "local volume operator" is used.

Expected results:
Consistently use "local storage operator".

Comment 1 Jan Safranek 2019-12-18 12:31:42 UTC
There is confusion about Local Storage Operator (the operator itself) and Local Volume operator APIs (the CRD / CRs managed by the operator).

I propose using Local Volumes (without "operator") for the CRD / CRs. I.e. Local Storage Operator provides Local Volume API and don't use "operator" anywhere in the API.

Comment 3 Liang Xia 2020-01-07 06:26:42 UTC
Verified the issue is fixed with,

Local Storage 4.4.0-202001062016
OpenShift Version 4.4.0-0.nightly-2020-01-06-072200

Comment 5 errata-xmlrpc 2020-05-13 21:55:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.