Irreconcilable Differences scale-up test: apply disk discovering on vSphere scale-up test - #6343
Irreconcilable Differences scale-up test: apply disk discovering on vSphere scale-up test#6343proietfb wants to merge 2 commits into
Conversation
…ble disk paths at runtime
On vSphere, the PVSCSI controller's PCI address is not guaranteed to be
fixed across all VM hardware versions, making /dev/disk/by-path/ entries
non-predictable at test-write time. Additionally, the raw /dev/sdb /dev/sdc
names passed to the Ignition MachineConfig caused the newly provisioned VM
to boot without ever obtaining a network IP address, timing out the
WaitUntilReady("10m") call with a context deadline exceeded error.
Apply the same probe-node pattern already used for AWS NVMe disks.
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughThe irreconcilable machine config test adds runtime discovery of non-boot vSphere SCSI disks, extends probe-node setup to vSphere, selects disk discovery by platform, validates two disks, and broadens scale-up node selection. ChangesPlatform-specific disk discovery and scaling
Estimated code review effort: 3 (Moderate) | ~20 minutes Suggested reviewers: Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional. ❌ Failed checks (1 error, 2 warnings)
✅ Passed checks (12 passed)
✨ Finishing Touches🧪 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 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: proietfb 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 |
|
/payload-job periodic-ci-openshift-machine-config-operator-release-5.0-periodics-e2e-vsphere-mco-disruptive-techpreview |
|
@proietfb: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/18b2b8f0-89c3-11f1-9de2-5f4a7266e8dc-0 |
There was a problem hiding this comment.
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 `@test/extended-priv/mco_irreconcilablechanges.go`:
- Around line 248-258: Replace the branch-local := declarations in the platform
conditional with assignments to the outer discoveredDisks declared before it, so
the AWS and vSphere discovery results remain available when assigning disks
afterward. Preserve the existing discovery functions and length assertions.
🪄 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: openshift/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 6cd1507a-817e-4412-a440-79731d148d7b
📒 Files selected for processing (1)
test/extended-priv/mco_irreconcilablechanges.go
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
|
/payload-job periodic-ci-openshift-machine-config-operator-release-5.0-periodics-e2e-vsphere-mco-disruptive-techpreview |
|
@proietfb: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b34f25a0-89c4-11f1-8dad-1493eca28f53-0 |
|
/hold |
[PolarionID:84219] vSphere scale-up test by discovering stable disk paths at runtime
On vSphere, the PVSCSI controller's PCI address is not guaranteed to be fixed across all VM hardware versions, making /dev/disk/by-path/ entries non-predictable at test-write time. Additionally, the raw /dev/sdb /dev/sdc names passed to the Ignition MachineConfig caused the newly provisioned VM to boot without ever obtaining a network IP address, timing out the WaitUntilReady("10m") call with a context deadline exceeded error.
Apply the same probe-node pattern already used for AWS NVMe disks.
- What I did
In place discovery of provisioned disks by-path instead of by-name
Summary by CodeRabbit