@akrejcir IIRC you already have a PR for this one

I don't, but it should be a simple patch.

I tried to reproduce this issue, but I cannot. For me, it works as expected.

Versions:
OCP: 4.8.0
Kubevirt: v0.39.0
Template validator: v0.9.0


Ruth, on which versions of components did you see this issue?

Andrej, because of bug 1937307, I cannot extract the API version.
The cluster is with OCP 4.8.0-0.nightly-2021-03-17-045622, kubevirt-template-validator-container-v4.8.0-3

I have created a PR, that should fix this bug. But I cannot verify it, because I cannot reproduce the issue.

# Openshift cluster
4.8.0-fc.2

# HCO Operator
$ oc -n openshift-cnv get deploy hco-operator -oyaml
        image: registry.redhat.io/container-native-virtualization/hyperconverged-cluster-operator@sha256:7a233fab66fe0e38258ab2876cbb2a8394fae9a9f108f724cc92bc76b9a56c91

hyperconverged-cluster-operator-container-v4.8.0-46

# SSP Operator
$ oc -n openshift-cnv get deploy ssp-operator -oyaml
        image: registry.redhat.io/container-native-virtualization/kubevirt-ssp-operator@sha256:2a97a915503dafbe583bfe5a202ab39f72acb32f69dc094a8aa78845971e1f2d

kubevirt-ssp-operator-container-v4.8.0-27



The validation for fedora-server-tiny is for a minimum requested memory of 1Gi

$ oc get template -n openshift fedora-server-tiny -oyaml
...
- apiVersion: kubevirt.io/v1
  kind: VirtualMachine
  metadata:
    annotations:
      vm.kubevirt.io/validations: |
        [
          {
            "name": "minimal-required-memory",
            "path": "jsonpath::.spec.domain.resources.requests.memory",
            "rule": "integer",
            "message": "This VM requires more memory.",
            "min": 1073741824
          }
        ]
    labels:
      app: ${NAME}
      vm.kubevirt.io/template: fedora-server-tiny
      vm.kubevirt.io/template.revision: "1"
      vm.kubevirt.io/template.version: v0.14.0
...



Example 1 (Requesting 1Mi):

cat << EOF > test-vm.yaml
apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
  name: fedora
  annotations:
    vm.kubevirt.io/flavor: tiny
    vm.kubevirt.io/os: fedora
    vm.kubevirt.io/workload: server
spec:
  running: false
  template:
    spec:
      domain:
        cpu:
          sockets: 1
          cores: 1
          threads: 1
        resources:
          requests:
            memory: 1Mi
        devices: {}
EOF



$ oc create -f test-vm.yaml

Expected:
The request is invalid: spec.template.spec.domain.resources.requests.memory: spec.template.spec.domain.resources.requests.memory '1Mi': must be greater than or equal to 1Gi.

Actual:
virtualmachine.kubevirt.io/fedora created


Example 2 (Requesting 900Ki):

cat << EOF > test-vm2.yaml
apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
  name: fedora
  annotations:
    vm.kubevirt.io/flavor: tiny
    vm.kubevirt.io/os: fedora
    vm.kubevirt.io/workload: server
spec:
  running: false
  template:
    spec:
      domain:
        cpu:
          sockets: 1
          cores: 1
          threads: 1
        resources:
          requests:
            memory: 900Ki
        devices: {}
EOF

$ oc create -f test-vm2.yaml

Expected:
The request is invalid: spec.template.spec.domain.resources.requests.memory: spec.template.spec.domain.resources.requests.memory '900Ki': must be greater than or equal to 1Gi.

Actual:
The request is invalid: spec.template.spec.domain.resources.requests.memory: spec.template.spec.domain.resources.requests.memory '900Ki': must be greater than or equal to 1M.

The verification method as described in Comment 8 is incorrect.

The VMs are missing required labels or annotation, without them the template validator will ignore the VM. Surprisingly, the "Example 2" VM should also be ignored by the validator, but it is not.

The VM needs these labels to reference an existing template:
- vm.kubevirt.io/template: "fedora-server-tiny",
- vm.kubevirt.io/template.revision: "1",
- vm.kubevirt.io/template.version: "v0.14.0"

Or an annotation that contains validation rules:
- vm.kubevirt.io/validations: ...



While testing the new validator, I have come across a related issue. The validator response was missing some required fields and so k8s webhook call failed with the following error:

$ oc create -f test-vm.yaml

Error from server (InternalError): error when creating "test-vm.yaml": Internal error occurred: failed calling webhook "virt-template-admission.kubevirt.io": expected webhook response of admission.k8s.io/v1, Kind=AdmissionReview, got /, Kind=


I have posted a PR to fix it.

Verified.

$ cat <<EOF > test-vm.yaml
apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
  name: fedora-test-vm
  namespace: sarah-test
  annotations:
      vm.kubevirt.io/validations: '[
        {
            "name": "minimal-required-memory",
            "path": "jsonpath::.spec.domain.resources.requests.memory",
            "rule": "integer",
            "message": "This VM requires more memory.",
            "min": 1073741824
        }
      ]'
  labels:
      vm.kubevirt.io/template: "fedora-server-tiny"
      vm.kubevirt.io/template.revision: "1"
      vm.kubevirt.io/template.version: "v0.14.0"
spec:
  running: false
  template:
    spec:
      domain:
        cpu:
          sockets: 1
          cores: 1
          threads: 1
        resources:
          requests:
            memory: 1000Mi
        devices: {}
EOF

$ oc create -f test-vm.yaml

Expected/Actual:
The request is invalid: .spec.domain.resources.requests.memory: This VM requires more memory.: value 1048576000 is lower than minimum [1073741824]


Same test performed with memory request at "1Gi" and "1073741824".
In both cases, Expected/Actual:
virtualmachine.kubevirt.io/fedora-test-vm created

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Virtualization 4.8.0 Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:2920