+ export WORKSPACE=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release + WORKSPACE=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release + [[ k8s-1.11.0-release =~ openshift-.* ]] + [[ k8s-1.11.0-release =~ .*-1.10.4-.* ]] + export KUBEVIRT_PROVIDER=k8s-1.11.0 + KUBEVIRT_PROVIDER=k8s-1.11.0 + export KUBEVIRT_NUM_NODES=2 + KUBEVIRT_NUM_NODES=2 + export NFS_WINDOWS_DIR=/home/nfs/images/windows2016 + NFS_WINDOWS_DIR=/home/nfs/images/windows2016 + export NAMESPACE=kube-system + NAMESPACE=kube-system + trap '{ make cluster-down; }' EXIT SIGINT SIGTERM SIGSTOP + make cluster-down ./cluster/down.sh + make cluster-up ./cluster/up.sh Downloading ....... Downloading ....... 2018/08/03 20:50:51 Waiting for host: 192.168.66.101:22 2018/08/03 20:50:54 Problem with dial: dial tcp 192.168.66.101:22: getsockopt: no route to host. Sleeping 5s 2018/08/03 20:51:06 Connected to tcp://192.168.66.101:22 ++ systemctl status docker ++ grep active ++ wc -l + [[ 1 -eq 0 ]] + kubeadm init --config /etc/kubernetes/kubeadm.conf [init] using Kubernetes version: v1.11.0 [preflight] running pre-flight checks I0803 20:51:06.815572 1259 feature_gate.go:230] feature gates: &{map[]} I0803 20:51:06.882644 1259 kernel_validator.go:81] Validating kernel version I0803 20:51:06.882904 1259 kernel_validator.go:96] Validating kernel config [preflight/images] Pulling images required for setting up a Kubernetes cluster [preflight/images] This might take a minute or two, depending on the speed of your internet connection [preflight/images] You can also perform this action in beforehand using 'kubeadm config images pull' [kubelet] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env" [kubelet] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml" [preflight] Activating the kubelet service [certificates] Generated ca certificate and key. [certificates] Generated apiserver certificate and key. [certificates] apiserver serving cert is signed for DNS names [node01 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 192.168.66.101] [certificates] Generated apiserver-kubelet-client certificate and key. [certificates] Generated sa key and public key. [certificates] Generated front-proxy-ca certificate and key. [certificates] Generated front-proxy-client certificate and key. [certificates] Generated etcd/ca certificate and key. [certificates] Generated etcd/server certificate and key. [certificates] etcd/server serving cert is signed for DNS names [node01 localhost] and IPs [127.0.0.1 ::1] [certificates] Generated etcd/peer certificate and key. [certificates] etcd/peer serving cert is signed for DNS names [node01 localhost] and IPs [192.168.66.101 127.0.0.1 ::1] [certificates] Generated etcd/healthcheck-client certificate and key. [certificates] Generated apiserver-etcd-client certificate and key. [certificates] valid certificates and keys now exist in "/etc/kubernetes/pki" [kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/admin.conf" [kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/kubelet.conf" [kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/controller-manager.conf" [kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/scheduler.conf" [controlplane] wrote Static Pod manifest for component kube-apiserver to "/etc/kubernetes/manifests/kube-apiserver.yaml" [controlplane] wrote Static Pod manifest for component kube-controller-manager to "/etc/kubernetes/manifests/kube-controller-manager.yaml" [controlplane] wrote Static Pod manifest for component kube-scheduler to "/etc/kubernetes/manifests/kube-scheduler.yaml" [etcd] Wrote Static Pod manifest for a local etcd instance to "/etc/kubernetes/manifests/etcd.yaml" [init] waiting for the kubelet to boot up the control plane as Static Pods from directory "/etc/kubernetes/manifests" [init] this might take a minute or longer if the control plane images have to be pulled [apiclient] All control plane components are healthy after 43.003838 seconds [uploadconfig] storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace [kubelet] Creating a ConfigMap "kubelet-config-1.11" in namespace kube-system with the configuration for the kubelets in the cluster [markmaster] Marking the node node01 as master by adding the label "node-role.kubernetes.io/master=''" [markmaster] Marking the node node01 as master by adding the taints [node-role.kubernetes.io/master:NoSchedule] [patchnode] Uploading the CRI Socket information "/var/run/dockershim.sock" to the Node API object "node01" as an annotation [bootstraptoken] using token: abcdef.1234567890123456 [bootstraptoken] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials [bootstraptoken] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token [bootstraptoken] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster [bootstraptoken] creating the "cluster-info" ConfigMap in the "kube-public" namespace [addons] Applied essential addon: CoreDNS [addons] Applied essential addon: kube-proxy Your Kubernetes master has initialized successfully! To start using your cluster, you need to run the following as a regular user: mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config You should now deploy a pod network to the cluster. Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at: https://kubernetes.io/docs/concepts/cluster-administration/addons/ You can now join any number of machines by running the following on each node as root: kubeadm join 192.168.66.101:6443 --token abcdef.1234567890123456 --discovery-token-ca-cert-hash sha256:34927dad0255ec669d66c4dea3b87ccf8480e957b296228cada1bd9a22d2a593 + kubectl --kubeconfig=/etc/kubernetes/admin.conf apply -f https://raw.githubusercontent.com/coreos/flannel/v0.9.1/Documentation/kube-flannel.yml clusterrole.rbac.authorization.k8s.io/flannel created clusterrolebinding.rbac.authorization.k8s.io/flannel created serviceaccount/flannel created configmap/kube-flannel-cfg created daemonset.extensions/kube-flannel-ds created + kubectl --kubeconfig=/etc/kubernetes/admin.conf taint nodes node01 node-role.kubernetes.io/master:NoSchedule- node/node01 untainted + kubectl --kubeconfig=/etc/kubernetes/admin.conf create -f /tmp/local-volume.yaml storageclass.storage.k8s.io/local created configmap/local-storage-config created clusterrolebinding.rbac.authorization.k8s.io/local-storage-provisioner-pv-binding created clusterrole.rbac.authorization.k8s.io/local-storage-provisioner-node-clusterrole created clusterrolebinding.rbac.authorization.k8s.io/local-storage-provisioner-node-binding created role.rbac.authorization.k8s.io/local-storage-provisioner-jobs-role created rolebinding.rbac.authorization.k8s.io/local-storage-provisioner-jobs-rolebinding created serviceaccount/local-storage-admin created daemonset.extensions/local-volume-provisioner created 2018/08/03 20:52:08 Waiting for host: 192.168.66.102:22 2018/08/03 20:52:11 Problem with dial: dial tcp 192.168.66.102:22: getsockopt: no route to host. Sleeping 5s 2018/08/03 20:52:19 Problem with dial: dial tcp 192.168.66.102:22: getsockopt: connection refused. Sleeping 5s 2018/08/03 20:52:24 Connected to tcp://192.168.66.102:22 ++ systemctl status docker ++ grep active ++ wc -l + [[ 1 -eq 0 ]] + kubeadm join --token abcdef.1234567890123456 192.168.66.101:6443 --ignore-preflight-errors=all --discovery-token-unsafe-skip-ca-verification=true [preflight] running pre-flight checks [WARNING RequiredIPVSKernelModulesAvailable]: the IPVS proxier will not be used, because the following required kernel modules are not loaded: [ip_vs_sh ip_vs ip_vs_rr ip_vs_wrr] or no builtin kernel ipvs support: map[ip_vs:{} ip_vs_rr:{} ip_vs_wrr:{} ip_vs_sh:{} nf_conntrack_ipv4:{}] you can solve this problem with following methods: 1. Run 'modprobe -- ' to load missing kernel modules; 2. Provide the missing builtin kernel ipvs support I0803 20:52:24.861146 1259 kernel_validator.go:81] Validating kernel version I0803 20:52:24.861421 1259 kernel_validator.go:96] Validating kernel config [discovery] Trying to connect to API Server "192.168.66.101:6443" [discovery] Created cluster-info discovery client, requesting info from "https://192.168.66.101:6443" [discovery] Cluster info signature and contents are valid and no TLS pinning was specified, will use API Server "192.168.66.101:6443" [discovery] Successfully established connection with API Server "192.168.66.101:6443" [kubelet] Downloading configuration for the kubelet from the "kubelet-config-1.11" ConfigMap in the kube-system namespace [kubelet] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml" [kubelet] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env" [preflight] Activating the kubelet service [tlsbootstrap] Waiting for the kubelet to perform the TLS Bootstrap... [patchnode] Uploading the CRI Socket information "/var/run/dockershim.sock" to the Node API object "node02" as an annotation This node has joined the cluster: * Certificate signing request was sent to master and a response was received. * The Kubelet was informed of the new secure connection details. Run 'kubectl get nodes' on the master to see this node join the cluster. Sending file modes: C0755 38739968 kubectl Sending file modes: C0600 5454 admin.conf Cluster "kubernetes" set. Cluster "kubernetes" set. + set +e + kubectl get nodes --no-headers + cluster/kubectl.sh get nodes --no-headers node01 Ready master 38s v1.11.0 node02 Ready 14s v1.11.0 + kubectl_rc=0 + '[' 0 -ne 0 ']' ++ kubectl get nodes --no-headers ++ grep NotReady ++ cluster/kubectl.sh get nodes --no-headers + '[' -n '' ']' + set -e + echo 'Nodes are ready:' Nodes are ready: + kubectl get nodes + cluster/kubectl.sh get nodes NAME STATUS ROLES AGE VERSION node01 Ready master 39s v1.11.0 node02 Ready 15s v1.11.0 + make cluster-sync ./cluster/build.sh Building ... Untagged: localhost:33048/kubevirt/virt-controller:devel Untagged: localhost:33048/kubevirt/virt-controller@sha256:9d37dbd7fedcbced8c14c90efe844c37d881c64fb2e42251fbaecf29db97acda Deleted: sha256:6579ac924e807e69d83c6a97ed101c80a4fa4ecba1c1adbec4c39502d3aeb985 Deleted: sha256:c177bd392d59426883a348df1f72d9c651ce895ac2997aa15a39fb91e0884d19 Deleted: sha256:ef76d70201052eaec6bf2a8848647aed5821a24fa9da648672667be933238b32 Deleted: sha256:5bfde4a79142f9eac75f62c78b992efa4ef68adbb8ac14a0cfbeb6bcf214c1a2 Untagged: localhost:33048/kubevirt/virt-launcher:devel Untagged: localhost:33048/kubevirt/virt-launcher@sha256:b739bd50601417d92e7d6a353a7c57faa697a756705cdb7069be5937152f5533 Deleted: sha256:557696e9d7c6e11b438525084cb8fcfb9dc121ef23a893cd1792f28527c8300c Deleted: sha256:21486b846a27de51fa0d61d0a26d59952a560b23d40b7f588cb03b7731771502 Deleted: sha256:4dbbd5ea37cb8c0fd4d0ee772aa6041ec46f8e341c2c41219e68593fdea8fd8b Deleted: sha256:a2cb68f42592b164e88e3208331515b9b4a756f64c58e5c1a5cc61619bc41e77 Deleted: sha256:edc6ba5761b36c58c85438274f41aee0d519a970dca126ba6833e4a124049bcf Deleted: sha256:007b2056b231e59d7cf228d1bd1fe367ef59e8f4412b83fd0200e5b34e713458 Deleted: sha256:905782f5f394cce8ba14a4f9d7aba680ef3b71e7d5d0f94b4cbac56da4c82bb6 Deleted: sha256:afba1f322006fa64afa6c7676a1b9ac1b61835bf07725f3020afd45b15674333 Deleted: sha256:1904c2b6b9c3a15dda92d57bd360a3e8a667d4663742b59a969bb684b1c0777b Deleted: sha256:d72c72fc191e2cf95adfd809809aacd42c946d092845482df4138cdc9c5471eb Untagged: localhost:33048/kubevirt/virt-handler:devel Untagged: localhost:33048/kubevirt/virt-handler@sha256:07d801d3b1d2bba3008eda9027f80367f73522fa4086b80a31d7c47fcb52fd41 Deleted: sha256:5e0c22d69962d3342d83b4fc5bdc5d870b334ca3f94e09a5f5d7f9ea6ab5d3da Deleted: sha256:0281d5948995af996c2415c3f11a52a99830812b5edccb0cb50d814bd03db58f Deleted: sha256:87e846be67e4980b6e4222de4b404ad7c197a029886ad2b5a9db9b9b0d15af30 Deleted: sha256:44edc6f714149fcf12d123f1f97aa4b15cbdb69dd40573a50f16ffca7b804c01 Untagged: localhost:33048/kubevirt/virt-api:devel Untagged: localhost:33048/kubevirt/virt-api@sha256:dd5066d7cf882dd394f1da7c14e7b7ae2396db17a0cb09239b5e34ad9c19c818 Deleted: sha256:01e3643934adb783f5151cb1b0db218129c89accf760063f8d9eb4f8d0e68b52 Deleted: sha256:9a0d06fc21ef4d02a3c4113a4ac4e468ea7c1164cf62f08b0e5fcb0947476596 Deleted: sha256:406fa672fa25d6fa771cef5a644ae560ab6e82c3a47e9a51d30081fce7aa9d3b Deleted: sha256:e52ed72f1f770fc12bc6560de5f6532ca3542be0cfe21bbd853803633f34e6ad Untagged: localhost:33048/kubevirt/subresource-access-test:devel Untagged: localhost:33048/kubevirt/subresource-access-test@sha256:395b3bc8edeb0fa8848966742ba670d623cdc0255f7c629cd27268cf884afbd3 Deleted: sha256:a558a56c63546705b15a33bbf5473040df8454a466edb79c4797ac6aad93bb92 Deleted: sha256:51392861586b04f095a9c26ca0df6c0c4017d8bf76ae7c8490c531452458296c Deleted: sha256:8c69e76bfbe21b6013fb2b17ec7e8f8deef7d214330b932df0be7d0ff3b43c8b Deleted: sha256:0f4eee1085cf38b3b2bbb5ed3b8d35bfcfe6cc30388fb82e8878d47ce7e8fa71 Untagged: localhost:33048/kubevirt/example-hook-sidecar:devel Untagged: localhost:33048/kubevirt/example-hook-sidecar@sha256:685e96851a8ecfc6a7b8647bbb00e5ab8be82594b820989eef6cdc46ae3d1ed1 Deleted: sha256:901be91977dac9ecdc2bfa54f8caed1ac47aad075bfea09d8efabfaf375e34c4 Deleted: sha256:b8dc4c7553efc470743e0e815d640babcf10031f86ea099008da9f770c27ba0e Deleted: sha256:b9ad6bdbaacd5d3b131d3e9bf52cac6e04d62ab55838cde3fbf711d42bd2b575 Deleted: sha256:8e314d29524af75510da2c5aa7eadd3147aa374e18997fce76cb5977c1711a50 sha256:ceba12cbc33e4e37a707840478a630db561e2427b78c8c9f9cd6d0b73276ab32 go version go1.10 linux/amd64 Waiting for rsyncd to be ready go version go1.10 linux/amd64 make[1]: Entering directory `/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt' hack/dockerized "./hack/check.sh && KUBEVIRT_VERSION= ./hack/build-go.sh install " && ./hack/build-copy-artifacts.sh sha256:ceba12cbc33e4e37a707840478a630db561e2427b78c8c9f9cd6d0b73276ab32 go version go1.10 linux/amd64 go version go1.10 linux/amd64 find: '/root/go/src/kubevirt.io/kubevirt/_out/cmd': No such file or directory Compiling tests... compiled tests.test hack/build-docker.sh build Sending build context to Docker daemon 40.39 MB Step 1/8 : FROM fedora:28 ---> cc510acfcd70 Step 2/8 : MAINTAINER "The KubeVirt Project" ---> Using cache ---> 84920e004a40 Step 3/8 : RUN useradd -u 1001 --create-home -s /bin/bash virt-controller ---> Using cache ---> b4f3251c6468 Step 4/8 : WORKDIR /home/virt-controller ---> Using cache ---> 813752072d9d Step 5/8 : USER 1001 ---> Using cache ---> 88b3556f36b4 Step 6/8 : COPY virt-controller /usr/bin/virt-controller ---> 80de0155291f Removing intermediate container 48a32e41efc2 Step 7/8 : ENTRYPOINT /usr/bin/virt-controller ---> Running in e3708b25688a ---> a36c390eb594 Removing intermediate container e3708b25688a Step 8/8 : LABEL "kubevirt-functional-tests-k8s-1.11.0-release1" '' "virt-controller" '' ---> Running in 4685166c599c ---> e815b9dbc44b Removing intermediate container 4685166c599c Successfully built e815b9dbc44b Sending build context to Docker daemon 43.32 MB Step 1/10 : FROM kubevirt/libvirt:4.2.0 ---> 5f0bfe81a3e0 Step 2/10 : MAINTAINER "The KubeVirt Project" ---> Using cache ---> 09010a005182 Step 3/10 : RUN dnf -y install socat genisoimage util-linux libcgroup-tools ethtool net-tools sudo && dnf -y clean all && test $(id -u qemu) = 107 # make sure that the qemu user really is 107 ---> Using cache ---> fc9481693838 Step 4/10 : COPY virt-launcher /usr/bin/virt-launcher ---> 72b71539935a Removing intermediate container 38e71e0f2875 Step 5/10 : COPY kubevirt-sudo /etc/sudoers.d/kubevirt ---> df4b1782d898 Removing intermediate container 71eaffe2aec9 Step 6/10 : RUN setcap CAP_NET_BIND_SERVICE=+eip /usr/bin/qemu-system-x86_64 ---> Running in 554d618f2870  ---> 3be92119c842 Removing intermediate container 554d618f2870 Step 7/10 : RUN mkdir -p /usr/share/kubevirt/virt-launcher ---> Running in 38de71678187  ---> f28a12d73483 Removing intermediate container 38de71678187 Step 8/10 : COPY entrypoint.sh libvirtd.sh sock-connector /usr/share/kubevirt/virt-launcher/ ---> 59cb95ea17fa Removing intermediate container 92b82d62a11c Step 9/10 : ENTRYPOINT /usr/share/kubevirt/virt-launcher/entrypoint.sh ---> Running in 6b682e1b43d8 ---> d58725396082 Removing intermediate container 6b682e1b43d8 Step 10/10 : LABEL "kubevirt-functional-tests-k8s-1.11.0-release1" '' "virt-launcher" '' ---> Running in c49c8d07c860 ---> 9991721c9e97 Removing intermediate container c49c8d07c860 Successfully built 9991721c9e97 Sending build context to Docker daemon 38.45 MB Step 1/5 : FROM fedora:28 ---> cc510acfcd70 Step 2/5 : MAINTAINER "The KubeVirt Project" ---> Using cache ---> 84920e004a40 Step 3/5 : COPY virt-handler /usr/bin/virt-handler ---> e4cf58079185 Removing intermediate container 34eb7ca96e0c Step 4/5 : ENTRYPOINT /usr/bin/virt-handler ---> Running in f3c5c6d9f4b0 ---> 4045a8a8cc0e Removing intermediate container f3c5c6d9f4b0 Step 5/5 : LABEL "kubevirt-functional-tests-k8s-1.11.0-release1" '' "virt-handler" '' ---> Running in 0ca50584bde4 ---> 3620a2c32195 Removing intermediate container 0ca50584bde4 Successfully built 3620a2c32195 Sending build context to Docker daemon 38.81 MB Step 1/8 : FROM fedora:28 ---> cc510acfcd70 Step 2/8 : MAINTAINER "The KubeVirt Project" ---> Using cache ---> 84920e004a40 Step 3/8 : RUN useradd -u 1001 --create-home -s /bin/bash virt-api ---> Using cache ---> 3cff23506e80 Step 4/8 : WORKDIR /home/virt-api ---> Using cache ---> e94c5606b96b Step 5/8 : USER 1001 ---> Using cache ---> af16317199f5 Step 6/8 : COPY virt-api /usr/bin/virt-api ---> 217ceffda64a Removing intermediate container 7d1d60438b3e Step 7/8 : ENTRYPOINT /usr/bin/virt-api ---> Running in d34337ae01c4 ---> e64cfc789250 Removing intermediate container d34337ae01c4 Step 8/8 : LABEL "kubevirt-functional-tests-k8s-1.11.0-release1" '' "virt-api" '' ---> Running in 48688b6be98c ---> ee853954d01e Removing intermediate container 48688b6be98c Successfully built ee853954d01e Sending build context to Docker daemon 4.096 kB Step 1/7 : FROM fedora:28 ---> cc510acfcd70 Step 2/7 : MAINTAINER "The KubeVirt Project" ---> Using cache ---> 84920e004a40 Step 3/7 : ENV container docker ---> Using cache ---> aed3ca4ac3a3 Step 4/7 : RUN mkdir -p /images/custom /images/alpine && truncate -s 64M /images/custom/disk.img && curl http://dl-cdn.alpinelinux.org/alpine/v3.7/releases/x86_64/alpine-virt-3.7.0-x86_64.iso > /images/alpine/disk.img ---> Using cache ---> c7d0cf8fc982 Step 5/7 : ADD entrypoint.sh / ---> Using cache ---> 0393e5ee0c37 Step 6/7 : CMD /entrypoint.sh ---> Using cache ---> 23798f49dea3 Step 7/7 : LABEL "disks-images-provider" '' "kubevirt-functional-tests-k8s-1.11.0-release1" '' ---> Using cache ---> c2a355bd725c Successfully built c2a355bd725c Sending build context to Docker daemon 2.56 kB Step 1/5 : FROM fedora:28 ---> cc510acfcd70 Step 2/5 : MAINTAINER "The KubeVirt Project" ---> Using cache ---> 84920e004a40 Step 3/5 : ENV container docker ---> Using cache ---> aed3ca4ac3a3 Step 4/5 : RUN dnf -y install procps-ng nmap-ncat && dnf -y clean all ---> Using cache ---> d8c990eaf575 Step 5/5 : LABEL "kubevirt-functional-tests-k8s-1.11.0-release1" '' "vm-killer" '' ---> Using cache ---> a35b53eec8f8 Successfully built a35b53eec8f8 Sending build context to Docker daemon 5.12 kB Step 1/7 : FROM debian:sid ---> 68f33cf86aab Step 2/7 : MAINTAINER "David Vossel" \ ---> Using cache ---> 50fc79ebe51c Step 3/7 : ENV container docker ---> Using cache ---> b8e063496923 Step 4/7 : RUN apt-get update && apt-get install -y bash curl bzip2 qemu-utils && mkdir -p /disk && rm -rf /var/lib/apt/lists/* ---> Using cache ---> 8adb1572b35c Step 5/7 : ADD entry-point.sh / ---> Using cache ---> 8c0c5a52e4df Step 6/7 : CMD /entry-point.sh ---> Using cache ---> 1a4b838e5dee Step 7/7 : LABEL "kubevirt-functional-tests-k8s-1.11.0-release1" '' "registry-disk-v1alpha" '' ---> Using cache ---> d2597d227e63 Successfully built d2597d227e63 Sending build context to Docker daemon 2.56 kB Step 1/4 : FROM localhost:33331/kubevirt/registry-disk-v1alpha:devel ---> d2597d227e63 Step 2/4 : MAINTAINER "David Vossel" \ ---> Using cache ---> 31d87a3e7551 Step 3/4 : RUN curl https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img > /disk/cirros.img ---> Using cache ---> 8b729e3d9cc8 Step 4/4 : LABEL "cirros-registry-disk-demo" '' "kubevirt-functional-tests-k8s-1.11.0-release1" '' ---> Using cache ---> e164bf7eb7ce Successfully built e164bf7eb7ce Sending build context to Docker daemon 2.56 kB Step 1/4 : FROM localhost:33331/kubevirt/registry-disk-v1alpha:devel ---> d2597d227e63 Step 2/4 : MAINTAINER "The KubeVirt Project" ---> Using cache ---> 8b026f4503d0 Step 3/4 : RUN curl -g -L https://download.fedoraproject.org/pub/fedora/linux/releases/27/CloudImages/x86_64/images/Fedora-Cloud-Base-27-1.6.x86_64.qcow2 > /disk/fedora.qcow2 ---> Using cache ---> 8108a03f9df8 Step 4/4 : LABEL "fedora-cloud-registry-disk-demo" '' "kubevirt-functional-tests-k8s-1.11.0-release1" '' ---> Using cache ---> b3c420487c6f Successfully built b3c420487c6f Sending build context to Docker daemon 2.56 kB Step 1/4 : FROM localhost:33331/kubevirt/registry-disk-v1alpha:devel ---> d2597d227e63 Step 2/4 : MAINTAINER "The KubeVirt Project" ---> Using cache ---> 8b026f4503d0 Step 3/4 : RUN curl http://dl-cdn.alpinelinux.org/alpine/v3.7/releases/x86_64/alpine-virt-3.7.0-x86_64.iso > /disk/alpine.iso ---> Using cache ---> 8e751825aa41 Step 4/4 : LABEL "alpine-registry-disk-demo" '' "kubevirt-functional-tests-k8s-1.11.0-release1" '' ---> Using cache ---> c3fe0249b081 Successfully built c3fe0249b081 Sending build context to Docker daemon 35.59 MB Step 1/8 : FROM fedora:28 ---> cc510acfcd70 Step 2/8 : MAINTAINER "The KubeVirt Project" ---> Using cache ---> 84920e004a40 Step 3/8 : RUN useradd -u 1001 --create-home -s /bin/bash virtctl ---> Using cache ---> d74088d7a4fc Step 4/8 : WORKDIR /home/virtctl ---> Using cache ---> c8c857bf8d96 Step 5/8 : USER 1001 ---> Using cache ---> 36730a67b946 Step 6/8 : COPY subresource-access-test /subresource-access-test ---> becd736925fd Removing intermediate container c90847a51b2d Step 7/8 : ENTRYPOINT /subresource-access-test ---> Running in fce315bbd88c ---> d790f8ddabea Removing intermediate container fce315bbd88c Step 8/8 : LABEL "kubevirt-functional-tests-k8s-1.11.0-release1" '' "subresource-access-test" '' ---> Running in c16a70672770 ---> bac59af96bb9 Removing intermediate container c16a70672770 Successfully built bac59af96bb9 Sending build context to Docker daemon 3.072 kB Step 1/9 : FROM fedora:28 ---> cc510acfcd70 Step 2/9 : MAINTAINER "The KubeVirt Project" ---> Using cache ---> 84920e004a40 Step 3/9 : ENV container docker ---> Using cache ---> aed3ca4ac3a3 Step 4/9 : RUN dnf -y install make git gcc && dnf -y clean all ---> Using cache ---> 6050b24a5d85 Step 5/9 : ENV GIMME_GO_VERSION 1.9.2 ---> Using cache ---> 0447d2178073 Step 6/9 : RUN mkdir -p /gimme && curl -sL https://raw.githubusercontent.com/travis-ci/gimme/master/gimme | HOME=/gimme bash >> /etc/profile.d/gimme.sh ---> Using cache ---> 291db82d955f Step 7/9 : ENV GOPATH "/go" GOBIN "/usr/bin" ---> Using cache ---> 793556477837 Step 8/9 : RUN mkdir -p /go && source /etc/profile.d/gimme.sh && go get github.com/masterzen/winrm-cli ---> Using cache ---> fd5c6e1f9461 Step 9/9 : LABEL "kubevirt-functional-tests-k8s-1.11.0-release1" '' "winrmcli" '' ---> Using cache ---> 17a9aaffc747 Successfully built 17a9aaffc747 Sending build context to Docker daemon 36.8 MB Step 1/5 : FROM fedora:27 ---> 9110ae7f579f Step 2/5 : MAINTAINER "The KubeVirt Project" ---> Using cache ---> 71a8c548e503 Step 3/5 : COPY example-hook-sidecar /example-hook-sidecar ---> 9396a4cf6ad2 Removing intermediate container 5d3ee2433fc3 Step 4/5 : ENTRYPOINT /example-hook-sidecar ---> Running in 5d94954f0a18 ---> 1756cf32ef9e Removing intermediate container 5d94954f0a18 Step 5/5 : LABEL "example-hook-sidecar" '' "kubevirt-functional-tests-k8s-1.11.0-release1" '' ---> Running in 51599e61dcb1 ---> b56f3bc53d1c Removing intermediate container 51599e61dcb1 Successfully built b56f3bc53d1c hack/build-docker.sh push The push refers to a repository [localhost:33331/kubevirt/virt-controller] 77980b461047: Preparing b2f5abdac324: Preparing 891e1e4ef82a: Preparing b2f5abdac324: Pushed 77980b461047: Pushed 891e1e4ef82a: Pushed devel: digest: sha256:62164e5c03ddd449769743706f5d5970430ff9e6022ace4e10ac293a39e681f5 size: 949 The push refers to a repository [localhost:33331/kubevirt/virt-launcher] 3935f2713797: Preparing 6707c99c5bca: Preparing eafe844fdd61: Preparing cd05c570b181: Preparing da88639ec5f8: Preparing 0b99c4111657: Preparing da38cf808aa5: Preparing b83399358a92: Preparing 186d8b3e4fd8: Preparing fa6154170bf5: Preparing 5eefb9960a36: Preparing 891e1e4ef82a: Preparing 0b99c4111657: Waiting 186d8b3e4fd8: Waiting da38cf808aa5: Waiting b83399358a92: Waiting 891e1e4ef82a: Waiting fa6154170bf5: Waiting 5eefb9960a36: Waiting cd05c570b181: Pushed 3935f2713797: Pushed 6707c99c5bca: Pushed da38cf808aa5: Pushed eafe844fdd61: Pushed b83399358a92: Pushed fa6154170bf5: Pushed 186d8b3e4fd8: Pushed 891e1e4ef82a: Mounted from kubevirt/virt-controller da88639ec5f8: Pushed 0b99c4111657: Pushed 5eefb9960a36: Pushed devel: digest: sha256:5c144ec120c021623ba3a0b4b3dd02486095e543decedc589cce7e4b82d9b5ab size: 2828 The push refers to a repository [localhost:33331/kubevirt/virt-handler] 51a379014b7a: Preparing 891e1e4ef82a: Preparing 891e1e4ef82a: Mounted from kubevirt/virt-launcher 51a379014b7a: Pushed devel: digest: sha256:83c97578fbefad23068e9e6fa3714365843eb68225752cf95cf95715013c9886 size: 740 The push refers to a repository [localhost:33331/kubevirt/virt-api] 7486953628eb: Preparing afd1d781e4d1: Preparing 891e1e4ef82a: Preparing 891e1e4ef82a: Mounted from kubevirt/virt-handler afd1d781e4d1: Pushed 7486953628eb: Pushed devel: digest: sha256:4b9fcbe3300b92dd35fdf172c64861928b73ee358b920b826bda54ab2ffff2cc size: 948 The push refers to a repository [localhost:33331/kubevirt/disks-images-provider] dc0875c44573: Preparing 8fc77a44094f: Preparing 891e1e4ef82a: Preparing 891e1e4ef82a: Mounted from kubevirt/virt-api dc0875c44573: Pushed 8fc77a44094f: Pushed devel: digest: sha256:cb6348df94e8afd7658fdc2dddc7cf282373350661587253e1644793a1b1a8de size: 948 The push refers to a repository [localhost:33331/kubevirt/vm-killer] d1b69e768421: Preparing 891e1e4ef82a: Preparing 891e1e4ef82a: Mounted from kubevirt/disks-images-provider d1b69e768421: Pushed devel: digest: sha256:018237675286c2660cb5fc9687f728d8390fbb946c8a9f3173cf1e0332f2b48a size: 740 The push refers to a repository [localhost:33331/kubevirt/registry-disk-v1alpha] 2a15632f54d4: Preparing 91a924e03d7c: Preparing 25edbec0eaea: Preparing 2a15632f54d4: Pushed 91a924e03d7c: Pushed 25edbec0eaea: Pushed devel: digest: sha256:9ee50b797053306bd5f3e02582611d3af223831ab5cd25047070b588b9e8c7c9 size: 948 The push refers to a repository [localhost:33331/kubevirt/cirros-registry-disk-demo] a4d34e46c815: Preparing 2a15632f54d4: Preparing 91a924e03d7c: Preparing 25edbec0eaea: Preparing 2a15632f54d4: Mounted from kubevirt/registry-disk-v1alpha 25edbec0eaea: Mounted from kubevirt/registry-disk-v1alpha 91a924e03d7c: Mounted from kubevirt/registry-disk-v1alpha a4d34e46c815: Pushed devel: digest: sha256:39d7e91e514c3c4edb49dd2167f75ccf2ec5d81389804655bf95ff577efaad38 size: 1160 The push refers to a repository [localhost:33331/kubevirt/fedora-cloud-registry-disk-demo] d811f437a779: Preparing 2a15632f54d4: Preparing 91a924e03d7c: Preparing 25edbec0eaea: Preparing 2a15632f54d4: Mounted from kubevirt/cirros-registry-disk-demo 25edbec0eaea: Mounted from kubevirt/cirros-registry-disk-demo 91a924e03d7c: Mounted from kubevirt/cirros-registry-disk-demo d811f437a779: Pushed devel: digest: sha256:bc40df962eee7e2654678bd77ec073c5257dfad1ebbaacf9c29872e035a91a55 size: 1161 The push refers to a repository [localhost:33331/kubevirt/alpine-registry-disk-demo] ccc249ff5804: Preparing 2a15632f54d4: Preparing 91a924e03d7c: Preparing 25edbec0eaea: Preparing 2a15632f54d4: Mounted from kubevirt/fedora-cloud-registry-disk-demo 91a924e03d7c: Mounted from kubevirt/fedora-cloud-registry-disk-demo 25edbec0eaea: Mounted from kubevirt/fedora-cloud-registry-disk-demo ccc249ff5804: Pushed devel: digest: sha256:2e01f3baf16a9bdba2dbd8e07b2acbb03ffbd493e29d56baef08b214b6ca3c36 size: 1160 The push refers to a repository [localhost:33331/kubevirt/subresource-access-test] 09fda3fbd731: Preparing 4052ce9d0aff: Preparing 891e1e4ef82a: Preparing 891e1e4ef82a: Mounted from kubevirt/vm-killer 4052ce9d0aff: Pushed 09fda3fbd731: Pushed devel: digest: sha256:c6bd78293b5e9e45b66ecc652e433b84d9e690e4c0a2957aed02f8d2fab896b2 size: 948 The push refers to a repository [localhost:33331/kubevirt/winrmcli] 64ccc7ac4271: Preparing 4242962b50c3: Preparing 0e374d8c733e: Preparing 891e1e4ef82a: Preparing 891e1e4ef82a: Mounted from kubevirt/subresource-access-test 64ccc7ac4271: Pushed 0e374d8c733e: Pushed 4242962b50c3: Pushed devel: digest: sha256:36f030f5f71fd7b4686092ec1e8f115463056fcd62248338b1db2f82587b5a28 size: 1165 The push refers to a repository [localhost:33331/kubevirt/example-hook-sidecar] 959693adbb90: Preparing 39bae602f753: Preparing 959693adbb90: Pushed 39bae602f753: Pushed devel: digest: sha256:f4bbe57485b2078b4ea356b5768b1bb433c103bc6bb29543b703ddced9c962ca size: 740 make[1]: Leaving directory `/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt' Done ./cluster/clean.sh + source hack/common.sh ++++ dirname 'hack/common.sh[0]' +++ cd hack/../ +++ pwd ++ KUBEVIRT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt ++ OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out ++ VENDOR_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/vendor ++ CMD_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out/cmd ++ TESTS_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out/tests ++ APIDOCS_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out/apidocs ++ MANIFESTS_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out/manifests ++ MANIFEST_TEMPLATES_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out/templates/manifests ++ PYTHON_CLIENT_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out/client-python ++ KUBEVIRT_PROVIDER=k8s-1.11.0 ++ KUBEVIRT_NUM_NODES=2 ++ '[' -z kubevirt-functional-tests-k8s-1.11.0-release ']' ++ provider_prefix=kubevirt-functional-tests-k8s-1.11.0-release1 ++ job_prefix=kubevirt-functional-tests-k8s-1.11.0-release1 +++ kubevirt_version +++ '[' -n '' ']' +++ '[' -d /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/.git ']' ++++ git describe --always --tags +++ echo v0.7.0-189-g96d0165 ++ KUBEVIRT_VERSION=v0.7.0-189-g96d0165 + source cluster/k8s-1.11.0/provider.sh ++ set -e ++ image=k8s-1.11.0@sha256:6c1caf5559eb02a144bf606de37eb0194c06ace4d77ad4561459f3bde876151c ++ source cluster/ephemeral-provider-common.sh +++ set -e +++ _cli='docker run --privileged --net=host --rm -v /var/run/docker.sock:/var/run/docker.sock kubevirtci/gocli@sha256:aa7f295a7908fa333ab5e98ef3af0bfafbabfd3cee2b83f9af47f722e3000f6a' + source hack/config.sh ++ unset binaries docker_images docker_prefix docker_tag manifest_templates master_ip network_provider kubeconfig manifest_docker_prefix namespace ++ KUBEVIRT_PROVIDER=k8s-1.11.0 ++ source hack/config-default.sh source hack/config-k8s-1.11.0.sh +++ binaries='cmd/virt-controller cmd/virt-launcher cmd/virt-handler cmd/virtctl cmd/fake-qemu-process cmd/virt-api cmd/subresource-access-test cmd/example-hook-sidecar' +++ docker_images='cmd/virt-controller cmd/virt-launcher cmd/virt-handler cmd/virt-api images/disks-images-provider images/vm-killer cmd/registry-disk-v1alpha images/cirros-registry-disk-demo images/fedora-cloud-registry-disk-demo images/alpine-registry-disk-demo cmd/subresource-access-test images/winrmcli cmd/example-hook-sidecar' +++ docker_prefix=kubevirt +++ docker_tag=latest +++ master_ip=192.168.200.2 +++ network_provider=flannel +++ namespace=kube-system ++ test -f hack/config-provider-k8s-1.11.0.sh ++ source hack/config-provider-k8s-1.11.0.sh +++ master_ip=127.0.0.1 +++ docker_tag=devel +++ kubeconfig=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/cluster/k8s-1.11.0/.kubeconfig +++ kubectl=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/cluster/k8s-1.11.0/.kubectl +++ docker_prefix=localhost:33331/kubevirt +++ manifest_docker_prefix=registry:5000/kubevirt ++ test -f hack/config-local.sh ++ export binaries docker_images docker_prefix docker_tag manifest_templates master_ip network_provider kubeconfig namespace + echo 'Cleaning up ...' Cleaning up ... + cluster/kubectl.sh get vmis --all-namespaces -o=custom-columns=NAME:.metadata.name,NAMESPACE:.metadata.namespace,FINALIZERS:.metadata.finalizers --no-headers + grep foregroundDeleteVirtualMachine + read p error: the server doesn't have a resource type "vmis" + _kubectl delete ds -l kubevirt.io -n kube-system --cascade=false --grace-period 0 No resources found + _kubectl delete pods -n kube-system -l=kubevirt.io=libvirt --force --grace-period 0 No resources found + _kubectl delete pods -n kube-system -l=kubevirt.io=virt-handler --force --grace-period 0 No resources found + namespaces=(default ${namespace}) + for i in '${namespaces[@]}' + _kubectl -n default delete apiservices -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n default delete apiservices -l kubevirt.io No resources found + _kubectl -n default delete deployment -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n default delete deployment -l kubevirt.io No resources found + _kubectl -n default delete rs -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n default delete rs -l kubevirt.io No resources found + _kubectl -n default delete services -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n default delete services -l kubevirt.io No resources found + _kubectl -n default delete apiservices -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n default delete apiservices -l kubevirt.io No resources found + _kubectl -n default delete validatingwebhookconfiguration -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n default delete validatingwebhookconfiguration -l kubevirt.io No resources found + _kubectl -n default delete secrets -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n default delete secrets -l kubevirt.io No resources found + _kubectl -n default delete pv -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n default delete pv -l kubevirt.io No resources found + _kubectl -n default delete pvc -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n default delete pvc -l kubevirt.io No resources found + _kubectl -n default delete ds -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n default delete ds -l kubevirt.io No resources found + _kubectl -n default delete customresourcedefinitions -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n default delete customresourcedefinitions -l kubevirt.io No resources found + _kubectl -n default delete pods -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n default delete pods -l kubevirt.io No resources found + _kubectl -n default delete clusterrolebinding -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n default delete clusterrolebinding -l kubevirt.io No resources found + _kubectl -n default delete rolebinding -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n default delete rolebinding -l kubevirt.io No resources found + _kubectl -n default delete roles -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n default delete roles -l kubevirt.io No resources found + _kubectl -n default delete clusterroles -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n default delete clusterroles -l kubevirt.io No resources found + _kubectl -n default delete serviceaccounts -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n default delete serviceaccounts -l kubevirt.io No resources found ++ _kubectl -n default get crd offlinevirtualmachines.kubevirt.io ++ wc -l ++ export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig ++ KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig ++ cluster/k8s-1.11.0/.kubectl -n default get crd offlinevirtualmachines.kubevirt.io No resources found. Error from server (NotFound): customresourcedefinitions.apiextensions.k8s.io "offlinevirtualmachines.kubevirt.io" not found + '[' 0 -gt 0 ']' + for i in '${namespaces[@]}' + _kubectl -n kube-system delete apiservices -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n kube-system delete apiservices -l kubevirt.io No resources found + _kubectl -n kube-system delete deployment -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n kube-system delete deployment -l kubevirt.io No resources found + _kubectl -n kube-system delete rs -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n kube-system delete rs -l kubevirt.io No resources found + _kubectl -n kube-system delete services -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n kube-system delete services -l kubevirt.io No resources found + _kubectl -n kube-system delete apiservices -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n kube-system delete apiservices -l kubevirt.io No resources found + _kubectl -n kube-system delete validatingwebhookconfiguration -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n kube-system delete validatingwebhookconfiguration -l kubevirt.io No resources found + _kubectl -n kube-system delete secrets -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n kube-system delete secrets -l kubevirt.io No resources found + _kubectl -n kube-system delete pv -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n kube-system delete pv -l kubevirt.io No resources found + _kubectl -n kube-system delete pvc -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n kube-system delete pvc -l kubevirt.io No resources found + _kubectl -n kube-system delete ds -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n kube-system delete ds -l kubevirt.io No resources found + _kubectl -n kube-system delete customresourcedefinitions -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n kube-system delete customresourcedefinitions -l kubevirt.io No resources found + _kubectl -n kube-system delete pods -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n kube-system delete pods -l kubevirt.io No resources found + _kubectl -n kube-system delete clusterrolebinding -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n kube-system delete clusterrolebinding -l kubevirt.io No resources found + _kubectl -n kube-system delete rolebinding -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n kube-system delete rolebinding -l kubevirt.io No resources found + _kubectl -n kube-system delete roles -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n kube-system delete roles -l kubevirt.io No resources found + _kubectl -n kube-system delete clusterroles -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n kube-system delete clusterroles -l kubevirt.io No resources found + _kubectl -n kube-system delete serviceaccounts -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl -n kube-system delete serviceaccounts -l kubevirt.io No resources found ++ _kubectl -n kube-system get crd offlinevirtualmachines.kubevirt.io ++ wc -l ++ export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig ++ KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig ++ cluster/k8s-1.11.0/.kubectl -n kube-system get crd offlinevirtualmachines.kubevirt.io No resources found. Error from server (NotFound): customresourcedefinitions.apiextensions.k8s.io "offlinevirtualmachines.kubevirt.io" not found + '[' 0 -gt 0 ']' + sleep 2 + echo Done Done ./cluster/deploy.sh + source hack/common.sh ++++ dirname 'hack/common.sh[0]' +++ cd hack/../ +++ pwd ++ KUBEVIRT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt ++ OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out ++ VENDOR_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/vendor ++ CMD_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out/cmd ++ TESTS_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out/tests ++ APIDOCS_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out/apidocs ++ MANIFESTS_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out/manifests ++ MANIFEST_TEMPLATES_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out/templates/manifests ++ PYTHON_CLIENT_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out/client-python ++ KUBEVIRT_PROVIDER=k8s-1.11.0 ++ KUBEVIRT_NUM_NODES=2 ++ '[' -z kubevirt-functional-tests-k8s-1.11.0-release ']' ++ provider_prefix=kubevirt-functional-tests-k8s-1.11.0-release1 ++ job_prefix=kubevirt-functional-tests-k8s-1.11.0-release1 +++ kubevirt_version +++ '[' -n '' ']' +++ '[' -d /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/.git ']' ++++ git describe --always --tags +++ echo v0.7.0-189-g96d0165 ++ KUBEVIRT_VERSION=v0.7.0-189-g96d0165 + source cluster/k8s-1.11.0/provider.sh ++ set -e ++ image=k8s-1.11.0@sha256:6c1caf5559eb02a144bf606de37eb0194c06ace4d77ad4561459f3bde876151c ++ source cluster/ephemeral-provider-common.sh +++ set -e +++ _cli='docker run --privileged --net=host --rm -v /var/run/docker.sock:/var/run/docker.sock kubevirtci/gocli@sha256:aa7f295a7908fa333ab5e98ef3af0bfafbabfd3cee2b83f9af47f722e3000f6a' + source hack/config.sh ++ unset binaries docker_images docker_prefix docker_tag manifest_templates master_ip network_provider kubeconfig manifest_docker_prefix namespace ++ KUBEVIRT_PROVIDER=k8s-1.11.0 ++ source hack/config-default.sh source hack/config-k8s-1.11.0.sh +++ binaries='cmd/virt-controller cmd/virt-launcher cmd/virt-handler cmd/virtctl cmd/fake-qemu-process cmd/virt-api cmd/subresource-access-test cmd/example-hook-sidecar' +++ docker_images='cmd/virt-controller cmd/virt-launcher cmd/virt-handler cmd/virt-api images/disks-images-provider images/vm-killer cmd/registry-disk-v1alpha images/cirros-registry-disk-demo images/fedora-cloud-registry-disk-demo images/alpine-registry-disk-demo cmd/subresource-access-test images/winrmcli cmd/example-hook-sidecar' +++ docker_prefix=kubevirt +++ docker_tag=latest +++ master_ip=192.168.200.2 +++ network_provider=flannel +++ namespace=kube-system ++ test -f hack/config-provider-k8s-1.11.0.sh ++ source hack/config-provider-k8s-1.11.0.sh +++ master_ip=127.0.0.1 +++ docker_tag=devel +++ kubeconfig=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/cluster/k8s-1.11.0/.kubeconfig +++ kubectl=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/cluster/k8s-1.11.0/.kubectl +++ docker_prefix=localhost:33331/kubevirt +++ manifest_docker_prefix=registry:5000/kubevirt ++ test -f hack/config-local.sh ++ export binaries docker_images docker_prefix docker_tag manifest_templates master_ip network_provider kubeconfig namespace + echo 'Deploying ...' Deploying ... + [[ -z k8s-1.11.0-release ]] + [[ k8s-1.11.0-release =~ .*-dev ]] + [[ k8s-1.11.0-release =~ .*-release ]] + for manifest in '${MANIFESTS_OUT_DIR}/release/*' + [[ /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out/manifests/release/demo-content.yaml =~ .*demo.* ]] + continue + for manifest in '${MANIFESTS_OUT_DIR}/release/*' + [[ /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out/manifests/release/kubevirt.yaml =~ .*demo.* ]] + _kubectl create -f /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out/manifests/release/kubevirt.yaml + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl create -f /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out/manifests/release/kubevirt.yaml clusterrole.rbac.authorization.k8s.io/kubevirt.io:admin created clusterrole.rbac.authorization.k8s.io/kubevirt.io:edit created clusterrole.rbac.authorization.k8s.io/kubevirt.io:view created serviceaccount/kubevirt-apiserver created clusterrolebinding.rbac.authorization.k8s.io/kubevirt-apiserver created clusterrolebinding.rbac.authorization.k8s.io/kubevirt-apiserver-auth-delegator created rolebinding.rbac.authorization.k8s.io/kubevirt-apiserver created role.rbac.authorization.k8s.io/kubevirt-apiserver created clusterrole.rbac.authorization.k8s.io/kubevirt-apiserver created clusterrole.rbac.authorization.k8s.io/kubevirt-controller created serviceaccount/kubevirt-controller created serviceaccount/kubevirt-privileged created clusterrolebinding.rbac.authorization.k8s.io/kubevirt-controller created clusterrolebinding.rbac.authorization.k8s.io/kubevirt-controller-cluster-admin created clusterrolebinding.rbac.authorization.k8s.io/kubevirt-privileged-cluster-admin created clusterrole.rbac.authorization.k8s.io/kubevirt.io:default created clusterrolebinding.rbac.authorization.k8s.io/kubevirt.io:default created service/virt-api created deployment.extensions/virt-api created deployment.extensions/virt-controller created daemonset.extensions/virt-handler created customresourcedefinition.apiextensions.k8s.io/virtualmachineinstances.kubevirt.io created customresourcedefinition.apiextensions.k8s.io/virtualmachineinstancereplicasets.kubevirt.io created customresourcedefinition.apiextensions.k8s.io/virtualmachineinstancepresets.kubevirt.io created customresourcedefinition.apiextensions.k8s.io/virtualmachines.kubevirt.io created + _kubectl create -f /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out/manifests/testing -R + export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig + cluster/k8s-1.11.0/.kubectl create -f /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/go/src/kubevirt.io/kubevirt/_out/manifests/testing -R persistentvolumeclaim/disk-alpine created persistentvolume/host-path-disk-alpine created persistentvolumeclaim/disk-custom created persistentvolume/host-path-disk-custom created daemonset.extensions/disks-images-provider created serviceaccount/kubevirt-testing created clusterrolebinding.rbac.authorization.k8s.io/kubevirt-testing-cluster-admin created + [[ k8s-1.11.0 =~ os-* ]] + echo Done Done + namespaces=(kube-system default) + [[ kube-system != \k\u\b\e\-\s\y\s\t\e\m ]] + timeout=300 + sample=30 + for i in '${namespaces[@]}' + current_time=0 ++ kubectl get pods -n kube-system --no-headers ++ grep -v Running ++ cluster/kubectl.sh get pods -n kube-system --no-headers + '[' -n 'virt-api-bcc6b587d-jtzlz 0/1 ContainerCreating 0 2s virt-api-bcc6b587d-qjd4t 0/1 ContainerCreating 0 2s virt-controller-67dcdd8464-4sb5c 0/1 ContainerCreating 0 2s virt-controller-67dcdd8464-54rkr 0/1 ContainerCreating 0 2s virt-handler-bjddl 0/1 ContainerCreating 0 2s virt-handler-dckgz 0/1 ContainerCreating 0 2s' ']' + echo 'Waiting for kubevirt pods to enter the Running state ...' Waiting for kubevirt pods to enter the Running state ... + kubectl get pods -n kube-system --no-headers + grep -v Running + cluster/kubectl.sh get pods -n kube-system --no-headers virt-api-bcc6b587d-jtzlz 0/1 ContainerCreating 0 2s virt-api-bcc6b587d-qjd4t 0/1 ContainerCreating 0 2s virt-controller-67dcdd8464-4sb5c 0/1 ContainerCreating 0 2s virt-controller-67dcdd8464-54rkr 0/1 ContainerCreating 0 2s virt-handler-bjddl 0/1 ContainerCreating 0 2s virt-handler-dckgz 0/1 ContainerCreating 0 2s + sleep 30 + current_time=30 + '[' 30 -gt 300 ']' ++ kubectl get pods -n kube-system --no-headers ++ grep -v Running ++ cluster/kubectl.sh get pods -n kube-system --no-headers + '[' -n '' ']' + current_time=0 ++ kubectl get pods -n kube-system '-ocustom-columns=status:status.containerStatuses[*].ready' --no-headers ++ grep false ++ cluster/kubectl.sh get pods -n kube-system '-ocustom-columns=status:status.containerStatuses[*].ready' --no-headers + '[' -n '' ']' + kubectl get pods -n kube-system + cluster/kubectl.sh get pods -n kube-system NAME READY STATUS RESTARTS AGE coredns-78fcdf6894-rrh5c 1/1 Running 0 7m coredns-78fcdf6894-vqm4k 1/1 Running 0 7m disks-images-provider-nbv8b 1/1 Running 0 30s disks-images-provider-pk27m 1/1 Running 0 30s etcd-node01 1/1 Running 0 6m kube-apiserver-node01 1/1 Running 0 6m kube-controller-manager-node01 1/1 Running 0 6m kube-flannel-ds-r2hrv 1/1 Running 0 7m kube-flannel-ds-t5s2d 1/1 Running 0 7m kube-proxy-75gwk 1/1 Running 0 7m kube-proxy-m2j4d 1/1 Running 0 7m kube-scheduler-node01 1/1 Running 0 6m virt-api-bcc6b587d-jtzlz 1/1 Running 0 33s virt-api-bcc6b587d-qjd4t 1/1 Running 0 33s virt-controller-67dcdd8464-4sb5c 1/1 Running 0 33s virt-controller-67dcdd8464-54rkr 1/1 Running 0 33s virt-handler-bjddl 1/1 Running 0 33s virt-handler-dckgz 1/1 Running 0 33s + for i in '${namespaces[@]}' + current_time=0 ++ kubectl get pods -n default --no-headers ++ cluster/kubectl.sh get pods -n default --no-headers ++ grep -v Running + '[' -n '' ']' + current_time=0 ++ kubectl get pods -n default '-ocustom-columns=status:status.containerStatuses[*].ready' --no-headers ++ cluster/kubectl.sh get pods -n default '-ocustom-columns=status:status.containerStatuses[*].ready' --no-headers ++ grep false + '[' -n '' ']' + kubectl get pods -n default + cluster/kubectl.sh get pods -n default NAME READY STATUS RESTARTS AGE local-volume-provisioner-6dtnt 1/1 Running 0 7m local-volume-provisioner-6lwjf 1/1 Running 0 7m + kubectl version + cluster/kubectl.sh version Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.0", GitCommit:"91e7b4fd31fcd3d5f436da26c980becec37ceefe", GitTreeState:"clean", BuildDate:"2018-06-27T20:17:28Z", GoVersion:"go1.10.2", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.0", GitCommit:"91e7b4fd31fcd3d5f436da26c980becec37ceefe", GitTreeState:"clean", BuildDate:"2018-06-27T20:08:34Z", GoVersion:"go1.10.2", Compiler:"gc", Platform:"linux/amd64"} + ginko_params='--ginkgo.noColor --junit-output=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/junit.xml' + [[ k8s-1.11.0-release =~ windows.* ]] + FUNC_TEST_ARGS='--ginkgo.noColor --junit-output=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-release/junit.xml' + make functest hack/dockerized "hack/build-func-tests.sh" sha256:ceba12cbc33e4e37a707840478a630db561e2427b78c8c9f9cd6d0b73276ab32 go version go1.10 linux/amd64 go version go1.10 linux/amd64 Compiling tests... compiled tests.test hack/functests.sh Running Suite: Tests Suite ========================== Random Seed: 1533329981 Will run 148 of 148 specs • Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running 2018/08/03 21:01:02 http: TLS handshake error from 10.244.0.1:39160: EOF 2018/08/03 21:01:12 http: TLS handshake error from 10.244.0.1:39220: EOF 2018/08/03 21:01:22 http: TLS handshake error from 10.244.0.1:39280: EOF level=info timestamp=2018-08-03T21:01:29.179015Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:01:32 http: TLS handshake error from 10.244.0.1:39340: EOF 2018/08/03 21:01:42 http: TLS handshake error from 10.244.0.1:39400: EOF 2018/08/03 21:01:52 http: TLS handshake error from 10.244.0.1:39460: EOF level=info timestamp=2018-08-03T21:01:59.151289Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:01:59.158826Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:01:59.214723Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:02:02 http: TLS handshake error from 10.244.0.1:39520: EOF 2018/08/03 21:02:12 http: TLS handshake error from 10.244.0.1:39580: EOF 2018/08/03 21:02:22 http: TLS handshake error from 10.244.0.1:39640: EOF level=info timestamp=2018-08-03T21:02:29.156688Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:02:32 http: TLS handshake error from 10.244.0.1:39700: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T21:01:53.428893Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:01:53.742920Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:01:56 http: TLS handshake error from 10.244.1.1:33766: EOF level=info timestamp=2018-08-03T21:02:00.198182Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:02:04.861097Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:02:04.862302Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:02:05.176127Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:02:06 http: TLS handshake error from 10.244.1.1:33772: EOF 2018/08/03 21:02:16 http: TLS handshake error from 10.244.1.1:33778: EOF level=info timestamp=2018-08-03T21:02:23.477174Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:02:23.795190Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:02:26 http: TLS handshake error from 10.244.1.1:33784: EOF level=info timestamp=2018-08-03T21:02:30.218943Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:02:35.229664Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:02:36 http: TLS handshake error from 10.244.1.1:33790: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T20:59:02.622108Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmiInformer" level=info timestamp=2018-08-03T20:59:02.622139Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer kubeVirtPodInformer" level=info timestamp=2018-08-03T20:59:02.622164Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer kubeVirtNodeInformer" level=info timestamp=2018-08-03T20:59:02.622278Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmiPresetInformer" level=info timestamp=2018-08-03T20:59:02.622401Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmirsInformer" level=info timestamp=2018-08-03T20:59:02.622429Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T20:59:02.622686Z pos=vm.go:85 component=virt-controller service=http msg="Starting VirtualMachine controller." level=info timestamp=2018-08-03T20:59:02.629215Z pos=node.go:104 component=virt-controller service=http msg="Starting node controller." level=info timestamp=2018-08-03T20:59:02.629283Z pos=vmi.go:129 component=virt-controller service=http msg="Starting vmi controller." level=info timestamp=2018-08-03T20:59:02.629320Z pos=replicaset.go:111 component=virt-controller service=http msg="Starting VirtualMachineInstanceReplicaSet controller." level=info timestamp=2018-08-03T20:59:02.629384Z pos=preset.go:74 component=virt-controller service=http msg="Starting Virtual Machine Initializer." level=info timestamp=2018-08-03T20:59:41.805641Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8whgc kind= uid=240382f8-9760-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T20:59:41.807162Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8whgc kind= uid=240382f8-9760-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T20:59:42.182188Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikvvtn kind= uid=2443a054-9760-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T20:59:42.182355Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikvvtn kind= uid=2443a054-9760-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-bjddl Pod phase: Running level=info timestamp=2018-08-03T20:59:04.565554Z pos=virt-handler.go:89 component=virt-handler hostname=node02 level=info timestamp=2018-08-03T20:59:04.572490Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T20:59:05.072933Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T20:59:05.073624Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=info timestamp=2018-08-03T20:59:05.076625Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:00:53.037453Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:01:57.780654Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=info timestamp=2018-08-03T20:59:04.753622Z pos=virt-handler.go:89 component=virt-handler hostname=node01 level=info timestamp=2018-08-03T20:59:04.763811Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T20:59:04.971209Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=info timestamp=2018-08-03T20:59:04.980637Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T20:59:04.983943Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:00:52.868308Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:01:57.610617Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmikvvtn-2x7lw Pod phase: Pending ------------------------------ • Failure [180.610 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Creating a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:72 should start it [It] /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:78 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T20:59:42.454723Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmikvvtn kind=VirtualMachineInstance uid=2443a054-9760-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmikvvtn-2x7lw" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T21:03:59.160245Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:04:02 http: TLS handshake error from 10.244.0.1:40244: EOF 2018/08/03 21:04:12 http: TLS handshake error from 10.244.0.1:40304: EOF 2018/08/03 21:04:22 http: TLS handshake error from 10.244.0.1:40364: EOF level=info timestamp=2018-08-03T21:04:29.157565Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:04:32 http: TLS handshake error from 10.244.0.1:40424: EOF 2018/08/03 21:04:42 http: TLS handshake error from 10.244.0.1:40484: EOF 2018/08/03 21:04:52 http: TLS handshake error from 10.244.0.1:40544: EOF level=info timestamp=2018-08-03T21:04:59.184958Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:05:02 http: TLS handshake error from 10.244.0.1:40604: EOF 2018/08/03 21:05:12 http: TLS handshake error from 10.244.0.1:40664: EOF 2018/08/03 21:05:22 http: TLS handshake error from 10.244.0.1:40724: EOF level=info timestamp=2018-08-03T21:05:29.184971Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:05:32 http: TLS handshake error from 10.244.0.1:40784: EOF 2018/08/03 21:05:42 http: TLS handshake error from 10.244.0.1:40844: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T21:04:53.735786Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:04:54.060426Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:04:56 http: TLS handshake error from 10.244.1.1:33874: EOF level=info timestamp=2018-08-03T21:05:00.308536Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:05:04.866805Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:05:04.867976Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:05:05.496903Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:05:06 http: TLS handshake error from 10.244.1.1:33880: EOF 2018/08/03 21:05:16 http: TLS handshake error from 10.244.1.1:33886: EOF level=info timestamp=2018-08-03T21:05:23.791892Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:05:24.104610Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:05:26 http: TLS handshake error from 10.244.1.1:33892: EOF level=info timestamp=2018-08-03T21:05:30.331452Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:05:35.551520Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:05:36 http: TLS handshake error from 10.244.1.1:33898: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T20:59:02.622401Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmirsInformer" level=info timestamp=2018-08-03T20:59:02.622429Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T20:59:02.622686Z pos=vm.go:85 component=virt-controller service=http msg="Starting VirtualMachine controller." level=info timestamp=2018-08-03T20:59:02.629215Z pos=node.go:104 component=virt-controller service=http msg="Starting node controller." level=info timestamp=2018-08-03T20:59:02.629283Z pos=vmi.go:129 component=virt-controller service=http msg="Starting vmi controller." level=info timestamp=2018-08-03T20:59:02.629320Z pos=replicaset.go:111 component=virt-controller service=http msg="Starting VirtualMachineInstanceReplicaSet controller." level=info timestamp=2018-08-03T20:59:02.629384Z pos=preset.go:74 component=virt-controller service=http msg="Starting Virtual Machine Initializer." level=info timestamp=2018-08-03T20:59:41.805641Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8whgc kind= uid=240382f8-9760-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T20:59:41.807162Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8whgc kind= uid=240382f8-9760-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T20:59:42.182188Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikvvtn kind= uid=2443a054-9760-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T20:59:42.182355Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikvvtn kind= uid=2443a054-9760-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:02:42.636201Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin9cp4 kind= uid=8fd2f648-9760-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:02:42.637601Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin9cp4 kind= uid=8fd2f648-9760-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:02:42.707673Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmin9cp4\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmin9cp4" level=info timestamp=2018-08-03T21:02:42.721225Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmin9cp4\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmin9cp4" Pod name: virt-handler-bjddl Pod phase: Running level=info timestamp=2018-08-03T20:59:04.565554Z pos=virt-handler.go:89 component=virt-handler hostname=node02 level=info timestamp=2018-08-03T20:59:04.572490Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T20:59:05.072933Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T20:59:05.073624Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=info timestamp=2018-08-03T20:59:05.076625Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:00:53.037453Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:01:57.780654Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:09.067392Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:16.060713Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.742384Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=info timestamp=2018-08-03T20:59:04.753622Z pos=virt-handler.go:89 component=virt-handler hostname=node01 level=info timestamp=2018-08-03T20:59:04.763811Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T20:59:04.971209Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=info timestamp=2018-08-03T20:59:04.980637Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T20:59:04.983943Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:00:52.868308Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:01:57.610617Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:08.892924Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:15.888504Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.567968Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmin9cp4-drl9p Pod phase: Pending • Failure [180.440 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Creating a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:72 should attach virt-launcher to it [It] /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:84 Timed out after 90.006s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T21:02:42.899039Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmin9cp4 kind=VirtualMachineInstance uid=8fd2f648-9760-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmin9cp4-drl9p" •••• Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T21:06:59.185023Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:07:02 http: TLS handshake error from 10.244.0.1:41324: EOF 2018/08/03 21:07:12 http: TLS handshake error from 10.244.0.1:41384: EOF 2018/08/03 21:07:22 http: TLS handshake error from 10.244.0.1:41444: EOF level=info timestamp=2018-08-03T21:07:29.188453Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:07:32 http: TLS handshake error from 10.244.0.1:41504: EOF 2018/08/03 21:07:42 http: TLS handshake error from 10.244.0.1:41564: EOF 2018/08/03 21:07:52 http: TLS handshake error from 10.244.0.1:41624: EOF level=info timestamp=2018-08-03T21:07:59.168151Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:08:02 http: TLS handshake error from 10.244.0.1:41684: EOF 2018/08/03 21:08:12 http: TLS handshake error from 10.244.0.1:41744: EOF 2018/08/03 21:08:22 http: TLS handshake error from 10.244.0.1:41804: EOF level=info timestamp=2018-08-03T21:08:29.195723Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:08:32 http: TLS handshake error from 10.244.0.1:41864: EOF 2018/08/03 21:08:42 http: TLS handshake error from 10.244.0.1:41924: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T21:07:54.061496Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:07:54.365306Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:07:56 http: TLS handshake error from 10.244.1.1:33982: EOF level=info timestamp=2018-08-03T21:08:00.426224Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:08:04.920028Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:08:04.921312Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:08:05.819036Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:08:06 http: TLS handshake error from 10.244.1.1:33988: EOF 2018/08/03 21:08:16 http: TLS handshake error from 10.244.1.1:33994: EOF level=info timestamp=2018-08-03T21:08:24.111787Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:08:24.417304Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:08:26 http: TLS handshake error from 10.244.1.1:34000: EOF level=info timestamp=2018-08-03T21:08:30.445943Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:08:35.872754Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:08:36 http: TLS handshake error from 10.244.1.1:34006: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T20:59:42.182188Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikvvtn kind= uid=2443a054-9760-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T20:59:42.182355Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikvvtn kind= uid=2443a054-9760-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:02:42.636201Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin9cp4 kind= uid=8fd2f648-9760-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:02:42.637601Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin9cp4 kind= uid=8fd2f648-9760-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:02:42.707673Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmin9cp4\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmin9cp4" level=info timestamp=2018-08-03T21:02:42.721225Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmin9cp4\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmin9cp4" level=info timestamp=2018-08-03T21:05:43.169647Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmissg7t kind= uid=fb6e5b7b-9760-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:05:43.169830Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmissg7t kind= uid=fb6e5b7b-9760-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:05:43.207716Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmissg7t\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmissg7t" level=info timestamp=2018-08-03T21:05:43.213934Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmissg7t\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmissg7t" level=info timestamp=2018-08-03T21:05:43.260171Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmissg7t\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmissg7t, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: fb6e5b7b-9760-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmissg7t" level=info timestamp=2018-08-03T21:05:43.386983Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmit94kq kind= uid=fb8fce87-9760-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:05:43.387122Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmit94kq kind= uid=fb8fce87-9760-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:05:43.617283Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih2qsh kind= uid=fbb2d92f-9760-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:05:43.617397Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih2qsh kind= uid=fbb2d92f-9760-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-bjddl Pod phase: Running level=info timestamp=2018-08-03T20:59:04.565554Z pos=virt-handler.go:89 component=virt-handler hostname=node02 level=info timestamp=2018-08-03T20:59:04.572490Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T20:59:05.072933Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T20:59:05.073624Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=info timestamp=2018-08-03T20:59:05.076625Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:00:53.037453Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:01:57.780654Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:09.067392Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:16.060713Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.742384Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:07:14.853959Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=info timestamp=2018-08-03T20:59:04.753622Z pos=virt-handler.go:89 component=virt-handler hostname=node01 level=info timestamp=2018-08-03T20:59:04.763811Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T20:59:04.971209Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=info timestamp=2018-08-03T20:59:04.980637Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T20:59:04.983943Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:00:52.868308Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:01:57.610617Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:08.892924Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:15.888504Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.567968Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:07:14.678144Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmih2qsh-6qpvh Pod phase: Pending ------------------------------ • Failure [180.444 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Creating a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:72 with boot order /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:172 should be able to boot from selected disk /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 Alpine as first boot [It] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.005s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ STEP: defining a VirtualMachineInstance with an Alpine disk STEP: adding a Cirros Disk STEP: setting boot order STEP: starting VirtualMachineInstance STEP: Waiting the VirtualMachineInstance start level=info timestamp=2018-08-03T21:05:43.873519Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmih2qsh kind=VirtualMachineInstance uid=fbb2d92f-9760-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmih2qsh-6qpvh" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T21:09:59.184775Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:10:02 http: TLS handshake error from 10.244.0.1:42404: EOF 2018/08/03 21:10:12 http: TLS handshake error from 10.244.0.1:42464: EOF 2018/08/03 21:10:22 http: TLS handshake error from 10.244.0.1:42524: EOF level=info timestamp=2018-08-03T21:10:29.200744Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:10:32 http: TLS handshake error from 10.244.0.1:42584: EOF 2018/08/03 21:10:42 http: TLS handshake error from 10.244.0.1:42644: EOF 2018/08/03 21:10:52 http: TLS handshake error from 10.244.0.1:42704: EOF level=info timestamp=2018-08-03T21:10:59.173778Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:11:02 http: TLS handshake error from 10.244.0.1:42764: EOF 2018/08/03 21:11:12 http: TLS handshake error from 10.244.0.1:42824: EOF 2018/08/03 21:11:22 http: TLS handshake error from 10.244.0.1:42884: EOF level=info timestamp=2018-08-03T21:11:29.160905Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:11:32 http: TLS handshake error from 10.244.0.1:42944: EOF 2018/08/03 21:11:42 http: TLS handshake error from 10.244.0.1:43004: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T21:10:36.086315Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:10:46 http: TLS handshake error from 10.244.1.1:34084: EOF level=info timestamp=2018-08-03T21:10:54.374599Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:10:54.676115Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:10:56 http: TLS handshake error from 10.244.1.1:34090: EOF level=info timestamp=2018-08-03T21:11:00.572861Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:11:06 http: TLS handshake error from 10.244.1.1:34096: EOF level=info timestamp=2018-08-03T21:11:06.139674Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:11:16 http: TLS handshake error from 10.244.1.1:34102: EOF level=info timestamp=2018-08-03T21:11:24.426384Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:11:24.732702Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:11:26 http: TLS handshake error from 10.244.1.1:34108: EOF level=info timestamp=2018-08-03T21:11:30.595782Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:11:36 http: TLS handshake error from 10.244.1.1:34114: EOF level=info timestamp=2018-08-03T21:11:36.192699Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T21:02:42.636201Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin9cp4 kind= uid=8fd2f648-9760-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:02:42.637601Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin9cp4 kind= uid=8fd2f648-9760-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:02:42.707673Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmin9cp4\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmin9cp4" level=info timestamp=2018-08-03T21:02:42.721225Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmin9cp4\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmin9cp4" level=info timestamp=2018-08-03T21:05:43.169647Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmissg7t kind= uid=fb6e5b7b-9760-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:05:43.169830Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmissg7t kind= uid=fb6e5b7b-9760-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:05:43.207716Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmissg7t\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmissg7t" level=info timestamp=2018-08-03T21:05:43.213934Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmissg7t\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmissg7t" level=info timestamp=2018-08-03T21:05:43.260171Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmissg7t\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmissg7t, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: fb6e5b7b-9760-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmissg7t" level=info timestamp=2018-08-03T21:05:43.386983Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmit94kq kind= uid=fb8fce87-9760-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:05:43.387122Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmit94kq kind= uid=fb8fce87-9760-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:05:43.617283Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih2qsh kind= uid=fbb2d92f-9760-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:05:43.617397Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih2qsh kind= uid=fbb2d92f-9760-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:08:44.089011Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitm445 kind= uid=6741acb3-9761-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:08:44.089163Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitm445 kind= uid=6741acb3-9761-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-bjddl Pod phase: Running level=info timestamp=2018-08-03T20:59:04.565554Z pos=virt-handler.go:89 component=virt-handler hostname=node02 level=info timestamp=2018-08-03T20:59:04.572490Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T20:59:05.072933Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T20:59:05.073624Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=info timestamp=2018-08-03T20:59:05.076625Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:00:53.037453Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:01:57.780654Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:09.067392Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:16.060713Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.742384Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:07:14.853959Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:09:13.451265Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:10:47.264832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=info timestamp=2018-08-03T20:59:04.753622Z pos=virt-handler.go:89 component=virt-handler hostname=node01 level=info timestamp=2018-08-03T20:59:04.763811Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T20:59:04.971209Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=info timestamp=2018-08-03T20:59:04.980637Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T20:59:04.983943Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:00:52.868308Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:01:57.610617Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:08.892924Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:15.888504Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.567968Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:07:14.678144Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:09:13.274993Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:10:47.051196Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmitm445-ncqz9 Pod phase: Pending • Failure [180.477 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Creating a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:72 with boot order /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:172 should be able to boot from selected disk /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 Cirros as first boot [It] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ STEP: defining a VirtualMachineInstance with an Alpine disk STEP: adding a Cirros Disk STEP: setting boot order STEP: starting VirtualMachineInstance STEP: Waiting the VirtualMachineInstance start level=info timestamp=2018-08-03T21:08:44.360392Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmitm445 kind=VirtualMachineInstance uid=6741acb3-9761-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmitm445-ncqz9" • [SLOW TEST:60.236 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Creating a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:72 with user-data /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:203 without k8s secret /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:204 should retry starting the VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:205 ------------------------------ •! Panic [60.225 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Creating a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:72 with user-data /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:203 without k8s secret /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:204 should log warning and proceed once the secret is there [It] /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:235 Test Panicked runtime error: invalid memory address or nil pointer dereference /gimme/.gimme/versions/go1.10.linux.amd64/src/runtime/panic.go:505 Full Stack Trace /gimme/.gimme/versions/go1.10.linux.amd64/src/runtime/panic.go:505 +0x229 kubevirt.io/kubevirt/tests_test.glob..func16.3.9.1.2() /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:256 +0x431 kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*runner).runSync(0xc4202871a0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /root/go/src/kubevirt.io/kubevirt/tests/tests_suite_test.go:43 +0xaa testing.tRunner(0xc4200efe00, 0x1339680) /gimme/.gimme/versions/go1.10.linux.amd64/src/testing/testing.go:777 +0xd0 created by testing.(*T).Run /gimme/.gimme/versions/go1.10.linux.amd64/src/testing/testing.go:824 +0x2e0 ------------------------------ STEP: Starting a VirtualMachineInstance STEP: Checking that VirtualMachineInstance start failed level=info timestamp=2018-08-03T21:12:45.011492Z pos=utils.go:255 component=tests namespace=kubevirt-test-default name=testvmibb6vt kind=VirtualMachineInstance uid=f6ba7f5b-9761-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmibb6vt-jn89g" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T21:14:59.163039Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:15:02 http: TLS handshake error from 10.244.0.1:44204: EOF 2018/08/03 21:15:12 http: TLS handshake error from 10.244.0.1:44264: EOF 2018/08/03 21:15:22 http: TLS handshake error from 10.244.0.1:44324: EOF level=info timestamp=2018-08-03T21:15:29.186341Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:15:32 http: TLS handshake error from 10.244.0.1:44384: EOF 2018/08/03 21:15:42 http: TLS handshake error from 10.244.0.1:44444: EOF 2018/08/03 21:15:52 http: TLS handshake error from 10.244.0.1:44504: EOF level=info timestamp=2018-08-03T21:15:59.184724Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:16:02 http: TLS handshake error from 10.244.0.1:44564: EOF 2018/08/03 21:16:12 http: TLS handshake error from 10.244.0.1:44624: EOF 2018/08/03 21:16:22 http: TLS handshake error from 10.244.0.1:44684: EOF level=info timestamp=2018-08-03T21:16:29.166739Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:16:32 http: TLS handshake error from 10.244.0.1:44744: EOF 2018/08/03 21:16:42 http: TLS handshake error from 10.244.0.1:44804: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T21:15:36.620738Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:15:46 http: TLS handshake error from 10.244.1.1:34264: EOF level=info timestamp=2018-08-03T21:15:54.903239Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:15:55.193869Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:15:56 http: TLS handshake error from 10.244.1.1:34270: EOF level=info timestamp=2018-08-03T21:16:00.780315Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:16:06 http: TLS handshake error from 10.244.1.1:34276: EOF level=info timestamp=2018-08-03T21:16:06.674378Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:16:16 http: TLS handshake error from 10.244.1.1:34282: EOF level=info timestamp=2018-08-03T21:16:24.955269Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:16:25.249045Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:16:26 http: TLS handshake error from 10.244.1.1:34288: EOF level=info timestamp=2018-08-03T21:16:30.799596Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:16:36 http: TLS handshake error from 10.244.1.1:34294: EOF level=info timestamp=2018-08-03T21:16:36.727889Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T21:05:43.386983Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmit94kq kind= uid=fb8fce87-9760-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:05:43.387122Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmit94kq kind= uid=fb8fce87-9760-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:05:43.617283Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih2qsh kind= uid=fbb2d92f-9760-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:05:43.617397Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih2qsh kind= uid=fbb2d92f-9760-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:08:44.089011Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitm445 kind= uid=6741acb3-9761-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:08:44.089163Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitm445 kind= uid=6741acb3-9761-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:11:44.549741Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4b4xm kind= uid=d2d3cf04-9761-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:11:44.549902Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4b4xm kind= uid=d2d3cf04-9761-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:11:44.587455Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi4b4xm\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi4b4xm" level=info timestamp=2018-08-03T21:12:44.776965Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibb6vt kind= uid=f6ba7f5b-9761-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:12:44.777102Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibb6vt kind= uid=f6ba7f5b-9761-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:12:44.804508Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmibb6vt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmibb6vt" level=info timestamp=2018-08-03T21:13:45.042258Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi999sh kind= uid=1aa1faad-9762-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:13:45.042469Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi999sh kind= uid=1aa1faad-9762-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:13:45.119722Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi999sh\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi999sh" Pod name: virt-handler-bjddl Pod phase: Running level=info timestamp=2018-08-03T20:59:05.072933Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T20:59:05.073624Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=info timestamp=2018-08-03T20:59:05.076625Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:00:53.037453Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:01:57.780654Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:09.067392Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:16.060713Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.742384Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:07:14.853959Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:09:13.451265Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:10:47.264832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:07.658851Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:13:28.777336Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:15:17.688496Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:16:32.338048Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=info timestamp=2018-08-03T20:59:04.971209Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=info timestamp=2018-08-03T20:59:04.980637Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T20:59:04.983943Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:00:52.868308Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:01:57.610617Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:08.892924Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:15.888504Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.567968Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:07:14.678144Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:09:13.274993Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:10:47.051196Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:07.443128Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:13:28.565673Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:15:17.469257Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:16:32.109632Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmi999sh-8gcrk Pod phase: Pending • Failure [180.488 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Creating a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:72 when virt-launcher crashes /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:283 should be stopped and have Failed phase [It] /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:284 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T21:13:45.369693Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi999sh kind=VirtualMachineInstance uid=1aa1faad-9762-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi999sh-8gcrk" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T21:17:59.188075Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:18:02 http: TLS handshake error from 10.244.0.1:45284: EOF 2018/08/03 21:18:12 http: TLS handshake error from 10.244.0.1:45344: EOF 2018/08/03 21:18:22 http: TLS handshake error from 10.244.0.1:45404: EOF level=info timestamp=2018-08-03T21:18:29.163791Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:18:32 http: TLS handshake error from 10.244.0.1:45464: EOF 2018/08/03 21:18:42 http: TLS handshake error from 10.244.0.1:45524: EOF 2018/08/03 21:18:52 http: TLS handshake error from 10.244.0.1:45584: EOF level=info timestamp=2018-08-03T21:18:59.202505Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:19:02 http: TLS handshake error from 10.244.0.1:45644: EOF 2018/08/03 21:19:12 http: TLS handshake error from 10.244.0.1:45704: EOF 2018/08/03 21:19:22 http: TLS handshake error from 10.244.0.1:45764: EOF level=info timestamp=2018-08-03T21:19:29.193269Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:19:32 http: TLS handshake error from 10.244.0.1:45824: EOF 2018/08/03 21:19:42 http: TLS handshake error from 10.244.0.1:45884: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T21:18:36.940273Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:18:46 http: TLS handshake error from 10.244.1.1:34372: EOF level=info timestamp=2018-08-03T21:18:55.212746Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:18:55.509951Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:18:56 http: TLS handshake error from 10.244.1.1:34378: EOF level=info timestamp=2018-08-03T21:19:00.897104Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:19:06 http: TLS handshake error from 10.244.1.1:34384: EOF level=info timestamp=2018-08-03T21:19:06.993089Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:19:16 http: TLS handshake error from 10.244.1.1:34390: EOF level=info timestamp=2018-08-03T21:19:25.267397Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:19:25.559163Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:19:26 http: TLS handshake error from 10.244.1.1:34396: EOF level=info timestamp=2018-08-03T21:19:30.915167Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:19:36 http: TLS handshake error from 10.244.1.1:34402: EOF level=info timestamp=2018-08-03T21:19:37.047540Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T21:05:43.617397Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih2qsh kind= uid=fbb2d92f-9760-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:08:44.089011Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitm445 kind= uid=6741acb3-9761-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:08:44.089163Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitm445 kind= uid=6741acb3-9761-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:11:44.549741Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4b4xm kind= uid=d2d3cf04-9761-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:11:44.549902Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4b4xm kind= uid=d2d3cf04-9761-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:11:44.587455Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi4b4xm\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi4b4xm" level=info timestamp=2018-08-03T21:12:44.776965Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibb6vt kind= uid=f6ba7f5b-9761-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:12:44.777102Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibb6vt kind= uid=f6ba7f5b-9761-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:12:44.804508Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmibb6vt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmibb6vt" level=info timestamp=2018-08-03T21:13:45.042258Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi999sh kind= uid=1aa1faad-9762-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:13:45.042469Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi999sh kind= uid=1aa1faad-9762-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:13:45.119722Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi999sh\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi999sh" level=info timestamp=2018-08-03T21:16:45.491808Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4dt2g kind= uid=86349ec9-9762-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:16:45.491949Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4dt2g kind= uid=86349ec9-9762-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:16:45.542075Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi4dt2g\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi4dt2g" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T20:59:05.073624Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=info timestamp=2018-08-03T20:59:05.076625Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:00:53.037453Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:01:57.780654Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:09.067392Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:16.060713Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.742384Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:07:14.853959Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:09:13.451265Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:10:47.264832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:07.658851Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:13:28.777336Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:15:17.688496Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:16:32.338048Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:18:13.438893Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=info timestamp=2018-08-03T20:59:04.980637Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T20:59:04.983943Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:00:52.868308Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:01:57.610617Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:08.892924Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:15.888504Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.567968Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:07:14.678144Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:09:13.274993Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:10:47.051196Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:07.443128Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:13:28.565673Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:15:17.469257Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:16:32.109632Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:18:13.210218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmi4dt2g-bkns6 Pod phase: Pending • Failure [180.442 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Creating a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:72 when virt-handler crashes /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:307 should recover and continue management [It] /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:308 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T21:16:45.731229Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi4dt2g kind=VirtualMachineInstance uid=86349ec9-9762-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi4dt2g-bkns6" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T21:17:59.188075Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:18:02 http: TLS handshake error from 10.244.0.1:45284: EOF 2018/08/03 21:18:12 http: TLS handshake error from 10.244.0.1:45344: EOF 2018/08/03 21:18:22 http: TLS handshake error from 10.244.0.1:45404: EOF level=info timestamp=2018-08-03T21:18:29.163791Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:18:32 http: TLS handshake error from 10.244.0.1:45464: EOF 2018/08/03 21:18:42 http: TLS handshake error from 10.244.0.1:45524: EOF 2018/08/03 21:18:52 http: TLS handshake error from 10.244.0.1:45584: EOF level=info timestamp=2018-08-03T21:18:59.202505Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:19:02 http: TLS handshake error from 10.244.0.1:45644: EOF 2018/08/03 21:19:12 http: TLS handshake error from 10.244.0.1:45704: EOF 2018/08/03 21:19:22 http: TLS handshake error from 10.244.0.1:45764: EOF level=info timestamp=2018-08-03T21:19:29.193269Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:19:32 http: TLS handshake error from 10.244.0.1:45824: EOF 2018/08/03 21:19:42 http: TLS handshake error from 10.244.0.1:45884: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T21:18:36.940273Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:18:46 http: TLS handshake error from 10.244.1.1:34372: EOF level=info timestamp=2018-08-03T21:18:55.212746Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:18:55.509951Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:18:56 http: TLS handshake error from 10.244.1.1:34378: EOF level=info timestamp=2018-08-03T21:19:00.897104Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:19:06 http: TLS handshake error from 10.244.1.1:34384: EOF level=info timestamp=2018-08-03T21:19:06.993089Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:19:16 http: TLS handshake error from 10.244.1.1:34390: EOF level=info timestamp=2018-08-03T21:19:25.267397Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:19:25.559163Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:19:26 http: TLS handshake error from 10.244.1.1:34396: EOF level=info timestamp=2018-08-03T21:19:30.915167Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:19:36 http: TLS handshake error from 10.244.1.1:34402: EOF level=info timestamp=2018-08-03T21:19:37.047540Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T21:05:43.617397Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih2qsh kind= uid=fbb2d92f-9760-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:08:44.089011Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitm445 kind= uid=6741acb3-9761-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:08:44.089163Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitm445 kind= uid=6741acb3-9761-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:11:44.549741Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4b4xm kind= uid=d2d3cf04-9761-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:11:44.549902Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4b4xm kind= uid=d2d3cf04-9761-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:11:44.587455Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi4b4xm\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi4b4xm" level=info timestamp=2018-08-03T21:12:44.776965Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibb6vt kind= uid=f6ba7f5b-9761-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:12:44.777102Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibb6vt kind= uid=f6ba7f5b-9761-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:12:44.804508Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmibb6vt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmibb6vt" level=info timestamp=2018-08-03T21:13:45.042258Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi999sh kind= uid=1aa1faad-9762-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:13:45.042469Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi999sh kind= uid=1aa1faad-9762-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:13:45.119722Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi999sh\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi999sh" level=info timestamp=2018-08-03T21:16:45.491808Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4dt2g kind= uid=86349ec9-9762-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:16:45.491949Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4dt2g kind= uid=86349ec9-9762-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:16:45.542075Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi4dt2g\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi4dt2g" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T20:59:05.073624Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=info timestamp=2018-08-03T20:59:05.076625Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:00:53.037453Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:01:57.780654Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:09.067392Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:16.060713Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.742384Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:07:14.853959Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:09:13.451265Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:10:47.264832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:07.658851Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:13:28.777336Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:15:17.688496Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:16:32.338048Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:18:13.438893Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=info timestamp=2018-08-03T20:59:04.980637Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T20:59:04.983943Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:00:52.868308Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:01:57.610617Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:08.892924Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:15.888504Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.567968Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:07:14.678144Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:09:13.274993Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:10:47.051196Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:07.443128Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:13:28.565673Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:15:17.469257Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:16:32.109632Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:18:13.210218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" • Failure [0.331 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Creating a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:72 when virt-handler is responsive /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:338 should indicate that a node is ready for vmis [It] /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:339 Expected <[]v1.Node | len:0, cap:0>: [] not to be empty /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:344 ------------------------------ STEP: adding a heartbeat annotation and a schedulable label to the node Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running 2018/08/03 21:21:02 http: TLS handshake error from 10.244.0.1:46364: EOF 2018/08/03 21:21:12 http: TLS handshake error from 10.244.0.1:46424: EOF 2018/08/03 21:21:22 http: TLS handshake error from 10.244.0.1:46484: EOF level=info timestamp=2018-08-03T21:21:29.185916Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:21:32 http: TLS handshake error from 10.244.0.1:46544: EOF 2018/08/03 21:21:42 http: TLS handshake error from 10.244.0.1:46604: EOF 2018/08/03 21:21:52 http: TLS handshake error from 10.244.0.1:46664: EOF level=info timestamp=2018-08-03T21:21:59.152165Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:21:59.215757Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:22:02 http: TLS handshake error from 10.244.0.1:46724: EOF 2018/08/03 21:22:12 http: TLS handshake error from 10.244.0.1:46784: EOF 2018/08/03 21:22:22 http: TLS handshake error from 10.244.0.1:46844: EOF level=info timestamp=2018-08-03T21:22:29.165788Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:22:32 http: TLS handshake error from 10.244.0.1:46904: EOF 2018/08/03 21:22:42 http: TLS handshake error from 10.244.0.1:46964: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T21:21:55.823168Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:21:56 http: TLS handshake error from 10.244.1.1:34486: EOF level=info timestamp=2018-08-03T21:22:01.014910Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:22:04.836427Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:22:04.837617Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:22:06 http: TLS handshake error from 10.244.1.1:34492: EOF level=info timestamp=2018-08-03T21:22:07.314977Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:22:16 http: TLS handshake error from 10.244.1.1:34498: EOF level=info timestamp=2018-08-03T21:22:25.572081Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:22:25.884289Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:22:26 http: TLS handshake error from 10.244.1.1:34504: EOF level=info timestamp=2018-08-03T21:22:31.041051Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:22:36 http: TLS handshake error from 10.244.1.1:34510: EOF level=info timestamp=2018-08-03T21:22:37.372058Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:22:46 http: TLS handshake error from 10.244.1.1:34516: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T21:11:44.587455Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi4b4xm\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi4b4xm" level=info timestamp=2018-08-03T21:12:44.776965Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibb6vt kind= uid=f6ba7f5b-9761-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:12:44.777102Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibb6vt kind= uid=f6ba7f5b-9761-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:12:44.804508Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmibb6vt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmibb6vt" level=info timestamp=2018-08-03T21:13:45.042258Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi999sh kind= uid=1aa1faad-9762-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:13:45.042469Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi999sh kind= uid=1aa1faad-9762-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:13:45.119722Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi999sh\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi999sh" level=info timestamp=2018-08-03T21:16:45.491808Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4dt2g kind= uid=86349ec9-9762-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:16:45.491949Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4dt2g kind= uid=86349ec9-9762-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:16:45.542075Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi4dt2g\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi4dt2g" level=info timestamp=2018-08-03T21:19:46.092024Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitl8ng kind= uid=f1d9f13a-9762-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:19:46.092212Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitl8ng kind= uid=f1d9f13a-9762-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:19:46.126369Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitl8ng\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitl8ng" level=info timestamp=2018-08-03T21:19:46.137397Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitl8ng\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitl8ng" level=info timestamp=2018-08-03T21:19:46.146280Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitl8ng\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitl8ng" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:00:53.037453Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:01:57.780654Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:09.067392Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:16.060713Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.742384Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:07:14.853959Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:09:13.451265Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:10:47.264832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:07.658851Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:13:28.777336Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:15:17.688496Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:16:32.338048Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:18:13.438893Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:20:15.550940Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:21:36.668841Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:00:52.868308Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:01:57.610617Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:08.892924Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:15.888504Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.567968Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:07:14.678144Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:09:13.274993Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:10:47.051196Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:07.443128Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:13:28.565673Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:15:17.469257Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:16:32.109632Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:18:13.210218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:20:15.325675Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:21:36.439524Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmitl8ng-c7flq Pod phase: Pending • Failure in Spec Setup (BeforeEach) [180.264 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Creating a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:72 when virt-handler is not responsive /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:369 the node controller should react [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:408 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T21:19:46.408171Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmitl8ng kind=VirtualMachineInstance uid=f1d9f13a-9762-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmitl8ng-c7flq" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T21:23:59.199790Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:24:02 http: TLS handshake error from 10.244.0.1:47444: EOF 2018/08/03 21:24:12 http: TLS handshake error from 10.244.0.1:47504: EOF 2018/08/03 21:24:22 http: TLS handshake error from 10.244.0.1:47564: EOF level=info timestamp=2018-08-03T21:24:29.201688Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:24:32 http: TLS handshake error from 10.244.0.1:47624: EOF 2018/08/03 21:24:42 http: TLS handshake error from 10.244.0.1:47684: EOF 2018/08/03 21:24:52 http: TLS handshake error from 10.244.0.1:47744: EOF level=info timestamp=2018-08-03T21:24:59.176372Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:25:02 http: TLS handshake error from 10.244.0.1:47804: EOF 2018/08/03 21:25:12 http: TLS handshake error from 10.244.0.1:47864: EOF 2018/08/03 21:25:22 http: TLS handshake error from 10.244.0.1:47924: EOF level=info timestamp=2018-08-03T21:25:29.182547Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:25:32 http: TLS handshake error from 10.244.0.1:47984: EOF 2018/08/03 21:25:42 http: TLS handshake error from 10.244.0.1:48044: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running 2018/08/03 21:24:56 http: TLS handshake error from 10.244.1.1:34594: EOF level=info timestamp=2018-08-03T21:24:56.131760Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:25:01.151348Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:25:04.843054Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:25:04.844244Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:25:06 http: TLS handshake error from 10.244.1.1:34600: EOF level=info timestamp=2018-08-03T21:25:07.638968Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:25:16 http: TLS handshake error from 10.244.1.1:34606: EOF level=info timestamp=2018-08-03T21:25:25.880348Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:25:26 http: TLS handshake error from 10.244.1.1:34612: EOF level=info timestamp=2018-08-03T21:25:26.188385Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:25:31.173253Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:25:36 http: TLS handshake error from 10.244.1.1:34618: EOF level=info timestamp=2018-08-03T21:25:37.692321Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:25:46 http: TLS handshake error from 10.244.1.1:34624: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T21:12:44.804508Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmibb6vt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmibb6vt" level=info timestamp=2018-08-03T21:13:45.042258Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi999sh kind= uid=1aa1faad-9762-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:13:45.042469Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi999sh kind= uid=1aa1faad-9762-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:13:45.119722Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi999sh\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi999sh" level=info timestamp=2018-08-03T21:16:45.491808Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4dt2g kind= uid=86349ec9-9762-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:16:45.491949Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4dt2g kind= uid=86349ec9-9762-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:16:45.542075Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi4dt2g\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi4dt2g" level=info timestamp=2018-08-03T21:19:46.092024Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitl8ng kind= uid=f1d9f13a-9762-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:19:46.092212Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitl8ng kind= uid=f1d9f13a-9762-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:19:46.126369Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitl8ng\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitl8ng" level=info timestamp=2018-08-03T21:19:46.137397Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitl8ng\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitl8ng" level=info timestamp=2018-08-03T21:19:46.146280Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitl8ng\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitl8ng" level=info timestamp=2018-08-03T21:22:46.354118Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitl8ng\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmitl8ng, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: f1d9f13a-9762-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitl8ng" level=info timestamp=2018-08-03T21:22:46.608791Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi25jxp kind= uid=5d6a088e-9763-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:22:46.609033Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi25jxp kind= uid=5d6a088e-9763-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:03:09.067392Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:16.060713Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.742384Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:07:14.853959Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:09:13.451265Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:10:47.264832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:07.658851Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:13:28.777336Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:15:17.688496Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:16:32.338048Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:18:13.438893Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:20:15.550940Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:21:36.668841Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:23:30.871158Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:25:33.196297Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:03:08.892924Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:15.888504Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.567968Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:07:14.678144Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:09:13.274993Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:10:47.051196Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:07.443128Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:13:28.565673Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:15:17.469257Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:16:32.109632Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:18:13.210218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:20:15.325675Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:21:36.439524Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:23:30.635782Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:25:32.955367Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmi25jxp-9gptv Pod phase: Pending • Failure [180.481 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Creating a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:72 with node tainted /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:461 the vmi with tolerations should be scheduled [It] /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:483 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T21:22:46.883539Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi25jxp kind=VirtualMachineInstance uid=5d6a088e-9763-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi25jxp-9gptv" • Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T21:26:59.221154Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:27:02 http: TLS handshake error from 10.244.0.1:48524: EOF 2018/08/03 21:27:12 http: TLS handshake error from 10.244.0.1:48584: EOF 2018/08/03 21:27:22 http: TLS handshake error from 10.244.0.1:48644: EOF level=info timestamp=2018-08-03T21:27:29.206747Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:27:32 http: TLS handshake error from 10.244.0.1:48704: EOF 2018/08/03 21:27:42 http: TLS handshake error from 10.244.0.1:48764: EOF 2018/08/03 21:27:52 http: TLS handshake error from 10.244.0.1:48824: EOF level=info timestamp=2018-08-03T21:27:59.192263Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:28:02 http: TLS handshake error from 10.244.0.1:48884: EOF 2018/08/03 21:28:12 http: TLS handshake error from 10.244.0.1:48944: EOF 2018/08/03 21:28:22 http: TLS handshake error from 10.244.0.1:49004: EOF level=info timestamp=2018-08-03T21:28:29.169527Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:28:32 http: TLS handshake error from 10.244.0.1:49064: EOF 2018/08/03 21:28:42 http: TLS handshake error from 10.244.0.1:49124: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T21:27:56.143998Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:27:56.442908Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:28:01.281191Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:28:04.871351Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:28:04.872351Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:28:06 http: TLS handshake error from 10.244.1.1:34708: EOF level=info timestamp=2018-08-03T21:28:07.959322Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:28:16 http: TLS handshake error from 10.244.1.1:34714: EOF 2018/08/03 21:28:26 http: TLS handshake error from 10.244.1.1:34720: EOF level=info timestamp=2018-08-03T21:28:26.193630Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:28:26.496437Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:28:31.303461Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:28:36 http: TLS handshake error from 10.244.1.1:34726: EOF level=info timestamp=2018-08-03T21:28:38.012839Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:28:46 http: TLS handshake error from 10.244.1.1:34732: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T21:19:46.126369Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitl8ng\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitl8ng" level=info timestamp=2018-08-03T21:19:46.137397Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitl8ng\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitl8ng" level=info timestamp=2018-08-03T21:19:46.146280Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitl8ng\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitl8ng" level=info timestamp=2018-08-03T21:22:46.354118Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitl8ng\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmitl8ng, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: f1d9f13a-9762-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitl8ng" level=info timestamp=2018-08-03T21:22:46.608791Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi25jxp kind= uid=5d6a088e-9763-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:22:46.609033Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi25jxp kind= uid=5d6a088e-9763-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:25:46.870489Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi25jxp\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi25jxp, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 5d6a088e-9763-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi25jxp" level=info timestamp=2018-08-03T21:25:47.046279Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8hfzt kind= uid=c8fcd900-9763-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:25:47.046436Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8hfzt kind= uid=c8fcd900-9763-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:25:47.087686Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8hfzt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8hfzt" level=info timestamp=2018-08-03T21:25:47.097130Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8hfzt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8hfzt" level=info timestamp=2018-08-03T21:25:47.105612Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8hfzt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8hfzt" level=info timestamp=2018-08-03T21:25:48.147274Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8hfzt\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi8hfzt, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: c8fcd900-9763-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8hfzt" level=info timestamp=2018-08-03T21:25:48.326217Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitp4tn kind= uid=c9c0f1eb-9763-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:25:48.326390Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitp4tn kind= uid=c9c0f1eb-9763-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:05:37.742384Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:07:14.853959Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:09:13.451265Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:10:47.264832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:07.658851Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:13:28.777336Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:15:17.688496Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:16:32.338048Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:18:13.438893Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:20:15.550940Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:21:36.668841Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:23:30.871158Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:25:33.196297Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:27:23.377937Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:25.426417Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:05:37.567968Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:07:14.678144Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:09:13.274993Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:10:47.051196Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:07.443128Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:13:28.565673Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:15:17.469257Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:16:32.109632Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:18:13.210218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:20:15.325675Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:21:36.439524Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:23:30.635782Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:25:32.955367Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:27:23.129332Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:25.180944Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmitp4tn-t7l75 Pod phase: Pending ------------------------------ • Failure [180.490 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Creating a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:72 with non default namespace /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:533 should log libvirt start and stop lifecycle events of the domain /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 kubevirt-test-default [It] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ STEP: Creating a VirtualMachineInstance with different namespace level=info timestamp=2018-08-03T21:25:48.598867Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmitp4tn kind=VirtualMachineInstance uid=c9c0f1eb-9763-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmitp4tn-t7l75" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T21:29:59.179614Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:30:02 http: TLS handshake error from 10.244.0.1:49604: EOF 2018/08/03 21:30:12 http: TLS handshake error from 10.244.0.1:49664: EOF 2018/08/03 21:30:22 http: TLS handshake error from 10.244.0.1:49724: EOF level=info timestamp=2018-08-03T21:30:29.168764Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:30:32 http: TLS handshake error from 10.244.0.1:49784: EOF 2018/08/03 21:30:42 http: TLS handshake error from 10.244.0.1:49844: EOF 2018/08/03 21:30:52 http: TLS handshake error from 10.244.0.1:49904: EOF level=info timestamp=2018-08-03T21:30:59.181928Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:31:02 http: TLS handshake error from 10.244.0.1:49964: EOF 2018/08/03 21:31:12 http: TLS handshake error from 10.244.0.1:50024: EOF 2018/08/03 21:31:22 http: TLS handshake error from 10.244.0.1:50084: EOF level=info timestamp=2018-08-03T21:31:29.193855Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:31:32 http: TLS handshake error from 10.244.0.1:50144: EOF 2018/08/03 21:31:42 http: TLS handshake error from 10.244.0.1:50204: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running 2018/08/03 21:30:46 http: TLS handshake error from 10.244.1.1:34804: EOF 2018/08/03 21:30:56 http: TLS handshake error from 10.244.1.1:34810: EOF level=info timestamp=2018-08-03T21:30:56.452458Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:30:56.755149Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:31:01.413285Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:31:06 http: TLS handshake error from 10.244.1.1:34816: EOF level=info timestamp=2018-08-03T21:31:08.279078Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:31:16 http: TLS handshake error from 10.244.1.1:34822: EOF 2018/08/03 21:31:26 http: TLS handshake error from 10.244.1.1:34828: EOF level=info timestamp=2018-08-03T21:31:26.511628Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:31:26.810064Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:31:31.434941Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:31:36 http: TLS handshake error from 10.244.1.1:34834: EOF level=info timestamp=2018-08-03T21:31:38.333759Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:31:46 http: TLS handshake error from 10.244.1.1:34840: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T21:22:46.354118Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitl8ng\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmitl8ng, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: f1d9f13a-9762-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitl8ng" level=info timestamp=2018-08-03T21:22:46.608791Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi25jxp kind= uid=5d6a088e-9763-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:22:46.609033Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi25jxp kind= uid=5d6a088e-9763-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:25:46.870489Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi25jxp\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi25jxp, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 5d6a088e-9763-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi25jxp" level=info timestamp=2018-08-03T21:25:47.046279Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8hfzt kind= uid=c8fcd900-9763-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:25:47.046436Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8hfzt kind= uid=c8fcd900-9763-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:25:47.087686Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8hfzt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8hfzt" level=info timestamp=2018-08-03T21:25:47.097130Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8hfzt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8hfzt" level=info timestamp=2018-08-03T21:25:47.105612Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8hfzt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8hfzt" level=info timestamp=2018-08-03T21:25:48.147274Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8hfzt\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi8hfzt, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: c8fcd900-9763-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8hfzt" level=info timestamp=2018-08-03T21:25:48.326217Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitp4tn kind= uid=c9c0f1eb-9763-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:25:48.326390Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitp4tn kind= uid=c9c0f1eb-9763-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:28:48.597264Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitp4tn\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmitp4tn, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: c9c0f1eb-9763-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitp4tn" level=info timestamp=2018-08-03T21:28:48.786816Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-alternative name=testvmijxp47 kind= uid=3552cd5c-9764-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:28:48.786989Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-alternative name=testvmijxp47 kind= uid=3552cd5c-9764-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:07:14.853959Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:09:13.451265Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:10:47.264832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:07.658851Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:13:28.777336Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:15:17.688496Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:16:32.338048Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:18:13.438893Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:20:15.550940Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:21:36.668841Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:23:30.871158Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:25:33.196297Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:27:23.377937Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:25.426417Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:30:09.162692Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:07:14.678144Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:09:13.274993Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:10:47.051196Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:07.443128Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:13:28.565673Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:15:17.469257Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:16:32.109632Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:18:13.210218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:20:15.325675Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:21:36.439524Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:23:30.635782Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:25:32.955367Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:27:23.129332Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:25.180944Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:30:08.914811Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" • Failure [180.348 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Creating a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:72 with non default namespace /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:533 should log libvirt start and stop lifecycle events of the domain /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 kubevirt-test-alternative [It] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ STEP: Creating a VirtualMachineInstance with different namespace level=info timestamp=2018-08-03T21:28:49.040890Z pos=utils.go:244 component=tests namespace=kubevirt-test-alternative name=testvmijxp47 kind=VirtualMachineInstance uid=3552cd5c-9764-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmijxp47-lmnl9" S [SKIPPING] in Spec Setup (BeforeEach) [0.212 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Creating a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:72 VirtualMachineInstance Emulation Mode /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:590 should enable emulation in virt-launcher [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:602 Software emulation is not enabled on this cluster /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:598 ------------------------------ S [SKIPPING] in Spec Setup (BeforeEach) [0.039 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Creating a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:72 VirtualMachineInstance Emulation Mode /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:590 should be reflected in domain XML [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:639 Software emulation is not enabled on this cluster /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:598 ------------------------------ •• Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T21:32:59.172485Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:33:02 http: TLS handshake error from 10.244.0.1:50684: EOF 2018/08/03 21:33:12 http: TLS handshake error from 10.244.0.1:50744: EOF 2018/08/03 21:33:22 http: TLS handshake error from 10.244.0.1:50804: EOF level=info timestamp=2018-08-03T21:33:29.206599Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:33:32 http: TLS handshake error from 10.244.0.1:50864: EOF 2018/08/03 21:33:42 http: TLS handshake error from 10.244.0.1:50924: EOF 2018/08/03 21:33:52 http: TLS handshake error from 10.244.0.1:50984: EOF level=info timestamp=2018-08-03T21:33:59.186367Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:34:02 http: TLS handshake error from 10.244.0.1:51044: EOF 2018/08/03 21:34:12 http: TLS handshake error from 10.244.0.1:51104: EOF 2018/08/03 21:34:22 http: TLS handshake error from 10.244.0.1:51164: EOF level=info timestamp=2018-08-03T21:34:29.177703Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:34:32 http: TLS handshake error from 10.244.0.1:51224: EOF 2018/08/03 21:34:42 http: TLS handshake error from 10.244.0.1:51284: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running 2018/08/03 21:33:46 http: TLS handshake error from 10.244.1.1:34912: EOF 2018/08/03 21:33:56 http: TLS handshake error from 10.244.1.1:34918: EOF level=info timestamp=2018-08-03T21:33:56.774932Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:33:57.062023Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:34:01.548122Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:34:06 http: TLS handshake error from 10.244.1.1:34924: EOF level=info timestamp=2018-08-03T21:34:08.602001Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:34:16 http: TLS handshake error from 10.244.1.1:34930: EOF 2018/08/03 21:34:26 http: TLS handshake error from 10.244.1.1:34936: EOF level=info timestamp=2018-08-03T21:34:26.828178Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:34:27.118423Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:34:31.569369Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:34:36 http: TLS handshake error from 10.244.1.1:34942: EOF level=info timestamp=2018-08-03T21:34:38.658027Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:34:46 http: TLS handshake error from 10.244.1.1:34948: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T21:25:47.046436Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8hfzt kind= uid=c8fcd900-9763-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:25:47.087686Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8hfzt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8hfzt" level=info timestamp=2018-08-03T21:25:47.097130Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8hfzt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8hfzt" level=info timestamp=2018-08-03T21:25:47.105612Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8hfzt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8hfzt" level=info timestamp=2018-08-03T21:25:48.147274Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8hfzt\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi8hfzt, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: c8fcd900-9763-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8hfzt" level=info timestamp=2018-08-03T21:25:48.326217Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitp4tn kind= uid=c9c0f1eb-9763-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:25:48.326390Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitp4tn kind= uid=c9c0f1eb-9763-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:28:48.597264Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitp4tn\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmitp4tn, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: c9c0f1eb-9763-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitp4tn" level=info timestamp=2018-08-03T21:28:48.786816Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-alternative name=testvmijxp47 kind= uid=3552cd5c-9764-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:28:48.786989Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-alternative name=testvmijxp47 kind= uid=3552cd5c-9764-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:31:49.208984Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizcpcd kind= uid=a0dd1553-9764-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:31:49.209133Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizcpcd kind= uid=a0dd1553-9764-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:31:49.753787Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmizcpcd\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmizcpcd, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: a0dd1553-9764-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmizcpcd" level=info timestamp=2018-08-03T21:31:50.009249Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7zcq kind= uid=a156fed5-9764-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:31:50.009434Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7zcq kind= uid=a156fed5-9764-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:10:47.264832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:07.658851Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:13:28.777336Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:15:17.688496Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:16:32.338048Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:18:13.438893Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:20:15.550940Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:21:36.668841Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:23:30.871158Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:25:33.196297Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:27:23.377937Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:25.426417Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:30:09.162692Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:32:19.396762Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:33:25.130294Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:10:47.051196Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:07.443128Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:13:28.565673Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:15:17.469257Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:16:32.109632Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:18:13.210218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:20:15.325675Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:21:36.439524Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:23:30.635782Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:25:32.955367Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:27:23.129332Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:25.180944Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:30:08.914811Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:32:19.140813Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:33:24.869993Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmin7zcq-j6z78 Pod phase: Pending ------------------------------ • Failure [180.323 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Delete a VirtualMachineInstance's Pod /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:748 should result in the VirtualMachineInstance moving to a finalized state [It] /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:749 Timed out after 90.012s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ STEP: Creating the VirtualMachineInstance level=info timestamp=2018-08-03T21:31:50.267782Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmin7zcq kind=VirtualMachineInstance uid=a156fed5-9764-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmin7zcq-j6z78" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T21:35:59.193167Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:36:02 http: TLS handshake error from 10.244.0.1:51764: EOF 2018/08/03 21:36:12 http: TLS handshake error from 10.244.0.1:51824: EOF 2018/08/03 21:36:22 http: TLS handshake error from 10.244.0.1:51884: EOF level=info timestamp=2018-08-03T21:36:29.193733Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:36:32 http: TLS handshake error from 10.244.0.1:51944: EOF 2018/08/03 21:36:42 http: TLS handshake error from 10.244.0.1:52004: EOF 2018/08/03 21:36:52 http: TLS handshake error from 10.244.0.1:52064: EOF level=info timestamp=2018-08-03T21:36:59.215074Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:37:02 http: TLS handshake error from 10.244.0.1:52124: EOF 2018/08/03 21:37:12 http: TLS handshake error from 10.244.0.1:52184: EOF 2018/08/03 21:37:22 http: TLS handshake error from 10.244.0.1:52244: EOF level=info timestamp=2018-08-03T21:37:29.190611Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:37:32 http: TLS handshake error from 10.244.0.1:52304: EOF 2018/08/03 21:37:42 http: TLS handshake error from 10.244.0.1:52364: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T21:36:57.087100Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:36:57.382778Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:37:01.669800Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:37:04.806163Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:37:04.807706Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:37:06 http: TLS handshake error from 10.244.1.1:35032: EOF level=info timestamp=2018-08-03T21:37:08.926436Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:37:16 http: TLS handshake error from 10.244.1.1:35038: EOF 2018/08/03 21:37:26 http: TLS handshake error from 10.244.1.1:35044: EOF level=info timestamp=2018-08-03T21:37:27.140275Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:37:27.433774Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:37:31.690888Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:37:36 http: TLS handshake error from 10.244.1.1:35050: EOF level=info timestamp=2018-08-03T21:37:38.992122Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:37:46 http: TLS handshake error from 10.244.1.1:35056: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T21:25:48.147274Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8hfzt\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi8hfzt, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: c8fcd900-9763-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8hfzt" level=info timestamp=2018-08-03T21:25:48.326217Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitp4tn kind= uid=c9c0f1eb-9763-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:25:48.326390Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitp4tn kind= uid=c9c0f1eb-9763-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:28:48.597264Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitp4tn\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmitp4tn, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: c9c0f1eb-9763-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitp4tn" level=info timestamp=2018-08-03T21:28:48.786816Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-alternative name=testvmijxp47 kind= uid=3552cd5c-9764-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:28:48.786989Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-alternative name=testvmijxp47 kind= uid=3552cd5c-9764-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:31:49.208984Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizcpcd kind= uid=a0dd1553-9764-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:31:49.209133Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizcpcd kind= uid=a0dd1553-9764-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:31:49.753787Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmizcpcd\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmizcpcd, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: a0dd1553-9764-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmizcpcd" level=info timestamp=2018-08-03T21:31:50.009249Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7zcq kind= uid=a156fed5-9764-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:31:50.009434Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7zcq kind= uid=a156fed5-9764-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:34:50.475820Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmildsdr kind= uid=0ce80994-9765-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:34:50.475972Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmildsdr kind= uid=0ce80994-9765-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:34:50.526316Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmildsdr\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmildsdr" level=info timestamp=2018-08-03T21:34:50.534620Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmildsdr\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmildsdr" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:15:17.688496Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:16:32.338048Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:18:13.438893Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:20:15.550940Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:21:36.668841Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:23:30.871158Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:25:33.196297Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:27:23.377937Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:25.426417Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:30:09.162692Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:32:19.396762Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:33:25.130294Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:35:07.970255Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.691010Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:37:42.182878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:15:17.469257Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:16:32.109632Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:18:13.210218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:20:15.325675Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:21:36.439524Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:23:30.635782Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:25:32.955367Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:27:23.129332Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:25.180944Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:30:08.914811Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:32:19.140813Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:33:24.869993Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:35:07.702668Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.437175Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:37:41.940366Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmildsdr-cbdn7 Pod phase: Pending • Failure [180.444 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Delete a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:780 with an active pod. /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:781 should result in pod being terminated [It] /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:782 Timed out after 90.006s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ STEP: Creating the VirtualMachineInstance level=info timestamp=2018-08-03T21:34:50.715107Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmildsdr kind=VirtualMachineInstance uid=0ce80994-9765-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmildsdr-cbdn7" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T21:38:59.176546Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:39:02 http: TLS handshake error from 10.244.0.1:52844: EOF 2018/08/03 21:39:12 http: TLS handshake error from 10.244.0.1:52904: EOF 2018/08/03 21:39:22 http: TLS handshake error from 10.244.0.1:52964: EOF level=info timestamp=2018-08-03T21:39:29.196767Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:39:32 http: TLS handshake error from 10.244.0.1:53024: EOF 2018/08/03 21:39:42 http: TLS handshake error from 10.244.0.1:53084: EOF 2018/08/03 21:39:52 http: TLS handshake error from 10.244.0.1:53144: EOF level=info timestamp=2018-08-03T21:39:59.193918Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:40:02 http: TLS handshake error from 10.244.0.1:53204: EOF 2018/08/03 21:40:12 http: TLS handshake error from 10.244.0.1:53264: EOF 2018/08/03 21:40:22 http: TLS handshake error from 10.244.0.1:53324: EOF level=info timestamp=2018-08-03T21:40:29.183375Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:40:32 http: TLS handshake error from 10.244.0.1:53384: EOF 2018/08/03 21:40:42 http: TLS handshake error from 10.244.0.1:53444: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T21:39:57.398977Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:39:57.694193Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:40:01.790853Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:40:04.812954Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:40:04.814129Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:40:06 http: TLS handshake error from 10.244.1.1:35140: EOF level=info timestamp=2018-08-03T21:40:09.262630Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:40:16 http: TLS handshake error from 10.244.1.1:35146: EOF 2018/08/03 21:40:26 http: TLS handshake error from 10.244.1.1:35152: EOF level=info timestamp=2018-08-03T21:40:27.448238Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:40:27.746117Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:40:31.808925Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:40:36 http: TLS handshake error from 10.244.1.1:35158: EOF level=info timestamp=2018-08-03T21:40:39.316222Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:40:46 http: TLS handshake error from 10.244.1.1:35164: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T21:25:48.326390Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitp4tn kind= uid=c9c0f1eb-9763-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:28:48.597264Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitp4tn\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmitp4tn, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: c9c0f1eb-9763-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitp4tn" level=info timestamp=2018-08-03T21:28:48.786816Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-alternative name=testvmijxp47 kind= uid=3552cd5c-9764-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:28:48.786989Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-alternative name=testvmijxp47 kind= uid=3552cd5c-9764-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:31:49.208984Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizcpcd kind= uid=a0dd1553-9764-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:31:49.209133Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizcpcd kind= uid=a0dd1553-9764-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:31:49.753787Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmizcpcd\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmizcpcd, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: a0dd1553-9764-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmizcpcd" level=info timestamp=2018-08-03T21:31:50.009249Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7zcq kind= uid=a156fed5-9764-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:31:50.009434Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7zcq kind= uid=a156fed5-9764-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:34:50.475820Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmildsdr kind= uid=0ce80994-9765-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:34:50.475972Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmildsdr kind= uid=0ce80994-9765-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:34:50.526316Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmildsdr\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmildsdr" level=info timestamp=2018-08-03T21:34:50.534620Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmildsdr\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmildsdr" level=info timestamp=2018-08-03T21:37:50.917423Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqjls2 kind= uid=78756143-9765-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:37:50.917594Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqjls2 kind= uid=78756143-9765-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:18:13.438893Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:20:15.550940Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:21:36.668841Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:23:30.871158Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:25:33.196297Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:27:23.377937Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:25.426417Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:30:09.162692Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:32:19.396762Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:33:25.130294Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:35:07.970255Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.691010Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:37:42.182878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:39:21.156556Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:41.220845Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:18:13.210218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:20:15.325675Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:21:36.439524Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:23:30.635782Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:25:32.955367Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:27:23.129332Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:25.180944Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:30:08.914811Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:32:19.140813Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:33:24.869993Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:35:07.702668Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.437175Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:37:41.940366Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:39:20.908825Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:40.978299Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmiqjls2-lzv5l Pod phase: Pending • Failure [180.442 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Delete a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:780 with ACPI and 0 grace period seconds /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:806 should result in vmi status failed [It] /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:807 Timed out after 90.007s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ STEP: Creating the VirtualMachineInstance level=info timestamp=2018-08-03T21:37:51.164348Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmiqjls2 kind=VirtualMachineInstance uid=78756143-9765-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmiqjls2-lzv5l" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T21:41:59.225694Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:42:02 http: TLS handshake error from 10.244.0.1:53924: EOF 2018/08/03 21:42:12 http: TLS handshake error from 10.244.0.1:53984: EOF 2018/08/03 21:42:22 http: TLS handshake error from 10.244.0.1:54044: EOF level=info timestamp=2018-08-03T21:42:29.174705Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:42:32 http: TLS handshake error from 10.244.0.1:54104: EOF 2018/08/03 21:42:42 http: TLS handshake error from 10.244.0.1:54164: EOF 2018/08/03 21:42:52 http: TLS handshake error from 10.244.0.1:54224: EOF level=info timestamp=2018-08-03T21:42:59.199319Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:43:02 http: TLS handshake error from 10.244.0.1:54284: EOF 2018/08/03 21:43:12 http: TLS handshake error from 10.244.0.1:54344: EOF 2018/08/03 21:43:22 http: TLS handshake error from 10.244.0.1:54404: EOF level=info timestamp=2018-08-03T21:43:29.175305Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:43:32 http: TLS handshake error from 10.244.0.1:54464: EOF 2018/08/03 21:43:42 http: TLS handshake error from 10.244.0.1:54524: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T21:42:57.708307Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:42:58.005205Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:43:01.930800Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:43:04.849129Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:43:04.850046Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:43:06 http: TLS handshake error from 10.244.1.1:35248: EOF level=info timestamp=2018-08-03T21:43:09.587050Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:43:16 http: TLS handshake error from 10.244.1.1:35254: EOF 2018/08/03 21:43:26 http: TLS handshake error from 10.244.1.1:35260: EOF level=info timestamp=2018-08-03T21:43:27.757262Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:43:28.050944Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:43:31.951011Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:43:36 http: TLS handshake error from 10.244.1.1:35266: EOF level=info timestamp=2018-08-03T21:43:39.642308Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:43:46 http: TLS handshake error from 10.244.1.1:35272: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T21:28:48.786989Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-alternative name=testvmijxp47 kind= uid=3552cd5c-9764-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:31:49.208984Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizcpcd kind= uid=a0dd1553-9764-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:31:49.209133Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizcpcd kind= uid=a0dd1553-9764-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:31:49.753787Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmizcpcd\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmizcpcd, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: a0dd1553-9764-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmizcpcd" level=info timestamp=2018-08-03T21:31:50.009249Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7zcq kind= uid=a156fed5-9764-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:31:50.009434Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7zcq kind= uid=a156fed5-9764-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:34:50.475820Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmildsdr kind= uid=0ce80994-9765-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:34:50.475972Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmildsdr kind= uid=0ce80994-9765-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:34:50.526316Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmildsdr\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmildsdr" level=info timestamp=2018-08-03T21:34:50.534620Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmildsdr\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmildsdr" level=info timestamp=2018-08-03T21:37:50.917423Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqjls2 kind= uid=78756143-9765-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:37:50.917594Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqjls2 kind= uid=78756143-9765-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:40:51.368887Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi64t6z kind= uid=e4031b42-9765-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:40:51.369028Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi64t6z kind= uid=e4031b42-9765-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:40:51.406288Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi64t6z\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi64t6z" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:21:36.668841Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:23:30.871158Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:25:33.196297Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:27:23.377937Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:25.426417Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:30:09.162692Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:32:19.396762Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:33:25.130294Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:35:07.970255Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.691010Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:37:42.182878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:39:21.156556Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:41.220845Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.705272Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.923512Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:21:36.439524Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:23:30.635782Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:25:32.955367Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:27:23.129332Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:25.180944Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:30:08.914811Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:32:19.140813Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:33:24.869993Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:35:07.702668Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.437175Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:37:41.940366Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:39:20.908825Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:40.978299Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.461580Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.674759Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmi64t6z-zmc7g Pod phase: Pending • Failure [180.448 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Delete a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:780 with ACPI and some grace period seconds /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:831 should result in vmi status succeeded [It] /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:832 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ STEP: Creating the VirtualMachineInstance level=info timestamp=2018-08-03T21:40:51.684771Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi64t6z kind=VirtualMachineInstance uid=e4031b42-9765-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi64t6z-zmc7g" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T21:44:59.175699Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:45:02 http: TLS handshake error from 10.244.0.1:55004: EOF 2018/08/03 21:45:12 http: TLS handshake error from 10.244.0.1:55064: EOF 2018/08/03 21:45:22 http: TLS handshake error from 10.244.0.1:55124: EOF level=info timestamp=2018-08-03T21:45:29.199838Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:45:32 http: TLS handshake error from 10.244.0.1:55184: EOF 2018/08/03 21:45:42 http: TLS handshake error from 10.244.0.1:55244: EOF 2018/08/03 21:45:52 http: TLS handshake error from 10.244.0.1:55304: EOF level=info timestamp=2018-08-03T21:45:59.185584Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:46:02 http: TLS handshake error from 10.244.0.1:55364: EOF 2018/08/03 21:46:12 http: TLS handshake error from 10.244.0.1:55424: EOF 2018/08/03 21:46:22 http: TLS handshake error from 10.244.0.1:55484: EOF level=info timestamp=2018-08-03T21:46:29.176456Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:46:32 http: TLS handshake error from 10.244.0.1:55544: EOF 2018/08/03 21:46:42 http: TLS handshake error from 10.244.0.1:55604: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running 2018/08/03 21:45:46 http: TLS handshake error from 10.244.1.1:35344: EOF 2018/08/03 21:45:56 http: TLS handshake error from 10.244.1.1:35350: EOF level=info timestamp=2018-08-03T21:45:58.021090Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:45:58.315149Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:46:02.055889Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:46:06 http: TLS handshake error from 10.244.1.1:35356: EOF level=info timestamp=2018-08-03T21:46:09.907685Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:46:16 http: TLS handshake error from 10.244.1.1:35362: EOF 2018/08/03 21:46:26 http: TLS handshake error from 10.244.1.1:35368: EOF level=info timestamp=2018-08-03T21:46:28.069955Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:46:28.364267Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:46:32.076462Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:46:36 http: TLS handshake error from 10.244.1.1:35374: EOF level=info timestamp=2018-08-03T21:46:39.960481Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:46:46 http: TLS handshake error from 10.244.1.1:35380: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T21:31:49.753787Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmizcpcd\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmizcpcd, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: a0dd1553-9764-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmizcpcd" level=info timestamp=2018-08-03T21:31:50.009249Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7zcq kind= uid=a156fed5-9764-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:31:50.009434Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7zcq kind= uid=a156fed5-9764-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:34:50.475820Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmildsdr kind= uid=0ce80994-9765-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:34:50.475972Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmildsdr kind= uid=0ce80994-9765-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:34:50.526316Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmildsdr\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmildsdr" level=info timestamp=2018-08-03T21:34:50.534620Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmildsdr\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmildsdr" level=info timestamp=2018-08-03T21:37:50.917423Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqjls2 kind= uid=78756143-9765-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:37:50.917594Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqjls2 kind= uid=78756143-9765-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:40:51.368887Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi64t6z kind= uid=e4031b42-9765-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:40:51.369028Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi64t6z kind= uid=e4031b42-9765-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:40:51.406288Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi64t6z\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi64t6z" level=info timestamp=2018-08-03T21:43:51.822756Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwzcrf kind= uid=4f92fdb8-9766-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:43:51.822935Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwzcrf kind= uid=4f92fdb8-9766-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:43:51.859554Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiwzcrf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiwzcrf" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:23:30.871158Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:25:33.196297Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:27:23.377937Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:25.426417Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:30:09.162692Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:32:19.396762Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:33:25.130294Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:35:07.970255Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.691010Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:37:42.182878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:39:21.156556Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:41.220845Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.705272Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.923512Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.721246Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:23:30.635782Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:25:32.955367Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:27:23.129332Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:25.180944Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:30:08.914811Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:32:19.140813Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:33:24.869993Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:35:07.702668Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.437175Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:37:41.940366Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:39:20.908825Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:40.978299Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.461580Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.674759Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.467832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmiwzcrf-zqftm Pod phase: Pending • Failure [180.449 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Delete a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:780 with grace period greater than 0 /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:856 should run graceful shutdown [It] /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:857 Timed out after 90.003s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ STEP: Setting a VirtualMachineInstance termination grace period to 5 STEP: Creating the VirtualMachineInstance level=info timestamp=2018-08-03T21:43:52.076646Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmiwzcrf kind=VirtualMachineInstance uid=4f92fdb8-9766-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmiwzcrf-zqftm" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T21:47:59.203653Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:48:02 http: TLS handshake error from 10.244.0.1:56084: EOF 2018/08/03 21:48:12 http: TLS handshake error from 10.244.0.1:56144: EOF 2018/08/03 21:48:22 http: TLS handshake error from 10.244.0.1:56204: EOF level=info timestamp=2018-08-03T21:48:29.197047Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:48:32 http: TLS handshake error from 10.244.0.1:56264: EOF 2018/08/03 21:48:42 http: TLS handshake error from 10.244.0.1:56324: EOF 2018/08/03 21:48:52 http: TLS handshake error from 10.244.0.1:56384: EOF level=info timestamp=2018-08-03T21:48:59.185362Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:49:02 http: TLS handshake error from 10.244.0.1:56444: EOF 2018/08/03 21:49:12 http: TLS handshake error from 10.244.0.1:56504: EOF 2018/08/03 21:49:22 http: TLS handshake error from 10.244.0.1:56564: EOF level=info timestamp=2018-08-03T21:49:29.210677Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:49:32 http: TLS handshake error from 10.244.0.1:56624: EOF 2018/08/03 21:49:42 http: TLS handshake error from 10.244.0.1:56684: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running 2018/08/03 21:48:46 http: TLS handshake error from 10.244.1.1:35452: EOF 2018/08/03 21:48:56 http: TLS handshake error from 10.244.1.1:35458: EOF level=info timestamp=2018-08-03T21:48:58.331087Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:48:58.626658Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:49:02.180167Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:49:06 http: TLS handshake error from 10.244.1.1:35464: EOF level=info timestamp=2018-08-03T21:49:10.241899Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:49:16 http: TLS handshake error from 10.244.1.1:35470: EOF 2018/08/03 21:49:26 http: TLS handshake error from 10.244.1.1:35476: EOF level=info timestamp=2018-08-03T21:49:28.382027Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:49:28.679554Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:49:32.198094Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:49:36 http: TLS handshake error from 10.244.1.1:35482: EOF level=info timestamp=2018-08-03T21:49:40.294993Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:49:46 http: TLS handshake error from 10.244.1.1:35488: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T21:31:50.009434Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7zcq kind= uid=a156fed5-9764-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:34:50.475820Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmildsdr kind= uid=0ce80994-9765-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:34:50.475972Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmildsdr kind= uid=0ce80994-9765-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:34:50.526316Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmildsdr\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmildsdr" level=info timestamp=2018-08-03T21:34:50.534620Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmildsdr\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmildsdr" level=info timestamp=2018-08-03T21:37:50.917423Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqjls2 kind= uid=78756143-9765-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:37:50.917594Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqjls2 kind= uid=78756143-9765-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:40:51.368887Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi64t6z kind= uid=e4031b42-9765-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:40:51.369028Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi64t6z kind= uid=e4031b42-9765-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:40:51.406288Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi64t6z\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi64t6z" level=info timestamp=2018-08-03T21:43:51.822756Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwzcrf kind= uid=4f92fdb8-9766-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:43:51.822935Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwzcrf kind= uid=4f92fdb8-9766-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:43:51.859554Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiwzcrf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiwzcrf" level=info timestamp=2018-08-03T21:46:52.263968Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9rblb kind= uid=bb200734-9766-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:46:52.264180Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9rblb kind= uid=bb200734-9766-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:27:23.377937Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:25.426417Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:30:09.162692Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:32:19.396762Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:33:25.130294Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:35:07.970255Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.691010Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:37:42.182878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:39:21.156556Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:41.220845Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.705272Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.923512Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.721246Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.784295Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:34.187516Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:27:23.129332Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:25.180944Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:30:08.914811Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:32:19.140813Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:33:24.869993Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:35:07.702668Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.437175Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:37:41.940366Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:39:20.908825Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:40.978299Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.461580Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.674759Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.467832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.536520Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:33.944092Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmi9rblb-pnttq Pod phase: Pending • Failure [180.441 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Killed VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:908 should be in Failed phase [It] /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:909 Timed out after 90.003s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ STEP: Starting a VirtualMachineInstance level=info timestamp=2018-08-03T21:46:52.577588Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi9rblb kind=VirtualMachineInstance uid=bb200734-9766-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi9rblb-pnttq" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running 2018/08/03 21:51:12 http: TLS handshake error from 10.244.0.1:57224: EOF 2018/08/03 21:51:22 http: TLS handshake error from 10.244.0.1:57284: EOF level=info timestamp=2018-08-03T21:51:29.194052Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:51:32 http: TLS handshake error from 10.244.0.1:57344: EOF 2018/08/03 21:51:42 http: TLS handshake error from 10.244.0.1:57404: EOF 2018/08/03 21:51:52 http: TLS handshake error from 10.244.0.1:57464: EOF level=info timestamp=2018-08-03T21:51:59.151742Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:51:59.224709Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:52:02 http: TLS handshake error from 10.244.0.1:57524: EOF 2018/08/03 21:52:12 http: TLS handshake error from 10.244.0.1:57584: EOF 2018/08/03 21:52:22 http: TLS handshake error from 10.244.0.1:57644: EOF level=info timestamp=2018-08-03T21:52:29.196246Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:52:32 http: TLS handshake error from 10.244.0.1:57704: EOF 2018/08/03 21:52:42 http: TLS handshake error from 10.244.0.1:57764: EOF 2018/08/03 21:52:52 http: TLS handshake error from 10.244.0.1:57824: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T21:51:58.642878Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:51:58.941766Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:52:02.304423Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:52:04.930220Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:52:04.931711Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:52:06 http: TLS handshake error from 10.244.1.1:35572: EOF level=info timestamp=2018-08-03T21:52:10.561622Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:52:16 http: TLS handshake error from 10.244.1.1:35578: EOF 2018/08/03 21:52:26 http: TLS handshake error from 10.244.1.1:35584: EOF level=info timestamp=2018-08-03T21:52:28.691949Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:52:29.007362Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:52:32.335068Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:52:36 http: TLS handshake error from 10.244.1.1:35590: EOF level=info timestamp=2018-08-03T21:52:40.615318Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:52:46 http: TLS handshake error from 10.244.1.1:35596: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T21:34:50.475972Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmildsdr kind= uid=0ce80994-9765-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:34:50.526316Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmildsdr\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmildsdr" level=info timestamp=2018-08-03T21:34:50.534620Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmildsdr\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmildsdr" level=info timestamp=2018-08-03T21:37:50.917423Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqjls2 kind= uid=78756143-9765-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:37:50.917594Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqjls2 kind= uid=78756143-9765-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:40:51.368887Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi64t6z kind= uid=e4031b42-9765-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:40:51.369028Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi64t6z kind= uid=e4031b42-9765-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:40:51.406288Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi64t6z\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi64t6z" level=info timestamp=2018-08-03T21:43:51.822756Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwzcrf kind= uid=4f92fdb8-9766-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:43:51.822935Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwzcrf kind= uid=4f92fdb8-9766-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:43:51.859554Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiwzcrf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiwzcrf" level=info timestamp=2018-08-03T21:46:52.263968Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9rblb kind= uid=bb200734-9766-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:46:52.264180Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9rblb kind= uid=bb200734-9766-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:49:52.702964Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7r6b5 kind= uid=26acff95-9767-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:49:52.703126Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7r6b5 kind= uid=26acff95-9767-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:30:09.162692Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:32:19.396762Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:33:25.130294Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:35:07.970255Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.691010Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:37:42.182878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:39:21.156556Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:41.220845Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.705272Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.923512Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.721246Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.784295Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:34.187516Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.597547Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.948912Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:30:08.914811Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:32:19.140813Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:33:24.869993Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:35:07.702668Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.437175Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:37:41.940366Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:39:20.908825Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:40.978299Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.461580Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.674759Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.467832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.536520Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:33.944092Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.351715Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.703648Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmi7r6b5-zsw6p Pod phase: Pending • Failure [180.441 seconds] VMIlifecycle /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:51 Killed VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:908 should be left alone by virt-handler [It] /root/go/src/kubevirt.io/kubevirt/tests/vmi_lifecycle_test.go:936 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ STEP: Starting a VirtualMachineInstance level=info timestamp=2018-08-03T21:49:52.950765Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi7r6b5 kind=VirtualMachineInstance uid=26acff95-9767-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi7r6b5-zsw6p" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running 2018/08/03 21:57:02 http: TLS handshake error from 10.244.0.1:59324: EOF 2018/08/03 21:57:12 http: TLS handshake error from 10.244.0.1:59384: EOF 2018/08/03 21:57:22 http: TLS handshake error from 10.244.0.1:59444: EOF level=info timestamp=2018-08-03T21:57:29.224130Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:57:32 http: TLS handshake error from 10.244.0.1:59504: EOF 2018/08/03 21:57:42 http: TLS handshake error from 10.244.0.1:59564: EOF 2018/08/03 21:57:52 http: TLS handshake error from 10.244.0.1:59624: EOF level=info timestamp=2018-08-03T21:57:59.235928Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:58:02 http: TLS handshake error from 10.244.0.1:59684: EOF 2018/08/03 21:58:12 http: TLS handshake error from 10.244.0.1:59744: EOF 2018/08/03 21:58:22 http: TLS handshake error from 10.244.0.1:59804: EOF level=info timestamp=2018-08-03T21:58:29.189980Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:58:32 http: TLS handshake error from 10.244.0.1:59864: EOF 2018/08/03 21:58:42 http: TLS handshake error from 10.244.0.1:59924: EOF 2018/08/03 21:58:52 http: TLS handshake error from 10.244.0.1:59984: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T21:57:59.265245Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:57:59.563686Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:58:02.570197Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:58:04.918745Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:58:04.919994Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:58:06 http: TLS handshake error from 10.244.1.1:35788: EOF level=info timestamp=2018-08-03T21:58:11.211661Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:58:16 http: TLS handshake error from 10.244.1.1:35794: EOF 2018/08/03 21:58:26 http: TLS handshake error from 10.244.1.1:35800: EOF level=info timestamp=2018-08-03T21:58:29.315259Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:58:29.613271Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:58:32.613979Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:58:36 http: TLS handshake error from 10.244.1.1:35806: EOF level=info timestamp=2018-08-03T21:58:41.264971Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:58:46 http: TLS handshake error from 10.244.1.1:35812: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T21:37:50.917423Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqjls2 kind= uid=78756143-9765-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:37:50.917594Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqjls2 kind= uid=78756143-9765-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:40:51.368887Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi64t6z kind= uid=e4031b42-9765-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:40:51.369028Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi64t6z kind= uid=e4031b42-9765-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:40:51.406288Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi64t6z\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi64t6z" level=info timestamp=2018-08-03T21:43:51.822756Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwzcrf kind= uid=4f92fdb8-9766-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:43:51.822935Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwzcrf kind= uid=4f92fdb8-9766-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:43:51.859554Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiwzcrf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiwzcrf" level=info timestamp=2018-08-03T21:46:52.263968Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9rblb kind= uid=bb200734-9766-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:46:52.264180Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9rblb kind= uid=bb200734-9766-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:49:52.702964Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7r6b5 kind= uid=26acff95-9767-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:49:52.703126Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7r6b5 kind= uid=26acff95-9767-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:52:52.970387Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi7r6b5\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi7r6b5, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 26acff95-9767-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi7r6b5" level=info timestamp=2018-08-03T21:52:53.147859Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmimtwjc kind= uid=923a6a4f-9767-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:52:53.148028Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmimtwjc kind= uid=923a6a4f-9767-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:36:29.691010Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:37:42.182878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:39:21.156556Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:41.220845Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.705272Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.923512Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.721246Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.784295Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:34.187516Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.597547Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.948912Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.323791Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.341421Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.755781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.929071Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:36:29.437175Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:37:41.940366Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:39:20.908825Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:40.978299Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.461580Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.674759Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.467832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.536520Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:33.944092Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.351715Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.703648Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.065136Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.088172Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.487472Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.664030Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmimtwjc-zvc9c Pod phase: Pending • Failure [360.439 seconds] RegistryDisk /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:41 Starting and stopping the same VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:90 with ephemeral registry disk /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:91 should success multiple times [It] /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:92 Timed out after 180.003s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1034 ------------------------------ STEP: Starting the VirtualMachineInstance level=info timestamp=2018-08-03T21:52:53.398388Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmimtwjc kind=VirtualMachineInstance uid=923a6a4f-9767-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmimtwjc-zvc9c" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running 2018/08/03 21:59:02 http: TLS handshake error from 10.244.0.1:60044: EOF 2018/08/03 21:59:12 http: TLS handshake error from 10.244.0.1:60104: EOF 2018/08/03 21:59:22 http: TLS handshake error from 10.244.0.1:60164: EOF level=info timestamp=2018-08-03T21:59:29.216949Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:59:32 http: TLS handshake error from 10.244.0.1:60224: EOF 2018/08/03 21:59:42 http: TLS handshake error from 10.244.0.1:60284: EOF 2018/08/03 21:59:52 http: TLS handshake error from 10.244.0.1:60344: EOF level=info timestamp=2018-08-03T21:59:59.204279Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:00:02 http: TLS handshake error from 10.244.0.1:60404: EOF 2018/08/03 22:00:12 http: TLS handshake error from 10.244.0.1:60464: EOF 2018/08/03 22:00:22 http: TLS handshake error from 10.244.0.1:60524: EOF level=info timestamp=2018-08-03T22:00:29.214376Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:00:32 http: TLS handshake error from 10.244.0.1:60584: EOF 2018/08/03 22:00:42 http: TLS handshake error from 10.244.0.1:60644: EOF 2018/08/03 22:00:52 http: TLS handshake error from 10.244.0.1:60704: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T21:59:59.472551Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:59:59.770724Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:00:02.677089Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:00:04.921832Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:00:04.923000Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:00:06 http: TLS handshake error from 10.244.1.1:35860: EOF level=info timestamp=2018-08-03T22:00:11.424268Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:00:16 http: TLS handshake error from 10.244.1.1:35866: EOF 2018/08/03 22:00:26 http: TLS handshake error from 10.244.1.1:35872: EOF level=info timestamp=2018-08-03T22:00:29.524521Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:00:29.818945Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:00:32.697797Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:00:36 http: TLS handshake error from 10.244.1.1:35878: EOF level=info timestamp=2018-08-03T22:00:41.477660Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:00:46 http: TLS handshake error from 10.244.1.1:35884: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T21:43:51.822756Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwzcrf kind= uid=4f92fdb8-9766-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:43:51.822935Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwzcrf kind= uid=4f92fdb8-9766-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:43:51.859554Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiwzcrf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiwzcrf" level=info timestamp=2018-08-03T21:46:52.263968Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9rblb kind= uid=bb200734-9766-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:46:52.264180Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9rblb kind= uid=bb200734-9766-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:49:52.702964Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7r6b5 kind= uid=26acff95-9767-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:49:52.703126Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7r6b5 kind= uid=26acff95-9767-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:52:52.970387Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi7r6b5\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi7r6b5, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 26acff95-9767-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi7r6b5" level=info timestamp=2018-08-03T21:52:53.147859Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmimtwjc kind= uid=923a6a4f-9767-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:52:53.148028Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmimtwjc kind= uid=923a6a4f-9767-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:58:53.404493Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmimtwjc\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmimtwjc, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 923a6a4f-9767-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmimtwjc" level=info timestamp=2018-08-03T21:58:53.615642Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9rwg7 kind= uid=69118d0f-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:58:53.615775Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9rwg7 kind= uid=69118d0f-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:58:53.676461Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi9rwg7\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi9rwg7" level=info timestamp=2018-08-03T21:58:53.686977Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi9rwg7\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi9rwg7" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:37:42.182878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:39:21.156556Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:41.220845Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.705272Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.923512Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.721246Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.784295Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:34.187516Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.597547Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.948912Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.323791Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.341421Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.755781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.929071Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.354298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:37:41.940366Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:39:20.908825Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:40.978299Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.461580Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.674759Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.467832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.536520Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:33.944092Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.351715Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.703648Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.065136Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.088172Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.487472Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.664030Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.093656Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmi9rwg7-hwckw Pod phase: Pending • Failure [120.468 seconds] RegistryDisk /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:41 Starting a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:111 with ephemeral registry disk /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:112 should not modify the spec on status update [It] /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:113 Timed out after 60.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1034 ------------------------------ STEP: Starting the VirtualMachineInstance level=info timestamp=2018-08-03T21:58:53.878967Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi9rwg7 kind=VirtualMachineInstance uid=69118d0f-9768-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi9rwg7-hwckw" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running 2018/08/03 22:00:02 http: TLS handshake error from 10.244.0.1:60404: EOF 2018/08/03 22:00:12 http: TLS handshake error from 10.244.0.1:60464: EOF 2018/08/03 22:00:22 http: TLS handshake error from 10.244.0.1:60524: EOF level=info timestamp=2018-08-03T22:00:29.214376Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:00:32 http: TLS handshake error from 10.244.0.1:60584: EOF 2018/08/03 22:00:42 http: TLS handshake error from 10.244.0.1:60644: EOF 2018/08/03 22:00:52 http: TLS handshake error from 10.244.0.1:60704: EOF level=info timestamp=2018-08-03T22:00:59.200926Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:01:02 http: TLS handshake error from 10.244.0.1:60764: EOF 2018/08/03 22:01:12 http: TLS handshake error from 10.244.0.1:60824: EOF 2018/08/03 22:01:22 http: TLS handshake error from 10.244.0.1:60884: EOF level=info timestamp=2018-08-03T22:01:29.193755Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:01:32 http: TLS handshake error from 10.244.0.1:60944: EOF 2018/08/03 22:01:42 http: TLS handshake error from 10.244.0.1:32772: EOF 2018/08/03 22:01:52 http: TLS handshake error from 10.244.0.1:32832: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running 2018/08/03 22:00:46 http: TLS handshake error from 10.244.1.1:35884: EOF 2018/08/03 22:00:56 http: TLS handshake error from 10.244.1.1:35890: EOF level=info timestamp=2018-08-03T22:00:59.576712Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:00:59.872036Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:01:02.713373Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:01:06 http: TLS handshake error from 10.244.1.1:35896: EOF level=info timestamp=2018-08-03T22:01:11.531115Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:01:16 http: TLS handshake error from 10.244.1.1:35902: EOF 2018/08/03 22:01:26 http: TLS handshake error from 10.244.1.1:35908: EOF level=info timestamp=2018-08-03T22:01:29.629153Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:01:29.919885Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:01:32.733375Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:01:36 http: TLS handshake error from 10.244.1.1:35914: EOF level=info timestamp=2018-08-03T22:01:41.584370Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:01:46 http: TLS handshake error from 10.244.1.1:35920: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T21:58:53.676461Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi9rwg7\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi9rwg7" level=info timestamp=2018-08-03T21:58:53.686977Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi9rwg7\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi9rwg7" level=info timestamp=2018-08-03T22:00:53.882043Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi9rwg7\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi9rwg7, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 69118d0f-9768-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi9rwg7" level=info timestamp=2018-08-03T22:00:54.059349Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiznvjf kind= uid=b0dfeba9-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:00:54.059531Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiznvjf kind= uid=b0dfeba9-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:00:54.067402Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8mtln kind= uid=b0e1396a-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:00:54.067523Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8mtln kind= uid=b0e1396a-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:00:54.090825Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9kg7q kind= uid=b0e365a2-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:00:54.090904Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9kg7q kind= uid=b0e365a2-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:00:54.107795Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi6rk2v kind= uid=b0e5d5ce-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:00:54.107854Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi6rk2v kind= uid=b0e5d5ce-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:00:54.154443Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikq2dv kind= uid=b0e9dc52-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:00:54.154534Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikq2dv kind= uid=b0e9dc52-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:00:54.478879Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi9kg7q\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi9kg7q" level=info timestamp=2018-08-03T22:00:55.680493Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi9kg7q\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi9kg7q" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:37:42.182878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:39:21.156556Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:41.220845Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.705272Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.923512Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.721246Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.784295Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:34.187516Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.597547Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.948912Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.323791Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.341421Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.755781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.929071Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.354298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:37:41.940366Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:39:20.908825Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:40.978299Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.461580Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.674759Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.467832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.536520Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:33.944092Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.351715Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.703648Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.065136Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.088172Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.487472Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.664030Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.093656Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmi6rk2v-fltpp Pod phase: Pending Pod name: virt-launcher-testvmi8mtln-x5grf Pod phase: Pending Pod name: virt-launcher-testvmi9kg7q-95jn4 Pod phase: Pending Pod name: virt-launcher-testvmikq2dv-lmjc5 Pod phase: Pending Pod name: virt-launcher-testvmiznvjf-gmnpq Pod phase: Pending • Failure [61.336 seconds] RegistryDisk /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:41 Starting multiple VMIs /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:129 with ephemeral registry disk /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:130 should success [It] /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:131 Timed out after 30.005s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1030 ------------------------------ STEP: Starting a VirtualMachineInstance STEP: Starting a VirtualMachineInstance STEP: Starting a VirtualMachineInstance STEP: Starting a VirtualMachineInstance STEP: Starting a VirtualMachineInstance level=info timestamp=2018-08-03T22:00:54.354441Z pos=utils.go:255 component=tests namespace=kubevirt-test-default name=testvmiznvjf kind=VirtualMachineInstance uid=b0dfeba9-9768-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmiznvjf-gmnpq" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T22:02:07.268025Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmivxr7w/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:02:08.321244Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:08.321314Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmivxr7w/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 22:02:12 http: TLS handshake error from 10.244.0.1:32984: EOF level=error timestamp=2018-08-03T22:02:13.570472Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:13.570569Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmivxr7w/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:02:16.726949Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:16.727042Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmivxr7w/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:02:20.934816Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:20.934928Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmivxr7w/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:02:21.985017Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:21.985107Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmivxr7w/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 22:02:22 http: TLS handshake error from 10.244.0.1:33064: EOF level=error timestamp=2018-08-03T22:02:25.152786Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:25.152858Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmivxr7w/console proto=HTTP/1.1 statusCode=400 contentLength=90 Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=error timestamp=2018-08-03T22:02:15.209412Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:15.209512Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmivxr7w/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 22:02:16 http: TLS handshake error from 10.244.1.1:35938: EOF level=error timestamp=2018-08-03T22:02:16.260990Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:16.261069Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmivxr7w/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:02:18.362665Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:18.362728Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmivxr7w/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:02:19.413360Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:19.413438Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmivxr7w/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:02:20.467066Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:20.467159Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmivxr7w/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:02:23.622108Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:23.622204Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmivxr7w/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:02:24.677936Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:24.678033Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmivxr7w/console proto=HTTP/1.1 statusCode=400 contentLength=90 Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T22:00:54.067402Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8mtln kind= uid=b0e1396a-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:00:54.067523Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8mtln kind= uid=b0e1396a-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:00:54.090825Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9kg7q kind= uid=b0e365a2-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:00:54.090904Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9kg7q kind= uid=b0e365a2-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:00:54.107795Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi6rk2v kind= uid=b0e5d5ce-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:00:54.107854Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi6rk2v kind= uid=b0e5d5ce-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:00:54.154443Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikq2dv kind= uid=b0e9dc52-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:00:54.154534Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikq2dv kind= uid=b0e9dc52-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:00:54.478879Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi9kg7q\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi9kg7q" level=info timestamp=2018-08-03T22:00:55.680493Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi9kg7q\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi9kg7q" level=info timestamp=2018-08-03T22:01:55.318773Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiznvjf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiznvjf" level=info timestamp=2018-08-03T22:01:55.417640Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiznvjf\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmiznvjf, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: b0dfeba9-9768-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiznvjf" level=info timestamp=2018-08-03T22:01:56.001288Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivxr7w kind= uid=d5cad86e-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:01:56.001399Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivxr7w kind= uid=d5cad86e-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:01:56.098111Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmivxr7w\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmivxr7w" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:39:21.156556Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:41.220845Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.705272Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.923512Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.721246Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.784295Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:34.187516Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.597547Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.948912Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.323791Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.341421Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.755781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.929071Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.354298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:26.049033Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:37:41.940366Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:39:20.908825Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:40.978299Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.461580Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.674759Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.467832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.536520Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:33.944092Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.351715Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.703648Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.065136Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.088172Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.487472Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.664030Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.093656Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmivxr7w-44k4j Pod phase: Pending • Failure [31.032 seconds] Console /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:37 A new VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:65 with a serial console /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:66 with a cirros image /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:67 should return that we are running cirros [It] /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:68 Expected error: <*errors.errorString | 0xc4208c81a0>: { s: "Timeout trying to connect to the virtual machine instance", } Timeout trying to connect to the virtual machine instance not to have occurred /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:55 ------------------------------ STEP: Creating a new VirtualMachineInstance STEP: Expecting the VirtualMachineInstance console Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T22:02:38.511241Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmigbqj5/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:02:40.617549Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:40.617625Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmigbqj5/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 22:02:42 http: TLS handshake error from 10.244.0.1:33224: EOF level=error timestamp=2018-08-03T22:02:44.830669Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:44.830759Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmigbqj5/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:02:46.930738Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:46.930830Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmigbqj5/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:02:47.981024Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:47.981125Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmigbqj5/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 22:02:52 http: TLS handshake error from 10.244.0.1:33302: EOF level=error timestamp=2018-08-03T22:02:54.304811Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:54.304886Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmigbqj5/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:02:55.355477Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:55.355560Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmigbqj5/console proto=HTTP/1.1 statusCode=400 contentLength=90 Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T22:02:44.365822Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmigbqj5/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 22:02:46 http: TLS handshake error from 10.244.1.1:35956: EOF level=error timestamp=2018-08-03T22:02:46.466819Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:46.466897Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmigbqj5/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:02:49.627925Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:49.628006Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmigbqj5/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:02:50.678974Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:50.679047Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmigbqj5/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:02:51.735117Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:51.735182Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmigbqj5/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:02:52.790340Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:52.790442Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmigbqj5/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:02:53.841234Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:02:53.841308Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmigbqj5/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 22:02:56 http: TLS handshake error from 10.244.1.1:35962: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T22:00:54.090904Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9kg7q kind= uid=b0e365a2-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:00:54.107795Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi6rk2v kind= uid=b0e5d5ce-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:00:54.107854Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi6rk2v kind= uid=b0e5d5ce-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:00:54.154443Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikq2dv kind= uid=b0e9dc52-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:00:54.154534Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikq2dv kind= uid=b0e9dc52-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:00:54.478879Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi9kg7q\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi9kg7q" level=info timestamp=2018-08-03T22:00:55.680493Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi9kg7q\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi9kg7q" level=info timestamp=2018-08-03T22:01:55.318773Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiznvjf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiznvjf" level=info timestamp=2018-08-03T22:01:55.417640Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiznvjf\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmiznvjf, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: b0dfeba9-9768-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiznvjf" level=info timestamp=2018-08-03T22:01:56.001288Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivxr7w kind= uid=d5cad86e-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:01:56.001399Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivxr7w kind= uid=d5cad86e-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:01:56.098111Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmivxr7w\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmivxr7w" level=info timestamp=2018-08-03T22:02:26.250038Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmivxr7w\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmivxr7w, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: d5cad86e-9768-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmivxr7w" level=info timestamp=2018-08-03T22:02:26.430531Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigbqj5 kind= uid=e7ee724c-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:02:26.430704Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigbqj5 kind= uid=e7ee724c-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:39:21.156556Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:41.220845Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.705272Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.923512Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.721246Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.784295Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:34.187516Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.597547Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.948912Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.323791Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.341421Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.755781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.929071Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.354298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:26.049033Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:39:20.908825Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:40.978299Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.461580Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.674759Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.467832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.536520Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:33.944092Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.351715Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.703648Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.065136Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.088172Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.487472Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.664030Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.093656Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:25.788153Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmigbqj5-2b8mc Pod phase: Pending • Failure [30.429 seconds] Console /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:37 A new VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:65 with a serial console /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:66 with a fedora image /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:77 should return that we are running fedora [It] /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:78 Expected error: <*errors.errorString | 0xc4205a7810>: { s: "Timeout trying to connect to the virtual machine instance", } Timeout trying to connect to the virtual machine instance not to have occurred /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:55 ------------------------------ STEP: Creating a new VirtualMachineInstance STEP: Expecting the VirtualMachineInstance console Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=error timestamp=2018-08-03T22:03:15.248992Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:15.249078Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmix6rsw/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:03:16.295197Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:16.295292Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmix6rsw/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:03:17.345917Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:17.346000Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmix6rsw/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:03:18.428646Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:18.428762Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmix6rsw/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:03:19.494142Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:19.494219Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmix6rsw/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 22:03:22 http: TLS handshake error from 10.244.0.1:33542: EOF level=error timestamp=2018-08-03T22:03:22.646015Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:22.646100Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmix6rsw/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:03:24.747069Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:24.747160Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmix6rsw/console proto=HTTP/1.1 statusCode=400 contentLength=90 Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T22:03:11.843836Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=error timestamp=2018-08-03T22:03:12.685635Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:12.685724Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmix6rsw/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:03:14.784534Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:14.784656Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmix6rsw/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 22:03:16 http: TLS handshake error from 10.244.1.1:35974: EOF level=error timestamp=2018-08-03T22:03:21.130675Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:21.130768Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmix6rsw/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:03:22.181370Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:22.181457Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmix6rsw/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:03:24.283063Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:24.283155Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmix6rsw/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 22:03:26 http: TLS handshake error from 10.244.1.1:35980: EOF level=error timestamp=2018-08-03T22:03:26.382260Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:26.382327Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmix6rsw/console proto=HTTP/1.1 statusCode=400 contentLength=90 Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T22:00:54.478879Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi9kg7q\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi9kg7q" level=info timestamp=2018-08-03T22:00:55.680493Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi9kg7q\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi9kg7q" level=info timestamp=2018-08-03T22:01:55.318773Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiznvjf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiznvjf" level=info timestamp=2018-08-03T22:01:55.417640Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiznvjf\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmiznvjf, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: b0dfeba9-9768-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiznvjf" level=info timestamp=2018-08-03T22:01:56.001288Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivxr7w kind= uid=d5cad86e-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:01:56.001399Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivxr7w kind= uid=d5cad86e-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:01:56.098111Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmivxr7w\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmivxr7w" level=info timestamp=2018-08-03T22:02:26.250038Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmivxr7w\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmivxr7w, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: d5cad86e-9768-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmivxr7w" level=info timestamp=2018-08-03T22:02:26.430531Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigbqj5 kind= uid=e7ee724c-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:02:26.430704Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigbqj5 kind= uid=e7ee724c-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:02:56.703524Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmigbqj5\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmigbqj5, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: e7ee724c-9768-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmigbqj5" level=info timestamp=2018-08-03T22:02:56.855550Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmix6rsw kind= uid=fa1135e3-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:02:56.855708Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmix6rsw kind= uid=fa1135e3-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:02:56.886871Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmix6rsw\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmix6rsw" level=info timestamp=2018-08-03T22:02:56.899700Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmix6rsw\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmix6rsw" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:39:21.156556Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:41.220845Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.705272Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.923512Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.721246Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.784295Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:34.187516Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.597547Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.948912Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.323791Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.341421Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.755781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.929071Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.354298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:26.049033Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:39:20.908825Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:40.978299Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.461580Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.674759Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.467832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.536520Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:33.944092Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.351715Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.703648Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.065136Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.088172Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.487472Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.664030Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.093656Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:25.788153Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmix6rsw-t55c2 Pod phase: Pending • Failure [30.427 seconds] Console /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:37 A new VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:65 with a serial console /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:66 should be able to reconnect to console multiple times [It] /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:87 Expected error: <*errors.errorString | 0xc4206a2820>: { s: "Timeout trying to connect to the virtual machine instance", } Timeout trying to connect to the virtual machine instance not to have occurred /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:100 ------------------------------ STEP: Creating a new VirtualMachineInstance STEP: Checking that the console output equals to expected one Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=error timestamp=2018-08-03T22:03:43.573930Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:43.574022Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmizkgrf/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:03:44.632895Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:44.633029Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmizkgrf/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:03:48.828861Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:48.828967Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmizkgrf/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:03:49.893637Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:49.893737Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmizkgrf/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:03:50.943577Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:50.943652Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmizkgrf/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 22:03:52 http: TLS handshake error from 10.244.0.1:33782: EOF level=error timestamp=2018-08-03T22:03:53.050166Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:53.050246Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmizkgrf/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:03:56.226079Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:56.226155Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmizkgrf/console proto=HTTP/1.1 statusCode=400 contentLength=90 Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T22:03:43.117832Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmizkgrf/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 22:03:46 http: TLS handshake error from 10.244.1.1:35992: EOF level=error timestamp=2018-08-03T22:03:46.267063Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:46.267136Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmizkgrf/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:03:47.315314Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:47.315392Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmizkgrf/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:03:48.367921Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:48.367983Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmizkgrf/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:03:52.585039Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:52.585119Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmizkgrf/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:03:54.712697Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:54.712828Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmizkgrf/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:03:55.766066Z pos=subresource.go:54 component=virt-api reason="Unable to connect to VirtualMachineInstance because phase is Scheduling instead of Running" msg="Failed to gather remote exec info for subresource request." level=info timestamp=2018-08-03T22:03:55.766152Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmizkgrf/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 22:03:56 http: TLS handshake error from 10.244.1.1:35998: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T22:01:55.417640Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiznvjf\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmiznvjf, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: b0dfeba9-9768-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiznvjf" level=info timestamp=2018-08-03T22:01:56.001288Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivxr7w kind= uid=d5cad86e-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:01:56.001399Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivxr7w kind= uid=d5cad86e-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:01:56.098111Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmivxr7w\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmivxr7w" level=info timestamp=2018-08-03T22:02:26.250038Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmivxr7w\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmivxr7w, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: d5cad86e-9768-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmivxr7w" level=info timestamp=2018-08-03T22:02:26.430531Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigbqj5 kind= uid=e7ee724c-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:02:26.430704Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigbqj5 kind= uid=e7ee724c-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:02:56.703524Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmigbqj5\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmigbqj5, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: e7ee724c-9768-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmigbqj5" level=info timestamp=2018-08-03T22:02:56.855550Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmix6rsw kind= uid=fa1135e3-9768-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:02:56.855708Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmix6rsw kind= uid=fa1135e3-9768-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:02:56.886871Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmix6rsw\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmix6rsw" level=info timestamp=2018-08-03T22:02:56.899700Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmix6rsw\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmix6rsw" level=info timestamp=2018-08-03T22:03:27.281722Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizkgrf kind= uid=0c33d39a-9769-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:03:27.281882Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizkgrf kind= uid=0c33d39a-9769-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:03:27.348449Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmizkgrf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmizkgrf" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:39:21.156556Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:41.220845Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.705272Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.923512Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.721246Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.784295Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:34.187516Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.597547Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.948912Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.323791Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.341421Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.755781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.929071Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.354298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:26.049033Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:39:20.908825Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:40:40.978299Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:42:11.461580Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:49.674759Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.467832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.536520Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:33.944092Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.351715Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.703648Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.065136Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.088172Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.487472Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.664030Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.093656Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:25.788153Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmizkgrf-qrhm4 Pod phase: Pending • Failure [30.424 seconds] Console /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:37 A new VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:65 with a serial console /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:66 should wait until the virtual machine is in running state and return a stream interface [It] /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:103 Expected error: <*errors.errorString | 0xc4208c9ec0>: { s: "Timeout trying to connect to the virtual machine instance", } Timeout trying to connect to the virtual machine instance not to have occurred /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:109 ------------------------------ STEP: Creating a new VirtualMachineInstance • [SLOW TEST:30.221 seconds] Console /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:37 A new VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:65 with a serial console /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:66 should fail waiting for the virtual machine instance to be running /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:111 ------------------------------ • [SLOW TEST:30.220 seconds] Console /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:37 A new VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:65 with a serial console /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:66 should fail waiting for the expecter /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:134 ------------------------------ • [SLOW TEST:5.187 seconds] User Access /root/go/src/kubevirt.io/kubevirt/tests/access_test.go:33 With default kubevirt service accounts /root/go/src/kubevirt.io/kubevirt/tests/access_test.go:41 should verify permissions are correct for view, edit, and admin /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 given a vmi /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 ------------------------------ ••• Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T22:06:29.217009Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:06:32 http: TLS handshake error from 10.244.0.1:34872: EOF 2018/08/03 22:06:42 http: TLS handshake error from 10.244.0.1:34932: EOF 2018/08/03 22:06:52 http: TLS handshake error from 10.244.0.1:34992: EOF level=info timestamp=2018-08-03T22:06:59.243314Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:07:02 http: TLS handshake error from 10.244.0.1:35052: EOF 2018/08/03 22:07:12 http: TLS handshake error from 10.244.0.1:35112: EOF 2018/08/03 22:07:22 http: TLS handshake error from 10.244.0.1:35172: EOF level=info timestamp=2018-08-03T22:07:29.216214Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:07:32 http: TLS handshake error from 10.244.0.1:35232: EOF 2018/08/03 22:07:42 http: TLS handshake error from 10.244.0.1:35292: EOF 2018/08/03 22:07:52 http: TLS handshake error from 10.244.0.1:35352: EOF level=info timestamp=2018-08-03T22:07:59.211827Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:08:02 http: TLS handshake error from 10.244.0.1:35412: EOF 2018/08/03 22:08:12 http: TLS handshake error from 10.244.0.1:35472: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T22:07:30.258787Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:07:30.551380Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:07:33.039709Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:07:36 http: TLS handshake error from 10.244.1.1:36130: EOF level=info timestamp=2018-08-03T22:07:42.324807Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:07:46 http: TLS handshake error from 10.244.1.1:36136: EOF 2018/08/03 22:07:56 http: TLS handshake error from 10.244.1.1:36142: EOF level=info timestamp=2018-08-03T22:08:00.307440Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:08:00.604401Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:08:03.060468Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:08:04.997104Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:08:04.998051Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:08:06 http: TLS handshake error from 10.244.1.1:36148: EOF level=info timestamp=2018-08-03T22:08:12.377940Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:08:16 http: TLS handshake error from 10.244.1.1:36154: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T22:03:57.526084Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmizkgrf\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmizkgrf, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 0c33d39a-9769-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmizkgrf" level=info timestamp=2018-08-03T22:03:57.710346Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiljqdk kind= uid=1e568e73-9769-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:03:57.710485Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiljqdk kind= uid=1e568e73-9769-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:04:27.929129Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivl5kc kind= uid=3059e8c6-9769-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:04:27.929304Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivl5kc kind= uid=3059e8c6-9769-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:05:18.064242Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiz7qwd kind= uid=4e3ab373-9769-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:18.064374Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiz7qwd kind= uid=4e3ab373-9769-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:05:18.074195Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmik2dxb kind= uid=4e3d7ec9-9769-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:18.074268Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmik2dxb kind= uid=4e3d7ec9-9769-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:05:18.085855Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilgg4m kind= uid=4e3ef1c0-9769-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:18.085905Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilgg4m kind= uid=4e3ef1c0-9769-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:05:18.121649Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivqhjg kind= uid=4e40c296-9769-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:18.121708Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivqhjg kind= uid=4e40c296-9769-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:05:18.134467Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmik2dxb\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmik2dxb" level=info timestamp=2018-08-03T22:05:18.147246Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmilgg4m\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmilgg4m" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:43:49.923512Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.721246Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.784295Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:34.187516Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.597547Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.948912Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.323791Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.341421Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.755781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.929071Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.354298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:26.049033Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:04:18.642359Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:06:23.242976Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:08:12.409242Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:43:49.674759Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:45:46.467832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.536520Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:33.944092Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.351715Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.703648Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.065136Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.088172Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.487472Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.664030Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.093656Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:25.788153Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:04:18.372050Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:06:22.991700Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:08:12.155318Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmik2dxb-l9zjz Pod phase: Pending Pod name: virt-launcher-testvmilgg4m-wzjj8 Pod phase: Pending Pod name: virt-launcher-testvmivqhjg-fg8d9 Pod phase: Pending Pod name: virt-launcher-testvmiz7qwd-28chv Pod phase: Pending ------------------------------ • Failure in Spec Setup (BeforeEach) [180.966 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 should be able to reach [BeforeEach] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 the Inbound VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T22:05:18.347568Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmiz7qwd kind=VirtualMachineInstance uid=4e3ab373-9769-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmiz7qwd-28chv" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T22:09:29.193140Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:09:32 http: TLS handshake error from 10.244.0.1:35952: EOF 2018/08/03 22:09:42 http: TLS handshake error from 10.244.0.1:36012: EOF 2018/08/03 22:09:52 http: TLS handshake error from 10.244.0.1:36072: EOF level=info timestamp=2018-08-03T22:09:59.189633Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:10:02 http: TLS handshake error from 10.244.0.1:36132: EOF 2018/08/03 22:10:12 http: TLS handshake error from 10.244.0.1:36192: EOF 2018/08/03 22:10:22 http: TLS handshake error from 10.244.0.1:36252: EOF level=info timestamp=2018-08-03T22:10:29.207930Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:10:32 http: TLS handshake error from 10.244.0.1:36312: EOF 2018/08/03 22:10:42 http: TLS handshake error from 10.244.0.1:36372: EOF 2018/08/03 22:10:52 http: TLS handshake error from 10.244.0.1:36432: EOF level=info timestamp=2018-08-03T22:10:59.224912Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:11:02 http: TLS handshake error from 10.244.0.1:36492: EOF 2018/08/03 22:11:12 http: TLS handshake error from 10.244.0.1:36552: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running 2018/08/03 22:10:16 http: TLS handshake error from 10.244.1.1:36226: EOF 2018/08/03 22:10:26 http: TLS handshake error from 10.244.1.1:36232: EOF level=info timestamp=2018-08-03T22:10:30.570012Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:10:30.866482Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:10:33.174139Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:10:36 http: TLS handshake error from 10.244.1.1:36238: EOF level=info timestamp=2018-08-03T22:10:42.643651Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:10:46 http: TLS handshake error from 10.244.1.1:36244: EOF 2018/08/03 22:10:56 http: TLS handshake error from 10.244.1.1:36250: EOF level=info timestamp=2018-08-03T22:11:00.621975Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:11:00.913039Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:11:03.193880Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:11:06 http: TLS handshake error from 10.244.1.1:36256: EOF level=info timestamp=2018-08-03T22:11:12.696730Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:11:16 http: TLS handshake error from 10.244.1.1:36262: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T22:05:18.085855Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilgg4m kind= uid=4e3ef1c0-9769-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:18.085905Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilgg4m kind= uid=4e3ef1c0-9769-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:05:18.121649Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivqhjg kind= uid=4e40c296-9769-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:18.121708Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivqhjg kind= uid=4e40c296-9769-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:05:18.134467Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmik2dxb\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmik2dxb" level=info timestamp=2018-08-03T22:05:18.147246Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmilgg4m\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmilgg4m" level=info timestamp=2018-08-03T22:08:19.595067Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8hbk4 kind= uid=ba6efa07-9769-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:08:19.595243Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8hbk4 kind= uid=ba6efa07-9769-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:08:19.605882Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixs2dp kind= uid=ba708866-9769-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:08:19.605977Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixs2dp kind= uid=ba708866-9769-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:08:19.621538Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi777xg kind= uid=ba72d82d-9769-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:08:19.621649Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi777xg kind= uid=ba72d82d-9769-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:08:19.645621Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiczd2x kind= uid=ba757443-9769-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:08:19.645691Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiczd2x kind= uid=ba757443-9769-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:08:20.624344Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8hbk4\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8hbk4" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:45:46.721246Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.784295Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:34.187516Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.597547Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.948912Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.323791Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.341421Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.755781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.929071Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.354298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:26.049033Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:04:18.642359Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:06:23.242976Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:08:12.409242Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:10:22.909277Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:45:46.467832Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:47:12.536520Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:33.944092Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.351715Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.703648Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.065136Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.088172Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.487472Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.664030Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.093656Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:25.788153Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:04:18.372050Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:06:22.991700Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:08:12.155318Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:10:22.651385Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmi777xg-vh2lb Pod phase: Pending Pod name: virt-launcher-testvmi8hbk4-kln2h Pod phase: Pending Pod name: virt-launcher-testvmiczd2x-s47hw Pod phase: Pending Pod name: virt-launcher-testvmixs2dp-9tvlt Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.506 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 should be able to reach [BeforeEach] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 the Inbound VirtualMachineInstance with pod network connectivity explicitly set /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T22:08:19.854258Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi8hbk4 kind=VirtualMachineInstance uid=ba6efa07-9769-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi8hbk4-kln2h" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running level=info timestamp=2018-08-03T22:12:29.206392Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:12:32 http: TLS handshake error from 10.244.0.1:37032: EOF 2018/08/03 22:12:42 http: TLS handshake error from 10.244.0.1:37092: EOF 2018/08/03 22:12:52 http: TLS handshake error from 10.244.0.1:37152: EOF level=info timestamp=2018-08-03T22:12:59.193675Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:13:02 http: TLS handshake error from 10.244.0.1:37212: EOF 2018/08/03 22:13:12 http: TLS handshake error from 10.244.0.1:37272: EOF 2018/08/03 22:13:22 http: TLS handshake error from 10.244.0.1:37332: EOF level=info timestamp=2018-08-03T22:13:29.211529Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:13:32 http: TLS handshake error from 10.244.0.1:37392: EOF 2018/08/03 22:13:42 http: TLS handshake error from 10.244.0.1:37452: EOF 2018/08/03 22:13:52 http: TLS handshake error from 10.244.0.1:37512: EOF level=info timestamp=2018-08-03T22:13:59.203680Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:14:02 http: TLS handshake error from 10.244.0.1:37572: EOF 2018/08/03 22:14:12 http: TLS handshake error from 10.244.0.1:37632: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running 2018/08/03 22:13:16 http: TLS handshake error from 10.244.1.1:36334: EOF 2018/08/03 22:13:26 http: TLS handshake error from 10.244.1.1:36340: EOF level=info timestamp=2018-08-03T22:13:30.880303Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:13:31.176600Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:13:33.323685Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:13:36 http: TLS handshake error from 10.244.1.1:36346: EOF level=info timestamp=2018-08-03T22:13:42.967025Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:13:46 http: TLS handshake error from 10.244.1.1:36352: EOF 2018/08/03 22:13:56 http: TLS handshake error from 10.244.1.1:36358: EOF level=info timestamp=2018-08-03T22:14:00.932232Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:14:01.231666Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:14:03.345352Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:14:06 http: TLS handshake error from 10.244.1.1:36364: EOF level=info timestamp=2018-08-03T22:14:13.022269Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:14:16 http: TLS handshake error from 10.244.1.1:36370: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T22:08:19.605882Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixs2dp kind= uid=ba708866-9769-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:08:19.605977Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixs2dp kind= uid=ba708866-9769-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:08:19.621538Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi777xg kind= uid=ba72d82d-9769-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:08:19.621649Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi777xg kind= uid=ba72d82d-9769-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:08:19.645621Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiczd2x kind= uid=ba757443-9769-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:08:19.645691Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiczd2x kind= uid=ba757443-9769-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:08:20.624344Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8hbk4\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8hbk4" level=info timestamp=2018-08-03T22:11:21.293553Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivxr4w kind= uid=26bbeda7-976a-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:11:21.293792Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivxr4w kind= uid=26bbeda7-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:11:21.306760Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivc8r6 kind= uid=26bdad9c-976a-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:11:21.306892Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivc8r6 kind= uid=26bdad9c-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:11:21.318699Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8qm5g kind= uid=26bfbed2-976a-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:11:21.318776Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8qm5g kind= uid=26bfbed2-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:11:21.330454Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirjjsv kind= uid=26c13542-976a-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:11:21.330608Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirjjsv kind= uid=26c13542-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:48:34.187516Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.597547Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.948912Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.323791Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.341421Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.755781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.929071Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.354298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:26.049033Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:04:18.642359Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:06:23.242976Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:08:12.409242Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:10:22.909277Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:11:29.463925Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:13:38.235493Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:48:33.944092Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:50:38.351715Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:48.703648Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.065136Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.088172Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.487472Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.664030Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.093656Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:25.788153Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:04:18.372050Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:06:22.991700Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:08:12.155318Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:10:22.651385Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:11:29.205186Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:13:37.974590Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmi8qm5g-l5nfv Pod phase: Pending Pod name: virt-launcher-testvmirjjsv-wb9h7 Pod phase: Pending Pod name: virt-launcher-testvmivc8r6-6s8j8 Pod phase: Pending Pod name: virt-launcher-testvmivxr4w-nzg8c Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.690 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 should be able to reach [BeforeEach] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 the Inbound VirtualMachineInstance with custom MAC address /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T22:11:21.605516Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmivxr4w kind=VirtualMachineInstance uid=26bbeda7-976a-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmivxr4w-nzg8c" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running 2018/08/03 22:15:32 http: TLS handshake error from 10.244.0.1:38112: EOF 2018/08/03 22:15:42 http: TLS handshake error from 10.244.0.1:38172: EOF 2018/08/03 22:15:52 http: TLS handshake error from 10.244.0.1:38232: EOF level=info timestamp=2018-08-03T22:15:59.216311Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:16:02 http: TLS handshake error from 10.244.0.1:38292: EOF 2018/08/03 22:16:12 http: TLS handshake error from 10.244.0.1:38352: EOF 2018/08/03 22:16:22 http: TLS handshake error from 10.244.0.1:38412: EOF level=info timestamp=2018-08-03T22:16:29.201289Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:16:32 http: TLS handshake error from 10.244.0.1:38472: EOF 2018/08/03 22:16:42 http: TLS handshake error from 10.244.0.1:38532: EOF 2018/08/03 22:16:52 http: TLS handshake error from 10.244.0.1:38592: EOF level=info timestamp=2018-08-03T22:16:59.209089Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:17:02 http: TLS handshake error from 10.244.0.1:38652: EOF 2018/08/03 22:17:12 http: TLS handshake error from 10.244.0.1:38712: EOF 2018/08/03 22:17:22 http: TLS handshake error from 10.244.0.1:38772: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T22:16:31.190417Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:16:31.481992Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:16:33.456801Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:16:36 http: TLS handshake error from 10.244.1.1:36454: EOF level=info timestamp=2018-08-03T22:16:43.289319Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:16:46 http: TLS handshake error from 10.244.1.1:36460: EOF 2018/08/03 22:16:56 http: TLS handshake error from 10.244.1.1:36466: EOF level=info timestamp=2018-08-03T22:17:01.242555Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:17:01.542151Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:17:03.486745Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:17:04.938248Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:17:04.939329Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:17:06 http: TLS handshake error from 10.244.1.1:36472: EOF level=info timestamp=2018-08-03T22:17:13.343156Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:17:16 http: TLS handshake error from 10.244.1.1:36478: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T22:11:21.306892Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivc8r6 kind= uid=26bdad9c-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:11:21.318699Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8qm5g kind= uid=26bfbed2-976a-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:11:21.318776Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8qm5g kind= uid=26bfbed2-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:11:21.330454Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirjjsv kind= uid=26c13542-976a-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:11:21.330608Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirjjsv kind= uid=26c13542-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:14:22.278155Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmirjjsv\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmirjjsv, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 26c13542-976a-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmirjjsv" level=info timestamp=2018-08-03T22:14:22.982232Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih68d7 kind= uid=93079dae-976a-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:14:22.982425Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih68d7 kind= uid=93079dae-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:14:22.990855Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwgwn6 kind= uid=93091e9e-976a-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:14:22.991011Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwgwn6 kind= uid=93091e9e-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:14:23.001324Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmij4bw9 kind= uid=930aefdc-976a-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:14:23.001379Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmij4bw9 kind= uid=930aefdc-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:14:23.034946Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmij4bw9\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmij4bw9" level=info timestamp=2018-08-03T22:14:23.049116Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiggplx kind= uid=930d7509-976a-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:14:23.049183Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiggplx kind= uid=930d7509-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:52:48.948912Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.323791Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.341421Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.755781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.929071Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.354298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:26.049033Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:04:18.642359Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:06:23.242976Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:08:12.409242Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:10:22.909277Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:11:29.463925Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:13:38.235493Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:15:03.304303Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:16:53.061021Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:52:48.703648Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:53:54.065136Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.088172Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.487472Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.664030Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.093656Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:25.788153Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:04:18.372050Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:06:22.991700Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:08:12.155318Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:10:22.651385Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:11:29.205186Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:13:37.974590Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:15:03.039026Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:16:52.796098Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmiggplx-jvtgv Pod phase: Pending Pod name: virt-launcher-testvmih68d7-blt5g Pod phase: Pending Pod name: virt-launcher-testvmij4bw9-7nw5p Pod phase: Pending Pod name: virt-launcher-testvmiwgwn6-69477 Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.708 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 should be able to reach [BeforeEach] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 the internet /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T22:14:23.248443Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmih68d7 kind=VirtualMachineInstance uid=93079dae-976a-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmih68d7-blt5g" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running 2018/08/03 22:18:32 http: TLS handshake error from 10.244.0.1:39192: EOF 2018/08/03 22:18:42 http: TLS handshake error from 10.244.0.1:39252: EOF 2018/08/03 22:18:52 http: TLS handshake error from 10.244.0.1:39312: EOF level=info timestamp=2018-08-03T22:18:59.214790Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:19:02 http: TLS handshake error from 10.244.0.1:39372: EOF 2018/08/03 22:19:12 http: TLS handshake error from 10.244.0.1:39432: EOF 2018/08/03 22:19:22 http: TLS handshake error from 10.244.0.1:39492: EOF level=info timestamp=2018-08-03T22:19:29.197492Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:19:32 http: TLS handshake error from 10.244.0.1:39552: EOF 2018/08/03 22:19:42 http: TLS handshake error from 10.244.0.1:39612: EOF 2018/08/03 22:19:52 http: TLS handshake error from 10.244.0.1:39672: EOF level=info timestamp=2018-08-03T22:19:59.209929Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:20:02 http: TLS handshake error from 10.244.0.1:39732: EOF 2018/08/03 22:20:12 http: TLS handshake error from 10.244.0.1:39792: EOF 2018/08/03 22:20:22 http: TLS handshake error from 10.244.0.1:39852: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T22:19:31.498490Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:19:31.796439Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:19:33.598000Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:19:36 http: TLS handshake error from 10.244.1.1:36562: EOF level=info timestamp=2018-08-03T22:19:43.608675Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:19:46 http: TLS handshake error from 10.244.1.1:36568: EOF 2018/08/03 22:19:56 http: TLS handshake error from 10.244.1.1:36574: EOF level=info timestamp=2018-08-03T22:20:01.550331Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:20:01.851073Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:20:03.619759Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:20:04.943730Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:20:04.944925Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:20:06 http: TLS handshake error from 10.244.1.1:36580: EOF level=info timestamp=2018-08-03T22:20:13.661875Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:20:16 http: TLS handshake error from 10.244.1.1:36586: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T22:14:23.001324Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmij4bw9 kind= uid=930aefdc-976a-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:14:23.001379Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmij4bw9 kind= uid=930aefdc-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:14:23.034946Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmij4bw9\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmij4bw9" level=info timestamp=2018-08-03T22:14:23.049116Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiggplx kind= uid=930d7509-976a-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:14:23.049183Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiggplx kind= uid=930d7509-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:17:24.054827Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiwgwn6\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmiwgwn6, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 93091e9e-976a-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiwgwn6" level=info timestamp=2018-08-03T22:17:24.490606Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi44xkb kind= uid=ff379a74-976a-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:17:24.490762Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi44xkb kind= uid=ff379a74-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:17:24.502417Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmijkwcp kind= uid=ff395493-976a-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:17:24.502604Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmijkwcp kind= uid=ff395493-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:17:24.520557Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7227h kind= uid=ff3ac5b5-976a-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:17:24.520711Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7227h kind= uid=ff3ac5b5-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:17:24.548870Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmicrk42 kind= uid=ff3e16d0-976a-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:17:24.548946Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmicrk42 kind= uid=ff3e16d0-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:17:24.558860Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmijkwcp\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmijkwcp" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:53:54.323791Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.341421Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.755781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.929071Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.354298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:26.049033Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:04:18.642359Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:06:23.242976Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:08:12.409242Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:10:22.909277Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:11:29.463925Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:13:38.235493Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:15:03.304303Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:16:53.061021Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:18:44.257886Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:53:54.065136Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.088172Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:56:27.487472Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.664030Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.093656Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:25.788153Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:04:18.372050Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:06:22.991700Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:08:12.155318Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:10:22.651385Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:11:29.205186Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:13:37.974590Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:15:03.039026Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:16:52.796098Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:18:43.997829Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmi44xkb-42chg Pod phase: Pending Pod name: virt-launcher-testvmi7227h-cm8cn Pod phase: Pending Pod name: virt-launcher-testvmicrk42-8jbx4 Pod phase: Pending Pod name: virt-launcher-testvmijkwcp-rmpvc Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.505 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 should be reachable via the propagated IP from a Pod [BeforeEach] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 on the same node from Pod /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.003s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T22:17:24.760348Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi44xkb kind=VirtualMachineInstance uid=ff379a74-976a-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi44xkb-42chg" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running 2018/08/03 22:21:52 http: TLS handshake error from 10.244.0.1:40392: EOF level=info timestamp=2018-08-03T22:21:59.152264Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:21:59.189853Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:21:59.251645Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:22:02 http: TLS handshake error from 10.244.0.1:40452: EOF 2018/08/03 22:22:12 http: TLS handshake error from 10.244.0.1:40512: EOF 2018/08/03 22:22:22 http: TLS handshake error from 10.244.0.1:40572: EOF level=info timestamp=2018-08-03T22:22:29.196631Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:22:32 http: TLS handshake error from 10.244.0.1:40632: EOF 2018/08/03 22:22:42 http: TLS handshake error from 10.244.0.1:40692: EOF 2018/08/03 22:22:52 http: TLS handshake error from 10.244.0.1:40752: EOF level=info timestamp=2018-08-03T22:22:59.229250Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:23:02 http: TLS handshake error from 10.244.0.1:40812: EOF 2018/08/03 22:23:12 http: TLS handshake error from 10.244.0.1:40872: EOF 2018/08/03 22:23:22 http: TLS handshake error from 10.244.0.1:40932: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running level=info timestamp=2018-08-03T22:22:32.109550Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:22:33.729391Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:22:36 http: TLS handshake error from 10.244.1.1:36670: EOF level=info timestamp=2018-08-03T22:22:43.928897Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:22:46 http: TLS handshake error from 10.244.1.1:36676: EOF 2018/08/03 22:22:56 http: TLS handshake error from 10.244.1.1:36682: EOF level=info timestamp=2018-08-03T22:23:01.864451Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:23:02.161600Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:23:03.750824Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:23:04.914375Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:23:04.915322Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:23:06 http: TLS handshake error from 10.244.1.1:36688: EOF level=info timestamp=2018-08-03T22:23:13.988891Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:23:16 http: TLS handshake error from 10.244.1.1:36694: EOF 2018/08/03 22:23:26 http: TLS handshake error from 10.244.1.1:36700: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T22:17:24.502604Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmijkwcp kind= uid=ff395493-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:17:24.520557Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7227h kind= uid=ff3ac5b5-976a-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:17:24.520711Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7227h kind= uid=ff3ac5b5-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:17:24.548870Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmicrk42 kind= uid=ff3e16d0-976a-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:17:24.548946Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmicrk42 kind= uid=ff3e16d0-976a-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:17:24.558860Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmijkwcp\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmijkwcp" level=info timestamp=2018-08-03T22:20:26.198240Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8r8cm kind= uid=6b85bf21-976b-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:20:26.198409Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8r8cm kind= uid=6b85bf21-976b-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:20:26.208049Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmit54wc kind= uid=6b87770d-976b-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:20:26.208146Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmit54wc kind= uid=6b87770d-976b-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:20:26.217963Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilgwhx kind= uid=6b897f8c-976b-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:20:26.218026Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilgwhx kind= uid=6b897f8c-976b-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:20:26.256242Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirjf57 kind= uid=6b8ad0e2-976b-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:20:26.256318Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirjf57 kind= uid=6b8ad0e2-976b-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:20:26.262902Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8r8cm\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8r8cm" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T21:56:27.755781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.929071Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.354298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:26.049033Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:04:18.642359Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:06:23.242976Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:08:12.409242Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:10:22.909277Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:11:29.463925Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:13:38.235493Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:15:03.304303Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:16:53.061021Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:18:44.257886Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:20:31.037903Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:22:25.472550Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T21:56:27.487472Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:58:34.664030Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:00:28.093656Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:25.788153Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:04:18.372050Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:06:22.991700Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:08:12.155318Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:10:22.651385Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:11:29.205186Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:13:37.974590Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:15:03.039026Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:16:52.796098Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:18:43.997829Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:20:30.776463Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:22:25.208640Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmi8r8cm-zzv69 Pod phase: Pending Pod name: virt-launcher-testvmilgwhx-pjv89 Pod phase: Pending Pod name: virt-launcher-testvmirjf57-fgw9s Pod phase: Pending Pod name: virt-launcher-testvmit54wc-2mstf Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.704 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 should be reachable via the propagated IP from a Pod [BeforeEach] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 on a different node from Pod /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T22:20:26.465638Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi8r8cm kind=VirtualMachineInstance uid=6b85bf21-976b-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi8r8cm-zzv69" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running 2018/08/03 22:24:32 http: TLS handshake error from 10.244.0.1:41352: EOF 2018/08/03 22:24:42 http: TLS handshake error from 10.244.0.1:41412: EOF 2018/08/03 22:24:52 http: TLS handshake error from 10.244.0.1:41472: EOF level=info timestamp=2018-08-03T22:24:59.205141Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:25:02 http: TLS handshake error from 10.244.0.1:41532: EOF 2018/08/03 22:25:12 http: TLS handshake error from 10.244.0.1:41592: EOF 2018/08/03 22:25:22 http: TLS handshake error from 10.244.0.1:41652: EOF level=info timestamp=2018-08-03T22:25:29.197873Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:25:32 http: TLS handshake error from 10.244.0.1:41712: EOF 2018/08/03 22:25:42 http: TLS handshake error from 10.244.0.1:41772: EOF 2018/08/03 22:25:52 http: TLS handshake error from 10.244.0.1:41832: EOF level=info timestamp=2018-08-03T22:25:59.231499Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:26:02 http: TLS handshake error from 10.244.0.1:1024: EOF 2018/08/03 22:26:12 http: TLS handshake error from 10.244.0.1:41952: EOF 2018/08/03 22:26:22 http: TLS handshake error from 10.244.0.1:42012: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running 2018/08/03 22:25:26 http: TLS handshake error from 10.244.1.1:36772: EOF level=info timestamp=2018-08-03T22:25:32.124080Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:25:32.419631Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:25:33.855431Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:25:36 http: TLS handshake error from 10.244.1.1:36778: EOF level=info timestamp=2018-08-03T22:25:44.255701Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:25:46 http: TLS handshake error from 10.244.1.1:36784: EOF 2018/08/03 22:25:56 http: TLS handshake error from 10.244.1.1:36790: EOF level=info timestamp=2018-08-03T22:26:02.179194Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:26:02.471402Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:26:03.876719Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:26:06 http: TLS handshake error from 10.244.1.1:36796: EOF level=info timestamp=2018-08-03T22:26:14.308692Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:26:16 http: TLS handshake error from 10.244.1.1:36802: EOF 2018/08/03 22:26:26 http: TLS handshake error from 10.244.1.1:36808: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T22:20:26.218026Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilgwhx kind= uid=6b897f8c-976b-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:20:26.256242Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirjf57 kind= uid=6b8ad0e2-976b-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:20:26.256318Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirjf57 kind= uid=6b8ad0e2-976b-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:20:26.262902Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8r8cm\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8r8cm" level=info timestamp=2018-08-03T22:23:27.180344Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8r8cm\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi8r8cm, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 6b85bf21-976b-11e8-a522-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8r8cm" level=info timestamp=2018-08-03T22:23:27.902305Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmij27tm kind= uid=d7d3bca9-976b-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:23:27.902459Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmij27tm kind= uid=d7d3bca9-976b-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:23:27.909171Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8b674 kind= uid=d7d53b86-976b-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:23:27.909241Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8b674 kind= uid=d7d53b86-976b-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:23:27.935252Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikh779 kind= uid=d7d71a7f-976b-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:23:27.935332Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikh779 kind= uid=d7d71a7f-976b-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:23:27.956364Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmib5kjw kind= uid=d7db67b0-976b-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:23:27.956412Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmib5kjw kind= uid=d7db67b0-976b-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:23:27.959803Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8b674\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8b674" level=info timestamp=2018-08-03T22:23:28.136164Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmij27tm\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmij27tm" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T22:00:28.354298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:26.049033Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:04:18.642359Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:06:23.242976Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:08:12.409242Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:10:22.909277Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:11:29.463925Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:13:38.235493Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:15:03.304303Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:16:53.061021Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:18:44.257886Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:20:31.037903Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:22:25.472550Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:23:54.557853Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:25:03.986654Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T22:00:28.093656Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:02:25.788153Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:04:18.372050Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:06:22.991700Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:08:12.155318Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:10:22.651385Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:11:29.205186Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:13:37.974590Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:15:03.039026Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:16:52.796098Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:18:43.997829Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:20:30.776463Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:22:25.208640Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:23:54.294130Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:25:03.716115Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmi8b674-th9jz Pod phase: Pending Pod name: virt-launcher-testvmib5kjw-n7hs7 Pod phase: Pending Pod name: virt-launcher-testvmij27tm-nwpp9 Pod phase: Pending Pod name: virt-launcher-testvmikh779-64shd Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.695 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 should be reachable via the propagated IP from a Pod [BeforeEach] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 on the same node from Node /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T22:23:28.203222Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmij27tm kind=VirtualMachineInstance uid=d7d3bca9-976b-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmij27tm-nwpp9" Pod name: disks-images-provider-nbv8b Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-pk27m Pod phase: Running copy all images to host mount directory Pod name: virt-api-bcc6b587d-jtzlz Pod phase: Running 2018/08/03 22:27:32 http: TLS handshake error from 10.244.0.1:42432: EOF 2018/08/03 22:27:42 http: TLS handshake error from 10.244.0.1:42492: EOF 2018/08/03 22:27:52 http: TLS handshake error from 10.244.0.1:42552: EOF level=info timestamp=2018-08-03T22:27:59.213734Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:28:02 http: TLS handshake error from 10.244.0.1:42612: EOF 2018/08/03 22:28:12 http: TLS handshake error from 10.244.0.1:42672: EOF 2018/08/03 22:28:22 http: TLS handshake error from 10.244.0.1:42732: EOF level=info timestamp=2018-08-03T22:28:29.359680Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:28:32 http: TLS handshake error from 10.244.0.1:42792: EOF 2018/08/03 22:28:42 http: TLS handshake error from 10.244.0.1:42852: EOF 2018/08/03 22:28:52 http: TLS handshake error from 10.244.0.1:42912: EOF level=info timestamp=2018-08-03T22:28:59.230722Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:29:02 http: TLS handshake error from 10.244.0.1:42972: EOF 2018/08/03 22:29:12 http: TLS handshake error from 10.244.0.1:43032: EOF 2018/08/03 22:29:22 http: TLS handshake error from 10.244.0.1:43092: EOF Pod name: virt-api-bcc6b587d-qjd4t Pod phase: Running 2018/08/03 22:28:26 http: TLS handshake error from 10.244.1.1:36880: EOF level=info timestamp=2018-08-03T22:28:32.441459Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:28:32.730887Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:28:33.978303Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:28:36 http: TLS handshake error from 10.244.1.1:36886: EOF level=info timestamp=2018-08-03T22:28:44.575688Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:28:46 http: TLS handshake error from 10.244.1.1:36892: EOF 2018/08/03 22:28:56 http: TLS handshake error from 10.244.1.1:36898: EOF level=info timestamp=2018-08-03T22:29:02.491215Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:29:02.782473Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:29:04.002549Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:29:06 http: TLS handshake error from 10.244.1.1:36904: EOF level=info timestamp=2018-08-03T22:29:14.628986Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url="/apis/subresources.kubevirt.io/v1alpha2?timeout=32s" proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:29:16 http: TLS handshake error from 10.244.1.1:36910: EOF 2018/08/03 22:29:26 http: TLS handshake error from 10.244.1.1:36916: EOF Pod name: virt-controller-67dcdd8464-4sb5c Pod phase: Running level=info timestamp=2018-08-03T20:59:03.180976Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-54rkr Pod phase: Running level=info timestamp=2018-08-03T22:23:27.909241Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8b674 kind= uid=d7d53b86-976b-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:23:27.935252Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikh779 kind= uid=d7d71a7f-976b-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:23:27.935332Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikh779 kind= uid=d7d71a7f-976b-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:23:27.956364Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmib5kjw kind= uid=d7db67b0-976b-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:23:27.956412Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmib5kjw kind= uid=d7db67b0-976b-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:23:27.959803Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8b674\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8b674" level=info timestamp=2018-08-03T22:23:28.136164Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmij27tm\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmij27tm" level=info timestamp=2018-08-03T22:26:29.598666Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizvkxp kind= uid=44207707-976c-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:26:29.598997Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizvkxp kind= uid=44207707-976c-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:26:29.610193Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixq8jw kind= uid=4421e6fe-976c-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:26:29.610306Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixq8jw kind= uid=4421e6fe-976c-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:26:29.619894Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi94r88 kind= uid=44239e83-976c-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:26:29.620030Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi94r88 kind= uid=44239e83-976c-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:26:29.632119Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi52w8f kind= uid=4424f760-976c-11e8-a522-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:26:29.632192Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi52w8f kind= uid=4424f760-976c-11e8-a522-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-bjddl Pod phase: Running level=error timestamp=2018-08-03T22:04:18.642359Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:06:23.242976Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:08:12.409242Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:10:22.909277Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:11:29.463925Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:13:38.235493Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:15:03.304303Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:16:53.061021Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:18:44.257886Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:20:31.037903Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:22:25.472550Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:23:54.557853Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:25:03.986654Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:27:14.991087Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:28:38.203007Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-handler-dckgz Pod phase: Running level=error timestamp=2018-08-03T22:04:18.372050Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:06:22.991700Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:08:12.155318Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:10:22.651385Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:11:29.205186Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:13:37.974590Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:15:03.039026Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:16:52.796098Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:18:43.997829Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:20:30.776463Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:22:25.208640Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:23:54.294130Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:25:03.716115Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:27:14.733874Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:28:37.939713Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" Pod name: virt-launcher-testvmi52w8f-t7fhv Pod phase: Pending Pod name: virt-launcher-testvmi94r88-99swb Pod phase: Pending Pod name: virt-launcher-testvmixq8jw-hndz8 Pod phase: Pending Pod name: virt-launcher-testvmizvkxp-w2hhz Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.698 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 should be reachable via the propagated IP from a Pod [BeforeEach] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 on a different node from Node /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T22:26:29.856558Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmizvkxp kind=VirtualMachineInstance uid=44207707-976c-11e8-a522-525500d15501 msg="Created virtual machine pod virt-launcher-testvmizvkxp-w2hhz" panic: test timed out after 1h30m0s goroutine 15222 [running]: testing.(*M).startAlarm.func1() /gimme/.gimme/versions/go1.10.linux.amd64/src/testing/testing.go:1240 +0xfc created by time.goFunc /gimme/.gimme/versions/go1.10.linux.amd64/src/time/sleep.go:172 +0x44 goroutine 1 [chan receive, 90 minutes]: testing.(*T).Run(0xc4200efe00, 0x12ad0d7, 0x9, 0x1339680, 0x47fa16) /gimme/.gimme/versions/go1.10.linux.amd64/src/testing/testing.go:825 +0x301 testing.runTests.func1(0xc4200efd10) /gimme/.gimme/versions/go1.10.linux.amd64/src/testing/testing.go:1063 +0x64 testing.tRunner(0xc4200efd10, 0xc4206a1df8) /gimme/.gimme/versions/go1.10.linux.amd64/src/testing/testing.go:777 +0xd0 testing.runTests(0xc420753780, 0x1bc0e20, 0x1, 0x1, 0x412009) /gimme/.gimme/versions/go1.10.linux.amd64/src/testing/testing.go:1061 +0x2c4 testing.(*M).Run(0xc42089ff80, 0x0) /gimme/.gimme/versions/go1.10.linux.amd64/src/testing/testing.go:978 +0x171 main.main() _testmain.go:44 +0x151 goroutine 5 [chan receive]: kubevirt.io/kubevirt/vendor/github.com/golang/glog.(*loggingT).flushDaemon(0x1be7be0) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/golang/glog/glog.go:879 +0x8b created by kubevirt.io/kubevirt/vendor/github.com/golang/glog.init.0 /root/go/src/kubevirt.io/kubevirt/vendor/github.com/golang/glog/glog.go:410 +0x203 goroutine 6 [syscall, 90 minutes]: os/signal.signal_recv(0x0) /gimme/.gimme/versions/go1.10.linux.amd64/src/runtime/sigqueue.go:139 +0xa6 os/signal.loop() /gimme/.gimme/versions/go1.10.linux.amd64/src/os/signal/signal_unix.go:22 +0x22 created by os/signal.init.0 /gimme/.gimme/versions/go1.10.linux.amd64/src/os/signal/signal_unix.go:28 +0x41 goroutine 9 [select]: kubevirt.io/kubevirt/tests.(*ObjectEventWatcher).Watch(0xc420b49030, 0xc420794630) /root/go/src/kubevirt.io/kubevirt/tests/utils.go:284 +0x579 kubevirt.io/kubevirt/tests.(*ObjectEventWatcher).WaitFor(0xc420b49030, 0x12a90a0, 0x6, 0x111b660, 0x13b0aa0, 0x0) /root/go/src/kubevirt.io/kubevirt/tests/utils.go:294 +0xba kubevirt.io/kubevirt/tests.waitForVMIStart(0x13b9580, 0xc4205c9b80, 0x5a, 0x0, 0x0, 0x0) /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1010 +0x50e kubevirt.io/kubevirt/tests.WaitForSuccessfulVMIStart(0x13b9580, 0xc4205c9b80, 0xc420b49120, 0xa206ae) /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 +0x43 kubevirt.io/kubevirt/tests.WaitUntilVMIReady(0xc4205c9b80, 0x1339658, 0x1c06250) /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1052 +0x3b kubevirt.io/kubevirt/tests_test.glob..func18.4() /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:135 +0x72b kubevirt.io/kubevirt/tests.BeforeAll.func1() /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1334 +0x3f kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*runner).runSync(0xc42079bf20, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113 +0x9c kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*runner).run(0xc42079bf20, 0xc42067a9a0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:64 +0x13e kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*SetupNode).Run(0xc4202704a8, 0x13b5fc0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/leafnodes/setup_nodes.go:15 +0x7f kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/spec.(*Spec).runSample(0xc4202a5950, 0x0, 0x13b5fc0, 0xc420057500) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/spec/spec.go:181 +0x1f1 kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/spec.(*Spec).Run(0xc4202a5950, 0x13b5fc0, 0xc420057500) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/spec/spec.go:138 +0xff kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).runSpec(0xc42010be00, 0xc4202a5950, 0x0) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:200 +0x10d kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).runSpecs(0xc42010be00, 0x1) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:170 +0x329 kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).Run(0xc42010be00, 0xb) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:66 +0x11b kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/suite.(*Suite).Run(0xc4200ceaf0, 0x7f78436ec3a0, 0xc4200efe00, 0x12af51b, 0xb, 0xc4207537c0, 0x2, 0x2, 0x13d0ca0, 0xc420057500, ...) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/suite/suite.go:62 +0x27c kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo.RunSpecsWithCustomReporters(0x13b6d00, 0xc4200efe00, 0x12af51b, 0xb, 0xc4207537a0, 0x2, 0x2, 0x2) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/ginkgo_dsl.go:221 +0x258 kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo.RunSpecsWithDefaultAndCustomReporters(0x13b6d00, 0xc4200efe00, 0x12af51b, 0xb, 0xc4203cc710, 0x1, 0x1, 0x1) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/ginkgo_dsl.go:209 +0xab kubevirt.io/kubevirt/tests_test.TestTests(0xc4200efe00) /root/go/src/kubevirt.io/kubevirt/tests/tests_suite_test.go:43 +0xaa testing.tRunner(0xc4200efe00, 0x1339680) /gimme/.gimme/versions/go1.10.linux.amd64/src/testing/testing.go:777 +0xd0 created by testing.(*T).Run /gimme/.gimme/versions/go1.10.linux.amd64/src/testing/testing.go:824 +0x2e0 goroutine 10 [chan receive, 90 minutes]: kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).registerForInterrupts(0xc42010be00, 0xc4207e4c60) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:223 +0xd1 created by kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).Run /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:60 +0x88 goroutine 11 [select, 90 minutes, locked to thread]: runtime.gopark(0x133b4c0, 0x0, 0x12a9dde, 0x6, 0x18, 0x1) /gimme/.gimme/versions/go1.10.linux.amd64/src/runtime/proc.go:291 +0x11a runtime.selectgo(0xc420076750, 0xc4207e4d20) /gimme/.gimme/versions/go1.10.linux.amd64/src/runtime/select.go:392 +0xe50 runtime.ensureSigM.func1() /gimme/.gimme/versions/go1.10.linux.amd64/src/runtime/signal_unix.go:549 +0x1f4 runtime.goexit() /gimme/.gimme/versions/go1.10.linux.amd64/src/runtime/asm_amd64.s:2361 +0x1 goroutine 51 [IO wait]: internal/poll.runtime_pollWait(0x7f78436d8f00, 0x72, 0xc42008b850) /gimme/.gimme/versions/go1.10.linux.amd64/src/runtime/netpoll.go:173 +0x57 internal/poll.(*pollDesc).wait(0xc4204fc898, 0x72, 0xffffffffffffff00, 0x13b7ca0, 0x1ad8640) /gimme/.gimme/versions/go1.10.linux.amd64/src/internal/poll/fd_poll_runtime.go:85 +0x9b internal/poll.(*pollDesc).waitRead(0xc4204fc898, 0xc420a5c000, 0x8000, 0x8000) /gimme/.gimme/versions/go1.10.linux.amd64/src/internal/poll/fd_poll_runtime.go:90 +0x3d internal/poll.(*FD).Read(0xc4204fc880, 0xc420a5c000, 0x8000, 0x8000, 0x0, 0x0, 0x0) /gimme/.gimme/versions/go1.10.linux.amd64/src/internal/poll/fd_unix.go:157 +0x17d net.(*netFD).Read(0xc4204fc880, 0xc420a5c000, 0x8000, 0x8000, 0x0, 0x8, 0x7ffb) /gimme/.gimme/versions/go1.10.linux.amd64/src/net/fd_unix.go:202 +0x4f net.(*conn).Read(0xc42000eb68, 0xc420a5c000, 0x8000, 0x8000, 0x0, 0x0, 0x0) /gimme/.gimme/versions/go1.10.linux.amd64/src/net/net.go:176 +0x6a crypto/tls.(*block).readFromUntil(0xc4206ddaa0, 0x7f78436ec620, 0xc42000eb68, 0x5, 0xc42000eb68, 0x0) /gimme/.gimme/versions/go1.10.linux.amd64/src/crypto/tls/conn.go:493 +0x96 crypto/tls.(*Conn).readRecord(0xc4200d9500, 0x133b617, 0xc4200d9620, 0x20) /gimme/.gimme/versions/go1.10.linux.amd64/src/crypto/tls/conn.go:595 +0xe0 crypto/tls.(*Conn).Read(0xc4200d9500, 0xc42071f000, 0x1000, 0x1000, 0x0, 0x0, 0x0) /gimme/.gimme/versions/go1.10.linux.amd64/src/crypto/tls/conn.go:1156 +0x100 bufio.(*Reader).Read(0xc420875aa0, 0xc4208722d8, 0x9, 0x9, 0xc4200a8c28, 0x1, 0x0) /gimme/.gimme/versions/go1.10.linux.amd64/src/bufio/bufio.go:216 +0x238 io.ReadAtLeast(0x13b4e00, 0xc420875aa0, 0xc4208722d8, 0x9, 0x9, 0x9, 0xc4207d65a0, 0x43f2c1, 0xc420a92a80) /gimme/.gimme/versions/go1.10.linux.amd64/src/io/io.go:309 +0x86 io.ReadFull(0x13b4e00, 0xc420875aa0, 0xc4208722d8, 0x9, 0x9, 0x133b608, 0xc42008bd10, 0x462d33) /gimme/.gimme/versions/go1.10.linux.amd64/src/io/io.go:327 +0x58 kubevirt.io/kubevirt/vendor/golang.org/x/net/http2.readFrameHeader(0xc4208722d8, 0x9, 0x9, 0x13b4e00, 0xc420875aa0, 0x0, 0xc400000000, 0x7babc0, 0xc420c9d068) /root/go/src/kubevirt.io/kubevirt/vendor/golang.org/x/net/http2/frame.go:237 +0x7b kubevirt.io/kubevirt/vendor/golang.org/x/net/http2.(*Framer).ReadFrame(0xc4208722a0, 0xc42074fc50, 0x0, 0x0, 0x0) /root/go/src/kubevirt.io/kubevirt/vendor/golang.org/x/net/http2/frame.go:492 +0xa4 kubevirt.io/kubevirt/vendor/golang.org/x/net/http2.(*clientConnReadLoop).run(0xc42008bfb0, 0x133a5d8, 0xc42046b7b0) /root/go/src/kubevirt.io/kubevirt/vendor/golang.org/x/net/http2/transport.go:1428 +0x8e kubevirt.io/kubevirt/vendor/golang.org/x/net/http2.(*ClientConn).readLoop(0xc4206d8000) /root/go/src/kubevirt.io/kubevirt/vendor/golang.org/x/net/http2/transport.go:1354 +0x76 created by kubevirt.io/kubevirt/vendor/golang.org/x/net/http2.(*Transport).newClientConn /root/go/src/kubevirt.io/kubevirt/vendor/golang.org/x/net/http2/transport.go:579 +0x651 goroutine 15220 [semacquire]: sync.runtime_notifyListWait(0xc420c9d080, 0xc400000001) /gimme/.gimme/versions/go1.10.linux.amd64/src/runtime/sema.go:510 +0x10b sync.(*Cond).Wait(0xc420c9d070) /gimme/.gimme/versions/go1.10.linux.amd64/src/sync/cond.go:56 +0x80 kubevirt.io/kubevirt/vendor/golang.org/x/net/http2.(*pipe).Read(0xc420c9d068, 0xc420b8f201, 0x5ff, 0x5ff, 0x0, 0x0, 0x0) /root/go/src/kubevirt.io/kubevirt/vendor/golang.org/x/net/http2/pipe.go:64 +0x8f kubevirt.io/kubevirt/vendor/golang.org/x/net/http2.transportResponseBody.Read(0xc420c9d040, 0xc420b8f201, 0x5ff, 0x5ff, 0x0, 0x0, 0x0) /root/go/src/kubevirt.io/kubevirt/vendor/golang.org/x/net/http2/transport.go:1674 +0xa1 encoding/json.(*Decoder).refill(0xc4201acf00, 0x7fb90a, 0x9) /gimme/.gimme/versions/go1.10.linux.amd64/src/encoding/json/stream.go:159 +0x132 encoding/json.(*Decoder).readValue(0xc4201acf00, 0x0, 0x0, 0x112bf00) /gimme/.gimme/versions/go1.10.linux.amd64/src/encoding/json/stream.go:134 +0x23d encoding/json.(*Decoder).Decode(0xc4201acf00, 0x1145800, 0xc4207601e0, 0x13bc280, 0xc420697680) /gimme/.gimme/versions/go1.10.linux.amd64/src/encoding/json/stream.go:63 +0x78 kubevirt.io/kubevirt/vendor/k8s.io/apimachinery/pkg/util/framer.(*jsonFrameReader).Read(0xc42075dda0, 0xc420a45800, 0x400, 0x400, 0xc420b85180, 0x40, 0x38) /root/go/src/kubevirt.io/kubevirt/vendor/k8s.io/apimachinery/pkg/util/framer/framer.go:150 +0x295 kubevirt.io/kubevirt/vendor/k8s.io/apimachinery/pkg/runtime/serializer/streaming.(*decoder).Decode(0xc42067c1e0, 0x0, 0x13bdf40, 0xc420b85180, 0x380, 0x13bc280, 0xc4207c1498, 0x456ae0, 0xc4207c1440) /root/go/src/kubevirt.io/kubevirt/vendor/k8s.io/apimachinery/pkg/runtime/serializer/streaming/streaming.go:77 +0x95 kubevirt.io/kubevirt/vendor/k8s.io/client-go/rest/watch.(*Decoder).Decode(0xc420753620, 0xc4208b9fa8, 0x5, 0x13bc280, 0xc420697680, 0x0, 0x0) /root/go/src/kubevirt.io/kubevirt/vendor/k8s.io/client-go/rest/watch/decoder.go:49 +0x7c kubevirt.io/kubevirt/vendor/k8s.io/apimachinery/pkg/watch.(*StreamWatcher).receive(0xc42075ddd0) /root/go/src/kubevirt.io/kubevirt/vendor/k8s.io/apimachinery/pkg/watch/streamwatcher.go:93 +0x12e created by kubevirt.io/kubevirt/vendor/k8s.io/apimachinery/pkg/watch.NewStreamWatcher /root/go/src/kubevirt.io/kubevirt/vendor/k8s.io/apimachinery/pkg/watch/streamwatcher.go:60 +0xa8 goroutine 15221 [chan receive]: kubevirt.io/kubevirt/tests.(*ObjectEventWatcher).Watch.func3(0x13be4c0, 0xc42075ddd0, 0xc420a54ca0, 0xc4207c14a0) /root/go/src/kubevirt.io/kubevirt/tests/utils.go:275 +0x93 created by kubevirt.io/kubevirt/tests.(*ObjectEventWatcher).Watch /root/go/src/kubevirt.io/kubevirt/tests/utils.go:273 +0x4ae make: *** [functest] Error 2 + make cluster-down ./cluster/down.sh