Skip to content

infra: update virt template vm creation test case #131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
RoniKishner wants to merge 1 commit into
base: main
Choose a base branch
from
+11 −3
Open

infra: update virt template vm creation test case #131

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 11 additions & 3 deletions stps/sig-infra/virtual-machine-template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -234,7 +234,7 @@ The following conditions must be met before testing can begin:
- *Priority:* P0

- **[CNV-73392]** — As a VM owner, I want to create a VM directly from a template in one step where the product supports it
- *Test Scenario:* [Tier 1] Validate the supported single-step create-from-template flow, including expected namespace placement and access behavior.
- *Test Scenario:* [Tier 2] Validate the supported create-from-template flow using a common instance type: the resulting VM references the selected instance type correctly, and the VM is placed in the expected namespace.

@0xFelix 0xFelix Aug 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Shouldn't it be a T1 test case in kubevirt/virt-template?

- *Priority:* P0

- **[CNV-73392]** — As a cluster admin, I want to restrict users to create VMs only from approved templates
Expand Down Expand Up @@ -269,8 +269,16 @@ The following conditions must be met before testing can begin:
- *Test Scenario:* [Tier 2] Validate upgrade continuity for existing templates and vm template requests, including post-upgrade template usability.
- *Priority:* P1

- **[CNV-73392]** — As a template author, I want the cluster to reject templates that would always produce an invalid VM when defaults fill required parameters (OpenShift Virtualization 4.22)
- *Test Scenario:* [Tier 2] Validate admission behavior for invalid-by-default templates and acceptance behavior for valid templates under defaulted parameters.
- **[CNV-73392]** — As a template author, I want saving a well-formed template to succeed so I can reuse it to provision VMs
- *Test Scenario:* [Tier 2] Create a template whose default parameter values produce a complete, valid VM configuration and confirm the template is available for use.

@0xFelix 0xFelix Aug 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Isn't that covered by T1 already?

- *Priority:* P2

- **[CNV-73392]** — As a VM owner, I want VMs created from my template to run as expected with the sizing and preferences I specified using instance types

@0xFelix 0xFelix Aug 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Isn't this case a dup of the one on L237?

- *Test Scenario:* [Tier 2] Provision a VM from a template using instance types and verify the resulting VM has the specified fields in the template.
- *Priority:* P2

- **[CNV-73392]** — As a template author, I want the platform to reject a template whose defaults would always produce an unusable VM and to tell me clearly why it was rejected

@0xFelix 0xFelix Aug 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Covered in unit/integration tests in T1 already? Could be extended in T1 too.

- *Test Scenario:* [Tier 2] Attempt to create a template whose default parameter values produce an invalid VM configuration; verify the save is rejected with a clear, actionable error message and no template resource is created.
- *Priority:* P2

- **[CNV-73392]** — As a cluster admin, I want template workflows unavailable when the Template capability is disabled
Expand Down
Loading