Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 1670343 [details] error message Description of problem (please be detailed as possible and provide log snippests): When creating PV based Backing Store the character limit for Backing Store name is not low enough and creation fails due to kubernetes requirement that pod name should not exceed 64 characters. The only place i found this error is in the Stateful Set event log in ocs. Version of all relevant components (if applicable): Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? No 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)? 2 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: no Steps to Reproduce: 1. Create a PV Backing Store in MTG with a very long name 2. Go to oc Stateful Set create by noobaa and watch event log Actual results: Creation of backing store fails Expected results: Lower character limit on Backing Store Additional info: Attached error message below
Hi Amit, How exactly did you create the PV Backing Store? if it was through CLI please add the command. when you said this issue can reproduced from the UI, did you mean Noobaa UI?
Hi Rom, You can create a pv backingstore in what ever way you wish and the problem would reproduce. The issue is created when NooBaa creates the Statefulset and adds noobaa-noobaa to it as well as noobaa-noobaa-(number) to the pods.
Not sure this should be on MODIFIED: It is not qa_acke-ed, so not approved for 4.4.0.
@Michael, Talked about it with Raz yesterday, I think we just missed the flag .
Noobaa UI and CLI verified as fixed. Bug still occurs when creating pv backing store with the OCS UI and with YAML file as well.
You cannot limit on a yaml edit ... Regarding the UI, its a different component and different issue. I think we should create a new BZ for the UI and move this one according to its state.
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. https://access.redhat.com/errata/RHBA-2020:2393