Bug 1868630 - 'Ceph` in error message for storage pool creation
Summary: 'Ceph` in error message for storage pool creation
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Storage Plugin
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.6.0
Assignee: Kanika Murarka
QA Contact: Neha Berry
Depends On:
TreeView+ depends on / blocked
Reported: 2020-08-13 10:26 UTC by Kanika Murarka
Modified: 2020-10-27 16:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-10-27 16:28:09 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 6311 0 None closed Bug 1868630: Removes 'ceph block pool model' from the error message for pool creation 2020-09-21 09:04:35 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:28:26 UTC

Description Kanika Murarka 2020-08-13 10:26:13 UTC
Description of problem:
`Ceph` is shown in error message when we try to create a pool of same name.

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

How reproducible:

Steps to Reproduce:
1. Navigate to storage class list view
2. Click on `Create Storage Class`
3. Select `openshift-storage.rbd.csi.ceph.com` in provisioner dropdown
4. Click on `Create New Pool` in Storage Pool dropdown
5. Create a Pool named - pool1
6. Create another pool, named - pool1

Actual results:
The error message says 'cephblockpools.ceph.rook.io` already exist.

Expected results:
The message shouldnt have `ceph`. 

Additional info:

Comment 5 errata-xmlrpc 2020-10-27 16:28:09 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 (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.

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


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