Format:

Export:

Test cases(24 of 50)

Show

Priority

Category

0/24 completed0%

Complete prerequisites first ([PRE-01](PRE-01) → [PRE-08](PRE-08) minimum) before running these tests. Go to prerequisites

Verify golden image import and PVC clone

Create and boot first VM from template (RHEL 9)

Masquerade uses OVN-K over eno2/br-ex — no bridge setup required

VM live migration (SNO: expected failure)

NOT POSSIBLE on SNO — live migration requires ≥2 nodes. Documented as an expected failure.

Create VM snapshots and perform restore

Test on local storage

Clone VM and use as template (Golden VM pattern)

Pod network (masquerade) and VM access via Service

Optimal for single-NIC — OVN-K over eno2/br-ex, no bridge setup required

VM directly reachable on LAN (OVN-K localnet) -- ⚠ HETZNER TOS VIOLATION

✗ NOT TESTABLE ON HETZNER -- TOS violation! OVN-K localnet works technically (verified 30.06.2026: ping successful), but any VM MAC that reaches eno2/the physical switch via this interface is detected and reported by Hetzner as an unauthorised MAC (server suspension threatened). Only the registered server MAC is permitted.

SR-IOV – high-performance networking (HW missing)

✗ NOT TESTABLE — SR-IOV requires a dedicated second NIC (Intel X710, Mellanox ConnectX). The sole NIC eno2 is consumed by OVN-K and cannot be used for SR-IOV VFs.

Test VLAN isolation — VMs in separate software bridges

Variant A uses pure software bridges br-net1/2/3 (port: []) — no VM MAC leaves eno2/the physical switch, no TOS risk. Variant B (on-premises, trunk port) is relevant only with your own switch.

Inter-VLAN routing via router VM (br-net1 ↔ br-net2)

purely internal software bridges br-net1/br-net2 (port: []) — no VM MAC leaves the node

VM with 3 Network Interfaces (Management + Data + Storage)

OVN-Kubernetes UserDefinedNetwork (Layer2 Overlay)

UserDefinedNetwork with Layer2 topology is a pure overlay (encapsulated Geneve tunnel within OVN-K) — explicitly NOT localnet, so no VM MAC leaves the node.

⚠️ DEDICATED NAMESPACE REQUIRED: see NOTE below.

Verify MetalLB Basic Functionality

2 Pools: internal-pool binds to br-net1 — external-pool binds to eno2, requires a 2nd public IP

Expose VM Services via MetalLB (SSH)

external-pool uses a provider-registered additional IP (e.g. Hetzner Additional IP); MetalLB speaker announces with the node's own MAC.

⚠️ SHARED RESOURCE: external-pool currently has only ONE IP — Clean up after this test (delete vm-ssh-lb) before starting TC-HCP-002

Make VMs reachable via a real, externally accessible IP directly (like a physical server) — no port-forward, no NodePort with random port. Requires a second IP (external-pool from PRE-09); if not yet delivered, use the NodePort variant further below.

Prerequisites checklist

Confirm these before running steps:

TC-MLB-001Verify MetalLB Basic Functionality
TC-VM-001Create and boot first VM from template (RHEL 9)
For external test: second Hetzner Additional IP delivered (otherwise NodePort fallback, see Commands / YAML tab)

1Verify prerequisite: VM test-vm-rhel9 running and MetalLB works (TC-MLB-001 green)

oc get vmi test-vm-rhel9 -n vmtest

oc get pods -n metallb-system

2Check which pool is currently available

oc get ipaddresspool -n metallb-system

→ external-pool present AND autoAssign:true?

3Apply LoadBalancer service for SSH — explicitly binds to external-pool (block in the 'Commands / YAML' tab)

4Wait for assigned EXTERNAL-IP and note it

watch oc get svc vm-ssh-lb -n vmtest

5Test SSH directly via the assigned IP (no NodePort, no tunnel) — with the SSH key, as the golden image has no password set

ssh -i ~/.ssh/ocp-vm-key cloud-user@<EXTERNAL-IP>

→ works like normal SSH access to a physical server, directly from laptop/internet

6Verify IP stability after a VM restart (important for production!)

virtctl restart test-vm-rhel9 -n vmtest

watch oc get vmi test-vm-rhel9 -n vmtest

oc get svc vm-ssh-lb -n vmtest

→ EXTERNAL-IP must be identical to the IP before restart

7Connect via SSH again to confirm the service is reachable after restart

ssh -i ~/.ssh/ocp-vm-key cloud-user@<EXTERNAL-IP>

8Test NodePort fallback

Create a NodePort service for SSH (see Commands / YAML tab)

Connect: ssh -i ~/.ssh/ocp-vm-key -p 30022 cloud-user@<EXTERNAL-IP>

9⚠️ Do NOT forget cleanup — external-pool has only ONE IP, also required by TC-HCP-002 (hosted cluster API endpoint). Without cleanup, MetalLB later silently falls back to internal-pool there (no error, but the IP is then not externally reachable)

oc delete svc vm-ssh-lb -n vmtest

oc delete svc vm-ssh-nodeport -n vmtest

MetalLB BGP Mode with Router Peering

⚠️ NOT usable by default on the current SNO cluster: there is no customer-controlled router in the path for peering. Left for documentation purposes and future tests.

Multiple IP Pools and Namespace Isolation

MetalLB + Isolated Software Bridges: LB IPs per Bridge Interface

L2Advertisement explicitly binds to br-net1/br-net2 — ARP announcements stay node-internal.

Verify HyperShift Operator and MCE

Single-NIC OK — HyperShift pods use the OVN-K pod network.

⚠️ Check Pod/Node Capacity before starting TC-HCP-002 — see steps below.

Create Hosted Cluster with KubeVirt provider

⚠️ SNO EXAMPLE INSTALLATION: --control-plane-availability-policy SingleReplica is mandatory on a single-node cluster.

Scale NodePool and change VM flavour

⚠️ Be sure enough compute resources are available on the SNO node before starting this test.

Remove Hosted Cluster cleanly (destroy)

DataVolume import from multiple sources

Import over OVN-K — bandwidth is shared with OCP traffic on eno2/br-ex in this cluster

Create VM backup with OADP

Restore VM from OADP backup

/ open searchJ/K next / previous card? keyboard shortcutsEsc close panels

🧪 Test cases(24 of 50)

Test cases(24 of 50)