Skip to content
This repository was archived by the owner on Sep 9, 2026. It is now read-only.

OSAC-1768: Enable storage controller in CI values - #336

Merged
openshift-merge-bot[bot] merged 1 commit into
osac-project:mainfrom
eliorerz:OSAC-1768-enable-storage-controller
Jun 26, 2026
Merged

openshift-merge-bot[bot] merged 1 commit into
osac-project:mainfrom
eliorerz:OSAC-1768-enable-storage-controller

Conversation

@eliorerz

@eliorerz eliorerz commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Summary

Context

The Storage Controller populates Tenant.Status.StorageClasses, which the ComputeInstance Controller reads and passes to AAP as tenant_storage_classes. Without it, all VM provisioning fails with "no tenant_storage_classes available".

Test plan

Summary by CodeRabbit

  • New Features

    • Enabled additional storage management capabilities in CI environments by turning on storage-related operator controls.
  • Chores

    • Updated the bundled operator to a newer revision across the CI and kustomization configurations.

@openshift-ci-robot

openshift-ci-robot commented Jun 24, 2026

Copy link
Copy Markdown

@eliorerz: This pull request references OSAC-1768 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

Context

The Storage Controller populates Tenant.Status.StorageClasses, which the ComputeInstance Controller reads and passes to AAP as tenant_storage_classes. Without it, all VM provisioning fails with "no tenant_storage_classes available".

Test plan

Instructions 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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci

openshift-ci Bot commented Jun 24, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eliorerz

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

The pull request process is described 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

@coderabbitai

coderabbitai Bot commented Jun 24, 2026

Copy link
Copy Markdown

Review Change Stack

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository: osac-project/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: c958dfe1-b4ce-4581-a2eb-b18a930ea706

📥 Commits

Reviewing files that changed from the base of the PR and between c81b24a and 03789ee.

📒 Files selected for processing (4)
  • base/kustomization.yaml
  • base/osac-operator
  • values/caas-ci/values.yaml
  • values/vmaas-ci/values.yaml

Walkthrough

Updated the operator checkout, image tag overrides, and enabled storageController in both CI values files.

Changes

Operator update and controller enablement

Layer / File(s) Summary
Submodule reference bump
base/osac-operator, base/kustomization.yaml
Updates the operator subproject commit reference and the base image tag override to the new operator build.
Storage controller flags
values/caas-ci/values.yaml, values/vmaas-ci/values.yaml
Updates the operator image tag in both CI values files and adds storageController: true to each operator.controllers map.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested labels

lgtm

Suggested reviewers

  • akshaynadkarni
  • adriengentil
  • eranco74

Poem

A commit turned, the operator gleamed,
Two CI values files quietly agreed.
Storage awoke with a single bright flag,
A tidy little sync in the deployment bag.
⚙️

🚥 Pre-merge checks | ✅ 11
✅ Passed checks (11 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the main change: enabling the storage controller in CI values.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
No-Hardcoded-Secrets ✅ Passed No hardcoded secret values found in the touched YAMLs; only secret references/names, image tags, and URLs without embedded credentials.
No-Weak-Crypto ✅ Passed Touched files only update operator image tags and enable storageController; no weak-crypto primitives or secret comparisons are present.
No-Injection-Vectors ✅ Passed Touched files are config-only; scans found no SQL/shell/eval/pickle/yaml-load/innerHTML injection patterns.
Container-Privileges ✅ Passed Diff only bumps osac-operator refs and adds storageController:true; no privileged/hostPID/hostNetwork/hostIPC/SYS_ADMIN/allowPrivilegeEscalation changes found.
No-Sensitive-Data-In-Logs ✅ Passed No logging code or log messages were changed; the PR only updates image tags, a submodule pointer, and enables a controller flag in values.
Ai-Attribution ✅ Passed PR description and commit message mention no AI tool use; HEAD has no Co-Authored-By, Assisted-by, or Generated-by trailers.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@eliorerz
eliorerz force-pushed the OSAC-1768-enable-storage-controller branch 3 times, most recently from e87658e to c81b24a Compare June 25, 2026 15:31
Enable storageController in both vmaas-ci and caas-ci values so
the operator populates Tenant.Status.StorageClasses, which is
required for ComputeInstance provisioning via AAP.
@eliorerz
eliorerz force-pushed the OSAC-1768-enable-storage-controller branch from c81b24a to 03789ee Compare June 26, 2026 01:32

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@values/caas-ci/values.yaml`:
- Around line 20-25: The controllers.storageController flag is only present in
the CI values and is not yet wired into the chart, so it has no effect. Update
the chart schema and any templates that gate controller deployment to consume
controllers.storageController, using the existing controllers settings in the
values structure and the relevant controller rendering logic to enable/disable
the storage controller consistently.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: osac-project/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: c958dfe1-b4ce-4581-a2eb-b18a930ea706

📥 Commits

Reviewing files that changed from the base of the PR and between c81b24a and 03789ee.

📒 Files selected for processing (4)
  • base/kustomization.yaml
  • base/osac-operator
  • values/caas-ci/values.yaml
  • values/vmaas-ci/values.yaml

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Inline review comments failed to post. This is likely due to GitHub's internal server error or limits when posting large numbers of comments. If you are seeing this consistently it is likely a permissions issue. Please check "Moderation" -> "Code review limits" under your organization settings.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@values/caas-ci/values.yaml`:
- Around line 20-25: The controllers.storageController flag is only present in
the CI values and is not yet wired into the chart, so it has no effect. Update
the chart schema and any templates that gate controller deployment to consume
controllers.storageController, using the existing controllers settings in the
values structure and the relevant controller rendering logic to enable/disable
the storage controller consistently.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: osac-project/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: c958dfe1-b4ce-4581-a2eb-b18a930ea706

📥 Commits

Reviewing files that changed from the base of the PR and between c81b24a and 03789ee.

📒 Files selected for processing (4)
  • base/kustomization.yaml
  • base/osac-operator
  • values/caas-ci/values.yaml
  • values/vmaas-ci/values.yaml
🛑 Comments failed to post (1)
values/caas-ci/values.yaml (1)

20-25: 🗄️ Data Integrity & Integration | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

schema_file="$(fd -p 'values.schema.json' charts . | head -n1 || true)"
values_file="$(fd -p 'values.yaml' charts/osac charts . | head -n1 || true)"

echo '--- storageController references ---'
rg -n -C2 'storageController' charts values . || true

if [[ -n "${schema_file}" ]]; then
  echo
  echo "--- schema hits: ${schema_file} ---"
  rg -n -C2 '"storageController"|storageController' "${schema_file}" || true
fi

if [[ -n "${values_file}" ]]; then
  echo
  echo "--- chart values hits: ${values_file} ---"
  rg -n -C2 'storageController' "${values_file}" || true
fi

Repository: osac-project/osac-installer

Length of output: 1358


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '--- files containing storageController ---'
rg -n -C2 'storageController' charts values base overlays . || true

schema='charts/osac/values.schema.json'
values='charts/osac/ci/bundled-postgres-values.yaml'

echo
echo "--- schema excerpt ---"
if [[ -f "$schema" ]]; then
  rg -n -C3 '"controllers"|storageController' "$schema" || true
fi

echo
echo "--- bundled postgres values excerpt ---"
if [[ -f "$values" ]]; then
  rg -n -C3 'storageController|controllers' "$values" || true
fi

Repository: osac-project/osac-installer

Length of output: 1522


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '--- files containing storageController ---'
rg -n -C2 'storageController' charts values base overlays . || true

schema='charts/osac/values.schema.json'
values='charts/osac/ci/bundled-postgres-values.yaml'

echo
echo "--- schema excerpt ---"
if [[ -f "$schema" ]]; then
  rg -n -C3 '"controllers"|storageController' "$schema" || true
fi

echo
echo "--- bundled postgres values excerpt ---"
if [[ -f "$values" ]]; then
  rg -n -C3 'storageController|controllers' "$values" || true
fi

Repository: osac-project/osac-installer

Length of output: 1522


Wire controllers.storageController through the chart schema and templates. It only appears in the CI values files, so the flag has no effect until the chart actually consumes it.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@values/caas-ci/values.yaml` around lines 20 - 25, The
controllers.storageController flag is only present in the CI values and is not
yet wired into the chart, so it has no effect. Update the chart schema and any
templates that gate controller deployment to consume
controllers.storageController, using the existing controllers settings in the
values structure and the relevant controller rendering logic to enable/disable
the storage controller consistently.

Source: Coding guidelines

@eliorerz eliorerz added the lgtm label Jun 26, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit 8e7b069 into osac-project:main Jun 26, 2026
8 checks passed
@eliorerz
eliorerz deleted the OSAC-1768-enable-storage-controller branch June 26, 2026 03:15
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants