Bug 2274193
| Summary: | cleartext postgres password in noobaa-db-pg init container logs | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Dmitry Mishin <mishindm> |
| Component: | Multi-Cloud Object Gateway | Assignee: | Nimrod Becker <nbecker> |
| Status: | CLOSED ERRATA | QA Contact: | Tiffany Nguyen <tunguyen> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.14 | CC: | csharpe, odf-bz-bot, tdesala |
| Target Milestone: | --- | ||
| Target Release: | ODF 4.16.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 4.16.0-73 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-07-17 13:18:43 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: | |||
Verified using ODF 4.16.0-76. There is no postgres password display in noobaa-db-pg logs. Confirmed that init container for Postgres DB pod was removed. 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 (Important: Red Hat OpenShift Data Foundation 4.16.0 security, enhancement & bug fix 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-2024:4591 |
Description of problem (please be detailed as possible and provide log snippests): init container for noobaa postgres db has "sh -x" oc get sts noobaa-db-pg -o yaml | grep -A 4 command: - command: - sh - -x - /init/initdb.sh env: As result in init container log we see oc logs noobaa-db-pg-0 --tail=-1 -c initialize-database | grep set=password ++ _psql --set=username=noobaa --set=password=CpYG7qwjZvrHhA== ++ psql --set ON_ERROR_STOP=1 --set=username=noobaa --set=password=CpYG7qwjZvrHhA== Version of all relevant components (if applicable): stable-4.14 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)? 1 Can this issue reproducible? yes Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. create a noobaa CR 2. check the postgres sts logs 3. Actual results: Expected results: Additional info: