Description of problem (please be detailed as possible and provide log snippests): Due to kubernetes pod name length limitation, the prefix automatically added by noobaa to the agent pod of the pv pool name is causing a failure in the pv-pool backing store creation 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)? Is there any workaround available to the best of your knowledge? enter a name shorter than 43 characters 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 always Can this issue reproduce from the UI? yes always If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. enter the backing store creation tool in the ui 2. create a backing store with a name longer than 43 character Actual results: backing store state is Rejected: Failed connecting all pods in backing store for more than 10 minutes Expected results: this should not be allowed, the name of a pv-pool should be limited to 43 both from the UI, Yaml and Cli Additional info: ***Important note*** The backing store as a resource in Noobaa UI looks ok and the pod,pvc,pv are all created and in state running and bound
This procedure is not fixed from the ui or yaml scenarios perspective. The OCS UI does not limit the resource name at all and the NooBaa Dashboard is allowing a 47 characters name limit instead of the required 43 characters. I've opened another bug for the OCS UI but we still need to fix in the NooBaa dashboard as well. (OCS UI bug: https://bugzilla.redhat.com/show_bug.cgi?id=1917395) The Yaml with this issue should be rejected but instead it is created and getting stuck both in ocs and in noobaa. OCP: 4.7.0-0.nightly-2021-01-17-065043 OCS: 4.7.0-231.ci
OCS: ocs-operator.v4.7.0-250.ci OCP: 4.7.0-0.nightly-2021-02-02-223803
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: Red Hat OpenShift Container Storage 4.7.0 security, bug fix, and enhancement 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:2041