Skip to content

OSAC-3276: fix volume reconciler test — drop obsolete PVCRef assertion - #366

Closed
danielerez wants to merge 1 commit into
osac-project:mainfrom
danielerez:fix/volume-reconciler-pvcref-test
Closed

OSAC-3276: fix volume reconciler test — drop obsolete PVCRef assertion#366
danielerez wants to merge 1 commit into
osac-project:mainfrom
danielerez:fix/volume-reconciler-pvcref-test

Conversation

@danielerez

@danielerez danielerez commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Problem

main is currently red on Run unit tests and Check Go and proto code. The volume package fails to
compile:

internal/controllers/volume/volume_reconciler_function_test.go:103:15:
spec.PVCRef undefined (type "…/osac-operator/api/v1alpha1".VolumeSpec
has no field or method PVCRef)

Root cause

A semantic merge conflict between two PRs (both by @akshaynadkarni), each green in isolation but incompatible
once both landed:

Fix

Remove the stale Expect(spec.PVCRef).To(BeNil()) assertion. PVCRef no longer exists on VolumeSpec; PVC/PV
tracking is planned for a future VolumeAttachment resource (OSAC-3278), not the Volume itself, so there is
nothing to re-point the assertion at.

  • 1 line removed
  • go vet ./internal/controllers/volume/ passes; gofmt clean

The volume reconciler unit test asserted `spec.PVCRef` on the CRD
VolumeSpec, but that field no longer exists, so the `volume` package
fails to compile and both "Run unit tests" and "Check Go and proto
code" are red on main:

  internal/controllers/volume/volume_reconciler_function_test.go:103:15:
    spec.PVCRef undefined (type v1alpha1.VolumeSpec has no field or
    method PVCRef)

Root cause is a semantic merge conflict between two PRs, both authored
by @akshaynadkarni:

  - osac-project#341 (OSAC-3274) removed pvcRef/pvRef from VolumeSpec, merged first
    (2026-08-17).
  - osac-project#339 (OSAC-3276) added the reconciler test referencing spec.PVCRef,
    merged second (2026-08-18) off a branch that predated osac-project#341 and was
    not re-validated against the updated main.

Each PR was green in isolation; combined on main they do not compile.
Remove the stale assertion to restore the build. PVC/PV tracking is
planned for a future VolumeAttachment resource (OSAC-3278), not the
Volume itself, so there is nothing to re-point the assertion at.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@openshift-ci-robot

openshift-ci-robot commented Aug 18, 2026

Copy link
Copy Markdown

@danielerez: This pull request references OSAC-3276 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 task to target the "5.1.0" version, but no target version was set.

Details

In response to this:

Problem

main is currently red on Run unit tests and Check Go and proto code. The volume package fails to
compile:

internal/controllers/volume/volume_reconciler_function_test.go:103:15:
spec.PVCRef undefined (type "…/osac-operator/api/v1alpha1".VolumeSpec
has no field or method PVCRef)

Root cause

A semantic merge conflict between two PRs (both by @akshaynadkarni), each green in isolation but incompatible
once both landed:

Fix

Remove the stale Expect(spec.PVCRef).To(BeNil()) assertion. PVCRef no longer exists on VolumeSpec; PVC/PV
tracking is planned for a future VolumeAttachment resource (OSAC-3278), not the Volume itself, so there is
nothing to re-point the assertion at.

  • 1 line removed
  • go vet ./internal/controllers/volume/ passes; gofmt clean

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 Aug 18, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danielerez

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 Aug 18, 2026

Copy link
Copy Markdown

Important

Review available on request

  • 🔍 Trigger review

Reviews should be triggered manually for repositories with fewer than 10 stars. Select Trigger review above or comment @coderabbitai review to review the latest changes. For a full review, comment @coderabbitai full review.

⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: 43d34fae-1e38-4e32-a179-f3f86dce3c53


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.

@fullsend-ai-review

fullsend-ai-review Bot commented Aug 18, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 3:28 PM UTC · Completed 3:36 PM UTC

Commit: e6ab420 · View workflow run →

@fullsend-ai-review

fullsend-ai-review Bot commented Aug 18, 2026

Copy link
Copy Markdown

Looks good to me


Labels: PR fixes a compilation error caused by a semantic merge conflict (stale test assertion references a removed struct field)

Previous run

Looks good to me

fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review fullsend-ai-review Bot added the requires-manual-review Review requires human judgment label Aug 18, 2026
@danielerez
danielerez marked this pull request as ready for review August 18, 2026 16:06
@openshift-ci
openshift-ci Bot requested review from rccrdpccl and rgolangh August 18, 2026 16:06
@danielerez
danielerez requested review from omer-vishlitzky and removed request for rccrdpccl and rgolangh August 18, 2026 16:06
@fullsend-ai-review

fullsend-ai-review Bot commented Aug 18, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 4:07 PM UTC · Completed 4:16 PM UTC

Commit: e6ab420 · View workflow run →

@fullsend-ai-review fullsend-ai-review Bot added ready-for-merge All reviewers approved — ready to merge bug Something isn't working and removed requires-manual-review Review requires human judgment labels Aug 18, 2026
@danielerez danielerez closed this Aug 18, 2026
auto-merge was automatically disabled August 18, 2026 17:56

Pull request was closed

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

Labels

approved bug Something isn't working jira/valid-reference ready-for-merge All reviewers approved — ready to merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants