Skip to content

Conversation

@mauricioharley
Copy link

Playbook Separation (based on PR #3543)

When performing Barbican adoption from OSP 17.1 to RHOSO 18, the image
creation and kustomization need to happen at different times. This PR
separates the logic into:

  • barbican-prepare-proteccio.yml: Creates custom Barbican images with
    HSM client software and sets up OpenShift secrets (certificates and login)
  • barbican-enable-proteccio.yml: Applies kustomization to configure
    the Barbican control plane to use Proteccio HSM

HSM Password Loading Fix

Added logic to load cifmw_hsm_password from the Zuul secret file at
/var/tmp/qe-secrets/proteccio_pin.yaml when the variable is not already
defined. This file is created by the qe-creds-crc.yaml pre-run playbook
in the components-integration-config repository.

This fixes the issue where the playbook would fail with:

'cifmw_hsm_password' is undefined

This commit separates the Barbican Proteccio playbook into two parts
to support adoption scenarios where image creation and kustomization
need to happen at different times:

- barbican-prepare-proteccio.yml: Creates custom Barbican images with
  HSM client and sets up OpenShift secrets
- barbican-enable-proteccio.yml: Applies kustomization to configure
  Barbican to use Proteccio HSM

Additionally, this adds support for loading the HSM password from a
Zuul secret file (/var/tmp/qe-secrets/proteccio_pin.yaml) when the
cifmw_hsm_password variable is not already defined. This file is
created by the qe-creds-crc.yaml pre-run playbook in the
components-integration-config repository.

This change is based on PR openstack-k8s-operators#3543 by Ade Lee, with the addition of
the HSM password file loading logic.

Jira: OSPRH-20112

Signed-off-by: Mauricio Harley <mharley@redhat.com>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 25, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign danpawlik for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant