NO_ISSUE: use osac-installer's built-in refresh and prepare scripts#79422
Conversation
The boot step maintained inline heredoc copies of refresh-after-snapshot.sh and prepare-fulfillment-service.sh that were mounted into the osac-installer container, overriding the built-in versions. These copies were added when the scripts hadn't been merged upstream yet (PR openshift#95, PR openshift#99). Both PRs are now merged. Remove the heredocs and volume mount overrides so the osac-installer image's built-in scripts are used directly. This picks up the refresh improvements from osac-installer PR openshift#99: - Keycloak realm sync via admin API - Fulfillment controller credentials recreation - Keycloak route domain patching - Parallel rollout waits after kustomize apply - User password setup
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
WalkthroughThis PR removes 137 lines from the boot commands script, eliminating the creation and SSH injection of two custom scripts ( Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danmanor, omer-vishlitzky The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
|
/pj-rehearse pull-ci-osac-project-fulfillment-service-main-e2e-vmaas pull-ci-osac-project-osac-installer-main-e2e-vmaas pull-ci-osac-project-osac-test-infra-main-e2e-vmaas pull-ci-osac-project-osac-operator-main-e2e-vmaas |
|
@omer-vishlitzky: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse ack |
|
@omer-vishlitzky: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@omer-vishlitzky: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
…shift#79422) The boot step maintained inline heredoc copies of refresh-after-snapshot.sh and prepare-fulfillment-service.sh that were mounted into the osac-installer container, overriding the built-in versions. These copies were added when the scripts hadn't been merged upstream yet (PR openshift#95, PR openshift#99). Both PRs are now merged. Remove the heredocs and volume mount overrides so the osac-installer image's built-in scripts are used directly. This picks up the refresh improvements from osac-installer PR openshift#99: - Keycloak realm sync via admin API - Fulfillment controller credentials recreation - Keycloak route domain patching - Parallel rollout waits after kustomize apply - User password setup
Summary
Remove inline heredoc copies of
refresh-after-snapshot.shandprepare-fulfillment-service.shfrom the CI boot step. These were temporary overrides added when the scripts hadn't been merged into osac-installer yet. Both are now merged (osac-installer PR #95, PR #99).The osac-installer image's built-in scripts are now used directly, picking up improvements from PR #99:
Changes
-v /root/refresh-after-snapshot.sh:...and-v /root/prepare-fulfillment-service.sh:...)Test plan
OSAC Cluster-Tool Boot Step: Eliminate Custom Script Injection
This PR updates the OSAC (OpenShift Advanced Cluster) CI infrastructure to use built-in scripts from the osac-installer container image rather than injecting custom script overrides.
What Changed
The PR modifies the cluster-tool boot step for the osac-project in the CI step registry. Previously, the boot workflow had to work around incomplete osac-installer functionality by:
refresh-after-snapshot.shandprepare-fulfillment-service.shWhy This Matters
Both required scripts have now been merged into osac-installer itself (via osac-installer PRs
#95and#99), making the custom script injection unnecessary. By removing this workaround, the CI now benefits from improvements added to osac-installer, including:Infrastructure Impact
The boot step now simplifies its container invocation by only mounting essential CI configuration (kubeconfig, pull-secret, AAP license) into the installer container, then calling the built-in scripts directly. This reduces script duplication from ~137 lines and removes the complexity of managing custom script overrides across the CI workflow.
Test Coverage
The change is expected to be validated by the rehearsal e2e-vmaas job.