Bug 2007136 - Creation of BackingStore, BucketClass, NamespaceStore fails
Summary: Creation of BackingStore, BucketClass, NamespaceStore fails
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Storage Plugin
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Bipul Adhikari
QA Contact: Elena Bondarenko
: 2022270 (view as bug list)
Depends On:
Blocks: 2017722
TreeView+ depends on / blocked
Reported: 2021-09-23 08:36 UTC by Bipul Adhikari
Modified: 2022-03-10 16:13 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2017722 (view as bug list)
Last Closed: 2022-03-10 16:12:52 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10128 0 None open Bug 2007136: Fix creation for BackingStore, BucketClass and NamespaceStore 2021-09-23 08:37:11 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:13:13 UTC

Description Bipul Adhikari 2021-09-23 08:36:03 UTC
Description of problem: As mentioned in the summary. 

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

How reproducible: 1/1

Steps to Reproduce:
1. Create BC/BS/NS
2. Error message is seen

Actual results: Creation of BC/BS/NS fails.

Expected results: Creation should succeed. 

Additional info:
It fails as the UI is not passing the namespace name in the request payload.

Comment 3 Elena Bondarenko 2021-10-29 13:22:01 UTC
I retested with 4.10.0-0.nightly-2021-10-28-211203. Creation of BackingStore, BucketClass, NamespaceStore was successful.

Comment 4 Bipul Adhikari 2021-11-16 03:54:20 UTC
*** Bug 2022270 has been marked as a duplicate of this bug. ***

Comment 7 errata-xmlrpc 2022-03-10 16:12:52 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.10.3 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.


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