Bug 1926154 - Create new pool with arbiter - wrong replica
Summary: Create new pool with arbiter - wrong replica
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Storage Plugin
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.8.0
Assignee: gowtham
QA Contact: Avi Liani
URL:
Whiteboard:
Depends On: 1920507
Blocks: 1932238 1932277 1953937
TreeView+ depends on / blocked
 
Reported: 2021-02-08 11:24 UTC by Avi Liani
Modified: 2021-07-27 22:42 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1932277 (view as bug list)
Environment:
Last Closed: 2021-07-27 22:42:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
replica selection during new pool creation (440.88 KB, image/png)
2021-02-24 08:14 UTC, Avi Liani
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 8117 0 None closed Bug 1926154: Fix for creating new pool with arbiter - wrong replica 2021-02-16 06:33:39 UTC
Github openshift console pull 8177 0 None open Bug 1926154: Fix pool replica for arbiter 2021-02-16 17:40:13 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:42:37 UTC

Description Avi Liani 2021-02-08 11:24:55 UTC
Description of problem (please be detailed as possible and provide log
snippests):

while trying to create new RDB pool (for compression) from the UI,
in the replica selection list, you can select replica-2 or replica-3, while the cluster was created with replica-4 (default for arbiter)

Version of all relevant components (if applicable):

OCP:    4.7.0-0.nightly-2021-02-06-084550
OCS:    ocs-operator.v4.7.0-254.ci

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

yes, creation of new pool for compressed data is impossible

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?

yes

If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. deploy OCP 4.7
2. deploy OCS 4.7 with Arbiter
3. create new SC with new Pool


Actual results:

in the replica section you can select replica-2 / replica-3

Expected results:

the list will contain replica-4


Additional info:

Comment 2 Neha Berry 2021-02-09 07:46:32 UTC
(In reply to Avi Liani from comment #0)
> Description of problem (please be detailed as possible and provide log
> snippests):

> 
> Actual results:
> 
> in the replica section you can select replica-2 / replica-3
> 
> Expected results:
> 
> the list will contain replica-4
> 

IMO, the fix should be that users  are not given any option to select replica values other than 4, rather than adding replica-4 to the list.

i.e. either a)disable replica 2 and 3 and add 4 or
b)  disable the whole replica field for arbiter and set default replica count for every pool as 4. (IMP more preferred). We can even mention the reason why the replica drop down is disabled 

WDYT ?

> Additional info:

Comment 3 Avi Liani 2021-02-09 08:10:01 UTC
(In reply to Neha Berry from comment #2)
> (In reply to Avi Liani from comment #0)
> > Description of problem (please be detailed as possible and provide log
> > snippests):
> 
> > 
> > Actual results:
> > 
> > in the replica section you can select replica-2 / replica-3
> > 
> > Expected results:
> > 
> > the list will contain replica-4
> > 
> 
> IMO, the fix should be that users  are not given any option to select
> replica values other than 4, rather than adding replica-4 to the list.
> 
> i.e. either a)disable replica 2 and 3 and add 4 or
> b)  disable the whole replica field for arbiter and set default replica
> count for every pool as 4. (IMP more preferred). We can even mention the
> reason why the replica drop down is disabled 
> 
> WDYT ?
I think that option b) is the preferred one.
> 
> > Additional info:

Comment 7 Avi Liani 2021-02-24 06:07:50 UTC
testing this on 

OCP : 4.7.0-rc.3
OSC: 4.7.0-268.ci
Ceph: 14.2.11-123.el8cp

and i see the same - when trying to create new compressed pool, i can select for replica : Replica-2 / Replica-3
and not Replica-4

Comment 8 Ankush Behl 2021-02-24 06:51:58 UTC
The fix is available in the 4.8(check target release) nightly builds of OCP and till this bug is verified in 4.8 we can't backport to 4.7. So we need to test with 4.8 builds.

Moving this to ON_QA again.

Comment 9 Avi Liani 2021-02-24 08:13:21 UTC
Tested and verified on :

Platform : AWS - i3
OCP      : 4.8.0-0.nightly-2021-02-24-021848
OCS      : ocs-operator.v4.7.0-268.ci
LSO      : local-storage-operator.4.7.0-202102110027.p0 

now it is working as expected and when i am trying to create new pool, in the replica selection i can see only replica-4.

screenshot is attached.

Comment 10 Avi Liani 2021-02-24 08:14:55 UTC
Created attachment 1759017 [details]
replica selection during new pool creation

Comment 13 errata-xmlrpc 2021-07-27 22:42:10 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHSA-2021:2438


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