Bug 1819549
| Summary: | [GSS] noobaa StatefulSet doesn't inherit cluster-wide proxy settings and fails to create first.bucket on VMware | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Container Storage | Reporter: | Vagner Farias <vfarias> |
| Component: | Multi-Cloud Object Gateway | Assignee: | Ohad <omitrani> |
| Status: | CLOSED ERRATA | QA Contact: | Parikshith <pbyregow> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2 | CC: | assingh, bkunal, dzaken, ebenahar, edonnell, etamir, fgiloux, hnallurv, nbecker, ocs-bugs, omitrani, ratamir, rcyriac, tdesala |
| Target Milestone: | --- | ||
| Target Release: | OCS 4.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 4.5.0-444.ci | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-09-15 10:16:04 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: | |||
| Attachments: | |||
|
Description
Vagner Farias
2020-04-01 03:13:36 UTC
Created attachment 1675284 [details]
oc describe deploy noobaa-operator (to demonstrate proxy settings)
Created attachment 1675285 [details]
oc describe sts noobaa-core
Note that cluster-wide proxy settings aren't available.
Created attachment 1675286 [details]
screenshot of error shown in OCP dashboard
Hi @vagner. the description is a bit unclear. do you mean that the default backing-store is not created? can you attach OCS must-gather diagnostics or noobaa operator+core logs? @ashish thanks for the diags. In the must gather I don't see any problem. both noobaa and the default backingstore are healthy and in a ready state. if there are other logs that show the problem then I can debug it. I don't know how the cluster-wide proxy works exactly in OCP, or why noobaa-core sts did not get the proxy settings as noobaa-operator did. we can propagate any proxy settings from noobaa-operator to noobaa-core, but I don't think this is the way it should work Created attachment 1675839 [details]
ocs must-gather
(In reply to Danny from comment #5) > Hi @vagner. > the description is a bit unclear. do you mean that the default backing-store > is not created? Correct. > > can you attach OCS must-gather diagnostics or noobaa operator+core logs? OCS must-gather is now attached to this bz. How do I provider noobaa operator+core logs? Created attachment 1675840 [details]
diagnostics gathered from noobaa management interface
From the attached MG I can verify that not all deployments and statefulsets have the PROXY_* environment variables set. A closer examination reveal that only the deployments created by OLM (the various operators' deployments) have the PROXY_* environment variables set up properly. The following documentation https://access.redhat.com/documentation/en-us/openshift_container_platform/4.4/html/operators/olm-adding-operators-to-a-cluster suggests (section 4.2) that the OLM is the one responsible for managing these envs for the operators' deployments, specifically the paragraph: > If a cluster-wide egress proxy is configured, applications created from Operators using the Operator Lifecycle Manager (OLM) inherit the cluster-wide proxy settings > on their Deployments and Pods. Cluster administrators can also override these proxy settings by configuring the Operator’s Subscription. and > OLM handles these environment variables as a unit; if at least one of them is set, all three are considered overridden > and the cluster-wide defaults are not used for the subscribed Operator’s Deployments. From this, I can deduce that setting these env variables is not an automatic process and that the controller for each deployment/statefulset has the responsibility to set them. If this is indeed the case the resolution for this BZ is to set these environment vars for the noobaa-core deployment in the noobaa operator reconcile loop. I fix was issued in the upstream project, see the links section 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 (Red Hat OpenShift Container Storage 4.5.0 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/RHBA-2020:3754 |