kubevirt: kubevirt - VM creation failed on OCP4.1 rc5

Is this a BUG REPORT or FEATURE REQUEST?: Bug Report

What happened: After installing kubevirt CR on OCP4.1 rc5 , virt-handler, virt-api and virt-controller not coming up which in turn fails the VM deployment.

What you expected to happen: All the virt-* pods should be up and running after kubevirt CR is installed and creation of VM should be successful.

How to reproduce it (as minimally and precisely as possible): Follow the steps -> Enable nested Virtualization -> Install a kubevirt Operator -> Install kubevirt CR -> deploy and test a sample VM.

Anything else we need to know?:

kubevirt version 0.17.0

Environment:

  • KubeVirt version (use virtctl version):
./virtctl version
Client Version: version.Info{GitVersion:"v0.17.0", GitCommit:"c0f960702dce718419a767f3913669f539229ff0", GitTreeState:"clean", BuildDate:"2019-05-05T08:09:14Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
the server could not find the requested resource
  • Kubernetes version (use kubectl version):
oc version
Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.0", GitCommit:"2793c3316", GitTreeState:"", BuildDate:"2019-04-23T07:46:06Z", GoVersion:"", Compiler:"", Platform:""}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.4+f2cc675", GitCommit:"f2cc675", GitTreeState:"clean", BuildDate:"2019-05-18T00:35:43Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
  • VM or VMI specifications:
oc apply -f https://raw.githubusercontent.com/kubevirt/kubevirt.github.io/master/labs/manifests/vm.yaml
  • Cloud provider or hardware configuration:
OCP4.1 on AWS 
  • OS (e.g. from /etc/os-release):
cat /etc/os-release 
NAME=Fedora
VERSION="29 (Workstation Edition)"
ID=fedora
VERSION_ID=29
VERSION_CODENAME=""
PLATFORM_ID="platform:f29"
PRETTY_NAME="Fedora 29 (Workstation Edition)"
ANSI_COLOR="0;34"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:29"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/"
SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=29
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=29
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Workstation Edition"
VARIANT_ID=workstation
  • Kernel (e.g. uname -a):
uname -a
Linux localhost.localdomain 5.0.9-200.fc29.x86_64 #1 SMP Mon Apr 22 00:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
  • Install tools:
oc get all -n kubevirt
NAME                                READY   STATUS    RESTARTS   AGE
pod/virt-operator-87cf8d97b-h5hc9   1/1     Running   0          70m
pod/virt-operator-87cf8d97b-lsq9v   1/1     Running   0          70m

NAME                                  TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)   AGE
service/kubevirt-prometheus-metrics   ClusterIP   172.30.121.203   <none>        443/TCP   58m
service/virt-api                      ClusterIP   172.30.21.11     <none>        443/TCP   58m

NAME                            READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/virt-operator   2/2     2            2           70m

NAME                                      DESIRED   CURRENT   READY   AGE
replicaset.apps/virt-operator-87cf8d97b   2         2         2       70m
  • Others: Error observed
oc apply -f https://raw.githubusercontent.com/kubevirt/kubevirt.github.io/master/labs/manifests/vm.yaml
Error from server (InternalError): error when creating "https://raw.githubusercontent.com/kubevirt/kubevirt.github.io/master/labs/manifests/vm.yaml": Internal error occurred: failed calling webhook "virtualmachines.kubevirt.io-tmp-validator": Post https://fake-validation-service.kubevirt.svc:443/fake-path/virtualmachines.kubevirt.io?timeout=30s: service "fake-validation-service" not found

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 16 (9 by maintainers)

Most upvoted comments

@DirectedSoul1 Yep, it should be, because we did not backport the fix to release-0.17

@DirectedSoul1 I can be related to the issue https://github.com/kubevirt/kubevirt/pull/2285, can you try to deploy from the master?