OCPSTRAT-3298: Add IEEE 829 test plan for NodePool rollout control - #1
redhat-chai-bot wants to merge 5 commits into
Conversation
…t control Add manual test plan covering the three e2e scenarios from HyperShift PR #8698: management-side image changes must not trigger rollouts, spec-driven MachineConfig changes must trigger rollouts and update hash annotations, and operator upgrade annotation seeding must occur without triggering rollouts. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
redhat-chai-bot
changed the title
| ``` | ||
| oc get nodepool upgrade-seed-test -n <hc-namespace> -o jsonpath='{.metadata.annotations.hypershift\.openshift\.io/nodePoolCurrentRolloutConfig}' | ||
| ``` | ||
| Expected: a non-empty value appears within 1 minute. |
There was a problem hiding this comment.
Should it verify that re-seeded value equals BASELINE_ROLLOUT_HASH?
There was a problem hiding this comment.
I checked OperatorUpgradeNoRolloutTest in HyperShift PR #8698. It does not record a baseline rollout-hash value or assert that the re-seeded value equals one. It asserts that the annotation is restored within one minute and non-empty, while separately verifying UpdatingConfig remains False, nodePoolCurrentConfig is unchanged, and node identities are preserved.
The plan intentionally mirrors those automated assertions, so I did not add a stronger equality requirement only to the manual fallback path. If the upstream e2e test is strengthened to assert baseline-hash equality, the plan should be updated to match.
AI-generated. Review for accuracy.
2 participants
Summary
Add
plans/ocpstrat-3298.md, an IEEE 829-2008-compliant manual test plan for the NodePool rollout-control behavior covered by openshift/hypershift#8698.Coverage
The plan documents three scenarios from the HyperShift e2e coverage:
The plan maps verified OCPSTRAT-3298 acceptance criteria to these scenarios and makes automated e2e tests primary, automated unit tests supplementary, and manual procedures fallback-only when automation is infeasible.
Validation
plans/ocpstrat-3298.md.OCPSTRAT-9238references remain.