+ export WORKSPACE=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev + WORKSPACE=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev + [[ k8s-1.11.0-dev =~ openshift-.* ]] + [[ k8s-1.11.0-dev =~ .*-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:43 Waiting for host: 192.168.66.101:22 2018/08/03 20:50:46 Problem with dial: dial tcp 192.168.66.101:22: getsockopt: no route to host. Sleeping 5s 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:50:59 Connected to tcp://192.168.66.101:22 ++ systemctl status docker ++ wc -l ++ grep active + [[ 1 -eq 0 ]] + kubeadm init --config /etc/kubernetes/kubeadm.conf [init] using Kubernetes version: v1.11.0 [preflight] running pre-flight checks I0803 20:50:59.865750 1256 feature_gate.go:230] feature gates: &{map[]} I0803 20:50:59.940752 1256 kernel_validator.go:81] Validating kernel version I0803 20:50:59.942014 1256 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 55.007585 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:175b4335028b6b8d00f508ecf60013e2ad803e7364f5c31eab63498284ca677c + 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:13 Waiting for host: 192.168.66.102:22 2018/08/03 20:52:16 Problem with dial: dial tcp 192.168.66.102:22: getsockopt: no route to host. Sleeping 5s 2018/08/03 20:52:28 Connected to tcp://192.168.66.102:22 ++ wc -l ++ grep active ++ systemctl status docker + [[ 0 -eq 0 ]] + sleep 2 ++ 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 ip_vs_rr ip_vs_wrr ip_vs_sh] 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:32.192124 1264 kernel_validator.go:81] Validating kernel version I0803 20:52:32.192332 1264 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 5450 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 56s v1.11.0 node02 Ready 24s v1.11.0 + kubectl_rc=0 + '[' 0 -ne 0 ']' ++ kubectl get nodes --no-headers ++ cluster/kubectl.sh get nodes --no-headers ++ grep NotReady + '[' -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 57s v1.11.0 node02 Ready 25s v1.11.0 + make cluster-sync ./cluster/build.sh Building ... Untagged: localhost:33134/kubevirt/virt-controller:devel Untagged: localhost:33134/kubevirt/virt-controller@sha256:bbe064e8bd57227f2ccc26666bf593c87fb3f466dc324218b754475612181cef Deleted: sha256:b9e6a696b39d97bea792339cb9e36c203e7dec93296804e519bef90723113204 Deleted: sha256:9895842547f931387aef92cf1506006ade96745800473ed598a30e582e3f808a Deleted: sha256:2e13773a0cd79c854460da2cd4c64eb4fa56660bd4d34145ac137ddc7200ac55 Deleted: sha256:10b69961dee56774b969c4f82584d32a297bba56e3d7a14002ef56625287dbd6 Untagged: localhost:33134/kubevirt/virt-launcher:devel Untagged: localhost:33134/kubevirt/virt-launcher@sha256:ccfde6470ca8a72e6206233012df1bf8cd47451c15019f07d54452d0adaf4abd Deleted: sha256:6f458d4350a232415555d3517d03445b1cad635b8fe48ee11bb55b68a2367ad2 Deleted: sha256:9d20c7fbf846bd5b7de7dc19538c873f60b3213af33479a8e165032678e4b89e Deleted: sha256:8a182b35b2e896f1317f2959e825aef85b6729dd6ae860441f5eed63ab0a9f69 Deleted: sha256:6288d06697710558804f056b2887e6c0a28ece352c6ea5bad77f6df7807a0b7c Deleted: sha256:7dc5a428196a7dad77f449ea05c84d0e3d62bd7f27c54f3e2ed8b09d871601ad Deleted: sha256:4ce84c197bf401b00cbe7218c2ede5f4834d55ef52f4d38ea40103530e388607 Deleted: sha256:c749bf4ef1d071d12bd93fe2c5ca26200a7561d932ed49ec3e8e4fe867286246 Deleted: sha256:c078587f7b7ac47f6907716e54a5972a546fe5e081fe2a76a7315e72ee59cedf Deleted: sha256:aea1b3ffeae0c063652085145ac171d479055436efc0ca623ac27be1674f3c95 Deleted: sha256:48d53b7e0a5a95b778eb2edb0c976aaa63d899432a9a9456ce422ff4613543e4 Untagged: localhost:33134/kubevirt/virt-handler:devel Untagged: localhost:33134/kubevirt/virt-handler@sha256:456fa7604dbc06a3f6858a1cf076019b0609807c73bd0398807d028ee351e68a Deleted: sha256:d1c95588f96666e85bf1aa1c2a98f10bfde558e237b1597ac1798cb8b83d1c10 Deleted: sha256:71dcbce8b4503f78b42e745e169d6c9892b2a48caf65a096ce066deb0877121e Deleted: sha256:8704f5221ac693dc52353851fbabc66960b129f7f1ffce1ad2b9c0098eb3e485 Deleted: sha256:93dbe010ea630a6f6039a4755c8aeb93d6ec957946a09c7fc2a466ce6da95a48 Untagged: localhost:33134/kubevirt/virt-api:devel Untagged: localhost:33134/kubevirt/virt-api@sha256:eb3836f895a29e7fd0d0dabc893090fc1f3f5a67ad918dfeb81b65e29161a407 Deleted: sha256:05cefa9af4f7160e5ec10e799551ee4cf75637a6d1070ca2402b77ea36da15ec Deleted: sha256:0154f4eabe6d252db0255cca6fe96304e009542f875d3b503aaafc4033fff074 Deleted: sha256:e1d4fe3c88f01a55978e3fe6f288fb55f095d371d0e6a43290b55821a222499d Deleted: sha256:1079d10bc77d31be416c813e471c4d8427f7c7b0721c54ffb32ce1213d40e8ca Untagged: localhost:33134/kubevirt/subresource-access-test:devel Untagged: localhost:33134/kubevirt/subresource-access-test@sha256:771f55c8003563dc7ebe26f9403779e7f3e29a6a171f5f6608bc7e1186db1d48 Deleted: sha256:09ed228093ffefe7bf30a82791f361a4c73c0c4165878e36d0108129ac6cae9f Deleted: sha256:a0087cb332049cc51b8338ed4115a1d0a6e894cfa9ef360bf8674bc1c7794279 Deleted: sha256:d1d20086adc2c98ef016440704fb0fcfa1fde02d55057566432263b26901d56c Deleted: sha256:e21c42b7cea4aeca1f43811e55b20593acfdabe12fc73a68046b3543eb79bb08 Untagged: localhost:33134/kubevirt/example-hook-sidecar:devel Untagged: localhost:33134/kubevirt/example-hook-sidecar@sha256:04ab6d3004cb363a68fae29a1898b822b22638526177ec708d382f0e8f3836b7 Deleted: sha256:de554bb5ff8e6c6e655e0355ad9a5999f4363105da7a373e8e0b90f23f75b721 Deleted: sha256:0fe33257c4dfd54d13957d6e58b4facc63afb20e56051ef2804acf563d69b9d9 Deleted: sha256:00a29bdedf7434fe1dd2f52ccd5c385a446ade2ae4217fa6a0edcbb52c98d386 Deleted: sha256:c9ed170b987c291cf2a5379a8a556a64f2cdefed4621bd1e1c3e52f77cdf256c sha256:dcf2b21fa2ed11dcf9dbba21b1cca0ee3fad521a0e9aee61c06d0b0b66a4b200 go version go1.10 linux/amd64 go version go1.10 linux/amd64 make[1]: Entering directory `/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/go/src/kubevirt.io/kubevirt' hack/dockerized "./hack/check.sh && KUBEVIRT_VERSION= ./hack/build-go.sh install " && ./hack/build-copy-artifacts.sh sha256:dcf2b21fa2ed11dcf9dbba21b1cca0ee3fad521a0e9aee61c06d0b0b66a4b200 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 ---> bfe77d5699ed Step 3/8 : RUN useradd -u 1001 --create-home -s /bin/bash virt-controller ---> Using cache ---> b00c84523b53 Step 4/8 : WORKDIR /home/virt-controller ---> Using cache ---> b76b8bd8cd39 Step 5/8 : USER 1001 ---> Using cache ---> b6d9ad9ed232 Step 6/8 : COPY virt-controller /usr/bin/virt-controller ---> 5200bf704485 Removing intermediate container 9ab7431f1087 Step 7/8 : ENTRYPOINT /usr/bin/virt-controller ---> Running in fa395d942528 ---> 2247cc3d94c8 Removing intermediate container fa395d942528 Step 8/8 : LABEL "kubevirt-functional-tests-k8s-1.11.0-dev0" '' "virt-controller" '' ---> Running in 455b959bad64 ---> 4934f43c4eab Removing intermediate container 455b959bad64 Successfully built 4934f43c4eab 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 ---> 945996802736 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 ---> 672f9ab56316 Step 4/10 : COPY virt-launcher /usr/bin/virt-launcher ---> b4a6bafe7250 Removing intermediate container 5e461f34cdb4 Step 5/10 : COPY kubevirt-sudo /etc/sudoers.d/kubevirt ---> 7674bdd0cc0f Removing intermediate container b179b92d4451 Step 6/10 : RUN setcap CAP_NET_BIND_SERVICE=+eip /usr/bin/qemu-system-x86_64 ---> Running in d314fd3c6437  ---> 6ef8645dfd21 Removing intermediate container d314fd3c6437 Step 7/10 : RUN mkdir -p /usr/share/kubevirt/virt-launcher ---> Running in 6eddb305d206  ---> 5c3e64c57221 Removing intermediate container 6eddb305d206 Step 8/10 : COPY entrypoint.sh libvirtd.sh sock-connector /usr/share/kubevirt/virt-launcher/ ---> 67fa77bc6dec Removing intermediate container 1dcf42a1dc90 Step 9/10 : ENTRYPOINT /usr/share/kubevirt/virt-launcher/entrypoint.sh ---> Running in 12d93c4f061e ---> 793f21bce80c Removing intermediate container 12d93c4f061e Step 10/10 : LABEL "kubevirt-functional-tests-k8s-1.11.0-dev0" '' "virt-launcher" '' ---> Running in 83bf4f8ef847 ---> f16b21020f7f Removing intermediate container 83bf4f8ef847 Successfully built f16b21020f7f 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 ---> bfe77d5699ed Step 3/5 : COPY virt-handler /usr/bin/virt-handler ---> c1e368e6066a Removing intermediate container 8b4a868844e7 Step 4/5 : ENTRYPOINT /usr/bin/virt-handler ---> Running in 9c6b80f4923b ---> 820cf2e803de Removing intermediate container 9c6b80f4923b Step 5/5 : LABEL "kubevirt-functional-tests-k8s-1.11.0-dev0" '' "virt-handler" '' ---> Running in 0ffc8788daff ---> c20e78efbe7b Removing intermediate container 0ffc8788daff Successfully built c20e78efbe7b 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 ---> bfe77d5699ed Step 3/8 : RUN useradd -u 1001 --create-home -s /bin/bash virt-api ---> Using cache ---> ed1ebf600ee1 Step 4/8 : WORKDIR /home/virt-api ---> Using cache ---> 0769dad023e5 Step 5/8 : USER 1001 ---> Using cache ---> 0cb65afb0c2b Step 6/8 : COPY virt-api /usr/bin/virt-api ---> 492f4f182385 Removing intermediate container e653d87faa79 Step 7/8 : ENTRYPOINT /usr/bin/virt-api ---> Running in acda86023738 ---> 5e9d82d28268 Removing intermediate container acda86023738 Step 8/8 : LABEL "kubevirt-functional-tests-k8s-1.11.0-dev0" '' "virt-api" '' ---> Running in f42c92a6074e ---> 5f4ee01624ad Removing intermediate container f42c92a6074e Successfully built 5f4ee01624ad 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 ---> bfe77d5699ed Step 3/7 : ENV container docker ---> Using cache ---> 62847a2a1fa8 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 ---> 02134835a6aa Step 5/7 : ADD entrypoint.sh / ---> Using cache ---> ec0843818da7 Step 6/7 : CMD /entrypoint.sh ---> Using cache ---> 754029bb4bd2 Step 7/7 : LABEL "disks-images-provider" '' "kubevirt-functional-tests-k8s-1.11.0-dev0" '' ---> Using cache ---> ce29f424cc93 Successfully built ce29f424cc93 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 ---> bfe77d5699ed Step 3/5 : ENV container docker ---> Using cache ---> 62847a2a1fa8 Step 4/5 : RUN dnf -y install procps-ng nmap-ncat && dnf -y clean all ---> Using cache ---> 207487abe7b2 Step 5/5 : LABEL "kubevirt-functional-tests-k8s-1.11.0-dev0" '' "vm-killer" '' ---> Using cache ---> 08e9fdc44c13 Successfully built 08e9fdc44c13 Sending build context to Docker daemon 5.12 kB Step 1/7 : FROM debian:sid ---> 68f33cf86aab Step 2/7 : MAINTAINER "David Vossel" \ ---> Using cache ---> 5734d749eb5c Step 3/7 : ENV container docker ---> Using cache ---> f8775a77966f 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 ---> 1a40cf222a61 Step 5/7 : ADD entry-point.sh / ---> Using cache ---> 77b545d92fe7 Step 6/7 : CMD /entry-point.sh ---> Using cache ---> dfe20d463305 Step 7/7 : LABEL "kubevirt-functional-tests-k8s-1.11.0-dev0" '' "registry-disk-v1alpha" '' ---> Using cache ---> 8de7f4959dd4 Successfully built 8de7f4959dd4 Sending build context to Docker daemon 2.56 kB Step 1/4 : FROM localhost:33587/kubevirt/registry-disk-v1alpha:devel ---> 8de7f4959dd4 Step 2/4 : MAINTAINER "David Vossel" \ ---> Using cache ---> 49a3f493dc16 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 ---> 8e5011e93ffa Step 4/4 : LABEL "cirros-registry-disk-demo" '' "kubevirt-functional-tests-k8s-1.11.0-dev0" '' ---> Using cache ---> a1b0ec251983 Successfully built a1b0ec251983 Sending build context to Docker daemon 2.56 kB Step 1/4 : FROM localhost:33587/kubevirt/registry-disk-v1alpha:devel ---> 8de7f4959dd4 Step 2/4 : MAINTAINER "The KubeVirt Project" ---> Using cache ---> d22f57947ffb 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 ---> 5c1be4f0e759 Step 4/4 : LABEL "fedora-cloud-registry-disk-demo" '' "kubevirt-functional-tests-k8s-1.11.0-dev0" '' ---> Using cache ---> 0d3284ce9dbb Successfully built 0d3284ce9dbb Sending build context to Docker daemon 2.56 kB Step 1/4 : FROM localhost:33587/kubevirt/registry-disk-v1alpha:devel ---> 8de7f4959dd4 Step 2/4 : MAINTAINER "The KubeVirt Project" ---> Using cache ---> d22f57947ffb 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 ---> b3fefa2de4bc Step 4/4 : LABEL "alpine-registry-disk-demo" '' "kubevirt-functional-tests-k8s-1.11.0-dev0" '' ---> Using cache ---> 0c1cb3296027 Successfully built 0c1cb3296027 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 ---> bfe77d5699ed Step 3/8 : RUN useradd -u 1001 --create-home -s /bin/bash virtctl ---> Using cache ---> 985fe391c056 Step 4/8 : WORKDIR /home/virtctl ---> Using cache ---> 3b2cae8ac543 Step 5/8 : USER 1001 ---> Using cache ---> 0c06e5b4a900 Step 6/8 : COPY subresource-access-test /subresource-access-test ---> b8db0646f024 Removing intermediate container b08c04eac59d Step 7/8 : ENTRYPOINT /subresource-access-test ---> Running in b76b6e95a35b ---> d524c4957628 Removing intermediate container b76b6e95a35b Step 8/8 : LABEL "kubevirt-functional-tests-k8s-1.11.0-dev0" '' "subresource-access-test" '' ---> Running in a87bab9b8e0e ---> b11d573fa72b Removing intermediate container a87bab9b8e0e Successfully built b11d573fa72b 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 ---> bfe77d5699ed Step 3/9 : ENV container docker ---> Using cache ---> 62847a2a1fa8 Step 4/9 : RUN dnf -y install make git gcc && dnf -y clean all ---> Using cache ---> d3456b1644b1 Step 5/9 : ENV GIMME_GO_VERSION 1.9.2 ---> Using cache ---> 0ba81fddbba1 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 ---> 5d33abe3f819 Step 7/9 : ENV GOPATH "/go" GOBIN "/usr/bin" ---> Using cache ---> 783826523be1 Step 8/9 : RUN mkdir -p /go && source /etc/profile.d/gimme.sh && go get github.com/masterzen/winrm-cli ---> Using cache ---> 711bc8d15952 Step 9/9 : LABEL "kubevirt-functional-tests-k8s-1.11.0-dev0" '' "winrmcli" '' ---> Using cache ---> 7693f5193568 Successfully built 7693f5193568 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 ---> e3238544ad97 Step 3/5 : COPY example-hook-sidecar /example-hook-sidecar ---> 8ff50de665fa Removing intermediate container bddc14c8374b Step 4/5 : ENTRYPOINT /example-hook-sidecar ---> Running in 2d22126333c6 ---> 3e877e8e3efc Removing intermediate container 2d22126333c6 Step 5/5 : LABEL "example-hook-sidecar" '' "kubevirt-functional-tests-k8s-1.11.0-dev0" '' ---> Running in 37bce2f03ad4 ---> 6b164dca48b3 Removing intermediate container 37bce2f03ad4 Successfully built 6b164dca48b3 hack/build-docker.sh push The push refers to a repository [localhost:33587/kubevirt/virt-controller] 6a1377fa7d58: Preparing aa89340cf7a8: Preparing 891e1e4ef82a: Preparing aa89340cf7a8: Pushed 6a1377fa7d58: Pushed 891e1e4ef82a: Pushed devel: digest: sha256:d3105e636236fdd5db79a82316102680c8096d772664eed4f2932d591cebffb9 size: 949 The push refers to a repository [localhost:33587/kubevirt/virt-launcher] 5d42131cfa75: Preparing b944abd209df: Preparing c0cc9e036393: Preparing 926ccafbbd0b: Preparing 5766fa5e1828: Preparing 633427c64a24: Preparing da38cf808aa5: Preparing 633427c64a24: Waiting b83399358a92: Preparing da38cf808aa5: Waiting 186d8b3e4fd8: Preparing fa6154170bf5: Preparing 186d8b3e4fd8: Waiting 5eefb9960a36: Preparing 891e1e4ef82a: Preparing 5eefb9960a36: Waiting fa6154170bf5: Waiting b944abd209df: Pushed 5d42131cfa75: Pushed 926ccafbbd0b: Pushed da38cf808aa5: Pushed b83399358a92: Pushed 186d8b3e4fd8: Pushed fa6154170bf5: Pushed 891e1e4ef82a: Mounted from kubevirt/virt-controller c0cc9e036393: Pushed 633427c64a24: Pushed 5766fa5e1828: Pushed 5eefb9960a36: Pushed devel: digest: sha256:5a0a7562944848f24b3fecf7e96e11092a75bdeb6e545f0e50abec8aa711491b size: 2828 The push refers to a repository [localhost:33587/kubevirt/virt-handler] 72f5f339d668: Preparing 891e1e4ef82a: Preparing 891e1e4ef82a: Mounted from kubevirt/virt-launcher 72f5f339d668: Pushed devel: digest: sha256:fc76bb928b1efdd4e46defd7743c8fea363b36c1e4454a55ca98414347e2b72b size: 740 The push refers to a repository [localhost:33587/kubevirt/virt-api] 65cc3ca80f17: Preparing 82fc744c99b4: Preparing 891e1e4ef82a: Preparing 891e1e4ef82a: Mounted from kubevirt/virt-handler 82fc744c99b4: Pushed 65cc3ca80f17: Pushed devel: digest: sha256:77b2d8f7d6d4f4cce7c14097ad8324f6ee65b51d609fe76aceae6bcad247fd2a size: 948 The push refers to a repository [localhost:33587/kubevirt/disks-images-provider] 71ad31feb2c5: Preparing 21d4b721776e: Preparing 891e1e4ef82a: Preparing 891e1e4ef82a: Mounted from kubevirt/virt-api 71ad31feb2c5: Pushed 21d4b721776e: Pushed devel: digest: sha256:93a2d8fbd58f732bcc0ddfa782eb0ec8b66841da3432d4d076031b0cf0374893 size: 948 The push refers to a repository [localhost:33587/kubevirt/vm-killer] c4cfadeeaf5f: Preparing 891e1e4ef82a: Preparing 891e1e4ef82a: Mounted from kubevirt/disks-images-provider c4cfadeeaf5f: Pushed devel: digest: sha256:1c6e16fdf1220d75998f09c67409a225579ff3e3d90208aa38d8f824316c1437 size: 740 The push refers to a repository [localhost:33587/kubevirt/registry-disk-v1alpha] 661cce8d8e52: Preparing 41e0baba3077: Preparing 25edbec0eaea: Preparing 661cce8d8e52: Pushed 41e0baba3077: Pushed 25edbec0eaea: Pushed devel: digest: sha256:03a06bd0321a8a1693e5ef2e7fac4e99c8a868c8d67c89d00d29393fc49834cf size: 948 The push refers to a repository [localhost:33587/kubevirt/cirros-registry-disk-demo] ce69c857cc6c: Preparing 661cce8d8e52: Preparing 41e0baba3077: Preparing 25edbec0eaea: Preparing 25edbec0eaea: Mounted from kubevirt/registry-disk-v1alpha 661cce8d8e52: Mounted from kubevirt/registry-disk-v1alpha 41e0baba3077: Mounted from kubevirt/registry-disk-v1alpha ce69c857cc6c: Pushed devel: digest: sha256:eaac17e61b627a9d84311f369185deb054f9e728f308695d91d7bedc9e1dcb86 size: 1160 The push refers to a repository [localhost:33587/kubevirt/fedora-cloud-registry-disk-demo] ac5988afc68a: Preparing 661cce8d8e52: Preparing 41e0baba3077: Preparing 25edbec0eaea: Preparing 41e0baba3077: Mounted from kubevirt/cirros-registry-disk-demo 25edbec0eaea: Mounted from kubevirt/cirros-registry-disk-demo 661cce8d8e52: Mounted from kubevirt/cirros-registry-disk-demo ac5988afc68a: Pushed devel: digest: sha256:bcd44fd2ce40c282482794eee80e6b10c3ff2a8be2b4c36c26d12a732df91434 size: 1161 The push refers to a repository [localhost:33587/kubevirt/alpine-registry-disk-demo] 2670ecb7d9d9: Preparing 661cce8d8e52: Preparing 41e0baba3077: Preparing 25edbec0eaea: Preparing 661cce8d8e52: Mounted from kubevirt/fedora-cloud-registry-disk-demo 41e0baba3077: Mounted from kubevirt/fedora-cloud-registry-disk-demo 25edbec0eaea: Mounted from kubevirt/fedora-cloud-registry-disk-demo 2670ecb7d9d9: Pushed devel: digest: sha256:82f5ee9b5fd9f1095618f692bae697f204012415acada61cadd3465f2075818d size: 1160 The push refers to a repository [localhost:33587/kubevirt/subresource-access-test] 558e43b6c1b1: Preparing 25cb73590a9d: Preparing 891e1e4ef82a: Preparing 891e1e4ef82a: Mounted from kubevirt/vm-killer 25cb73590a9d: Pushed 558e43b6c1b1: Pushed devel: digest: sha256:c088d9d1c9f4aaf3a2c705c6d03b061d7be134577119130431d4c262467b9ec8 size: 948 The push refers to a repository [localhost:33587/kubevirt/winrmcli] f8083e002d0b: Preparing 53c709abc882: Preparing 9ca98a0f492b: Preparing 891e1e4ef82a: Preparing 891e1e4ef82a: Mounted from kubevirt/subresource-access-test f8083e002d0b: Pushed 9ca98a0f492b: Pushed 53c709abc882: Pushed devel: digest: sha256:b90cb25cae51d5b205fd12ac5d635365f53da75eed215e41c0e50e01d75c9bf1 size: 1165 The push refers to a repository [localhost:33587/kubevirt/example-hook-sidecar] 23a50bf7c861: Preparing 39bae602f753: Preparing 23a50bf7c861: Pushed 39bae602f753: Pushed devel: digest: sha256:57acc813ef44a6081c366044e5db765f8f1e393353ca83d94eacdc195bb96e69 size: 740 make[1]: Leaving directory `/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/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-dev/go/src/kubevirt.io/kubevirt ++ OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/go/src/kubevirt.io/kubevirt/_out ++ VENDOR_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/go/src/kubevirt.io/kubevirt/vendor ++ CMD_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/go/src/kubevirt.io/kubevirt/_out/cmd ++ TESTS_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/go/src/kubevirt.io/kubevirt/_out/tests ++ APIDOCS_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/go/src/kubevirt.io/kubevirt/_out/apidocs ++ MANIFESTS_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/go/src/kubevirt.io/kubevirt/_out/manifests ++ MANIFEST_TEMPLATES_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/go/src/kubevirt.io/kubevirt/_out/templates/manifests ++ PYTHON_CLIENT_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/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-dev ']' ++ provider_prefix=kubevirt-functional-tests-k8s-1.11.0-dev0 ++ job_prefix=kubevirt-functional-tests-k8s-1.11.0-dev0 +++ kubevirt_version +++ '[' -n '' ']' +++ '[' -d /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/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-dev/go/src/kubevirt.io/kubevirt/cluster/k8s-1.11.0/.kubeconfig +++ kubectl=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/go/src/kubevirt.io/kubevirt/cluster/k8s-1.11.0/.kubectl +++ docker_prefix=localhost:33587/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 ++ export KUBECONFIG=cluster/k8s-1.11.0/.kubeconfig ++ wc -l ++ 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-dev/go/src/kubevirt.io/kubevirt ++ OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/go/src/kubevirt.io/kubevirt/_out ++ VENDOR_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/go/src/kubevirt.io/kubevirt/vendor ++ CMD_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/go/src/kubevirt.io/kubevirt/_out/cmd ++ TESTS_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/go/src/kubevirt.io/kubevirt/_out/tests ++ APIDOCS_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/go/src/kubevirt.io/kubevirt/_out/apidocs ++ MANIFESTS_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/go/src/kubevirt.io/kubevirt/_out/manifests ++ MANIFEST_TEMPLATES_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/go/src/kubevirt.io/kubevirt/_out/templates/manifests ++ PYTHON_CLIENT_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/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-dev ']' ++ provider_prefix=kubevirt-functional-tests-k8s-1.11.0-dev0 ++ job_prefix=kubevirt-functional-tests-k8s-1.11.0-dev0 +++ kubevirt_version +++ '[' -n '' ']' +++ '[' -d /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/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-dev/go/src/kubevirt.io/kubevirt/cluster/k8s-1.11.0/.kubeconfig +++ kubectl=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/go/src/kubevirt.io/kubevirt/cluster/k8s-1.11.0/.kubectl +++ docker_prefix=localhost:33587/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-dev ]] + [[ k8s-1.11.0-dev =~ .*-dev ]] + _kubectl create -f /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/go/src/kubevirt.io/kubevirt/_out/manifests/dev -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-dev/go/src/kubevirt.io/kubevirt/_out/manifests/dev -R 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:admin created clusterrole.rbac.authorization.k8s.io/kubevirt.io:edit created clusterrole.rbac.authorization.k8s.io/kubevirt.io:view created clusterrole.rbac.authorization.k8s.io/kubevirt.io:default created clusterrolebinding.rbac.authorization.k8s.io/kubevirt.io:default created customresourcedefinition.apiextensions.k8s.io/virtualmachineinstancereplicasets.kubevirt.io created service/virt-api created deployment.extensions/virt-api created service/virt-controller created deployment.extensions/virt-controller created daemonset.extensions/virt-handler created customresourcedefinition.apiextensions.k8s.io/virtualmachines.kubevirt.io created customresourcedefinition.apiextensions.k8s.io/virtualmachineinstances.kubevirt.io created customresourcedefinition.apiextensions.k8s.io/virtualmachineinstancepresets.kubevirt.io created + _kubectl create -f /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/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-dev/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 ++ cluster/kubectl.sh get pods -n kube-system --no-headers ++ grep -v Running + '[' -n 'virt-api-7d79975b94-s6lqg 0/1 ContainerCreating 0 2s virt-controller-67dcdd8464-kxznq 0/1 ContainerCreating 0 2s virt-controller-67dcdd8464-v2gbh 0/1 ContainerCreating 0 2s virt-handler-9xv5q 0/1 ContainerCreating 0 2s virt-handler-xtdm2 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 + cluster/kubectl.sh get pods -n kube-system --no-headers + grep -v Running disks-images-provider-b84rx 0/1 Pending 0 2s virt-api-7d79975b94-s6lqg 0/1 ContainerCreating 0 5s virt-controller-67dcdd8464-kxznq 0/1 ContainerCreating 0 5s virt-controller-67dcdd8464-v2gbh 0/1 ContainerCreating 0 5s virt-handler-9xv5q 0/1 ContainerCreating 0 5s virt-handler-xtdm2 0/1 ContainerCreating 0 5s + 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 ++ cluster/kubectl.sh get pods -n kube-system '-ocustom-columns=status:status.containerStatuses[*].ready' --no-headers ++ grep false + '[' -n '' ']' + kubectl get pods -n kube-system + cluster/kubectl.sh get pods -n kube-system NAME READY STATUS RESTARTS AGE coredns-78fcdf6894-89czv 1/1 Running 0 14m coredns-78fcdf6894-whcz2 1/1 Running 0 14m disks-images-provider-b84rx 1/1 Running 0 35s disks-images-provider-llf6l 1/1 Running 0 33s etcd-node01 1/1 Running 0 14m kube-apiserver-node01 1/1 Running 0 14m kube-controller-manager-node01 1/1 Running 0 14m kube-flannel-ds-8dqgw 1/1 Running 0 14m kube-flannel-ds-zb94q 1/1 Running 0 14m kube-proxy-mwzq9 1/1 Running 0 14m kube-proxy-slnn7 1/1 Running 0 14m kube-scheduler-node01 1/1 Running 0 14m virt-api-7d79975b94-s6lqg 1/1 Running 0 38s virt-controller-67dcdd8464-kxznq 1/1 Running 0 38s virt-controller-67dcdd8464-v2gbh 1/1 Running 0 38s virt-handler-9xv5q 1/1 Running 0 38s virt-handler-xtdm2 1/1 Running 0 38s + for i in '${namespaces[@]}' + current_time=0 ++ kubectl get pods -n default --no-headers ++ grep -v Running ++ cluster/kubectl.sh get pods -n default --no-headers + '[' -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-54s2x 1/1 Running 0 14m local-volume-provisioner-l7tbk 1/1 Running 0 14m + 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-dev/junit.xml' + [[ k8s-1.11.0-dev =~ windows.* ]] + FUNC_TEST_ARGS='--ginkgo.noColor --junit-output=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.11.0-dev/junit.xml' + make functest hack/dockerized "hack/build-func-tests.sh" sha256:dcf2b21fa2ed11dcf9dbba21b1cca0ee3fad521a0e9aee61c06d0b0b66a4b200 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: 1533330457 Will run 148 of 148 specs S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds] Templates /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:42 Launching VMI from VM Template [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:60 with given Fedora Template /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:193 should succeed to generate a VM JSON file using oc-process command /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:150 Skip test that requires oc binary /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1381 ------------------------------ S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds] Templates /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:42 Launching VMI from VM Template [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:60 with given Fedora Template /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:193 with given VM JSON from the Template /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:152 should succeed to create a VM using oc-create command /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:156 Skip test that requires oc binary /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1381 ------------------------------ S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds] Templates /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:42 Launching VMI from VM Template [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:60 with given Fedora Template /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:193 with given VM JSON from the Template /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:152 with given VM from the VM JSON /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:158 should succeed to launch a VMI using oc-patch command /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:161 Skip test that requires oc binary /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1381 ------------------------------ S [SKIPPING] in Spec Setup (BeforeEach) [0.001 seconds] Templates /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:42 Launching VMI from VM Template [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:60 with given Fedora Template /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:193 with given VM JSON from the Template /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:152 with given VM from the VM JSON /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:158 with given VMI from the VM /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:163 should succeed to terminate the VMI using oc-patch command /root/go/src/kubevirt.io/kubevirt/tests/template_test.go:166 Skip test that requires oc binary /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1381 ------------------------------ •• Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T21:10:00.011853Z 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:00.131268Z 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:01 http: TLS handshake error from 10.244.1.1:51572: EOF level=info timestamp=2018-08-03T21:10:05.389854Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:10:08.275270Z 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:11 http: TLS handshake error from 10.244.1.1:51578: EOF level=info timestamp=2018-08-03T21:10:14.499263Z 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:16.467057Z 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:10:16.471105Z 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:10:21 http: TLS handshake error from 10.244.1.1:51584: EOF level=info timestamp=2018-08-03T21:10:30.092130Z 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:30.203899Z 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:31 http: TLS handshake error from 10.244.1.1:51590: EOF level=info timestamp=2018-08-03T21:10:35.320188Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:10:38.377157Z 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-kxznq Pod phase: Running level=info timestamp=2018-08-03T21:06:39.848803Z pos=vm.go:85 component=virt-controller service=http msg="Starting VirtualMachine controller." level=info timestamp=2018-08-03T21:06:39.849906Z pos=node.go:104 component=virt-controller service=http msg="Starting node controller." level=info timestamp=2018-08-03T21:06:39.850400Z pos=vmi.go:129 component=virt-controller service=http msg="Starting vmi controller." level=info timestamp=2018-08-03T21:06:39.877452Z pos=preset.go:74 component=virt-controller service=http msg="Starting Virtual Machine Initializer." level=info timestamp=2018-08-03T21:06:39.897559Z pos=replicaset.go:111 component=virt-controller service=http msg="Starting VirtualMachineInstanceReplicaSet controller." E0803 21:06:55.304829 1 leaderelection.go:258] Failed to update lock: Operation cannot be fulfilled on endpoints "virt-controller": the object has been modified; please apply your changes to the latest version and try again E0803 21:06:57.151008 1 leaderelection.go:258] Failed to update lock: Operation cannot be fulfilled on endpoints "virt-controller": the object has been modified; please apply your changes to the latest version and try again level=info timestamp=2018-08-03T21:07:39.076617Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiql5sk kind= uid=40431cc0-9761-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:07:39.076952Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiql5sk kind= uid=40431cc0-9761-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:07:40.234926Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiql5sk\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiql5sk" level=info timestamp=2018-08-03T21:07:40.666793Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiql5sk\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiql5sk" level=info timestamp=2018-08-03T21:07:41.070663Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmit4shs kind= uid=418c100e-9761-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:07:41.071044Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmit4shs kind= uid=418c100e-9761-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:07:41.191974Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmit4shs\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmit4shs" level=info timestamp=2018-08-03T21:07:41.296583Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmit4shs\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmit4shs" Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T21:06:39.458066Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-handler-9xv5q Pod phase: Running level=info timestamp=2018-08-03T21:06:42.488425Z pos=virt-handler.go:89 component=virt-handler hostname=node01 level=info timestamp=2018-08-03T21:06:42.496226Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:06:42.600892Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T21:06:42.603388Z pos=health.go:55 component=virt-handler 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-03T21:06:42.611165Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:08:30.518101Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.487344Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=info timestamp=2018-08-03T21:06:46.689902Z pos=virt-handler.go:89 component=virt-handler hostname=node02 level=info timestamp=2018-08-03T21:06:46.697502Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:06:47.398966Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T21:06:47.399684Z pos=health.go:55 component=virt-handler 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-03T21:06:47.403528Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:08:36.176996Z pos=health.go:55 component=virt-handler reason="tun device does not 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:40.948971Z pos=health.go:55 component=virt-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-testvmit4shs-fvnrk Pod phase: Pending ------------------------------ • Failure [182.759 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.008s. 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:07:41.257696Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmit4shs kind=VirtualMachineInstance uid=418c100e-9761-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvmit4shs-fvnrk" Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T21:13:00.573797Z 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:13:01 http: TLS handshake error from 10.244.1.1:51680: EOF level=info timestamp=2018-08-03T21:13:05.281909Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:13:08.878009Z 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:13:11 http: TLS handshake error from 10.244.1.1:51686: EOF level=info timestamp=2018-08-03T21:13:13.639556Z 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:13:13.643069Z 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:13:15.370904Z 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:13:21 http: TLS handshake error from 10.244.1.1:51692: EOF level=info timestamp=2018-08-03T21:13:30.572459Z 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:13:30.640213Z 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:13:31 http: TLS handshake error from 10.244.1.1:51698: EOF level=info timestamp=2018-08-03T21:13:35.347197Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:13:38.972814Z 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:13:41 http: TLS handshake error from 10.244.1.1:51704: EOF Pod name: virt-controller-67dcdd8464-kxznq Pod phase: Running level=info timestamp=2018-08-03T21:06:39.850400Z pos=vmi.go:129 component=virt-controller service=http msg="Starting vmi controller." level=info timestamp=2018-08-03T21:06:39.877452Z pos=preset.go:74 component=virt-controller service=http msg="Starting Virtual Machine Initializer." level=info timestamp=2018-08-03T21:06:39.897559Z pos=replicaset.go:111 component=virt-controller service=http msg="Starting VirtualMachineInstanceReplicaSet controller." E0803 21:06:55.304829 1 leaderelection.go:258] Failed to update lock: Operation cannot be fulfilled on endpoints "virt-controller": the object has been modified; please apply your changes to the latest version and try again E0803 21:06:57.151008 1 leaderelection.go:258] Failed to update lock: Operation cannot be fulfilled on endpoints "virt-controller": the object has been modified; please apply your changes to the latest version and try again level=info timestamp=2018-08-03T21:07:39.076617Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiql5sk kind= uid=40431cc0-9761-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:07:39.076952Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiql5sk kind= uid=40431cc0-9761-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:07:40.234926Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiql5sk\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiql5sk" level=info timestamp=2018-08-03T21:07:40.666793Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiql5sk\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiql5sk" level=info timestamp=2018-08-03T21:07:41.070663Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmit4shs kind= uid=418c100e-9761-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:07:41.071044Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmit4shs kind= uid=418c100e-9761-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:07:41.191974Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmit4shs\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmit4shs" level=info timestamp=2018-08-03T21:07:41.296583Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmit4shs\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmit4shs" level=info timestamp=2018-08-03T21:10:42.158730Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibtxxm kind= uid=ad7b5e63-9761-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:10:42.163778Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibtxxm kind= uid=ad7b5e63-9761-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T21:06:39.458066Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-handler-9xv5q Pod phase: Running level=info timestamp=2018-08-03T21:06:42.488425Z pos=virt-handler.go:89 component=virt-handler hostname=node01 level=info timestamp=2018-08-03T21:06:42.496226Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:06:42.600892Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T21:06:42.603388Z pos=health.go:55 component=virt-handler 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-03T21:06:42.611165Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:08:30.518101Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.487344Z pos=health.go:55 component=virt-handler reason="tun device does not 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:46.919422Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:11:53.968060Z pos=health.go:55 component=virt-handler reason="tun device does not 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:15.720478Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=info timestamp=2018-08-03T21:06:46.689902Z pos=virt-handler.go:89 component=virt-handler hostname=node02 level=info timestamp=2018-08-03T21:06:46.697502Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:06:47.398966Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T21:06:47.399684Z pos=health.go:55 component=virt-handler 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-03T21:06:47.403528Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:08:36.176996Z pos=health.go:55 component=virt-handler reason="tun device does not 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:40.948971Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.242103Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:11:59.285715Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.025655Z pos=health.go:55 component=virt-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-testvmibtxxm-2fqkv Pod phase: Pending • Failure [180.753 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.015s. 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:10:42.387528Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmibtxxm kind=VirtualMachineInstance uid=ad7b5e63-9761-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvmibtxxm-2fqkv" •••• Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running 2018/08/03 21:15:51 http: TLS handshake error from 10.244.1.1:51782: EOF level=info timestamp=2018-08-03T21:16:00.965302Z 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:01.035705Z 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:01 http: TLS handshake error from 10.244.1.1:51788: EOF level=info timestamp=2018-08-03T21:16:05.382978Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:16:09.472542Z 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:11 http: TLS handshake error from 10.244.1.1:51794: EOF level=info timestamp=2018-08-03T21:16:16.246618Z 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:21 http: TLS handshake error from 10.244.1.1:51800: EOF level=info timestamp=2018-08-03T21:16:31.035856Z 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:31.109313Z 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:31 http: TLS handshake error from 10.244.1.1:51806: EOF level=info timestamp=2018-08-03T21:16:35.280452Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:16:39.570380Z 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:41 http: TLS handshake error from 10.244.1.1:51812: EOF Pod name: virt-controller-67dcdd8464-kxznq Pod phase: Running level=info timestamp=2018-08-03T21:07:41.191974Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmit4shs\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmit4shs" level=info timestamp=2018-08-03T21:07:41.296583Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmit4shs\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmit4shs" level=info timestamp=2018-08-03T21:10:42.158730Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibtxxm kind= uid=ad7b5e63-9761-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:10:42.163778Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibtxxm kind= uid=ad7b5e63-9761-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:13:43.323382Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmishlhd kind= uid=1978afd4-9762-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:13:43.324154Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmishlhd kind= uid=1978afd4-9762-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:13:43.450862Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmishlhd\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmishlhd" level=info timestamp=2018-08-03T21:13:43.611095Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmishlhd\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmishlhd, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 1978afd4-9762-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmishlhd" level=info timestamp=2018-08-03T21:13:43.685441Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikkl42 kind= uid=19b2247f-9762-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:13:43.685798Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikkl42 kind= uid=19b2247f-9762-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:13:43.800730Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmikkl42\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmikkl42" level=info timestamp=2018-08-03T21:13:43.872984Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmikkl42\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmikkl42" level=info timestamp=2018-08-03T21:13:43.951444Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmikkl42\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmikkl42, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 19b2247f-9762-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmikkl42" level=info timestamp=2018-08-03T21:13:44.085773Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitbt4d kind= uid=19ed1e81-9762-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:13:44.086091Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitbt4d kind= uid=19ed1e81-9762-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T21:06:39.458066Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-handler-9xv5q Pod phase: Running level=info timestamp=2018-08-03T21:06:42.488425Z pos=virt-handler.go:89 component=virt-handler hostname=node01 level=info timestamp=2018-08-03T21:06:42.496226Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:06:42.600892Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T21:06:42.603388Z pos=health.go:55 component=virt-handler 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-03T21:06:42.611165Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:08:30.518101Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.487344Z pos=health.go:55 component=virt-handler reason="tun device does not 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:46.919422Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:11:53.968060Z pos=health.go:55 component=virt-handler reason="tun device does not 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:15.720478Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:14:52.916557Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=info timestamp=2018-08-03T21:06:46.689902Z pos=virt-handler.go:89 component=virt-handler hostname=node02 level=info timestamp=2018-08-03T21:06:46.697502Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:06:47.398966Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T21:06:47.399684Z pos=health.go:55 component=virt-handler 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-03T21:06:47.403528Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:08:36.176996Z pos=health.go:55 component=virt-handler reason="tun device does not 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:40.948971Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.242103Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:11:59.285715Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.025655Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:14:58.167829Z pos=health.go:55 component=virt-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-testvmitbt4d-59cxb Pod phase: Pending ------------------------------ • Failure [180.714 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.011s. 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:13:44.136303Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmitbt4d kind=VirtualMachineInstance uid=19ed1e81-9762-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvmitbt4d-59cxb" Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running 2018/08/03 21:18:51 http: TLS handshake error from 10.244.1.1:51890: EOF level=info timestamp=2018-08-03T21:19:01.634552Z 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:01.660243Z 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:01 http: TLS handshake error from 10.244.1.1:51896: EOF level=info timestamp=2018-08-03T21:19:05.401130Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:19:10.121232Z 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:11 http: TLS handshake error from 10.244.1.1:51902: EOF level=info timestamp=2018-08-03T21:19:17.101082Z 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:21 http: TLS handshake error from 10.244.1.1:51908: EOF level=info timestamp=2018-08-03T21:19:31.711823Z 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:31 http: TLS handshake error from 10.244.1.1:51914: EOF level=info timestamp=2018-08-03T21:19:31.764163Z 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:35.407670Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:19:40.209620Z 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:41 http: TLS handshake error from 10.244.1.1:51920: EOF Pod name: virt-controller-67dcdd8464-kxznq Pod phase: Running level=info timestamp=2018-08-03T21:10:42.163778Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibtxxm kind= uid=ad7b5e63-9761-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:13:43.323382Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmishlhd kind= uid=1978afd4-9762-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:13:43.324154Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmishlhd kind= uid=1978afd4-9762-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:13:43.450862Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmishlhd\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmishlhd" level=info timestamp=2018-08-03T21:13:43.611095Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmishlhd\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmishlhd, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 1978afd4-9762-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmishlhd" level=info timestamp=2018-08-03T21:13:43.685441Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikkl42 kind= uid=19b2247f-9762-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:13:43.685798Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikkl42 kind= uid=19b2247f-9762-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:13:43.800730Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmikkl42\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmikkl42" level=info timestamp=2018-08-03T21:13:43.872984Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmikkl42\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmikkl42" level=info timestamp=2018-08-03T21:13:43.951444Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmikkl42\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmikkl42, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 19b2247f-9762-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmikkl42" level=info timestamp=2018-08-03T21:13:44.085773Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitbt4d kind= uid=19ed1e81-9762-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:13:44.086091Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitbt4d kind= uid=19ed1e81-9762-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:16:44.604933Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitbt4d\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmitbt4d, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 19ed1e81-9762-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitbt4d" level=info timestamp=2018-08-03T21:16:44.810033Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizqzxg kind= uid=85a42fbe-9762-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:16:44.810637Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizqzxg kind= uid=85a42fbe-9762-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T21:06:39.458066Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-handler-9xv5q Pod phase: Running level=info timestamp=2018-08-03T21:06:42.488425Z pos=virt-handler.go:89 component=virt-handler hostname=node01 level=info timestamp=2018-08-03T21:06:42.496226Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:06:42.600892Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T21:06:42.603388Z pos=health.go:55 component=virt-handler 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-03T21:06:42.611165Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:08:30.518101Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.487344Z pos=health.go:55 component=virt-handler reason="tun device does not 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:46.919422Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:11:53.968060Z pos=health.go:55 component=virt-handler reason="tun device does not 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:15.720478Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:14:52.916557Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.577251Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.429223Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=info timestamp=2018-08-03T21:06:46.689902Z pos=virt-handler.go:89 component=virt-handler hostname=node02 level=info timestamp=2018-08-03T21:06:46.697502Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:06:47.398966Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T21:06:47.399684Z pos=health.go:55 component=virt-handler 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-03T21:06:47.403528Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:08:36.176996Z pos=health.go:55 component=virt-handler reason="tun device does not 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:40.948971Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.242103Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:11:59.285715Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.025655Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:14:58.167829Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.775683Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.585437Z pos=health.go:55 component=virt-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-testvmizqzxg-k8bwm Pod phase: Pending • Failure [180.711 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.013s. 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:16:44.903806Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmizqzxg kind=VirtualMachineInstance uid=85a42fbe-9762-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvmizqzxg-k8bwm" • [SLOW TEST:60.308 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.327 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(0xc420783320, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /root/go/src/kubevirt.io/kubevirt/tests/tests_suite_test.go:43 +0xaa testing.tRunner(0xc42063be00, 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:20:45.852592Z pos=utils.go:255 component=tests namespace=kubevirt-test-default name=testvmip5twp kind=VirtualMachineInstance uid=15428262-9763-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvmip5twp-xrp8z" Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running 2018/08/03 21:23:51 http: TLS handshake error from 10.244.1.1:52070: EOF 2018/08/03 21:24:01 http: TLS handshake error from 10.244.1.1:52076: EOF level=info timestamp=2018-08-03T21:24:02.442028Z 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:24:02.506955Z 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:24:05.399926Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:24:11.208426Z 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:24:11 http: TLS handshake error from 10.244.1.1:52082: EOF level=info timestamp=2018-08-03T21:24:18.661451Z 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:24:21 http: TLS handshake error from 10.244.1.1:52088: EOF 2018/08/03 21:24:31 http: TLS handshake error from 10.244.1.1:52094: EOF level=info timestamp=2018-08-03T21:24:32.503969Z 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:24:32.564166Z 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:24:35.397598Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:24:41.352075Z 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:24:41 http: TLS handshake error from 10.244.1.1:52100: EOF Pod name: virt-controller-67dcdd8464-kxznq Pod phase: Running level=info timestamp=2018-08-03T21:13:43.951444Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmikkl42\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmikkl42, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 19b2247f-9762-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmikkl42" level=info timestamp=2018-08-03T21:13:44.085773Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitbt4d kind= uid=19ed1e81-9762-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:13:44.086091Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitbt4d kind= uid=19ed1e81-9762-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:16:44.604933Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitbt4d\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmitbt4d, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 19ed1e81-9762-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitbt4d" level=info timestamp=2018-08-03T21:16:44.810033Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizqzxg kind= uid=85a42fbe-9762-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:16:44.810637Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizqzxg kind= uid=85a42fbe-9762-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:19:45.440994Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibz9f2 kind= uid=f14fa0fd-9762-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:19:45.441750Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibz9f2 kind= uid=f14fa0fd-9762-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:20:45.761073Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip5twp kind= uid=15428262-9763-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:20:45.762035Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip5twp kind= uid=15428262-9763-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:20:45.932132Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmip5twp\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmip5twp" level=info timestamp=2018-08-03T21:21:45.944938Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmip5twp\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmip5twp, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 15428262-9763-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmip5twp" level=info timestamp=2018-08-03T21:21:46.095653Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikt22c kind= uid=3938cea1-9763-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:46.096183Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikt22c kind= uid=3938cea1-9763-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:46.205159Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmikt22c\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmikt22c" Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T21:06:39.458066Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-handler-9xv5q Pod phase: Running level=info timestamp=2018-08-03T21:06:42.600892Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T21:06:42.603388Z pos=health.go:55 component=virt-handler 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-03T21:06:42.611165Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:08:30.518101Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.487344Z pos=health.go:55 component=virt-handler reason="tun device does not 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:46.919422Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:11:53.968060Z pos=health.go:55 component=virt-handler reason="tun device does not 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:15.720478Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:14:52.916557Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.577251Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.429223Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:19:45.881537Z pos=health.go:55 component=virt-handler reason="tun device does not 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:07.067417Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:22:56.032707Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:24:10.780355Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=info timestamp=2018-08-03T21:06:47.398966Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T21:06:47.399684Z pos=health.go:55 component=virt-handler 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-03T21:06:47.403528Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:08:36.176996Z pos=health.go:55 component=virt-handler reason="tun device does not 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:40.948971Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.242103Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:11:59.285715Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.025655Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:14:58.167829Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.775683Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.585437Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:19:51.002840Z pos=health.go:55 component=virt-handler reason="tun device does not 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:12.153006Z pos=health.go:55 component=virt-handler reason="tun device does not 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:01.106395Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:24:15.788163Z pos=health.go:55 component=virt-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-testvmikt22c-tww6p Pod phase: Pending • Failure [180.770 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.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 ------------------------------ level=info timestamp=2018-08-03T21:21:46.154128Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmikt22c kind=VirtualMachineInstance uid=3938cea1-9763-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvmikt22c-tww6p" Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T21:27:03.091093Z 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:03.094155Z 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:05.423183Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:27:11 http: TLS handshake error from 10.244.1.1:52190: EOF level=info timestamp=2018-08-03T21:27:11.826862Z 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:14.433981Z 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:27:14.437999Z 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:27:19.549734Z 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:27:21 http: TLS handshake error from 10.244.1.1:52196: EOF 2018/08/03 21:27:31 http: TLS handshake error from 10.244.1.1:52202: EOF level=info timestamp=2018-08-03T21:27:33.190113Z 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:33.258630Z 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:35.375996Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:27:41 http: TLS handshake error from 10.244.1.1:52208: EOF level=info timestamp=2018-08-03T21:27:41.926265Z 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-kxznq Pod phase: Running level=info timestamp=2018-08-03T21:13:44.086091Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitbt4d kind= uid=19ed1e81-9762-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:16:44.604933Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitbt4d\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmitbt4d, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 19ed1e81-9762-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitbt4d" level=info timestamp=2018-08-03T21:16:44.810033Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizqzxg kind= uid=85a42fbe-9762-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:16:44.810637Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizqzxg kind= uid=85a42fbe-9762-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:19:45.440994Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibz9f2 kind= uid=f14fa0fd-9762-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:19:45.441750Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibz9f2 kind= uid=f14fa0fd-9762-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:20:45.761073Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip5twp kind= uid=15428262-9763-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:20:45.762035Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip5twp kind= uid=15428262-9763-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:20:45.932132Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmip5twp\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmip5twp" level=info timestamp=2018-08-03T21:21:45.944938Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmip5twp\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmip5twp, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 15428262-9763-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmip5twp" level=info timestamp=2018-08-03T21:21:46.095653Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikt22c kind= uid=3938cea1-9763-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:46.096183Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikt22c kind= uid=3938cea1-9763-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:46.205159Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmikt22c\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmikt22c" level=info timestamp=2018-08-03T21:24:46.826759Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip52p6 kind= uid=a4f43d9b-9763-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:24:46.827567Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip52p6 kind= uid=a4f43d9b-9763-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T21:06:39.458066Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:06:42.603388Z pos=health.go:55 component=virt-handler 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-03T21:06:42.611165Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:08:30.518101Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.487344Z pos=health.go:55 component=virt-handler reason="tun device does not 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:46.919422Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:11:53.968060Z pos=health.go:55 component=virt-handler reason="tun device does not 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:15.720478Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:14:52.916557Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.577251Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.429223Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:19:45.881537Z pos=health.go:55 component=virt-handler reason="tun device does not 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:07.067417Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:22:56.032707Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:24:10.780355Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.943934Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:06:47.399684Z pos=health.go:55 component=virt-handler 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-03T21:06:47.403528Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:08:36.176996Z pos=health.go:55 component=virt-handler reason="tun device does not 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:40.948971Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.242103Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:11:59.285715Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.025655Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:14:58.167829Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.775683Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.585437Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:19:51.002840Z pos=health.go:55 component=virt-handler reason="tun device does not 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:12.153006Z pos=health.go:55 component=virt-handler reason="tun device does not 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:01.106395Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:24:15.788163Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.908174Z pos=health.go:55 component=virt-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-testvmip52p6-s8ctg Pod phase: Pending • Failure [180.808 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.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 ------------------------------ level=info timestamp=2018-08-03T21:24:46.853878Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmip52p6 kind=VirtualMachineInstance uid=a4f43d9b-9763-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvmip52p6-s8ctg" Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T21:27:03.091093Z 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:03.094155Z 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:05.423183Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:27:11 http: TLS handshake error from 10.244.1.1:52190: EOF level=info timestamp=2018-08-03T21:27:11.826862Z 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:14.433981Z 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:27:14.437999Z 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:27:19.549734Z 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:27:21 http: TLS handshake error from 10.244.1.1:52196: EOF 2018/08/03 21:27:31 http: TLS handshake error from 10.244.1.1:52202: EOF level=info timestamp=2018-08-03T21:27:33.190113Z 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:33.258630Z 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:35.375996Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:27:41 http: TLS handshake error from 10.244.1.1:52208: EOF level=info timestamp=2018-08-03T21:27:41.926265Z 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-kxznq Pod phase: Running level=info timestamp=2018-08-03T21:13:44.086091Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitbt4d kind= uid=19ed1e81-9762-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:16:44.604933Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmitbt4d\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmitbt4d, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 19ed1e81-9762-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmitbt4d" level=info timestamp=2018-08-03T21:16:44.810033Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizqzxg kind= uid=85a42fbe-9762-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:16:44.810637Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizqzxg kind= uid=85a42fbe-9762-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:19:45.440994Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibz9f2 kind= uid=f14fa0fd-9762-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:19:45.441750Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibz9f2 kind= uid=f14fa0fd-9762-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:20:45.761073Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip5twp kind= uid=15428262-9763-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:20:45.762035Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip5twp kind= uid=15428262-9763-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:20:45.932132Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmip5twp\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmip5twp" level=info timestamp=2018-08-03T21:21:45.944938Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmip5twp\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmip5twp, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 15428262-9763-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmip5twp" level=info timestamp=2018-08-03T21:21:46.095653Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikt22c kind= uid=3938cea1-9763-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:46.096183Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikt22c kind= uid=3938cea1-9763-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:46.205159Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmikt22c\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmikt22c" level=info timestamp=2018-08-03T21:24:46.826759Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip52p6 kind= uid=a4f43d9b-9763-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:24:46.827567Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip52p6 kind= uid=a4f43d9b-9763-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T21:06:39.458066Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:06:42.603388Z pos=health.go:55 component=virt-handler 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-03T21:06:42.611165Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:08:30.518101Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.487344Z pos=health.go:55 component=virt-handler reason="tun device does not 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:46.919422Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:11:53.968060Z pos=health.go:55 component=virt-handler reason="tun device does not 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:15.720478Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:14:52.916557Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.577251Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.429223Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:19:45.881537Z pos=health.go:55 component=virt-handler reason="tun device does not 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:07.067417Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:22:56.032707Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:24:10.780355Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.943934Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:06:47.399684Z pos=health.go:55 component=virt-handler 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-03T21:06:47.403528Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:08:36.176996Z pos=health.go:55 component=virt-handler reason="tun device does not 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:40.948971Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.242103Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:11:59.285715Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.025655Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:14:58.167829Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.775683Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.585437Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:19:51.002840Z pos=health.go:55 component=virt-handler reason="tun device does not 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:12.153006Z pos=health.go:55 component=virt-handler reason="tun device does not 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:01.106395Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:24:15.788163Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.908174Z pos=health.go:55 component=virt-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.455 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-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T21:30:03.638346Z 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:03.726349Z 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:05.479231Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:30:11 http: TLS handshake error from 10.244.1.1:52298: EOF level=info timestamp=2018-08-03T21:30:12.465290Z 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:14.454170Z 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:30:14.457678Z 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:30:20.433442Z 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:30:21 http: TLS handshake error from 10.244.1.1:52304: EOF 2018/08/03 21:30:31 http: TLS handshake error from 10.244.1.1:52310: EOF level=info timestamp=2018-08-03T21:30:33.726304Z 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:33.793194Z 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:35.303374Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:30:41 http: TLS handshake error from 10.244.1.1:52316: EOF level=info timestamp=2018-08-03T21:30:42.579557Z 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-kxznq Pod phase: Running level=info timestamp=2018-08-03T21:16:44.810033Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizqzxg kind= uid=85a42fbe-9762-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:16:44.810637Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmizqzxg kind= uid=85a42fbe-9762-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:19:45.440994Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibz9f2 kind= uid=f14fa0fd-9762-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:19:45.441750Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibz9f2 kind= uid=f14fa0fd-9762-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:20:45.761073Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip5twp kind= uid=15428262-9763-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:20:45.762035Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip5twp kind= uid=15428262-9763-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:20:45.932132Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmip5twp\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmip5twp" level=info timestamp=2018-08-03T21:21:45.944938Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmip5twp\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmip5twp, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 15428262-9763-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmip5twp" level=info timestamp=2018-08-03T21:21:46.095653Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikt22c kind= uid=3938cea1-9763-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:46.096183Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikt22c kind= uid=3938cea1-9763-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:46.205159Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmikt22c\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmikt22c" level=info timestamp=2018-08-03T21:24:46.826759Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip52p6 kind= uid=a4f43d9b-9763-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:24:46.827567Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip52p6 kind= uid=a4f43d9b-9763-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:27:47.994025Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8frzz kind= uid=10ee6c59-9764-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:27:47.994764Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8frzz kind= uid=10ee6c59-9764-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T21:06:39.458066Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:08:30.518101Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.487344Z pos=health.go:55 component=virt-handler reason="tun device does not 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:46.919422Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:11:53.968060Z pos=health.go:55 component=virt-handler reason="tun device does not 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:15.720478Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:14:52.916557Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.577251Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.429223Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:19:45.881537Z pos=health.go:55 component=virt-handler reason="tun device does not 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:07.067417Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:22:56.032707Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:24:10.780355Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.943934Z pos=health.go:55 component=virt-handler reason="tun device does not 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:54.151686Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:29:15.329663Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:08:36.176996Z pos=health.go:55 component=virt-handler reason="tun device does not 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:40.948971Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.242103Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:11:59.285715Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.025655Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:14:58.167829Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.775683Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.585437Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:19:51.002840Z pos=health.go:55 component=virt-handler reason="tun device does not 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:12.153006Z pos=health.go:55 component=virt-handler reason="tun device does not 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:01.106395Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:24:15.788163Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.908174Z pos=health.go:55 component=virt-handler reason="tun device does not 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:59.054670Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:29:20.199608Z pos=health.go:55 component=virt-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-testvmi8frzz-qxx7m Pod phase: Pending • Failure in Spec Setup (BeforeEach) [180.516 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.011s. 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:27:48.077341Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi8frzz kind=VirtualMachineInstance uid=10ee6c59-9764-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi8frzz-qxx7m" Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T21:33:04.131863Z 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:04.193725Z 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:05.383182Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:33:11 http: TLS handshake error from 10.244.1.1:52406: EOF level=info timestamp=2018-08-03T21:33:13.065598Z 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:13.287292Z 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:33:13.290838Z 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:33:21.382302Z 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:33:21 http: TLS handshake error from 10.244.1.1:52412: EOF 2018/08/03 21:33:31 http: TLS handshake error from 10.244.1.1:52418: EOF level=info timestamp=2018-08-03T21:33:34.210591Z 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:34.300247Z 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:35.431232Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:33:41 http: TLS handshake error from 10.244.1.1:52424: EOF level=info timestamp=2018-08-03T21:33:43.105424Z 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-kxznq Pod phase: Running level=info timestamp=2018-08-03T21:20:45.761073Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip5twp kind= uid=15428262-9763-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:20:45.762035Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip5twp kind= uid=15428262-9763-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:20:45.932132Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmip5twp\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmip5twp" level=info timestamp=2018-08-03T21:21:45.944938Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmip5twp\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmip5twp, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 15428262-9763-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmip5twp" level=info timestamp=2018-08-03T21:21:46.095653Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikt22c kind= uid=3938cea1-9763-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:46.096183Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikt22c kind= uid=3938cea1-9763-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:46.205159Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmikt22c\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmikt22c" level=info timestamp=2018-08-03T21:24:46.826759Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip52p6 kind= uid=a4f43d9b-9763-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:24:46.827567Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip52p6 kind= uid=a4f43d9b-9763-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:27:47.994025Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8frzz kind= uid=10ee6c59-9764-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:27:47.994764Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8frzz kind= uid=10ee6c59-9764-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:30:48.512092Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8frzz\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi8frzz, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 10ee6c59-9764-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8frzz" level=info timestamp=2018-08-03T21:30:48.748833Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilptbx kind= uid=7caa5a5f-9764-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:30:48.749592Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilptbx kind= uid=7caa5a5f-9764-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:30:48.970447Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmilptbx\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmilptbx" Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T21:06:39.458066Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:10:46.919422Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:11:53.968060Z pos=health.go:55 component=virt-handler reason="tun device does not 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:15.720478Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:14:52.916557Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.577251Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.429223Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:19:45.881537Z pos=health.go:55 component=virt-handler reason="tun device does not 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:07.067417Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:22:56.032707Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:24:10.780355Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.943934Z pos=health.go:55 component=virt-handler reason="tun device does not 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:54.151686Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:29:15.329663Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:31:09.625983Z pos=health.go:55 component=virt-handler reason="tun device does not 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:12.036240Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:10:52.242103Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:11:59.285715Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.025655Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:14:58.167829Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.775683Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.585437Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:19:51.002840Z pos=health.go:55 component=virt-handler reason="tun device does not 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:12.153006Z pos=health.go:55 component=virt-handler reason="tun device does not 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:01.106395Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:24:15.788163Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.908174Z pos=health.go:55 component=virt-handler reason="tun device does not 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:59.054670Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:29:20.199608Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:31:14.461365Z pos=health.go:55 component=virt-handler reason="tun device does not 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:16.832698Z pos=health.go:55 component=virt-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-testvmilptbx-zhwp5 Pod phase: Pending • Failure [180.784 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.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 ------------------------------ level=info timestamp=2018-08-03T21:30:48.909635Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmilptbx kind=VirtualMachineInstance uid=7caa5a5f-9764-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvmilptbx-zhwp5" • Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T21:35:52.196870Z 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:36:01 http: TLS handshake error from 10.244.1.1:52508: EOF level=info timestamp=2018-08-03T21:36:04.620078Z 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:04.668348Z 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:05.395254Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:36:11 http: TLS handshake error from 10.244.1.1:52514: EOF level=info timestamp=2018-08-03T21:36:13.676963Z 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:36:21 http: TLS handshake error from 10.244.1.1:52520: EOF level=info timestamp=2018-08-03T21:36:22.371219Z 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:36:31 http: TLS handshake error from 10.244.1.1:52526: EOF level=info timestamp=2018-08-03T21:36:34.703088Z 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:34.773107Z 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:35.422393Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:36:41 http: TLS handshake error from 10.244.1.1:52532: EOF level=info timestamp=2018-08-03T21:36:43.808715Z 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-kxznq Pod phase: Running level=info timestamp=2018-08-03T21:24:46.827567Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmip52p6 kind= uid=a4f43d9b-9763-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:27:47.994025Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8frzz kind= uid=10ee6c59-9764-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:27:47.994764Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8frzz kind= uid=10ee6c59-9764-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:30:48.512092Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8frzz\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi8frzz, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 10ee6c59-9764-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8frzz" level=info timestamp=2018-08-03T21:30:48.748833Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilptbx kind= uid=7caa5a5f-9764-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:30:48.749592Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilptbx kind= uid=7caa5a5f-9764-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:30:48.970447Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmilptbx\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmilptbx" level=info timestamp=2018-08-03T21:33:49.524252Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmilptbx\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmilptbx, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 7caa5a5f-9764-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmilptbx" level=info timestamp=2018-08-03T21:33:49.701102Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihq2f6 kind= uid=e87fddae-9764-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:33:49.702624Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihq2f6 kind= uid=e87fddae-9764-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:33:49.886855Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmihq2f6\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmihq2f6" level=info timestamp=2018-08-03T21:33:51.155354Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisvh5c kind= uid=e96718f1-9764-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:33:51.155766Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisvh5c kind= uid=e96718f1-9764-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:33:51.220902Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmisvh5c\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmisvh5c" level=info timestamp=2018-08-03T21:33:51.275545Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmisvh5c\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmisvh5c" Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T21:06:39.458066Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:13:15.720478Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:14:52.916557Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.577251Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.429223Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:19:45.881537Z pos=health.go:55 component=virt-handler reason="tun device does not 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:07.067417Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:22:56.032707Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:24:10.780355Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.943934Z pos=health.go:55 component=virt-handler reason="tun device does not 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:54.151686Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:29:15.329663Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:31:09.625983Z pos=health.go:55 component=virt-handler reason="tun device does not 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:12.036240Z pos=health.go:55 component=virt-handler reason="tun device does not 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:02.282029Z pos=health.go:55 component=virt-handler reason="tun device does not 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:04.387281Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:13:21.025655Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:14:58.167829Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.775683Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.585437Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:19:51.002840Z pos=health.go:55 component=virt-handler reason="tun device does not 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:12.153006Z pos=health.go:55 component=virt-handler reason="tun device does not 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:01.106395Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:24:15.788163Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.908174Z pos=health.go:55 component=virt-handler reason="tun device does not 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:59.054670Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:29:20.199608Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:31:14.461365Z pos=health.go:55 component=virt-handler reason="tun device does not 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:16.832698Z pos=health.go:55 component=virt-handler reason="tun device does not 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.027120Z pos=health.go:55 component=virt-handler reason="tun device does not 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:09.107155Z pos=health.go:55 component=virt-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-testvmisvh5c-9bplc Pod phase: Pending ------------------------------ • Failure [180.766 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.010s. 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:33:51.170229Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmisvh5c kind=VirtualMachineInstance uid=e96718f1-9764-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvmisvh5c-9bplc" Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running 2018/08/03 21:39:01 http: TLS handshake error from 10.244.1.1:52616: EOF level=info timestamp=2018-08-03T21:39:05.120785Z 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:05.164932Z 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:05.374824Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:39:11 http: TLS handshake error from 10.244.1.1:52622: EOF level=info timestamp=2018-08-03T21:39:14.334640Z 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:39:21 http: TLS handshake error from 10.244.1.1:52628: EOF level=info timestamp=2018-08-03T21:39:23.225860Z 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:39:31 http: TLS handshake error from 10.244.1.1:52634: EOF level=info timestamp=2018-08-03T21:39:35.207204Z 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:35.279348Z 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:35.345951Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:39:41 http: TLS handshake error from 10.244.1.1:52640: EOF level=info timestamp=2018-08-03T21:39:44.444924Z 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:39:51 http: TLS handshake error from 10.244.1.1:52646: EOF Pod name: virt-controller-67dcdd8464-kxznq Pod phase: Running level=info timestamp=2018-08-03T21:30:48.748833Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilptbx kind= uid=7caa5a5f-9764-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:30:48.749592Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilptbx kind= uid=7caa5a5f-9764-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:30:48.970447Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmilptbx\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmilptbx" level=info timestamp=2018-08-03T21:33:49.524252Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmilptbx\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmilptbx, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 7caa5a5f-9764-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmilptbx" level=info timestamp=2018-08-03T21:33:49.701102Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihq2f6 kind= uid=e87fddae-9764-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:33:49.702624Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihq2f6 kind= uid=e87fddae-9764-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:33:49.886855Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmihq2f6\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmihq2f6" level=info timestamp=2018-08-03T21:33:51.155354Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisvh5c kind= uid=e96718f1-9764-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:33:51.155766Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisvh5c kind= uid=e96718f1-9764-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:33:51.220902Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmisvh5c\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmisvh5c" level=info timestamp=2018-08-03T21:33:51.275545Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmisvh5c\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmisvh5c" level=info timestamp=2018-08-03T21:36:51.866595Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-alternative name=testvmi742ks kind= uid=551c7605-9765-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:36:51.867328Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-alternative name=testvmi742ks kind= uid=551c7605-9765-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:36:51.985264Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi742ks\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-alternative/testvmi742ks" level=info timestamp=2018-08-03T21:36:52.011870Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi742ks\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-alternative/testvmi742ks" Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T21:06:39.458066Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:14:52.916557Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.577251Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.429223Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:19:45.881537Z pos=health.go:55 component=virt-handler reason="tun device does not 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:07.067417Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:22:56.032707Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:24:10.780355Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.943934Z pos=health.go:55 component=virt-handler reason="tun device does not 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:54.151686Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:29:15.329663Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:31:09.625983Z pos=health.go:55 component=virt-handler reason="tun device does not 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:12.036240Z pos=health.go:55 component=virt-handler reason="tun device does not 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:02.282029Z pos=health.go:55 component=virt-handler reason="tun device does not 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:04.387281Z pos=health.go:55 component=virt-handler reason="tun device does not 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:48.233860Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:14:58.167829Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.775683Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.585437Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:19:51.002840Z pos=health.go:55 component=virt-handler reason="tun device does not 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:12.153006Z pos=health.go:55 component=virt-handler reason="tun device does not 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:01.106395Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:24:15.788163Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.908174Z pos=health.go:55 component=virt-handler reason="tun device does not 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:59.054670Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:29:20.199608Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:31:14.461365Z pos=health.go:55 component=virt-handler reason="tun device does not 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:16.832698Z pos=health.go:55 component=virt-handler reason="tun device does not 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.027120Z pos=health.go:55 component=virt-handler reason="tun device does not 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:09.107155Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.856290Z pos=health.go:55 component=virt-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.633 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.011s. 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:36:51.879074Z pos=utils.go:244 component=tests namespace=kubevirt-test-alternative name=testvmi742ks kind=VirtualMachineInstance uid=551c7605-9765-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi742ks-f7kcs" S [SKIPPING] in Spec Setup (BeforeEach) [0.323 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.092 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-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T21:42:05.954155Z 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:05.977998Z 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:42:11 http: TLS handshake error from 10.244.1.1:52730: EOF level=info timestamp=2018-08-03T21:42:13.926695Z 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:42:13.931389Z 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:42:14.897332Z 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:42:21 http: TLS handshake error from 10.244.1.1:52736: EOF level=info timestamp=2018-08-03T21:42:24.246109Z 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:42:31 http: TLS handshake error from 10.244.1.1:52742: EOF level=info timestamp=2018-08-03T21:42:35.381436Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:42:36.007599Z 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:36.100842Z 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:42:41 http: TLS handshake error from 10.244.1.1:52748: EOF level=info timestamp=2018-08-03T21:42:45.013016Z 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:42:51 http: TLS handshake error from 10.244.1.1:52754: EOF Pod name: virt-controller-67dcdd8464-kxznq Pod phase: Running level=info timestamp=2018-08-03T21:33:49.886855Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmihq2f6\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmihq2f6" level=info timestamp=2018-08-03T21:33:51.155354Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisvh5c kind= uid=e96718f1-9764-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:33:51.155766Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisvh5c kind= uid=e96718f1-9764-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:33:51.220902Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmisvh5c\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmisvh5c" level=info timestamp=2018-08-03T21:33:51.275545Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmisvh5c\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmisvh5c" level=info timestamp=2018-08-03T21:36:51.866595Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-alternative name=testvmi742ks kind= uid=551c7605-9765-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:36:51.867328Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-alternative name=testvmi742ks kind= uid=551c7605-9765-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:36:51.985264Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi742ks\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-alternative/testvmi742ks" level=info timestamp=2018-08-03T21:36:52.011870Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi742ks\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-alternative/testvmi742ks" level=info timestamp=2018-08-03T21:39:52.706385Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigbrcj kind= uid=c0e6a230-9765-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:39:52.707210Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigbrcj kind= uid=c0e6a230-9765-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:39:52.784929Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmigbrcj\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmigbrcj" level=info timestamp=2018-08-03T21:39:53.688273Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi98kdw kind= uid=c17cf36a-9765-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:39:53.688699Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi98kdw kind= uid=c17cf36a-9765-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:39:53.762940Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi98kdw\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi98kdw" Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T21:06:39.458066Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:19:45.881537Z pos=health.go:55 component=virt-handler reason="tun device does not 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:07.067417Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:22:56.032707Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:24:10.780355Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.943934Z pos=health.go:55 component=virt-handler reason="tun device does not 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:54.151686Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:29:15.329663Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:31:09.625983Z pos=health.go:55 component=virt-handler reason="tun device does not 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:12.036240Z pos=health.go:55 component=virt-handler reason="tun device does not 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:02.282029Z pos=health.go:55 component=virt-handler reason="tun device does not 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:04.387281Z pos=health.go:55 component=virt-handler reason="tun device does not 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:48.233860Z pos=health.go:55 component=virt-handler reason="tun device does not 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:58.519304Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:41:04.337514Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.274442Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:19:51.002840Z pos=health.go:55 component=virt-handler reason="tun device does not 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:12.153006Z pos=health.go:55 component=virt-handler reason="tun device does not 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:01.106395Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:24:15.788163Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.908174Z pos=health.go:55 component=virt-handler reason="tun device does not 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:59.054670Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:29:20.199608Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:31:14.461365Z pos=health.go:55 component=virt-handler reason="tun device does not 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:16.832698Z pos=health.go:55 component=virt-handler reason="tun device does not 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.027120Z pos=health.go:55 component=virt-handler reason="tun device does not 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:09.107155Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.856290Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.106298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:41:08.868075Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.724155Z pos=health.go:55 component=virt-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-testvmi98kdw-bfk27 Pod phase: Pending ------------------------------ • Failure [180.493 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.011s. 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:39:53.671955Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi98kdw kind=VirtualMachineInstance uid=c17cf36a-9765-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi98kdw-bfk27" Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T21:45:06.375824Z 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:06.537174Z 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:45:11 http: TLS handshake error from 10.244.1.1:52838: EOF level=info timestamp=2018-08-03T21:45:13.947814Z 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:45:13.953553Z 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:45:15.506702Z 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:45:21 http: TLS handshake error from 10.244.1.1:52844: EOF level=info timestamp=2018-08-03T21:45:25.092616Z 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:45:31 http: TLS handshake error from 10.244.1.1:52850: EOF level=info timestamp=2018-08-03T21:45:35.361806Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:45:36.513182Z 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:36.645608Z 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:45:41 http: TLS handshake error from 10.244.1.1:52856: EOF level=info timestamp=2018-08-03T21:45:45.603148Z 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:45:51 http: TLS handshake error from 10.244.1.1:52862: EOF Pod name: virt-controller-67dcdd8464-kxznq Pod phase: Running level=info timestamp=2018-08-03T21:33:51.275545Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmisvh5c\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmisvh5c" level=info timestamp=2018-08-03T21:36:51.866595Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-alternative name=testvmi742ks kind= uid=551c7605-9765-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:36:51.867328Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-alternative name=testvmi742ks kind= uid=551c7605-9765-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:36:51.985264Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi742ks\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-alternative/testvmi742ks" level=info timestamp=2018-08-03T21:36:52.011870Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi742ks\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-alternative/testvmi742ks" level=info timestamp=2018-08-03T21:39:52.706385Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigbrcj kind= uid=c0e6a230-9765-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:39:52.707210Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigbrcj kind= uid=c0e6a230-9765-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:39:52.784929Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmigbrcj\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmigbrcj" level=info timestamp=2018-08-03T21:39:53.688273Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi98kdw kind= uid=c17cf36a-9765-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:39:53.688699Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi98kdw kind= uid=c17cf36a-9765-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:39:53.762940Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi98kdw\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi98kdw" level=info timestamp=2018-08-03T21:42:54.361766Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi2vnnk kind= uid=2d2cdd4f-9766-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:42:54.362429Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi2vnnk kind= uid=2d2cdd4f-9766-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:42:54.459020Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi2vnnk\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi2vnnk" level=info timestamp=2018-08-03T21:42:54.481128Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi2vnnk\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi2vnnk" Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T21:06:39.458066Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:22:56.032707Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:24:10.780355Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.943934Z pos=health.go:55 component=virt-handler reason="tun device does not 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:54.151686Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:29:15.329663Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:31:09.625983Z pos=health.go:55 component=virt-handler reason="tun device does not 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:12.036240Z pos=health.go:55 component=virt-handler reason="tun device does not 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:02.282029Z pos=health.go:55 component=virt-handler reason="tun device does not 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:04.387281Z pos=health.go:55 component=virt-handler reason="tun device does not 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:48.233860Z pos=health.go:55 component=virt-handler reason="tun device does not 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:58.519304Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:41:04.337514Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.274442Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:44:09.051278Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.609873Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:23:01.106395Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:24:15.788163Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.908174Z pos=health.go:55 component=virt-handler reason="tun device does not 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:59.054670Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:29:20.199608Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:31:14.461365Z pos=health.go:55 component=virt-handler reason="tun device does not 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:16.832698Z pos=health.go:55 component=virt-handler reason="tun device does not 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.027120Z pos=health.go:55 component=virt-handler reason="tun device does not 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:09.107155Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.856290Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.106298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:41:08.868075Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.724155Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:44:13.484191Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.991255Z pos=health.go:55 component=virt-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-testvmi2vnnk-g4zlm Pod phase: Pending • Failure [180.634 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.061s. 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:42:54.364326Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi2vnnk kind=VirtualMachineInstance uid=2d2cdd4f-9766-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi2vnnk-g4zlm" Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T21:48:06.908605Z 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:07.005896Z 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:48:11 http: TLS handshake error from 10.244.1.1:52946: EOF level=info timestamp=2018-08-03T21:48:13.189610Z 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:48:13.194581Z 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:48:16.106455Z 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:48:21 http: TLS handshake error from 10.244.1.1:52952: EOF level=info timestamp=2018-08-03T21:48:26.018294Z 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:48:31 http: TLS handshake error from 10.244.1.1:52958: EOF level=info timestamp=2018-08-03T21:48:35.423087Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:48:36.978084Z 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:37.076325Z 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:48:41 http: TLS handshake error from 10.244.1.1:52964: EOF level=info timestamp=2018-08-03T21:48:46.205715Z 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:48:51 http: TLS handshake error from 10.244.1.1:52970: EOF Pod name: virt-controller-67dcdd8464-kxznq Pod phase: Running level=info timestamp=2018-08-03T21:36:51.985264Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi742ks\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-alternative/testvmi742ks" level=info timestamp=2018-08-03T21:36:52.011870Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi742ks\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-alternative/testvmi742ks" level=info timestamp=2018-08-03T21:39:52.706385Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigbrcj kind= uid=c0e6a230-9765-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:39:52.707210Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigbrcj kind= uid=c0e6a230-9765-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:39:52.784929Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmigbrcj\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmigbrcj" level=info timestamp=2018-08-03T21:39:53.688273Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi98kdw kind= uid=c17cf36a-9765-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:39:53.688699Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi98kdw kind= uid=c17cf36a-9765-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:39:53.762940Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi98kdw\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi98kdw" level=info timestamp=2018-08-03T21:42:54.361766Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi2vnnk kind= uid=2d2cdd4f-9766-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:42:54.362429Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi2vnnk kind= uid=2d2cdd4f-9766-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:42:54.459020Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi2vnnk\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi2vnnk" level=info timestamp=2018-08-03T21:42:54.481128Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi2vnnk\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi2vnnk" level=info timestamp=2018-08-03T21:45:55.021108Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvminv6lj kind= uid=98d89edc-9766-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:45:55.021865Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvminv6lj kind= uid=98d89edc-9766-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:45:55.146913Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvminv6lj\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvminv6lj" Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T21:06:39.458066Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:25:51.943934Z pos=health.go:55 component=virt-handler reason="tun device does not 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:54.151686Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:29:15.329663Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:31:09.625983Z pos=health.go:55 component=virt-handler reason="tun device does not 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:12.036240Z pos=health.go:55 component=virt-handler reason="tun device does not 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:02.282029Z pos=health.go:55 component=virt-handler reason="tun device does not 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:04.387281Z pos=health.go:55 component=virt-handler reason="tun device does not 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:48.233860Z pos=health.go:55 component=virt-handler reason="tun device does not 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:58.519304Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:41:04.337514Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.274442Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:44:09.051278Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.609873Z pos=health.go:55 component=virt-handler reason="tun device does not 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:00.664914Z pos=health.go:55 component=virt-handler reason="tun device does not 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:20.797999Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:25:56.908174Z pos=health.go:55 component=virt-handler reason="tun device does not 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:59.054670Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:29:20.199608Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:31:14.461365Z pos=health.go:55 component=virt-handler reason="tun device does not 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:16.832698Z pos=health.go:55 component=virt-handler reason="tun device does not 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.027120Z pos=health.go:55 component=virt-handler reason="tun device does not 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:09.107155Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.856290Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.106298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:41:08.868075Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.724155Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:44:13.484191Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.991255Z pos=health.go:55 component=virt-handler reason="tun device does not 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:04.980101Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.097581Z pos=health.go:55 component=virt-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-testvminv6lj-9g4t4 Pod phase: Pending • Failure [180.699 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.011s. 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:45:55.030745Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvminv6lj kind=VirtualMachineInstance uid=98d89edc-9766-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvminv6lj-9g4t4" Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running 2018/08/03 21:51:01 http: TLS handshake error from 10.244.1.1:53048: EOF level=info timestamp=2018-08-03T21:51:05.454366Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:51:07.377533Z 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:07.484119Z 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:51:11 http: TLS handshake error from 10.244.1.1:53054: EOF level=info timestamp=2018-08-03T21:51:16.782130Z 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:51:21 http: TLS handshake error from 10.244.1.1:53060: EOF level=info timestamp=2018-08-03T21:51:27.027118Z 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:51:31 http: TLS handshake error from 10.244.1.1:53066: EOF level=info timestamp=2018-08-03T21:51:35.471101Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:51:37.492622Z 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:37.571229Z 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:51:41 http: TLS handshake error from 10.244.1.1:53072: EOF level=info timestamp=2018-08-03T21:51:46.882977Z 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:51:51 http: TLS handshake error from 10.244.1.1:53078: EOF Pod name: virt-controller-67dcdd8464-kxznq Pod phase: Running level=info timestamp=2018-08-03T21:39:52.707210Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigbrcj kind= uid=c0e6a230-9765-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:39:52.784929Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmigbrcj\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmigbrcj" level=info timestamp=2018-08-03T21:39:53.688273Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi98kdw kind= uid=c17cf36a-9765-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:39:53.688699Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi98kdw kind= uid=c17cf36a-9765-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:39:53.762940Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi98kdw\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi98kdw" level=info timestamp=2018-08-03T21:42:54.361766Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi2vnnk kind= uid=2d2cdd4f-9766-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:42:54.362429Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi2vnnk kind= uid=2d2cdd4f-9766-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:42:54.459020Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi2vnnk\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi2vnnk" level=info timestamp=2018-08-03T21:42:54.481128Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi2vnnk\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi2vnnk" level=info timestamp=2018-08-03T21:45:55.021108Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvminv6lj kind= uid=98d89edc-9766-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:45:55.021865Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvminv6lj kind= uid=98d89edc-9766-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:45:55.146913Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvminv6lj\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvminv6lj" level=info timestamp=2018-08-03T21:48:55.494835Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvminv6lj\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvminv6lj, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 98d89edc-9766-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvminv6lj" level=info timestamp=2018-08-03T21:48:55.662892Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7fbw kind= uid=0486341d-9767-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:48:55.663435Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7fbw kind= uid=0486341d-9767-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T21:06:39.458066Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:29:15.329663Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:31:09.625983Z pos=health.go:55 component=virt-handler reason="tun device does not 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:12.036240Z pos=health.go:55 component=virt-handler reason="tun device does not 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:02.282029Z pos=health.go:55 component=virt-handler reason="tun device does not 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:04.387281Z pos=health.go:55 component=virt-handler reason="tun device does not 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:48.233860Z pos=health.go:55 component=virt-handler reason="tun device does not 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:58.519304Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:41:04.337514Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.274442Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:44:09.051278Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.609873Z pos=health.go:55 component=virt-handler reason="tun device does not 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:00.664914Z pos=health.go:55 component=virt-handler reason="tun device does not 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:20.797999Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:51.342094Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:29.681841Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:29:20.199608Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:31:14.461365Z pos=health.go:55 component=virt-handler reason="tun device does not 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:16.832698Z pos=health.go:55 component=virt-handler reason="tun device does not 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.027120Z pos=health.go:55 component=virt-handler reason="tun device does not 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:09.107155Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.856290Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.106298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:41:08.868075Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.724155Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:44:13.484191Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.991255Z pos=health.go:55 component=virt-handler reason="tun device does not 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:04.980101Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.097581Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:55.594781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:33.833715Z pos=health.go:55 component=virt-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-testvmin7fbw-4txfv Pod phase: Pending • Failure [180.586 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.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:48:55.664155Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmin7fbw kind=VirtualMachineInstance uid=0486341d-9767-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvmin7fbw-4txfv" Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running 2018/08/03 21:54:01 http: TLS handshake error from 10.244.1.1:53156: EOF level=info timestamp=2018-08-03T21:54:05.488037Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:54:07.838861Z 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:54:07.934970Z 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:54:11 http: TLS handshake error from 10.244.1.1:53162: EOF level=info timestamp=2018-08-03T21:54:17.410607Z 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:54:21 http: TLS handshake error from 10.244.1.1:53168: EOF level=info timestamp=2018-08-03T21:54:27.937748Z 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:54:31 http: TLS handshake error from 10.244.1.1:53174: EOF level=info timestamp=2018-08-03T21:54:35.456243Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:54:37.920290Z 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:54:37.998604Z 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:54:41 http: TLS handshake error from 10.244.1.1:53180: EOF level=info timestamp=2018-08-03T21:54:47.514871Z 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:54:51 http: TLS handshake error from 10.244.1.1:53186: EOF Pod name: virt-controller-67dcdd8464-kxznq Pod phase: Running level=info timestamp=2018-08-03T21:39:53.688273Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi98kdw kind= uid=c17cf36a-9765-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:39:53.688699Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi98kdw kind= uid=c17cf36a-9765-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:39:53.762940Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi98kdw\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi98kdw" level=info timestamp=2018-08-03T21:42:54.361766Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi2vnnk kind= uid=2d2cdd4f-9766-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:42:54.362429Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi2vnnk kind= uid=2d2cdd4f-9766-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:42:54.459020Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi2vnnk\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi2vnnk" level=info timestamp=2018-08-03T21:42:54.481128Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi2vnnk\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi2vnnk" level=info timestamp=2018-08-03T21:45:55.021108Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvminv6lj kind= uid=98d89edc-9766-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:45:55.021865Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvminv6lj kind= uid=98d89edc-9766-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:45:55.146913Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvminv6lj\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvminv6lj" level=info timestamp=2018-08-03T21:48:55.494835Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvminv6lj\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvminv6lj, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 98d89edc-9766-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvminv6lj" level=info timestamp=2018-08-03T21:48:55.662892Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7fbw kind= uid=0486341d-9767-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:48:55.663435Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7fbw kind= uid=0486341d-9767-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:51:56.380252Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmichpxn kind= uid=703c2ee8-9767-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:51:56.381012Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmichpxn kind= uid=703c2ee8-9767-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T21:06:39.458066Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:33:12.036240Z pos=health.go:55 component=virt-handler reason="tun device does not 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:02.282029Z pos=health.go:55 component=virt-handler reason="tun device does not 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:04.387281Z pos=health.go:55 component=virt-handler reason="tun device does not 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:48.233860Z pos=health.go:55 component=virt-handler reason="tun device does not 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:58.519304Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:41:04.337514Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.274442Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:44:09.051278Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.609873Z pos=health.go:55 component=virt-handler reason="tun device does not 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:00.664914Z pos=health.go:55 component=virt-handler reason="tun device does not 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:20.797999Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:51.342094Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:29.681841Z pos=health.go:55 component=virt-handler reason="tun device does not 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:26.531834Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:52.680052Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:33:16.832698Z pos=health.go:55 component=virt-handler reason="tun device does not 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.027120Z pos=health.go:55 component=virt-handler reason="tun device does not 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:09.107155Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.856290Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.106298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:41:08.868075Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.724155Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:44:13.484191Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.991255Z pos=health.go:55 component=virt-handler reason="tun device does not 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:04.980101Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.097581Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:55.594781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:33.833715Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.639618Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:56.728047Z pos=health.go:55 component=virt-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-testvmichpxn-sbr82 Pod phase: Pending • Failure [180.854 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.017s. 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:51:56.497602Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmichpxn kind=VirtualMachineInstance uid=703c2ee8-9767-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvmichpxn-sbr82" Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T21:57:08.276103Z 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:08.674284Z 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:57:11 http: TLS handshake error from 10.244.1.1:53270: EOF level=info timestamp=2018-08-03T21:57:12.739244Z 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:57:12.742883Z 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:57:17.990696Z 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:57:21 http: TLS handshake error from 10.244.1.1:53276: EOF level=info timestamp=2018-08-03T21:57:28.886049Z 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:57:31 http: TLS handshake error from 10.244.1.1:53282: EOF level=info timestamp=2018-08-03T21:57:35.494301Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:57:38.459807Z 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:38.721424Z 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:57:41 http: TLS handshake error from 10.244.1.1:53288: EOF level=info timestamp=2018-08-03T21:57:48.082809Z 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:57:51 http: TLS handshake error from 10.244.1.1:53294: EOF Pod name: virt-controller-67dcdd8464-kxznq Pod phase: Running level=info timestamp=2018-08-03T21:42:54.361766Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi2vnnk kind= uid=2d2cdd4f-9766-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:42:54.362429Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi2vnnk kind= uid=2d2cdd4f-9766-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:42:54.459020Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi2vnnk\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi2vnnk" level=info timestamp=2018-08-03T21:42:54.481128Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi2vnnk\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi2vnnk" level=info timestamp=2018-08-03T21:45:55.021108Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvminv6lj kind= uid=98d89edc-9766-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:45:55.021865Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvminv6lj kind= uid=98d89edc-9766-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:45:55.146913Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvminv6lj\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvminv6lj" level=info timestamp=2018-08-03T21:48:55.494835Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvminv6lj\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvminv6lj, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 98d89edc-9766-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvminv6lj" level=info timestamp=2018-08-03T21:48:55.662892Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7fbw kind= uid=0486341d-9767-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:48:55.663435Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7fbw kind= uid=0486341d-9767-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:51:56.380252Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmichpxn kind= uid=703c2ee8-9767-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:51:56.381012Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmichpxn kind= uid=703c2ee8-9767-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:54:57.158834Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmipnqnh kind= uid=dbfdf9c7-9767-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:54:57.159587Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmipnqnh kind= uid=dbfdf9c7-9767-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:54:57.259911Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmipnqnh\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmipnqnh" Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T21:06:39.458066Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:35:02.282029Z pos=health.go:55 component=virt-handler reason="tun device does not 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:04.387281Z pos=health.go:55 component=virt-handler reason="tun device does not 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:48.233860Z pos=health.go:55 component=virt-handler reason="tun device does not 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:58.519304Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:41:04.337514Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.274442Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:44:09.051278Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.609873Z pos=health.go:55 component=virt-handler reason="tun device does not 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:00.664914Z pos=health.go:55 component=virt-handler reason="tun device does not 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:20.797999Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:51.342094Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:29.681841Z pos=health.go:55 component=virt-handler reason="tun device does not 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:26.531834Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:52.680052Z pos=health.go:55 component=virt-handler reason="tun device does not 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:14.155000Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:35:07.027120Z pos=health.go:55 component=virt-handler reason="tun device does not 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:09.107155Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.856290Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.106298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:41:08.868075Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.724155Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:44:13.484191Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.991255Z pos=health.go:55 component=virt-handler reason="tun device does not 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:04.980101Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.097581Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:55.594781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:33.833715Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.639618Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:56.728047Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.169941Z pos=health.go:55 component=virt-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-testvmipnqnh-8hxwp Pod phase: Pending • Failure [180.644 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.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: Starting a VirtualMachineInstance level=info timestamp=2018-08-03T21:54:57.128905Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmipnqnh kind=VirtualMachineInstance uid=dbfdf9c7-9767-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvmipnqnh-8hxwp" Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T22:00:08.863966Z 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:09.063037Z 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:11 http: TLS handshake error from 10.244.1.1:53378: EOF level=info timestamp=2018-08-03T22:00:12.758246Z 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:12.766338Z 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-03T22:00:18.573277Z 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:21 http: TLS handshake error from 10.244.1.1:53384: EOF level=info timestamp=2018-08-03T22:00:29.831585Z 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:31 http: TLS handshake error from 10.244.1.1:53390: EOF level=info timestamp=2018-08-03T22:00:35.460740Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:00:38.931029Z 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:39.151576Z 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:41 http: TLS handshake error from 10.244.1.1:53396: EOF level=info timestamp=2018-08-03T22:00:48.667624Z 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:51 http: TLS handshake error from 10.244.1.1:53402: EOF Pod name: virt-controller-67dcdd8464-kxznq Pod phase: Running level=info timestamp=2018-08-03T21:42:54.481128Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi2vnnk\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi2vnnk" level=info timestamp=2018-08-03T21:45:55.021108Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvminv6lj kind= uid=98d89edc-9766-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:45:55.021865Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvminv6lj kind= uid=98d89edc-9766-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:45:55.146913Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvminv6lj\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvminv6lj" level=info timestamp=2018-08-03T21:48:55.494835Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvminv6lj\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvminv6lj, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 98d89edc-9766-11e8-9f1a-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvminv6lj" level=info timestamp=2018-08-03T21:48:55.662892Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7fbw kind= uid=0486341d-9767-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:48:55.663435Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin7fbw kind= uid=0486341d-9767-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:51:56.380252Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmichpxn kind= uid=703c2ee8-9767-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:51:56.381012Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmichpxn kind= uid=703c2ee8-9767-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:54:57.158834Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmipnqnh kind= uid=dbfdf9c7-9767-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:54:57.159587Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmipnqnh kind= uid=dbfdf9c7-9767-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:54:57.259911Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmipnqnh\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmipnqnh" level=info timestamp=2018-08-03T21:57:57.814955Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi2zhns kind= uid=47aa416b-9768-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:57:57.815719Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi2zhns kind= uid=47aa416b-9768-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:57:57.911403Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi2zhns\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi2zhns" Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T21:06:39.458066Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:37:48.233860Z pos=health.go:55 component=virt-handler reason="tun device does not 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:58.519304Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:41:04.337514Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.274442Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:44:09.051278Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.609873Z pos=health.go:55 component=virt-handler reason="tun device does not 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:00.664914Z pos=health.go:55 component=virt-handler reason="tun device does not 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:20.797999Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:51.342094Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:29.681841Z pos=health.go:55 component=virt-handler reason="tun device does not 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:26.531834Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:52.680052Z pos=health.go:55 component=virt-handler reason="tun device does not 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:14.155000Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.606744Z pos=health.go:55 component=virt-handler reason="tun device does 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:29.038436Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:37:52.856290Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.106298Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:41:08.868075Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.724155Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:44:13.484191Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.991255Z pos=health.go:55 component=virt-handler reason="tun device does not 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:04.980101Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.097581Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:55.594781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:33.833715Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.639618Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:56.728047Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.169941Z pos=health.go:55 component=virt-handler reason="tun device does not 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:22.592901Z pos=health.go:55 component=virt-handler reason="tun device does 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:32.973851Z pos=health.go:55 component=virt-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-testvmi2zhns-8ptnc Pod phase: Pending • Failure [180.686 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.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: Starting a VirtualMachineInstance level=info timestamp=2018-08-03T21:57:57.775963Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi2zhns kind=VirtualMachineInstance uid=47aa416b-9768-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi2zhns-8ptnc" Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running 2018/08/03 22:03:31 http: TLS handshake error from 10.244.1.1:53492: EOF level=info timestamp=2018-08-03T22:03:35.526619Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:03:39.502194Z 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:03:39.596139Z 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:03:41 http: TLS handshake error from 10.244.1.1:53498: EOF level=info timestamp=2018-08-03T22:03:49.347100Z 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:03:51 http: TLS handshake error from 10.244.1.1:53504: EOF level=info timestamp=2018-08-03T22:04:00.976976Z 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:04:01 http: TLS handshake error from 10.244.1.1:53510: EOF level=info timestamp=2018-08-03T22:04:05.434661Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:04:09.585581Z 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:04:09.672351Z 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:04:11 http: TLS handshake error from 10.244.1.1:53516: EOF level=info timestamp=2018-08-03T22:04:19.446343Z 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:04:21 http: TLS handshake error from 10.244.1.1:53522: EOF Pod name: virt-controller-67dcdd8464-8gm9m Pod phase: Running level=info timestamp=2018-08-03T22:01:01.605956Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T22:01:17.922497Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmiInformer" level=info timestamp=2018-08-03T22:01:17.927372Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer kubeVirtPodInformer" level=info timestamp=2018-08-03T22:01:17.927481Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer kubeVirtNodeInformer" level=info timestamp=2018-08-03T22:01:17.927558Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmiPresetInformer" level=info timestamp=2018-08-03T22:01:17.930884Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmirsInformer" level=info timestamp=2018-08-03T22:01:17.930978Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T22:01:17.931046Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmInformer" level=info timestamp=2018-08-03T22:01:17.931134Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer limitrangeInformer" level=info timestamp=2018-08-03T22:01:17.931911Z pos=vm.go:85 component=virt-controller service=http msg="Starting VirtualMachine controller." level=info timestamp=2018-08-03T22:01:17.959938Z pos=node.go:104 component=virt-controller service=http msg="Starting node controller." level=info timestamp=2018-08-03T22:01:17.960203Z pos=vmi.go:129 component=virt-controller service=http msg="Starting vmi controller." level=info timestamp=2018-08-03T22:01:17.965273Z pos=replicaset.go:111 component=virt-controller service=http msg="Starting VirtualMachineInstanceReplicaSet controller." level=info timestamp=2018-08-03T22:01:18.000952Z pos=preset.go:74 component=virt-controller service=http msg="Starting Virtual Machine Initializer." level=info timestamp=2018-08-03T22:01:22.869557Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig2ngb kind= uid=c263895f-9768-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:01:22.870556Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig2ngb kind= uid=c263895f-9768-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:42:47.274442Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:44:09.051278Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.609873Z pos=health.go:55 component=virt-handler reason="tun device does not 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:00.664914Z pos=health.go:55 component=virt-handler reason="tun device does not 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:20.797999Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:51.342094Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:29.681841Z pos=health.go:55 component=virt-handler reason="tun device does not 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:26.531834Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:52.680052Z pos=health.go:55 component=virt-handler reason="tun device does not 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:14.155000Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.606744Z pos=health.go:55 component=virt-handler reason="tun device does 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:29.038436Z pos=health.go:55 component=virt-handler reason="tun device does 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:01:34.508562Z pos=health.go:55 component=virt-handler reason="tun device does 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:50.651768Z pos=health.go:55 component=virt-handler reason="tun device does 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:08.128212Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:42:51.724155Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:44:13.484191Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.991255Z pos=health.go:55 component=virt-handler reason="tun device does not 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:04.980101Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.097581Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:55.594781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:33.833715Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.639618Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:56.728047Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.169941Z pos=health.go:55 component=virt-handler reason="tun device does not 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:22.592901Z pos=health.go:55 component=virt-handler reason="tun device does 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:32.973851Z pos=health.go:55 component=virt-handler reason="tun device does 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:01:38.417418Z pos=health.go:55 component=virt-handler reason="tun device does 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:54.449791Z pos=health.go:55 component=virt-handler reason="tun device does 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:11.870527Z pos=health.go:55 component=virt-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-testvmig2ngb-sqlcz Pod phase: Pending • Failure [205.809 seconds] LeaderElection /root/go/src/kubevirt.io/kubevirt/tests/controller_leader_election_test.go:43 Start a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/controller_leader_election_test.go:53 when the controller pod is not running /root/go/src/kubevirt.io/kubevirt/tests/controller_leader_election_test.go:54 should success [It] /root/go/src/kubevirt.io/kubevirt/tests/controller_leader_election_test.go:55 Timed out after 90.010s. 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: Destroying the leading controller pod STEP: Starting a new VirtualMachineInstance level=info timestamp=2018-08-03T22:01:23.647906Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmig2ngb kind=VirtualMachineInstance uid=c263895f-9768-11e8-9f1a-525500d15501 msg="Created virtual machine pod virt-launcher-testvmig2ngb-sqlcz" • [SLOW TEST:13.420 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 ------------------------------ • [SLOW TEST:12.997 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 an vm /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 ------------------------------ • [SLOW TEST:12.800 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 preset /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 ------------------------------ • [SLOW TEST:12.794 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 replica set /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 ------------------------------ Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T22:05:39.817403Z 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:05:39.897588Z 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:05:40.271135Z 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:05:40.271304Z 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/testvmihpdcd/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:05:41.469702Z 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:05:41.469948Z 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/testvmihpdcd/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 22:05:41 http: TLS handshake error from 10.244.1.1:53570: EOF level=error timestamp=2018-08-03T22:05:42.583144Z 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:05:42.583326Z 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/testvmihpdcd/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:05:43.697966Z 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:05:43.698144Z 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/testvmihpdcd/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:05:44.822910Z 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:05:44.823081Z 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/testvmihpdcd/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:05:45.950701Z 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:05:45.950947Z 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/testvmihpdcd/console proto=HTTP/1.1 statusCode=400 contentLength=90 Pod name: virt-controller-67dcdd8464-8gm9m Pod phase: Running level=info timestamp=2018-08-03T22:01:01.605956Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T22:01:17.927481Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer kubeVirtNodeInformer" level=info timestamp=2018-08-03T22:01:17.927558Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmiPresetInformer" level=info timestamp=2018-08-03T22:01:17.930884Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmirsInformer" level=info timestamp=2018-08-03T22:01:17.930978Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T22:01:17.931046Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmInformer" level=info timestamp=2018-08-03T22:01:17.931134Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer limitrangeInformer" level=info timestamp=2018-08-03T22:01:17.931911Z pos=vm.go:85 component=virt-controller service=http msg="Starting VirtualMachine controller." level=info timestamp=2018-08-03T22:01:17.959938Z pos=node.go:104 component=virt-controller service=http msg="Starting node controller." level=info timestamp=2018-08-03T22:01:17.960203Z pos=vmi.go:129 component=virt-controller service=http msg="Starting vmi controller." level=info timestamp=2018-08-03T22:01:17.965273Z pos=replicaset.go:111 component=virt-controller service=http msg="Starting VirtualMachineInstanceReplicaSet controller." level=info timestamp=2018-08-03T22:01:18.000952Z pos=preset.go:74 component=virt-controller service=http msg="Starting Virtual Machine Initializer." level=info timestamp=2018-08-03T22:01:22.869557Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig2ngb kind= uid=c263895f-9768-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:01:22.870556Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig2ngb kind= uid=c263895f-9768-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:05:15.466204Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihpdcd kind= uid=4d03b23c-9769-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:15.467208Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihpdcd kind= uid=4d03b23c-9769-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:42:47.274442Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:44:09.051278Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.609873Z pos=health.go:55 component=virt-handler reason="tun device does not 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:00.664914Z pos=health.go:55 component=virt-handler reason="tun device does not 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:20.797999Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:51.342094Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:29.681841Z pos=health.go:55 component=virt-handler reason="tun device does not 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:26.531834Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:52.680052Z pos=health.go:55 component=virt-handler reason="tun device does not 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:14.155000Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.606744Z pos=health.go:55 component=virt-handler reason="tun device does 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:29.038436Z pos=health.go:55 component=virt-handler reason="tun device does 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:01:34.508562Z pos=health.go:55 component=virt-handler reason="tun device does 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:50.651768Z pos=health.go:55 component=virt-handler reason="tun device does 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:08.128212Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:42:51.724155Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:44:13.484191Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.991255Z pos=health.go:55 component=virt-handler reason="tun device does not 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:04.980101Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.097581Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:55.594781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:33.833715Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.639618Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:56.728047Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.169941Z pos=health.go:55 component=virt-handler reason="tun device does not 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:22.592901Z pos=health.go:55 component=virt-handler reason="tun device does 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:32.973851Z pos=health.go:55 component=virt-handler reason="tun device does 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:01:38.417418Z pos=health.go:55 component=virt-handler reason="tun device does 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:54.449791Z pos=health.go:55 component=virt-handler reason="tun device does 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:11.870527Z pos=health.go:55 component=virt-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-testvmihpdcd-k7lqx Pod phase: Pending • Failure [30.603 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 | 0xc420a41130>: { 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-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T22:06:09.897156Z 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:06:09.960149Z 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:06:10.856657Z 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:06:10.856896Z 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/testvmiqs52x/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 22:06:11 http: TLS handshake error from 10.244.1.1:53588: EOF level=error timestamp=2018-08-03T22:06:11.971327Z 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:06:11.971562Z 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/testvmiqs52x/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:06:13.088043Z 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:06:13.088248Z 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/testvmiqs52x/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:06:14.203278Z 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:06:14.203609Z 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/testvmiqs52x/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:06:15.336829Z 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:06:15.337036Z 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/testvmiqs52x/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:06:16.461653Z 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:06:16.461835Z 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/testvmiqs52x/console proto=HTTP/1.1 statusCode=400 contentLength=90 Pod name: virt-controller-67dcdd8464-8gm9m Pod phase: Running level=info timestamp=2018-08-03T22:01:01.605956Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T22:01:17.930884Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmirsInformer" level=info timestamp=2018-08-03T22:01:17.930978Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T22:01:17.931046Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmInformer" level=info timestamp=2018-08-03T22:01:17.931134Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer limitrangeInformer" level=info timestamp=2018-08-03T22:01:17.931911Z pos=vm.go:85 component=virt-controller service=http msg="Starting VirtualMachine controller." level=info timestamp=2018-08-03T22:01:17.959938Z pos=node.go:104 component=virt-controller service=http msg="Starting node controller." level=info timestamp=2018-08-03T22:01:17.960203Z pos=vmi.go:129 component=virt-controller service=http msg="Starting vmi controller." level=info timestamp=2018-08-03T22:01:17.965273Z pos=replicaset.go:111 component=virt-controller service=http msg="Starting VirtualMachineInstanceReplicaSet controller." level=info timestamp=2018-08-03T22:01:18.000952Z pos=preset.go:74 component=virt-controller service=http msg="Starting Virtual Machine Initializer." level=info timestamp=2018-08-03T22:01:22.869557Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig2ngb kind= uid=c263895f-9768-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:01:22.870556Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig2ngb kind= uid=c263895f-9768-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:05:15.466204Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihpdcd kind= uid=4d03b23c-9769-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:15.467208Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihpdcd kind= uid=4d03b23c-9769-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:05:46.153293Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqs52x kind= uid=5f4c700c-9769-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:46.155004Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqs52x kind= uid=5f4c700c-9769-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:44:09.051278Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.609873Z pos=health.go:55 component=virt-handler reason="tun device does not 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:00.664914Z pos=health.go:55 component=virt-handler reason="tun device does not 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:20.797999Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:51.342094Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:29.681841Z pos=health.go:55 component=virt-handler reason="tun device does not 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:26.531834Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:52.680052Z pos=health.go:55 component=virt-handler reason="tun device does not 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:14.155000Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.606744Z pos=health.go:55 component=virt-handler reason="tun device does 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:29.038436Z pos=health.go:55 component=virt-handler reason="tun device does 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:01:34.508562Z pos=health.go:55 component=virt-handler reason="tun device does 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:50.651768Z pos=health.go:55 component=virt-handler reason="tun device does 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:08.128212Z pos=health.go:55 component=virt-handler reason="tun device does 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:15.344903Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:42:51.724155Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:44:13.484191Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.991255Z pos=health.go:55 component=virt-handler reason="tun device does not 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:04.980101Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.097581Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:55.594781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:33.833715Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.639618Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:56.728047Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.169941Z pos=health.go:55 component=virt-handler reason="tun device does not 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:22.592901Z pos=health.go:55 component=virt-handler reason="tun device does 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:32.973851Z pos=health.go:55 component=virt-handler reason="tun device does 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:01:38.417418Z pos=health.go:55 component=virt-handler reason="tun device does 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:54.449791Z pos=health.go:55 component=virt-handler reason="tun device does 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:11.870527Z pos=health.go:55 component=virt-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-testvmiqs52x-7mppz Pod phase: Pending • Failure [30.634 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 | 0xc420a401a0>: { 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-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=error timestamp=2018-08-03T22:06:40.766140Z 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:06:40.766377Z 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/testvmivggch/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 22:06:41 http: TLS handshake error from 10.244.1.1:53606: EOF level=error timestamp=2018-08-03T22:06:41.888709Z 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:06:41.888876Z 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/testvmivggch/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:06:43.005132Z 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:06:43.005307Z 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/testvmivggch/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:06:44.123263Z 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:06:44.123453Z 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/testvmivggch/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:06:45.261885Z 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:06:45.262078Z 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/testvmivggch/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:06:46.386291Z 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:06:46.386534Z 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/testvmivggch/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:06:47.515136Z 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:06:47.515332Z 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/testvmivggch/console proto=HTTP/1.1 statusCode=400 contentLength=90 Pod name: virt-controller-67dcdd8464-8gm9m Pod phase: Running level=info timestamp=2018-08-03T22:01:01.605956Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T22:01:17.931046Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmInformer" level=info timestamp=2018-08-03T22:01:17.931134Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer limitrangeInformer" level=info timestamp=2018-08-03T22:01:17.931911Z pos=vm.go:85 component=virt-controller service=http msg="Starting VirtualMachine controller." level=info timestamp=2018-08-03T22:01:17.959938Z pos=node.go:104 component=virt-controller service=http msg="Starting node controller." level=info timestamp=2018-08-03T22:01:17.960203Z pos=vmi.go:129 component=virt-controller service=http msg="Starting vmi controller." level=info timestamp=2018-08-03T22:01:17.965273Z pos=replicaset.go:111 component=virt-controller service=http msg="Starting VirtualMachineInstanceReplicaSet controller." level=info timestamp=2018-08-03T22:01:18.000952Z pos=preset.go:74 component=virt-controller service=http msg="Starting Virtual Machine Initializer." level=info timestamp=2018-08-03T22:01:22.869557Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig2ngb kind= uid=c263895f-9768-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:01:22.870556Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig2ngb kind= uid=c263895f-9768-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:05:15.466204Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihpdcd kind= uid=4d03b23c-9769-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:15.467208Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihpdcd kind= uid=4d03b23c-9769-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:05:46.153293Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqs52x kind= uid=5f4c700c-9769-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:46.155004Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqs52x kind= uid=5f4c700c-9769-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:06:16.856113Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivggch kind= uid=719e7dfe-9769-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:06:16.858191Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivggch kind= uid=719e7dfe-9769-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:44:09.051278Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.609873Z pos=health.go:55 component=virt-handler reason="tun device does not 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:00.664914Z pos=health.go:55 component=virt-handler reason="tun device does not 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:20.797999Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:51.342094Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:29.681841Z pos=health.go:55 component=virt-handler reason="tun device does not 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:26.531834Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:52.680052Z pos=health.go:55 component=virt-handler reason="tun device does not 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:14.155000Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.606744Z pos=health.go:55 component=virt-handler reason="tun device does 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:29.038436Z pos=health.go:55 component=virt-handler reason="tun device does 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:01:34.508562Z pos=health.go:55 component=virt-handler reason="tun device does 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:50.651768Z pos=health.go:55 component=virt-handler reason="tun device does 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:08.128212Z pos=health.go:55 component=virt-handler reason="tun device does 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:15.344903Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:44:13.484191Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.991255Z pos=health.go:55 component=virt-handler reason="tun device does not 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:04.980101Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.097581Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:55.594781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:33.833715Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.639618Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:56.728047Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.169941Z pos=health.go:55 component=virt-handler reason="tun device does not 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:22.592901Z pos=health.go:55 component=virt-handler reason="tun device does 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:32.973851Z pos=health.go:55 component=virt-handler reason="tun device does 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:01:38.417418Z pos=health.go:55 component=virt-handler reason="tun device does 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:54.449791Z pos=health.go:55 component=virt-handler reason="tun device does 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:11.870527Z pos=health.go:55 component=virt-handler reason="tun device does 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:19.107026Z pos=health.go:55 component=virt-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-testvmivggch-7j88c Pod phase: Pending • Failure [30.728 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 | 0xc4205c4180>: { 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-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running 2018/08/03 22:07:11 http: TLS handshake error from 10.244.1.1:53624: EOF level=error timestamp=2018-08-03T22:07:12.554909Z 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:07:12.555123Z 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/testvmi7vw7p/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:07:13.667850Z 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:07:13.668049Z 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/testvmi7vw7p/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=info timestamp=2018-08-03T22:07:13.778428Z 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:07:13.784771Z 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=error timestamp=2018-08-03T22:07:14.781366Z 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:07:14.781622Z 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/testvmi7vw7p/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:07:15.939187Z 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:07:15.939593Z 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/testvmi7vw7p/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:07:17.072187Z 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:07:17.072449Z 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/testvmi7vw7p/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T22:07:18.192978Z 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:07:18.193230Z 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/testvmi7vw7p/console proto=HTTP/1.1 statusCode=400 contentLength=90 Pod name: virt-controller-67dcdd8464-8gm9m Pod phase: Running level=info timestamp=2018-08-03T22:01:01.605956Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T22:01:17.959938Z pos=node.go:104 component=virt-controller service=http msg="Starting node controller." level=info timestamp=2018-08-03T22:01:17.960203Z pos=vmi.go:129 component=virt-controller service=http msg="Starting vmi controller." level=info timestamp=2018-08-03T22:01:17.965273Z pos=replicaset.go:111 component=virt-controller service=http msg="Starting VirtualMachineInstanceReplicaSet controller." level=info timestamp=2018-08-03T22:01:18.000952Z pos=preset.go:74 component=virt-controller service=http msg="Starting Virtual Machine Initializer." level=info timestamp=2018-08-03T22:01:22.869557Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig2ngb kind= uid=c263895f-9768-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:01:22.870556Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig2ngb kind= uid=c263895f-9768-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:05:15.466204Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihpdcd kind= uid=4d03b23c-9769-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:15.467208Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihpdcd kind= uid=4d03b23c-9769-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:05:46.153293Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqs52x kind= uid=5f4c700c-9769-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:46.155004Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqs52x kind= uid=5f4c700c-9769-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:06:16.856113Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivggch kind= uid=719e7dfe-9769-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:06:16.858191Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivggch kind= uid=719e7dfe-9769-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:06:47.604454Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7vw7p kind= uid=83f1a748-9769-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:06:47.604823Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7vw7p kind= uid=83f1a748-9769-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:06:47.809549Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi7vw7p\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi7vw7p" Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:44:09.051278Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.609873Z pos=health.go:55 component=virt-handler reason="tun device does not 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:00.664914Z pos=health.go:55 component=virt-handler reason="tun device does not 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:20.797999Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:51.342094Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:29.681841Z pos=health.go:55 component=virt-handler reason="tun device does not 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:26.531834Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:52.680052Z pos=health.go:55 component=virt-handler reason="tun device does not 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:14.155000Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.606744Z pos=health.go:55 component=virt-handler reason="tun device does 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:29.038436Z pos=health.go:55 component=virt-handler reason="tun device does 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:01:34.508562Z pos=health.go:55 component=virt-handler reason="tun device does 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:50.651768Z pos=health.go:55 component=virt-handler reason="tun device does 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:08.128212Z pos=health.go:55 component=virt-handler reason="tun device does 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:15.344903Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:44:13.484191Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.991255Z pos=health.go:55 component=virt-handler reason="tun device does not 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:04.980101Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.097581Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:55.594781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:33.833715Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.639618Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:56.728047Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.169941Z pos=health.go:55 component=virt-handler reason="tun device does not 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:22.592901Z pos=health.go:55 component=virt-handler reason="tun device does 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:32.973851Z pos=health.go:55 component=virt-handler reason="tun device does 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:01:38.417418Z pos=health.go:55 component=virt-handler reason="tun device does 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:54.449791Z pos=health.go:55 component=virt-handler reason="tun device does 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:11.870527Z pos=health.go:55 component=virt-handler reason="tun device does 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:19.107026Z pos=health.go:55 component=virt-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-testvmi7vw7p-g28vs Pod phase: Pending • Failure [30.809 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 | 0xc4205c51b0>: { 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.297 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.359 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.324 seconds] Subresource Api /root/go/src/kubevirt.io/kubevirt/tests/subresource_api_test.go:37 Rbac Authorization For Version Command /root/go/src/kubevirt.io/kubevirt/tests/subresource_api_test.go:63 Without permissions /root/go/src/kubevirt.io/kubevirt/tests/subresource_api_test.go:71 should be able to access subresource version endpoint /root/go/src/kubevirt.io/kubevirt/tests/subresource_api_test.go:72 ------------------------------ •• Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T22:12:51.024046Z 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:12:51 http: TLS handshake error from 10.244.1.1:53836: EOF 2018/08/03 22:13:01 http: TLS handshake error from 10.244.1.1:53842: EOF level=info timestamp=2018-08-03T22:13:03.810067Z 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:05.509579Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:13:11.148204Z 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:11.209136Z 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:11 http: TLS handshake error from 10.244.1.1:53848: EOF level=info timestamp=2018-08-03T22:13:13.536098Z 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:13:13.540042Z 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-03T22:13:21.113684Z 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:21 http: TLS handshake error from 10.244.1.1:53854: EOF 2018/08/03 22:13:31 http: TLS handshake error from 10.244.1.1:53860: EOF level=info timestamp=2018-08-03T22:13:33.986923Z 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:35.395063Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 Pod name: virt-controller-67dcdd8464-8gm9m Pod phase: Running level=info timestamp=2018-08-03T22:01:01.605956Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T22:05:46.155004Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqs52x kind= uid=5f4c700c-9769-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:06:16.856113Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivggch kind= uid=719e7dfe-9769-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:06:16.858191Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivggch kind= uid=719e7dfe-9769-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:06:47.604454Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7vw7p kind= uid=83f1a748-9769-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:06:47.604823Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7vw7p kind= uid=83f1a748-9769-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:06:47.809549Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi7vw7p\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi7vw7p" level=info timestamp=2018-08-03T22:07:18.295390Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilrzjf kind= uid=963bd5e8-9769-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:07:18.299872Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilrzjf kind= uid=963bd5e8-9769-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:07:18.638039Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmilrzjf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmilrzjf" level=info timestamp=2018-08-03T22:07:48.654598Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigftfh kind= uid=a8548866-9769-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:07:48.654908Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigftfh kind= uid=a8548866-9769-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:08:38.391437Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihtw8t kind= uid=c5fb40bf-9769-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:08:38.391820Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihtw8t kind= uid=c5fb40bf-9769-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:08:38.586369Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmihtw8t\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmihtw8t" level=info timestamp=2018-08-03T22:08:38.620265Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmihtw8t\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmihtw8t" Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:48:20.797999Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:51.342094Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:29.681841Z pos=health.go:55 component=virt-handler reason="tun device does not 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:26.531834Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:52.680052Z pos=health.go:55 component=virt-handler reason="tun device does not 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:14.155000Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.606744Z pos=health.go:55 component=virt-handler reason="tun device does 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:29.038436Z pos=health.go:55 component=virt-handler reason="tun device does 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:01:34.508562Z pos=health.go:55 component=virt-handler reason="tun device does 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:50.651768Z pos=health.go:55 component=virt-handler reason="tun device does 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:08.128212Z pos=health.go:55 component=virt-handler reason="tun device does 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:15.344903Z pos=health.go:55 component=virt-handler reason="tun device does 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:08.904141Z pos=health.go:55 component=virt-handler reason="tun device does 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:06.681474Z pos=health.go:55 component=virt-handler reason="tun device does 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:59.362709Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:48:25.097581Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:49:55.594781Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:51:33.833715Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.639618Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:56.728047Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.169941Z pos=health.go:55 component=virt-handler reason="tun device does not 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:22.592901Z pos=health.go:55 component=virt-handler reason="tun device does 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:32.973851Z pos=health.go:55 component=virt-handler reason="tun device does 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:01:38.417418Z pos=health.go:55 component=virt-handler reason="tun device does 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:54.449791Z pos=health.go:55 component=virt-handler reason="tun device does 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:11.870527Z pos=health.go:55 component=virt-handler reason="tun device does 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:19.107026Z pos=health.go:55 component=virt-handler reason="tun device does 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.551706Z pos=health.go:55 component=virt-handler reason="tun device does 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:10.265107Z pos=health.go:55 component=virt-handler reason="tun device does 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:12:02.883631Z pos=health.go:55 component=virt-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-testvmihtw8t-pph5h Pod phase: Pending ------------------------------ • Failure [300.503 seconds] VirtualMachine /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:47 A valid VirtualMachine given /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:115 should update VirtualMachine once VMIs are up [It] /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:195 Timed out after 300.000s. Expected : false to be true /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:201 ------------------------------ •• Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T22:18:05.508035Z 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:18:05.516842Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:18:11 http: TLS handshake error from 10.244.1.1:54028: EOF level=info timestamp=2018-08-03T22:18:12.026014Z 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:18:12.093860Z 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:18:14.161945Z 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:18:14.165978Z 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:18:21 http: TLS handshake error from 10.244.1.1:54034: EOF level=info timestamp=2018-08-03T22:18:22.149446Z 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:18:31 http: TLS handshake error from 10.244.1.1:54040: EOF level=info timestamp=2018-08-03T22:18:35.418397Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:18:35.695889Z 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:18:41 http: TLS handshake error from 10.244.1.1:54046: EOF level=info timestamp=2018-08-03T22:18:42.085725Z 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:18:42.205895Z 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-8gm9m Pod phase: Running level=info timestamp=2018-08-03T22:01:01.605956Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T22:08:38.391820Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihtw8t kind= uid=c5fb40bf-9769-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:08:38.586369Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmihtw8t\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmihtw8t" level=info timestamp=2018-08-03T22:08:38.620265Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmihtw8t\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmihtw8t" level=error timestamp=2018-08-03T22:13:39.159102Z pos=vm.go:459 component=virt-controller service=http namespace=kubevirt-test-default name=testvmijgnv4 kind= uid=794062cf-976a-11e8-9f1a-525500d15501 msg="Cant find the matching VM for VirtualMachineInstance: testvmijgnv4" level=info timestamp=2018-08-03T22:13:39.161400Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmijgnv4 kind= uid=794062cf-976a-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:13:39.163806Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmijgnv4 kind= uid=794062cf-976a-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:13:39.252954Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmijgnv4\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmijgnv4" level=info timestamp=2018-08-03T22:13:41.556491Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifbdt9 kind= uid=7aaa944c-976a-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:13:41.557981Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifbdt9 kind= uid=7aaa944c-976a-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:13:42.595499Z pos=controller_ref_manager.go:291 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifbdt9 kind= uid=7aaa944c-976a-11e8-9f1a-525500d15501 msg="patching vmi to remove its controllerRef to kubevirt.io/v1alpha2/VirtualMachine:testvmifbdt9" level=info timestamp=2018-08-03T22:13:43.964061Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig5v4j kind= uid=7c1dab94-976a-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:13:43.964554Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig5v4j kind= uid=7c1dab94-976a-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:13:44.053237Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmig5v4j\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmig5v4j" level=info timestamp=2018-08-03T22:13:44.089826Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmig5v4j\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmig5v4j" level=info timestamp=2018-08-03T22:13:44.106344Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmig5v4j\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmig5v4j" Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:53:26.531834Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:52.680052Z pos=health.go:55 component=virt-handler reason="tun device does not 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:14.155000Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.606744Z pos=health.go:55 component=virt-handler reason="tun device does 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:29.038436Z pos=health.go:55 component=virt-handler reason="tun device does 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:01:34.508562Z pos=health.go:55 component=virt-handler reason="tun device does 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:50.651768Z pos=health.go:55 component=virt-handler reason="tun device does 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:08.128212Z pos=health.go:55 component=virt-handler reason="tun device does 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:15.344903Z pos=health.go:55 component=virt-handler reason="tun device does 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:08.904141Z pos=health.go:55 component=virt-handler reason="tun device does 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:06.681474Z pos=health.go:55 component=virt-handler reason="tun device does 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:59.362709Z pos=health.go:55 component=virt-handler reason="tun device does 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:14:04.019943Z pos=health.go:55 component=virt-handler reason="tun device does 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:53.254179Z pos=health.go:55 component=virt-handler reason="tun device does 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:03.809823Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:53:30.639618Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:54:56.728047Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.169941Z pos=health.go:55 component=virt-handler reason="tun device does not 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:22.592901Z pos=health.go:55 component=virt-handler reason="tun device does 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:32.973851Z pos=health.go:55 component=virt-handler reason="tun device does 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:01:38.417418Z pos=health.go:55 component=virt-handler reason="tun device does 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:54.449791Z pos=health.go:55 component=virt-handler reason="tun device does 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:11.870527Z pos=health.go:55 component=virt-handler reason="tun device does 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:19.107026Z pos=health.go:55 component=virt-handler reason="tun device does 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.551706Z pos=health.go:55 component=virt-handler reason="tun device does 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:10.265107Z pos=health.go:55 component=virt-handler reason="tun device does 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:12:02.883631Z pos=health.go:55 component=virt-handler reason="tun device does 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:14:07.509614Z pos=health.go:55 component=virt-handler reason="tun device does 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:56.703644Z pos=health.go:55 component=virt-handler reason="tun device does 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:07.229568Z pos=health.go:55 component=virt-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-testvmig5v4j-8dn59 Pod phase: Pending ------------------------------ • Failure [300.628 seconds] VirtualMachine /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:47 A valid VirtualMachine given /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:115 should recreate VirtualMachineInstance if it gets deleted [It] /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:245 Timed out after 300.000s. Expected : false to be true /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:157 ------------------------------ STEP: Starting the VirtualMachineInstance STEP: VMI has the running condition Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T22:20:05.422418Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:20:06.150017Z 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:11 http: TLS handshake error from 10.244.1.1:54100: EOF level=info timestamp=2018-08-03T22:20:12.368040Z 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:12.455896Z 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:14.172320Z 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:14.176230Z 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:21 http: TLS handshake error from 10.244.1.1:54106: EOF level=info timestamp=2018-08-03T22:20:22.576793Z 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:31 http: TLS handshake error from 10.244.1.1:54112: EOF level=info timestamp=2018-08-03T22:20:35.562606Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:20:36.298963Z 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:41 http: TLS handshake error from 10.244.1.1:54118: EOF level=info timestamp=2018-08-03T22:20:42.452941Z 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:42.538958Z 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-8gm9m Pod phase: Running level=info timestamp=2018-08-03T22:01:01.605956Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T22:08:38.620265Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmihtw8t\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmihtw8t" level=error timestamp=2018-08-03T22:13:39.159102Z pos=vm.go:459 component=virt-controller service=http namespace=kubevirt-test-default name=testvmijgnv4 kind= uid=794062cf-976a-11e8-9f1a-525500d15501 msg="Cant find the matching VM for VirtualMachineInstance: testvmijgnv4" level=info timestamp=2018-08-03T22:13:39.161400Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmijgnv4 kind= uid=794062cf-976a-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:13:39.163806Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmijgnv4 kind= uid=794062cf-976a-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:13:39.252954Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmijgnv4\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmijgnv4" level=info timestamp=2018-08-03T22:13:41.556491Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifbdt9 kind= uid=7aaa944c-976a-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:13:41.557981Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifbdt9 kind= uid=7aaa944c-976a-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:13:42.595499Z pos=controller_ref_manager.go:291 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifbdt9 kind= uid=7aaa944c-976a-11e8-9f1a-525500d15501 msg="patching vmi to remove its controllerRef to kubevirt.io/v1alpha2/VirtualMachine:testvmifbdt9" level=info timestamp=2018-08-03T22:13:43.964061Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig5v4j kind= uid=7c1dab94-976a-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:13:43.964554Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig5v4j kind= uid=7c1dab94-976a-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:13:44.053237Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmig5v4j\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmig5v4j" level=info timestamp=2018-08-03T22:13:44.089826Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmig5v4j\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmig5v4j" level=info timestamp=2018-08-03T22:13:44.106344Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmig5v4j\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmig5v4j" level=info timestamp=2018-08-03T22:18:44.689465Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4kfp5 kind= uid=2f5dd1ef-976b-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:18:44.693193Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4kfp5 kind= uid=2f5dd1ef-976b-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T21:54:52.680052Z pos=health.go:55 component=virt-handler reason="tun device does not 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:14.155000Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.606744Z pos=health.go:55 component=virt-handler reason="tun device does 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:29.038436Z pos=health.go:55 component=virt-handler reason="tun device does 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:01:34.508562Z pos=health.go:55 component=virt-handler reason="tun device does 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:50.651768Z pos=health.go:55 component=virt-handler reason="tun device does 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:08.128212Z pos=health.go:55 component=virt-handler reason="tun device does 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:15.344903Z pos=health.go:55 component=virt-handler reason="tun device does 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:08.904141Z pos=health.go:55 component=virt-handler reason="tun device does 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:06.681474Z pos=health.go:55 component=virt-handler reason="tun device does 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:59.362709Z pos=health.go:55 component=virt-handler reason="tun device does 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:14:04.019943Z pos=health.go:55 component=virt-handler reason="tun device does 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:53.254179Z pos=health.go:55 component=virt-handler reason="tun device does 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:03.809823Z pos=health.go:55 component=virt-handler reason="tun device does 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:19:10.441782Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T21:54:56.728047Z pos=health.go:55 component=virt-handler reason="tun device does not 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:18.169941Z pos=health.go:55 component=virt-handler reason="tun device does not 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:22.592901Z pos=health.go:55 component=virt-handler reason="tun device does 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:32.973851Z pos=health.go:55 component=virt-handler reason="tun device does 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:01:38.417418Z pos=health.go:55 component=virt-handler reason="tun device does 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:54.449791Z pos=health.go:55 component=virt-handler reason="tun device does 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:11.870527Z pos=health.go:55 component=virt-handler reason="tun device does 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:19.107026Z pos=health.go:55 component=virt-handler reason="tun device does 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.551706Z pos=health.go:55 component=virt-handler reason="tun device does 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:10.265107Z pos=health.go:55 component=virt-handler reason="tun device does 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:12:02.883631Z pos=health.go:55 component=virt-handler reason="tun device does 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:14:07.509614Z pos=health.go:55 component=virt-handler reason="tun device does 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:56.703644Z pos=health.go:55 component=virt-handler reason="tun device does 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:07.229568Z pos=health.go:55 component=virt-handler reason="tun device does 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:19:13.827592Z pos=health.go:55 component=virt-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-testvmi4kfp5-rb79x Pod phase: Pending • Failure [120.714 seconds] VirtualMachine /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:47 A valid VirtualMachine given /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:115 should recreate VirtualMachineInstance if the VirtualMachineInstance's pod gets deleted [It] /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:265 Timed out after 120.000s. Expected success, but got an error: <*errors.errorString | 0xc4205c4960>: { s: "vmi still isn't running", } vmi still isn't running /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:284 ------------------------------ STEP: Creating a new VMI STEP: Waiting for the VMI's VirtualMachineInstance to start Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T22:25:05.499529Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:25:07.817684Z 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:11 http: TLS handshake error from 10.244.1.1:54280: EOF level=info timestamp=2018-08-03T22:25:13.205413Z 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:13.300062Z 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:13.938737Z 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:25:13.942823Z 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:25:21 http: TLS handshake error from 10.244.1.1:54286: EOF level=info timestamp=2018-08-03T22:25:23.641759Z 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:31 http: TLS handshake error from 10.244.1.1:54292: EOF level=info timestamp=2018-08-03T22:25:35.501853Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:25:37.960247Z 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:41 http: TLS handshake error from 10.244.1.1:54298: EOF level=info timestamp=2018-08-03T22:25:43.326560Z 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:43.417863Z 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-8gm9m Pod phase: Running level=info timestamp=2018-08-03T22:01:01.605956Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T22:13:41.556491Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifbdt9 kind= uid=7aaa944c-976a-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:13:41.557981Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifbdt9 kind= uid=7aaa944c-976a-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:13:42.595499Z pos=controller_ref_manager.go:291 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifbdt9 kind= uid=7aaa944c-976a-11e8-9f1a-525500d15501 msg="patching vmi to remove its controllerRef to kubevirt.io/v1alpha2/VirtualMachine:testvmifbdt9" level=info timestamp=2018-08-03T22:13:43.964061Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig5v4j kind= uid=7c1dab94-976a-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:13:43.964554Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig5v4j kind= uid=7c1dab94-976a-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:13:44.053237Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmig5v4j\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmig5v4j" level=info timestamp=2018-08-03T22:13:44.089826Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmig5v4j\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmig5v4j" level=info timestamp=2018-08-03T22:13:44.106344Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmig5v4j\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmig5v4j" level=info timestamp=2018-08-03T22:18:44.689465Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4kfp5 kind= uid=2f5dd1ef-976b-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:18:44.693193Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4kfp5 kind= uid=2f5dd1ef-976b-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:20:45.447426Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiw5sgn kind= uid=77576cfa-976b-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:20:45.453100Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiw5sgn kind= uid=77576cfa-976b-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:20:45.549507Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiw5sgn\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiw5sgn" level=info timestamp=2018-08-03T22:20:45.605795Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiw5sgn\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiw5sgn" level=info timestamp=2018-08-03T22:20:45.634262Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiw5sgn\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiw5sgn" Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T22:00:29.038436Z pos=health.go:55 component=virt-handler reason="tun device does 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:01:34.508562Z pos=health.go:55 component=virt-handler reason="tun device does 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:50.651768Z pos=health.go:55 component=virt-handler reason="tun device does 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:08.128212Z pos=health.go:55 component=virt-handler reason="tun device does 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:15.344903Z pos=health.go:55 component=virt-handler reason="tun device does 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:08.904141Z pos=health.go:55 component=virt-handler reason="tun device does 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:06.681474Z pos=health.go:55 component=virt-handler reason="tun device does 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:59.362709Z pos=health.go:55 component=virt-handler reason="tun device does 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:14:04.019943Z pos=health.go:55 component=virt-handler reason="tun device does 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:53.254179Z pos=health.go:55 component=virt-handler reason="tun device does 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:03.809823Z pos=health.go:55 component=virt-handler reason="tun device does 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:19:10.441782Z pos=health.go:55 component=virt-handler reason="tun device does 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:21:17.278146Z pos=health.go:55 component=virt-handler reason="tun device does 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:26.114872Z pos=health.go:55 component=virt-handler reason="tun device does 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:24:51.241332Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T22:00:32.973851Z pos=health.go:55 component=virt-handler reason="tun device does 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:01:38.417418Z pos=health.go:55 component=virt-handler reason="tun device does 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:54.449791Z pos=health.go:55 component=virt-handler reason="tun device does 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:11.870527Z pos=health.go:55 component=virt-handler reason="tun device does 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:19.107026Z pos=health.go:55 component=virt-handler reason="tun device does 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.551706Z pos=health.go:55 component=virt-handler reason="tun device does 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:10.265107Z pos=health.go:55 component=virt-handler reason="tun device does 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:12:02.883631Z pos=health.go:55 component=virt-handler reason="tun device does 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:14:07.509614Z pos=health.go:55 component=virt-handler reason="tun device does 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:56.703644Z pos=health.go:55 component=virt-handler reason="tun device does 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:07.229568Z pos=health.go:55 component=virt-handler reason="tun device does 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:19:13.827592Z pos=health.go:55 component=virt-handler reason="tun device does 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:21:20.593451Z pos=health.go:55 component=virt-handler reason="tun device does 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:29.377660Z pos=health.go:55 component=virt-handler reason="tun device does 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:24:54.460082Z pos=health.go:55 component=virt-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-testvmiw5sgn-mbnwc Pod phase: Pending • Failure [301.868 seconds] VirtualMachine /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:47 A valid VirtualMachine given /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:115 should stop VirtualMachineInstance if running set to false [It] /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:325 Timed out after 300.000s. Expected : false to be true /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:157 ------------------------------ STEP: Starting the VirtualMachineInstance STEP: VMI has the running condition Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T22:30:05.578347Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:30:09.420223Z 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:30:11 http: TLS handshake error from 10.244.1.1:54460: EOF level=info timestamp=2018-08-03T22:30:13.972367Z 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:30:13.976299Z 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-03T22:30:14.145758Z 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:30:14.217754Z 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:30:21 http: TLS handshake error from 10.244.1.1:54466: EOF level=info timestamp=2018-08-03T22:30:24.750108Z 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:30:31 http: TLS handshake error from 10.244.1.1:54472: EOF level=info timestamp=2018-08-03T22:30:35.565814Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:30:39.572000Z 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:30:41 http: TLS handshake error from 10.244.1.1:54478: EOF level=info timestamp=2018-08-03T22:30:44.231816Z 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:30:44.323319Z 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-8gm9m Pod phase: Running level=info timestamp=2018-08-03T22:01:01.605956Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T22:13:43.964061Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig5v4j kind= uid=7c1dab94-976a-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:13:43.964554Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig5v4j kind= uid=7c1dab94-976a-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:13:44.053237Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmig5v4j\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmig5v4j" level=info timestamp=2018-08-03T22:13:44.089826Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmig5v4j\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmig5v4j" level=info timestamp=2018-08-03T22:13:44.106344Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmig5v4j\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmig5v4j" level=info timestamp=2018-08-03T22:18:44.689465Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4kfp5 kind= uid=2f5dd1ef-976b-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:18:44.693193Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4kfp5 kind= uid=2f5dd1ef-976b-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:20:45.447426Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiw5sgn kind= uid=77576cfa-976b-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:20:45.453100Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiw5sgn kind= uid=77576cfa-976b-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:20:45.549507Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiw5sgn\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiw5sgn" level=info timestamp=2018-08-03T22:20:45.605795Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiw5sgn\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiw5sgn" level=info timestamp=2018-08-03T22:20:45.634262Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiw5sgn\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiw5sgn" level=info timestamp=2018-08-03T22:25:47.300883Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmichzqx kind= uid=2b42a214-976c-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:25:47.301129Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmichzqx kind= uid=2b42a214-976c-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:25:47.380422Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmichzqx\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmichzqx" Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T22:04:08.128212Z pos=health.go:55 component=virt-handler reason="tun device does 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:15.344903Z pos=health.go:55 component=virt-handler reason="tun device does 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:08.904141Z pos=health.go:55 component=virt-handler reason="tun device does 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:06.681474Z pos=health.go:55 component=virt-handler reason="tun device does 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:59.362709Z pos=health.go:55 component=virt-handler reason="tun device does 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:14:04.019943Z pos=health.go:55 component=virt-handler reason="tun device does 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:53.254179Z pos=health.go:55 component=virt-handler reason="tun device does 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:03.809823Z pos=health.go:55 component=virt-handler reason="tun device does 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:19:10.441782Z pos=health.go:55 component=virt-handler reason="tun device does 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:21:17.278146Z pos=health.go:55 component=virt-handler reason="tun device does 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:26.114872Z pos=health.go:55 component=virt-handler reason="tun device does 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:24:51.241332Z pos=health.go:55 component=virt-handler reason="tun device does 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:26:41.069068Z pos=health.go:55 component=virt-handler reason="tun device does 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:20.876704Z pos=health.go:55 component=virt-handler reason="tun device does 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:30:15.387192Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T22:04:11.870527Z pos=health.go:55 component=virt-handler reason="tun device does 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:19.107026Z pos=health.go:55 component=virt-handler reason="tun device does 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.551706Z pos=health.go:55 component=virt-handler reason="tun device does 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:10.265107Z pos=health.go:55 component=virt-handler reason="tun device does 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:12:02.883631Z pos=health.go:55 component=virt-handler reason="tun device does 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:14:07.509614Z pos=health.go:55 component=virt-handler reason="tun device does 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:56.703644Z pos=health.go:55 component=virt-handler reason="tun device does 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:07.229568Z pos=health.go:55 component=virt-handler reason="tun device does 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:19:13.827592Z pos=health.go:55 component=virt-handler reason="tun device does 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:21:20.593451Z pos=health.go:55 component=virt-handler reason="tun device does 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:29.377660Z pos=health.go:55 component=virt-handler reason="tun device does 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:24:54.460082Z pos=health.go:55 component=virt-handler reason="tun device does 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:26:44.230220Z pos=health.go:55 component=virt-handler reason="tun device does 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:23.989034Z pos=health.go:55 component=virt-handler reason="tun device does 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:30:18.461163Z pos=health.go:55 component=virt-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-testvmichzqx-v76hc Pod phase: Pending • Failure [300.809 seconds] VirtualMachine /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:47 A valid VirtualMachine given /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:115 should start and stop VirtualMachineInstance multiple times [It] /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:333 Timed out after 300.000s. Expected : false to be true /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:157 ------------------------------ STEP: Doing run: 0 STEP: Starting the VirtualMachineInstance STEP: VMI has the running condition Pod name: disks-images-provider-b84rx Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-llf6l Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79975b94-s6lqg Pod phase: Running level=info timestamp=2018-08-03T22:35:55.857710Z 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:36:01 http: TLS handshake error from 10.244.1.1:54670: EOF level=info timestamp=2018-08-03T22:36:05.502101Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:36:11.245272Z 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:36:11 http: TLS handshake error from 10.244.1.1:54676: EOF level=info timestamp=2018-08-03T22:36:15.155435Z 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:36:15.260311Z 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:36:21 http: TLS handshake error from 10.244.1.1:54682: EOF level=info timestamp=2018-08-03T22:36:25.969095Z 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:36:31 http: TLS handshake error from 10.244.1.1:54688: EOF level=info timestamp=2018-08-03T22:36:35.537675Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.0 username=- method=GET url=/ proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:36:41.447663Z 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:36:41 http: TLS handshake error from 10.244.1.1:54694: EOF level=info timestamp=2018-08-03T22:36:45.228602Z 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:36:45.353652Z 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-8gm9m Pod phase: Running level=info timestamp=2018-08-03T22:01:01.605956Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-67dcdd8464-v2gbh Pod phase: Running level=info timestamp=2018-08-03T22:13:44.106344Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmig5v4j\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmig5v4j" level=info timestamp=2018-08-03T22:18:44.689465Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4kfp5 kind= uid=2f5dd1ef-976b-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:18:44.693193Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4kfp5 kind= uid=2f5dd1ef-976b-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:20:45.447426Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiw5sgn kind= uid=77576cfa-976b-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:20:45.453100Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiw5sgn kind= uid=77576cfa-976b-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:20:45.549507Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiw5sgn\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiw5sgn" level=info timestamp=2018-08-03T22:20:45.605795Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiw5sgn\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiw5sgn" level=info timestamp=2018-08-03T22:20:45.634262Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiw5sgn\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiw5sgn" level=info timestamp=2018-08-03T22:25:47.300883Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmichzqx kind= uid=2b42a214-976c-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:25:47.301129Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmichzqx kind= uid=2b42a214-976c-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:25:47.380422Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmichzqx\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmichzqx" level=info timestamp=2018-08-03T22:30:48.100041Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmijn8j9 kind= uid=de8d484e-976c-11e8-9f1a-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:30:48.100410Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmijn8j9 kind= uid=de8d484e-976c-11e8-9f1a-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=error timestamp=2018-08-03T22:30:48.167289Z pos=vm.go:201 component=virt-controller service=http namespace=kubevirt-test-default name=testvmijn8j9 kind= uid=de89a4c9-976c-11e8-9f1a-525500d15501 reason="Operation cannot be fulfilled on virtualmachines.kubevirt.io \"testvmijn8j9\": the object has been modified; please apply your changes to the latest version and try again" msg="Updating the VirtualMachine status failed." level=info timestamp=2018-08-03T22:30:48.167426Z pos=vm.go:111 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachines.kubevirt.io \"testvmijn8j9\": the object has been modified; please apply your changes to the latest version and try again" msg="re-enqueuing VirtualMachine kubevirt-test-default/testvmijn8j9" Pod name: virt-handler-9xv5q Pod phase: Running level=error timestamp=2018-08-03T22:10:06.681474Z pos=health.go:55 component=virt-handler reason="tun device does 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:59.362709Z pos=health.go:55 component=virt-handler reason="tun device does 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:14:04.019943Z pos=health.go:55 component=virt-handler reason="tun device does 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:53.254179Z pos=health.go:55 component=virt-handler reason="tun device does 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:03.809823Z pos=health.go:55 component=virt-handler reason="tun device does 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:19:10.441782Z pos=health.go:55 component=virt-handler reason="tun device does 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:21:17.278146Z pos=health.go:55 component=virt-handler reason="tun device does 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:26.114872Z pos=health.go:55 component=virt-handler reason="tun device does 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:24:51.241332Z pos=health.go:55 component=virt-handler reason="tun device does 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:26:41.069068Z pos=health.go:55 component=virt-handler reason="tun device does 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:20.876704Z pos=health.go:55 component=virt-handler reason="tun device does 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:30:15.387192Z pos=health.go:55 component=virt-handler reason="tun device does 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:31:44.552773Z pos=health.go:55 component=virt-handler reason="tun device does 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:32:54.033514Z pos=health.go:55 component=virt-handler reason="tun device does 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:35:05.091480Z pos=health.go:55 component=virt-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-xtdm2 Pod phase: Running level=error timestamp=2018-08-03T22:10:10.265107Z pos=health.go:55 component=virt-handler reason="tun device does 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:12:02.883631Z pos=health.go:55 component=virt-handler reason="tun device does 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:14:07.509614Z pos=health.go:55 component=virt-handler reason="tun device does 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:56.703644Z pos=health.go:55 component=virt-handler reason="tun device does 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:07.229568Z pos=health.go:55 component=virt-handler reason="tun device does 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:19:13.827592Z pos=health.go:55 component=virt-handler reason="tun device does 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:21:20.593451Z pos=health.go:55 component=virt-handler reason="tun device does 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:29.377660Z pos=health.go:55 component=virt-handler reason="tun device does 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:24:54.460082Z pos=health.go:55 component=virt-handler reason="tun device does 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:26:44.230220Z pos=health.go:55 component=virt-handler reason="tun device does 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:23.989034Z pos=health.go:55 component=virt-handler reason="tun device does 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:30:18.461163Z pos=health.go:55 component=virt-handler reason="tun device does 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:31:47.659295Z pos=health.go:55 component=virt-handler reason="tun device does 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:32:57.146195Z pos=health.go:55 component=virt-handler reason="tun device does 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:35:08.187593Z pos=health.go:55 component=virt-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-testvmijn8j9-7x6bl Pod phase: Pending • Failure [360.708 seconds] VirtualMachine /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:47 A valid VirtualMachine given /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:115 should not update the VirtualMachineInstance spec if Running [It] /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:346 Timed out after 360.000s. Expected : false to be true /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:353 ------------------------------ panic: test timed out after 1h30m0s goroutine 12417 [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(0xc42063be00, 0x12ad0d7, 0x9, 0x1339680, 0x47fa16) /gimme/.gimme/versions/go1.10.linux.amd64/src/testing/testing.go:825 +0x301 testing.runTests.func1(0xc42063bd10) /gimme/.gimme/versions/go1.10.linux.amd64/src/testing/testing.go:1063 +0x64 testing.tRunner(0xc42063bd10, 0xc42067bdf8) /gimme/.gimme/versions/go1.10.linux.amd64/src/testing/testing.go:777 +0xd0 testing.runTests(0xc4203db500, 0x1bc0e20, 0x1, 0x1, 0x412009) /gimme/.gimme/versions/go1.10.linux.amd64/src/testing/testing.go:1061 +0x2c4 testing.(*M).Run(0xc42089b100, 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 50 [select]: kubevirt.io/kubevirt/vendor/github.com/onsi/gomega/internal/asyncassertion.(*AsyncAssertion).match(0xc4206a7f80, 0x13c28e0, 0x1c06250, 0x412801, 0x0, 0x0, 0x0, 0x1c06250) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/gomega/internal/asyncassertion/async_assertion.go:139 +0x2e6 kubevirt.io/kubevirt/vendor/github.com/onsi/gomega/internal/asyncassertion.(*AsyncAssertion).Should(0xc4206a7f80, 0x13c28e0, 0x1c06250, 0x0, 0x0, 0x0, 0xc4206a7f80) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/gomega/internal/asyncassertion/async_assertion.go:48 +0x62 kubevirt.io/kubevirt/tests_test.glob..func13.3.2(0xc420350780, 0xc420350780) /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:157 +0x52c kubevirt.io/kubevirt/tests_test.glob..func13.3.12() /root/go/src/kubevirt.io/kubevirt/tests/vm_test.go:390 +0xd7 kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*runner).runSync(0xc4206c1320, 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(0xc4206c1320, 0x3, 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.(*ItNode).Run(0xc4207dae80, 0x13b5fc0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/leafnodes/it_node.go:26 +0x7f kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/spec.(*Spec).runSample(0xc4203f5c20, 0x0, 0x13b5fc0, 0xc4200c5500) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/spec/spec.go:203 +0x648 kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/spec.(*Spec).Run(0xc4203f5c20, 0x13b5fc0, 0xc4200c5500) /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(0xc4203f2640, 0xc4203f5c20, 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(0xc4203f2640, 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(0xc4203f2640, 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(0xc4200ecaf0, 0x7fe616c98a38, 0xc42063be00, 0x12af51b, 0xb, 0xc4203db540, 0x2, 0x2, 0x13d0ca0, 0xc4200c5500, ...) /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, 0xc42063be00, 0x12af51b, 0xb, 0xc4203db520, 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, 0xc42063be00, 0x12af51b, 0xb, 0xc4203cfd40, 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(0xc42063be00) /root/go/src/kubevirt.io/kubevirt/tests/tests_suite_test.go:43 +0xaa testing.tRunner(0xc42063be00, 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 51 [chan receive, 90 minutes]: kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).registerForInterrupts(0xc4203f2640, 0xc42021cea0) /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 52 [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(0xc420487750, 0xc42021cf60) /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 57 [IO wait]: internal/poll.runtime_pollWait(0x7fe616c7cf00, 0x72, 0xc420e95850) /gimme/.gimme/versions/go1.10.linux.amd64/src/runtime/netpoll.go:173 +0x57 internal/poll.(*pollDesc).wait(0xc42074e298, 0x72, 0xffffffffffffff00, 0x13b7ca0, 0x1ad8640) /gimme/.gimme/versions/go1.10.linux.amd64/src/internal/poll/fd_poll_runtime.go:85 +0x9b internal/poll.(*pollDesc).waitRead(0xc42074e298, 0xc4209d6000, 0x8000, 0x8000) /gimme/.gimme/versions/go1.10.linux.amd64/src/internal/poll/fd_poll_runtime.go:90 +0x3d internal/poll.(*FD).Read(0xc42074e280, 0xc4209d6000, 0x8000, 0x8000, 0x0, 0x0, 0x0) /gimme/.gimme/versions/go1.10.linux.amd64/src/internal/poll/fd_unix.go:157 +0x17d net.(*netFD).Read(0xc42074e280, 0xc4209d6000, 0x8000, 0x8000, 0x0, 0x8, 0x7ffb) /gimme/.gimme/versions/go1.10.linux.amd64/src/net/fd_unix.go:202 +0x4f net.(*conn).Read(0xc42000ed58, 0xc4209d6000, 0x8000, 0x8000, 0x0, 0x0, 0x0) /gimme/.gimme/versions/go1.10.linux.amd64/src/net/net.go:176 +0x6a crypto/tls.(*block).readFromUntil(0xc4208be5a0, 0x7fe616c98c70, 0xc42000ed58, 0x5, 0xc42000ed58, 0x0) /gimme/.gimme/versions/go1.10.linux.amd64/src/crypto/tls/conn.go:493 +0x96 crypto/tls.(*Conn).readRecord(0xc4203cb500, 0x133b617, 0xc4203cb620, 0x20) /gimme/.gimme/versions/go1.10.linux.amd64/src/crypto/tls/conn.go:595 +0xe0 crypto/tls.(*Conn).Read(0xc4203cb500, 0xc420585000, 0x1000, 0x1000, 0x0, 0x0, 0x0) /gimme/.gimme/versions/go1.10.linux.amd64/src/crypto/tls/conn.go:1156 +0x100 bufio.(*Reader).Read(0xc4208c91a0, 0xc4206b8ff8, 0x9, 0x9, 0xc42067ad78, 0xc420adc5c0, 0xc420e95d10) /gimme/.gimme/versions/go1.10.linux.amd64/src/bufio/bufio.go:216 +0x238 io.ReadAtLeast(0x13b4e00, 0xc4208c91a0, 0xc4206b8ff8, 0x9, 0x9, 0x9, 0xc420e95ce0, 0xc420e95ce0, 0x406614) /gimme/.gimme/versions/go1.10.linux.amd64/src/io/io.go:309 +0x86 io.ReadFull(0x13b4e00, 0xc4208c91a0, 0xc4206b8ff8, 0x9, 0x9, 0xc42067ad20, 0xc420e95d10, 0xc400005a01) /gimme/.gimme/versions/go1.10.linux.amd64/src/io/io.go:327 +0x58 kubevirt.io/kubevirt/vendor/golang.org/x/net/http2.readFrameHeader(0xc4206b8ff8, 0x9, 0x9, 0x13b4e00, 0xc4208c91a0, 0x0, 0xc400000000, 0x7baa0d, 0xc420e95fb0) /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(0xc4206b8fc0, 0xc4202dac90, 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(0xc420e95fb0, 0x133a5d8, 0xc420487fb0) /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(0xc420286ea0) /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 make: *** [functest] Error 2 + make cluster-down ./cluster/down.sh