Read whitebox DB password from osp-secret - #4090
Open
ashu-011 wants to merge 1 commit into
Open
Conversation
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
install_yamls PR openstack-k8s-operators/install_yamls#1158 replaced hardcoded passwords with dynamically generated per-service secrets. Whitebox Tempest needs Galera root credentials via whitebox-database.password, which must match DbRootPassword in osp-secret. Fetch DbRootPassword from osp-secret at runtime and inject it into tempestconfRun.overrides (including workflow steps) before applying the Tempest CR.
ashu-011
force-pushed
the
fix/whitebox-db-password
branch
from
August 6, 2026 05:52
57d678e to
29ee50b
Compare
sbauza
added a commit
to sbauza/ci-framework
that referenced
this pull request
Aug 6, 2026
install_yamls PR openstack-k8s-operators/install_yamls#1158 replaced hardcoded passwords with dynamically generated per-service secrets. The whitebox_tempest_plugin tempestconf overrides still reference the old hardcoded whitebox-database.password value ("12345678"), causing Access Denied errors against Galera. As a short-term fix, pin DB_ROOT_PASSWORD in the HCI ceph scenario so that the deployed Galera root password matches what whitebox tempest expects. A proper long-term fix (reading DbRootPassword from osp-secret at runtime) is tracked in openstack-k8s-operators#4090. Signed-off-by: Sylvain Bauza <sbauza@redhat.com> Assisted-by: Cursor <cursoragent@cursor.com> Co-authored-by: Cursor <cursoragent@cursor.com>
sbauza
added a commit
to sbauza/ci-framework
that referenced
this pull request
Aug 6, 2026
install_yamls PR openstack-k8s-operators/install_yamls#1158 replaced hardcoded passwords with dynamically generated per-service secrets. The whitebox_tempest_plugin tempestconf overrides still reference the old hardcoded whitebox-database.password value ("12345678"), causing Access Denied errors against Galera. As a short-term fix, pin DB_ROOT_PASSWORD in the HCI ceph scenario so that the deployed Galera root password matches what whitebox tempest expects. A proper long-term fix (reading DbRootPassword from osp-secret at runtime) is tracked in openstack-k8s-operators#4090. Signed-off-by: Sylvain Bauza <sbauza@redhat.com> Assisted-by: Cursor <cursoragent@cursor.com> Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
install_yamls PR openstack-k8s-operators/install_yamls#1158 replaced hardcoded passwords with dynamically generated per-service secrets. Whitebox Tempest needs Galera root credentials via whitebox-database.password, which must match DbRootPassword in osp-secret.
Fetch DbRootPassword from osp-secret at runtime and inject it into tempestconfRun.overrides (including workflow steps) before applying the Tempest CR.