NO-ISSUE: fix Volume reconciler test referencing removed VolumeSpec.PVCRef - #367
Conversation
…VCRef Cross-package semantic merge conflict between two PRs that merged back-to-back: - osac-project#341 (OSAC-3274) removed pvcRef/pvRef from VolumeSpec in osac-operator/api/v1alpha1. - osac-project#339 (OSAC-3276) added a Volume reconciler test in fulfillment-service asserting spec.PVCRef. PR osac-project#339 was branched before osac-project#341 merged, so it compiled against a VolumeSpec that still had PVCRef and passed its own CI. After both landed on main, the combined tree fails to compile: volume_reconciler_function_test.go:103:15: spec.PVCRef undefined (type v1alpha1.VolumeSpec has no field or method PVCRef) git merges both textually clean because neither touches the same lines; the breakage is only visible when the test package is built. Fix: drop the orphaned `Expect(spec.PVCRef).To(BeNil())` assertion. buildSpec() never populated PVCRef and no other code references it, so removal is the correct resolution (not restoring the field). Verified: go vet + go test ./internal/controllers/volume/ pass. Assisted-by: Claude Code <noreply@anthropic.com> Signed-off-by: Marc Sluiter <msluiter@redhat.com>
|
@slintes: This pull request explicitly references no jira issue. DetailsIn response to this:
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. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: osac-project/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
Included review availability: Your plan includes up to 1 review per rolling hour; 0 remain after this review. WalkthroughThe change removes the Changes
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This localized test-only change removes an assertion for a field that no longer exists, with the affected package passing verification. No actionable merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 11✅ Passed checks (11 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
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. Comment |
|
🤖 Finished Review · ✅ Success · Started 3:28 PM UTC · Completed 3:34 PM UTC Commit: |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: akshaynadkarni, slintes 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 |
|
Looks good to me Labels: PR fixes a volume reconciler test — storage domain |
84db065
osac-project#410, osac-project#417 (osac-project#645) At time of publishing this PR ( Aug 31 2026 ) Whats present in the osac-test-infra but missing from the osac mono repo are - PR#410: [OSAC-4272](https://redhat.atlassian.net/browse/OSAC-4272): register k8s_only NetworkClass manager for E2E - osac-project#410 - PR#417 : Storage tier protocol refactor (grpc_client.py) - PR#367: Per-disk storage tier tests (8 files) --------- Signed-off-by: Carlo Lobrano <c.lobrano@gmail.com> Signed-off-by: Ori Amizur <oamizur@redhat.com> Co-authored-by: Carlo Lobrano <c.lobrano@gmail.com> Co-authored-by: Ori Amizur <60868946+ori-amizur@users.noreply.github.com> Co-authored-by: Will Gordon <wgordon@redhat.com>
…osac-project#670) Ported from osac-project/osac-test-infra#423 After OSAC-3632, AAP will resolve a StorageClass per disk from the disk's storageTier field. When a disk has no tier, provisioning will fail. The [OSAC-3633](https://redhat.atlassian.net/browse/OSAC-3633) PR (osac-project#367) added the storage tier pattern but only in its new tests; pre-existing VM-provisioning tests still create tier-less instances. Changes: - Add boot_disk_storage_tier parameter to GRPCClient.create_compute_instance and GRPCClient.create_compute_instance_with_disk_image helpers - Move default_storage_tier fixture from tests/vmaas/conftest.py to root tests/conftest.py so all suites (catalog, references) can use it - Update all gRPC-based ComputeInstance creation calls across vmaas, catalog, and references suites to set boot_disk_storage_tier - Update _ci_create_data helper and inline gRPC data in references tests to include boot_disk with storage_tier Signed-off-by: Carlo Lobrano <c.lobrano@gmail.com>
…osac-project#670) Ported from osac-project/osac-test-infra#423 After OSAC-3632, AAP will resolve a StorageClass per disk from the disk's storageTier field. When a disk has no tier, provisioning will fail. The [OSAC-3633](https://redhat.atlassian.net/browse/OSAC-3633) PR (osac-project#367) added the storage tier pattern but only in its new tests; pre-existing VM-provisioning tests still create tier-less instances. Changes: - Add boot_disk_storage_tier parameter to GRPCClient.create_compute_instance and GRPCClient.create_compute_instance_with_disk_image helpers - Move default_storage_tier fixture from tests/vmaas/conftest.py to root tests/conftest.py so all suites (catalog, references) can use it - Update all gRPC-based ComputeInstance creation calls across vmaas, catalog, and references suites to set boot_disk_storage_tier - Update _ci_create_data helper and inline gRPC data in references tests to include boot_disk with storage_tier Signed-off-by: Carlo Lobrano <c.lobrano@gmail.com>
What
Removes an orphaned test assertion that broke the build on
main:Why — cross-package semantic merge conflict
Two PRs merged back-to-back with a conflict that neither CI could catch:
pvcRef/pvReffromVolumeSpecinosac-operator/api/v1alpha1.fulfillment-serviceassertingspec.PVCRef.PR 339 was branched before PR 341 merged, so it compiled against a
VolumeSpecthat still hadPVCRefand passed its own CI. After both landed, the combined tree no longer compiles.gitmerges both textually clean because they touch different files — the breakage only surfaces when the test package is built.Fix
Drop the stale
Expect(spec.PVCRef).To(BeNil())assertion.buildSpec()never populatedPVCRefand nothing else in the repo references it, so removal is the correct resolution (not restoring the field).Verification
go vet ./internal/controllers/volume/— cleango test ./internal/controllers/volume/— passFYI
🤖 Generated with Claude Code
Summary by CodeRabbit