Bug 1859520

Summary:	Missing noobaa endpoint in storageCluster CR for LSO deployment on I3
Product:	[Red Hat Storage] Red Hat OpenShift Container Storage	Reporter:	Petr Balogh <pbalogh>
Component:	documentation	Assignee:	Anjana Suparna Sriram <asriram>
Status:	CLOSED DUPLICATE	QA Contact:	Petr Balogh <pbalogh>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.5	CC:	etamir, nberry, ocs-bugs
Target Milestone:	---	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-09-14 09:42:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Petr Balogh 2020-07-22 10:20:10 UTC

Description of problem (please be detailed as possible and provide log
snippests):
More details in this BZ https://bugzilla.redhat.com/show_bug.cgi?id=1859516

From 4.5 there is new pod: noobaa-endpoint which IMO should be part of the limits for LSO deployment.

Another issue is that CPU limits now probably needs to be string values instead of integers as we see in this issue:
https://github.com/red-hat-storage/ocs-ci/issues/2551

Version of all relevant components (if applicable):
OCS 4.5
OCP 4.5



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?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


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


Steps to Reproduce:
1. Details are described in linked BZ
2.
3.


Actual results:


Expected results:


Additional info:

Comment 2 Petr Balogh 2020-07-22 10:22:43 UTC

I think that if the OCS 4.4 will be installed on OCP 4.5 we will hit the same issue described with integer/string error.

Once we have some clarity on this we need to maybe update the 4.4 documentation as well if the behavior in OCP 4.5 changed.

Comment 3 Petr Balogh 2020-07-29 12:42:50 UTC

Regards to integer change to string see reply here:
https://bugzilla.redhat.com/show_bug.cgi?id=1859386#c17

It looks like OCS issue which should be fixed.

Comment 5 Neha Berry 2020-09-14 09:42:23 UTC

We have removed all noobaa limits from OCS 4.5 docs. The final content for StorageCluster.yaml was decided via Bug 1858283(engg Bug 1859516#c18) and already updated in the 4.5 deployment guide [1]

Hence, IMO, we can close this BZ.

We would need some changes for upgrade docs, but that is handled via Bug 1877392

[1] - https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.5/html-single/deploying_openshift_container_storage_using_amazon_web_services/index?lb_target=preview#creating-openshift-container-storage-cluster-on-amazon-ec2_local-storage

*** This bug has been marked as a duplicate of bug 1858283 ***