+ export WORKSPACE=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release + WORKSPACE=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release + [[ k8s-1.10.4-release =~ openshift-.* ]] + [[ k8s-1.10.4-release =~ .*-1.10.4-.* ]] + export KUBEVIRT_PROVIDER=k8s-1.10.4 + KUBEVIRT_PROVIDER=k8s-1.10.4 + 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: connection refused. Sleeping 5s 2018/08/03 20:50:59 Connected to tcp://192.168.66.101:22 + kubeadm init --config /etc/kubernetes/kubeadm.conf [init] Using Kubernetes version: v1.10.4 [init] Using Authorization modes: [Node RBAC] [preflight] Running pre-flight checks. [WARNING FileExisting-crictl]: crictl not found in system path Suggestion: go get github.com/kubernetes-incubator/cri-tools/cmd/crictl Flag --admission-control has been deprecated, Use --enable-admission-plugins or --disable-admission-plugins instead. Will be removed in a future version. [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 [localhost] and IPs [127.0.0.1] [certificates] Generated etcd/peer certificate and key. [certificates] etcd/peer serving cert is signed for DNS names [node01] and IPs [192.168.66.101] [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 26.004639 seconds [uploadconfig] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace [markmaster] Will mark node node01 as master by adding a label and a taint [markmaster] Master node01 tainted and labelled with key/value: node-role.kubernetes.io/master="" [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: kube-dns [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:d830e375d80d29175ab9dc2afe70bdbfd21ba90a9306d37587b147b57fc8b8d3 + 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 2018/08/03 20:51:40 Waiting for host: 192.168.66.102:22 2018/08/03 20:51:43 Problem with dial: dial tcp 192.168.66.102:22: getsockopt: no route to host. Sleeping 5s 2018/08/03 20:51:55 Connected to tcp://192.168.66.102:22 + 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. [discovery] Trying to connect to API Server "192.168.66.101:6443" [WARNING FileExisting-crictl]: crictl not found in system path Suggestion: go get github.com/kubernetes-incubator/cri-tools/cmd/crictl [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" 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 39611920 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 32s v1.10.4 node02 NotReady 9s v1.10.4 + kubectl_rc=0 + '[' 0 -ne 0 ']' ++ kubectl get nodes --no-headers ++ cluster/kubectl.sh get nodes --no-headers ++ grep NotReady + '[' -n 'node02 NotReady 10s v1.10.4' ']' + echo 'Waiting for all nodes to become ready ...' Waiting for all nodes to become ready ... + kubectl get nodes --no-headers + cluster/kubectl.sh get nodes --no-headers node01 Ready master 33s v1.10.4 node02 NotReady 10s v1.10.4 + kubectl_rc=0 + sleep 10 + '[' 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 44s v1.10.4 node02 Ready 21s v1.10.4 + make cluster-sync ./cluster/build.sh Building ... Untagged: localhost:33142/kubevirt/virt-controller:devel Untagged: localhost:33142/kubevirt/virt-controller@sha256:8f9da14f2eab7740238a8d0b6a7e164ece1ca26ed423815cb054ae0f9df752cf Deleted: sha256:1b6eb9703d07a1c3165a5c8362c0da630f361b0a2a53d5d4b5b0fea7567cf41a Deleted: sha256:b98ab6f9a0b56d85e280299e3058f6114d2f6b2cbb46717b973135578f8e9b56 Deleted: sha256:93dce54ef419b40a86f0db80a860fa0f1064ebd9858b5ba77ac39236f17cbe41 Deleted: sha256:960ac29c2d0ed71e515305fbcea168ca4a57b1f02a0066f10fb727da9164dafb Untagged: localhost:33142/kubevirt/virt-launcher:devel Untagged: localhost:33142/kubevirt/virt-launcher@sha256:8022adb74e301ffd29bc0eed9278190c2d49b5defeaa6ac0c0a8caf5955a3732 Deleted: sha256:07c6627f0647a4aa28c2989790f91fe9e8a10de840fb41d571e561a8cd29aa54 Deleted: sha256:1d042bcb60d2fabad1dadd745685b85a9085665c8fc8315beee6a286ad56d84d Deleted: sha256:c5e3cef147fd85db6cb891bb0a4fa871f9cd98946d38525204c2609c1b1c324d Deleted: sha256:6fa2e1d5ebe2d9fe51bf6b77bf81e2b840db7e38b90a1a8a2543b35a647074d9 Deleted: sha256:37d49f7ac58b528e84b4c8cb5f842781c6c8edb1fded302ff6a108c49e476f7f Deleted: sha256:421586e25f201c7dac1aa19a3038153b3aaed06f3eeea285ce5f63852d78f464 Deleted: sha256:2779e99ff4d783c75aaf61c6f6c6218f6962a65a2f3755193d8e6e00429eb311 Deleted: sha256:05c2552b9da0b3eed7bab4994687f04743e6803fc718f7890af176c4c6dea0b0 Deleted: sha256:473d63bb161e82369faec9f230d77b98211bcb4e226ec3dfdf3978f20bd847ff Deleted: sha256:e0fcf5d52e52f5baa2672bb562c578e5a25a1b9b32c8ce20df5f57c89a63fa46 Deleted: sha256:25d447084b16578c887f04d54318c2904a98b88f7f042c9ed8cd5f8c078c8bbf Deleted: sha256:4d16d0b76ccaf49c08c773ae5afc11deb899ae5e1634c9e24c17f4943a519ffb Untagged: localhost:33142/kubevirt/virt-handler:devel Untagged: localhost:33142/kubevirt/virt-handler@sha256:8642db349f32556d58ce6eddce888f572cc312299381ea1494e278da21225100 Deleted: sha256:c0a1d305defbdd3d30dc0196f5bef3bf3f1fff75c2544c62136514c477ae959c Deleted: sha256:92d1da3e3f343533a91ff750b11d8b27ba3788138dcb2e2b7c980f67fd4f9d04 Deleted: sha256:9142f6eb65794346956697c06ca810aa89c813966800832e8e6d2612971a8f14 Deleted: sha256:c05000cbb82a4de75d9dc5f7aeb4b047bb96841e2a5c1e8048d4deb3fe37e5e9 Untagged: localhost:33142/kubevirt/virt-api:devel Untagged: localhost:33142/kubevirt/virt-api@sha256:064cfb110534386157d0cdc70dbf854be310138259b5fca841e99640fb9fe0c2 Deleted: sha256:977661d65f2c0e81ae3ca77043123dc9b45e351a967b0497b7754f09bfd70cdc Deleted: sha256:63f7c6e01c7653390046ba4f7a765f834468d76b0f565aed2d8aba4e60f67a77 Deleted: sha256:4857cfe3a913e6eaa34ddcc0cb67735879513c89d6bd7f6b1b9f1445377566eb Deleted: sha256:2ccad884de0a8be4f7d1bb3c86a696643edad9c4e632ab7a37eb4fa4bbf3813c Untagged: localhost:33142/kubevirt/subresource-access-test:devel Untagged: localhost:33142/kubevirt/subresource-access-test@sha256:780d65efd848a91bcc0883988c952c00c929e95af283d8e6ae7f82f3758a170e Deleted: sha256:ad0f6a66c0454e9895546997a091b397293d167d804df688ac9efb9b34b31e6e Deleted: sha256:becc7e2d4111cab89aaad72babbc9c7428bf3b5a63448020f5a72c9b1cc44f9a Deleted: sha256:4bc1dddc8f20838bad4a426e9a7834ae9171e11549a90ae2e13f20dcbccbb407 Deleted: sha256:94ba99777c85a9eefbf5aaac8eaa296b76243f0cbb91cf8ed460c3d4f58543c8 Untagged: localhost:33142/kubevirt/example-hook-sidecar:devel Untagged: localhost:33142/kubevirt/example-hook-sidecar@sha256:5abc8a5a9fea790a17bc094e11f33802cf7a3aebe6864643625d1d1bd4f8000a Deleted: sha256:e759ccb43a2bb80457c58aace4844e7d98a50aef7ee4d7fdabe4b19246a3243d Deleted: sha256:00e78cc095b2f13fbca3a438a0d80e5ae2450833c130bbcbae617aac07fee02f Deleted: sha256:84084bcc1c443f63917a01581bb19052fe5149bc7de8a16d263a13ddeaa0a023 Deleted: sha256:cdda6335d9e4bdf7e6a8637de41d3ab787b2109db32141961ed7b478c1aa3c71 sha256:559a45ac63f40982ccce3a1b80cb62788566f2032c847ad9c45ee993eb9c48d4 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.10.4-release/go/src/kubevirt.io/kubevirt' hack/dockerized "./hack/check.sh && KUBEVIRT_VERSION= ./hack/build-go.sh install " && ./hack/build-copy-artifacts.sh sha256:559a45ac63f40982ccce3a1b80cb62788566f2032c847ad9c45ee993eb9c48d4 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 ---> d3c656a2b485 Step 3/8 : RUN useradd -u 1001 --create-home -s /bin/bash virt-controller ---> Using cache ---> a776f834c795 Step 4/8 : WORKDIR /home/virt-controller ---> Using cache ---> 714b6ef15e78 Step 5/8 : USER 1001 ---> Using cache ---> cadd485aa8f4 Step 6/8 : COPY virt-controller /usr/bin/virt-controller ---> b7f70bed9e0c Removing intermediate container 9fb805bbbb45 Step 7/8 : ENTRYPOINT /usr/bin/virt-controller ---> Running in 7b15344cfaa4 ---> 8789d19a4ad8 Removing intermediate container 7b15344cfaa4 Step 8/8 : LABEL "kubevirt-functional-tests-k8s-1.10.4-release0" '' "virt-controller" '' ---> Running in 1566ee429e8c ---> 842089360071 Removing intermediate container 1566ee429e8c Successfully built 842089360071 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 ---> 795ad92a5172 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 ---> 49e8a67155c8 Step 4/10 : COPY virt-launcher /usr/bin/virt-launcher ---> b5a21988c516 Removing intermediate container 9c062503aff1 Step 5/10 : COPY kubevirt-sudo /etc/sudoers.d/kubevirt ---> afcf13e98737 Removing intermediate container bb77c03fe162 Step 6/10 : RUN setcap CAP_NET_BIND_SERVICE=+eip /usr/bin/qemu-system-x86_64 ---> Running in a841767f26ed  ---> 9715cb78d61b Removing intermediate container a841767f26ed Step 7/10 : RUN mkdir -p /usr/share/kubevirt/virt-launcher ---> Running in f5f1921f078b  ---> 4e7bb79262e1 Removing intermediate container f5f1921f078b Step 8/10 : COPY entrypoint.sh libvirtd.sh sock-connector /usr/share/kubevirt/virt-launcher/ ---> 526d70db70fc Removing intermediate container f4cbfaaf3773 Step 9/10 : ENTRYPOINT /usr/share/kubevirt/virt-launcher/entrypoint.sh ---> Running in c138d1bd7a0e ---> 66b5a5a69581 Removing intermediate container c138d1bd7a0e Step 10/10 : LABEL "kubevirt-functional-tests-k8s-1.10.4-release0" '' "virt-launcher" '' ---> Running in a391eef75257 ---> ecd35f6cb9e0 Removing intermediate container a391eef75257 Successfully built ecd35f6cb9e0 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 ---> d3c656a2b485 Step 3/5 : COPY virt-handler /usr/bin/virt-handler ---> 4479f2ff6a9d Removing intermediate container 1adafcbe0c27 Step 4/5 : ENTRYPOINT /usr/bin/virt-handler ---> Running in 81c59e1b8292 ---> a4f80980c575 Removing intermediate container 81c59e1b8292 Step 5/5 : LABEL "kubevirt-functional-tests-k8s-1.10.4-release0" '' "virt-handler" '' ---> Running in 96f0b8d543a4 ---> 8e52c17ab00b Removing intermediate container 96f0b8d543a4 Successfully built 8e52c17ab00b 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 ---> d3c656a2b485 Step 3/8 : RUN useradd -u 1001 --create-home -s /bin/bash virt-api ---> Using cache ---> 9bbbc9ec8ccc Step 4/8 : WORKDIR /home/virt-api ---> Using cache ---> 6ff95ae380a5 Step 5/8 : USER 1001 ---> Using cache ---> 0026fc44bed8 Step 6/8 : COPY virt-api /usr/bin/virt-api ---> 443a577b1544 Removing intermediate container ed02de74d2ec Step 7/8 : ENTRYPOINT /usr/bin/virt-api ---> Running in 4cc561465681 ---> b7056d2f5e38 Removing intermediate container 4cc561465681 Step 8/8 : LABEL "kubevirt-functional-tests-k8s-1.10.4-release0" '' "virt-api" '' ---> Running in 52fcb695d8b1 ---> 5e049d872ef8 Removing intermediate container 52fcb695d8b1 Successfully built 5e049d872ef8 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 ---> d3c656a2b485 Step 3/7 : ENV container docker ---> Using cache ---> d7ee9dd5410a 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 ---> 0b64ac188f84 Step 5/7 : ADD entrypoint.sh / ---> Using cache ---> c9569040fd52 Step 6/7 : CMD /entrypoint.sh ---> Using cache ---> b0887fd36d1c Step 7/7 : LABEL "disks-images-provider" '' "kubevirt-functional-tests-k8s-1.10.4-release0" '' ---> Using cache ---> 5e827c2df99f Successfully built 5e827c2df99f 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 ---> d3c656a2b485 Step 3/5 : ENV container docker ---> Using cache ---> d7ee9dd5410a Step 4/5 : RUN dnf -y install procps-ng nmap-ncat && dnf -y clean all ---> Using cache ---> e96d3e3c109a Step 5/5 : LABEL "kubevirt-functional-tests-k8s-1.10.4-release0" '' "vm-killer" '' ---> Using cache ---> b82659934a82 Successfully built b82659934a82 Sending build context to Docker daemon 5.12 kB Step 1/7 : FROM debian:sid ---> 68f33cf86aab Step 2/7 : MAINTAINER "David Vossel" \ ---> Using cache ---> b7f20b0c4c41 Step 3/7 : ENV container docker ---> Using cache ---> 83fc28f38982 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 ---> 604b0b292d97 Step 5/7 : ADD entry-point.sh / ---> Using cache ---> 78792d6f56cd Step 6/7 : CMD /entry-point.sh ---> Using cache ---> 7f24cc15e083 Step 7/7 : LABEL "kubevirt-functional-tests-k8s-1.10.4-release0" '' "registry-disk-v1alpha" '' ---> Using cache ---> 9f185ea05af0 Successfully built 9f185ea05af0 Sending build context to Docker daemon 2.56 kB Step 1/4 : FROM localhost:33279/kubevirt/registry-disk-v1alpha:devel ---> 9f185ea05af0 Step 2/4 : MAINTAINER "David Vossel" \ ---> Using cache ---> 144098c857f6 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 ---> 470c8c941f3b Step 4/4 : LABEL "cirros-registry-disk-demo" '' "kubevirt-functional-tests-k8s-1.10.4-release0" '' ---> Using cache ---> 5c3573aee555 Successfully built 5c3573aee555 Sending build context to Docker daemon 2.56 kB Step 1/4 : FROM localhost:33279/kubevirt/registry-disk-v1alpha:devel ---> 9f185ea05af0 Step 2/4 : MAINTAINER "The KubeVirt Project" ---> Using cache ---> 163d18ada1f5 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 ---> df03150f97f7 Step 4/4 : LABEL "fedora-cloud-registry-disk-demo" '' "kubevirt-functional-tests-k8s-1.10.4-release0" '' ---> Using cache ---> d2698a39e323 Successfully built d2698a39e323 Sending build context to Docker daemon 2.56 kB Step 1/4 : FROM localhost:33279/kubevirt/registry-disk-v1alpha:devel ---> 9f185ea05af0 Step 2/4 : MAINTAINER "The KubeVirt Project" ---> Using cache ---> 163d18ada1f5 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 ---> d98139a655a4 Step 4/4 : LABEL "alpine-registry-disk-demo" '' "kubevirt-functional-tests-k8s-1.10.4-release0" '' ---> Using cache ---> 9e041444a39a Successfully built 9e041444a39a 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 ---> d3c656a2b485 Step 3/8 : RUN useradd -u 1001 --create-home -s /bin/bash virtctl ---> Using cache ---> 5704030d2070 Step 4/8 : WORKDIR /home/virtctl ---> Using cache ---> 624a72b3ef33 Step 5/8 : USER 1001 ---> Using cache ---> 74157fb56326 Step 6/8 : COPY subresource-access-test /subresource-access-test ---> 5b99beb2c4ae Removing intermediate container 330059eeeecd Step 7/8 : ENTRYPOINT /subresource-access-test ---> Running in 4875830ee268 ---> aaaf9ebfa0d1 Removing intermediate container 4875830ee268 Step 8/8 : LABEL "kubevirt-functional-tests-k8s-1.10.4-release0" '' "subresource-access-test" '' ---> Running in d9c6fe27a00d ---> 075e48f40623 Removing intermediate container d9c6fe27a00d Successfully built 075e48f40623 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 ---> d3c656a2b485 Step 3/9 : ENV container docker ---> Using cache ---> d7ee9dd5410a Step 4/9 : RUN dnf -y install make git gcc && dnf -y clean all ---> Using cache ---> e4ae555b2a96 Step 5/9 : ENV GIMME_GO_VERSION 1.9.2 ---> Using cache ---> 4805ef8280c3 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 ---> 7c1f17e56984 Step 7/9 : ENV GOPATH "/go" GOBIN "/usr/bin" ---> Using cache ---> c388427c6a76 Step 8/9 : RUN mkdir -p /go && source /etc/profile.d/gimme.sh && go get github.com/masterzen/winrm-cli ---> Using cache ---> 5da240e34c8d Step 9/9 : LABEL "kubevirt-functional-tests-k8s-1.10.4-release0" '' "winrmcli" '' ---> Using cache ---> fc4af18e41a0 Successfully built fc4af18e41a0 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 ---> 58c7014d7bc4 Step 3/5 : COPY example-hook-sidecar /example-hook-sidecar ---> 63e013497597 Removing intermediate container b6df83180ada Step 4/5 : ENTRYPOINT /example-hook-sidecar ---> Running in 53230754e008 ---> 7a36fccba5a7 Removing intermediate container 53230754e008 Step 5/5 : LABEL "example-hook-sidecar" '' "kubevirt-functional-tests-k8s-1.10.4-release0" '' ---> Running in 2a3bee5f40e0 ---> f5285623e85c Removing intermediate container 2a3bee5f40e0 Successfully built f5285623e85c hack/build-docker.sh push The push refers to a repository [localhost:33279/kubevirt/virt-controller] 1d874c5dc1a8: Preparing efce1557ba86: Preparing 891e1e4ef82a: Preparing efce1557ba86: Pushed 1d874c5dc1a8: Pushed 891e1e4ef82a: Pushed devel: digest: sha256:7fdbfb9f373a5c299156dff98c0bfae685e28d64f8b2256404c4eba925d72cd9 size: 949 The push refers to a repository [localhost:33279/kubevirt/virt-launcher] 1e1c34c9c7a0: Preparing 8766babdecc6: Preparing 98566ae23705: Preparing a322ac007446: Preparing aa09843bde42: Preparing 779823b58976: Preparing da38cf808aa5: Preparing b83399358a92: Preparing 186d8b3e4fd8: Preparing fa6154170bf5: Preparing 5eefb9960a36: Preparing 891e1e4ef82a: Preparing 779823b58976: Waiting da38cf808aa5: Waiting b83399358a92: Waiting 186d8b3e4fd8: Waiting fa6154170bf5: Waiting 5eefb9960a36: Waiting 891e1e4ef82a: Waiting 8766babdecc6: Pushed 1e1c34c9c7a0: Pushed a322ac007446: Pushed da38cf808aa5: Pushed b83399358a92: Pushed 186d8b3e4fd8: Pushed fa6154170bf5: Pushed 891e1e4ef82a: Mounted from kubevirt/virt-controller 98566ae23705: Pushed aa09843bde42: Pushed 779823b58976: Pushed 5eefb9960a36: Pushed devel: digest: sha256:dcaac4e605fe1646175940aee6b11f949153c881e0e00c8475052034a848413c size: 2828 The push refers to a repository [localhost:33279/kubevirt/virt-handler] 3e3288654eb0: Preparing 891e1e4ef82a: Preparing 891e1e4ef82a: Mounted from kubevirt/virt-launcher 3e3288654eb0: Pushed devel: digest: sha256:112b5bf0b2cf62c2cbc915e4cb7579956b035829493f2b01718d43202a9d424c size: 740 The push refers to a repository [localhost:33279/kubevirt/virt-api] 4b501f30c945: Preparing 1cd776a5872d: Preparing 891e1e4ef82a: Preparing 891e1e4ef82a: Mounted from kubevirt/virt-handler 1cd776a5872d: Pushed 4b501f30c945: Pushed devel: digest: sha256:80630cdf873123b7e83f92ccc32855942e078c25f0f1b2c90fd8c25145deb92a size: 948 The push refers to a repository [localhost:33279/kubevirt/disks-images-provider] 031ac8f2509a: Preparing df0d85013ae0: Preparing 891e1e4ef82a: Preparing 891e1e4ef82a: Mounted from kubevirt/virt-api 031ac8f2509a: Pushed df0d85013ae0: Pushed devel: digest: sha256:0a781ba0f345d564653bd766261d224da653d3eb7df0f5abeb67f1fcb1226455 size: 948 The push refers to a repository [localhost:33279/kubevirt/vm-killer] c6d1250c13a6: Preparing 891e1e4ef82a: Preparing 891e1e4ef82a: Mounted from kubevirt/disks-images-provider c6d1250c13a6: Pushed devel: digest: sha256:5680325ca88ab683e8ee0ce34f458871a0ea66b9031da653a8255dfdea55ffa2 size: 740 The push refers to a repository [localhost:33279/kubevirt/registry-disk-v1alpha] 3e288742e937: Preparing 7c38bbdf0880: Preparing 25edbec0eaea: Preparing 3e288742e937: Pushed 7c38bbdf0880: Pushed 25edbec0eaea: Pushed devel: digest: sha256:2c4bce549c7130c9b25183e6b8ff2d59d86b0e679a57b41b0efa5bebf9dee583 size: 948 The push refers to a repository [localhost:33279/kubevirt/cirros-registry-disk-demo] a899196b92d1: Preparing 3e288742e937: Preparing 7c38bbdf0880: Preparing 25edbec0eaea: Preparing 25edbec0eaea: Mounted from kubevirt/registry-disk-v1alpha 7c38bbdf0880: Mounted from kubevirt/registry-disk-v1alpha 3e288742e937: Mounted from kubevirt/registry-disk-v1alpha a899196b92d1: Pushed devel: digest: sha256:5454dcadb097cd68f295984545c12abb43aeeacde79b1e0e8a64a55119f1bf11 size: 1160 The push refers to a repository [localhost:33279/kubevirt/fedora-cloud-registry-disk-demo] aac41f162526: Preparing 3e288742e937: Preparing 7c38bbdf0880: Preparing 25edbec0eaea: Preparing 7c38bbdf0880: Mounted from kubevirt/cirros-registry-disk-demo 3e288742e937: Mounted from kubevirt/cirros-registry-disk-demo 25edbec0eaea: Mounted from kubevirt/cirros-registry-disk-demo aac41f162526: Pushed devel: digest: sha256:b0168476647c9b25e598d6123cd4b3e0b4797127716e28b6f0acd0304d343c3f size: 1161 The push refers to a repository [localhost:33279/kubevirt/alpine-registry-disk-demo] 92fe70a24761: Preparing 3e288742e937: Preparing 7c38bbdf0880: Preparing 25edbec0eaea: Preparing 7c38bbdf0880: Mounted from kubevirt/fedora-cloud-registry-disk-demo 3e288742e937: Mounted from kubevirt/fedora-cloud-registry-disk-demo 25edbec0eaea: Mounted from kubevirt/fedora-cloud-registry-disk-demo 92fe70a24761: Pushed devel: digest: sha256:14e0b91736ca44747541e9799c0909b4ad13e9eed7036941119c6f8cf63ee57e size: 1160 The push refers to a repository [localhost:33279/kubevirt/subresource-access-test] b87eef380f46: Preparing c3b63a8b92e2: Preparing 891e1e4ef82a: Preparing 891e1e4ef82a: Mounted from kubevirt/vm-killer c3b63a8b92e2: Pushed b87eef380f46: Pushed devel: digest: sha256:8bd5687ea28bf1be7e1cfc05b06a71f2619b47ee88fa2d727b0743565196587c size: 948 The push refers to a repository [localhost:33279/kubevirt/winrmcli] 03859482cdc2: Preparing a0f8b95b0bdd: Preparing 2aa87109f2ed: Preparing 891e1e4ef82a: Preparing 891e1e4ef82a: Mounted from kubevirt/subresource-access-test 03859482cdc2: Pushed 2aa87109f2ed: Pushed a0f8b95b0bdd: Pushed devel: digest: sha256:d75c7d87431edda3eeae4a8a02a774789bb14105c171bc6ed0141bb778390775 size: 1165 The push refers to a repository [localhost:33279/kubevirt/example-hook-sidecar] 2ba38c20c45d: Preparing 39bae602f753: Preparing 2ba38c20c45d: Pushed 39bae602f753: Pushed devel: digest: sha256:5e6244c0bcd6d60a00f8fad5db9ba89dd9c65b990162bb52e372621555cc449a size: 740 make[1]: Leaving directory `/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt' Done ./cluster/clean.sh + source hack/common.sh ++++ dirname 'hack/common.sh[0]' +++ cd hack/../ +++ pwd ++ KUBEVIRT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt ++ OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out ++ VENDOR_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/vendor ++ CMD_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out/cmd ++ TESTS_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out/tests ++ APIDOCS_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out/apidocs ++ MANIFESTS_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out/manifests ++ MANIFEST_TEMPLATES_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out/templates/manifests ++ PYTHON_CLIENT_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out/client-python ++ KUBEVIRT_PROVIDER=k8s-1.10.4 ++ KUBEVIRT_NUM_NODES=2 ++ '[' -z kubevirt-functional-tests-k8s-1.10.4-release ']' ++ provider_prefix=kubevirt-functional-tests-k8s-1.10.4-release0 ++ job_prefix=kubevirt-functional-tests-k8s-1.10.4-release0 +++ kubevirt_version +++ '[' -n '' ']' +++ '[' -d /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/.git ']' ++++ git describe --always --tags +++ echo v0.7.0-189-g96d0165 ++ KUBEVIRT_VERSION=v0.7.0-189-g96d0165 + source cluster/k8s-1.10.4/provider.sh ++ set -e ++ image=k8s-1.10.4@sha256:09ac918cc16f13a5d0af51d4c98e3e25cbf4f97b7b32fe18ec61b32f04ca1009 ++ 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.10.4 ++ source hack/config-default.sh source hack/config-k8s-1.10.4.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.10.4.sh ++ source hack/config-provider-k8s-1.10.4.sh +++ master_ip=127.0.0.1 +++ docker_tag=devel +++ kubeconfig=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/cluster/k8s-1.10.4/.kubeconfig +++ kubectl=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/cluster/k8s-1.10.4/.kubectl +++ docker_prefix=localhost:33279/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.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl -n default delete apiservices -l kubevirt.io No resources found + _kubectl -n default delete deployment -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl -n default delete deployment -l kubevirt.io No resources found + _kubectl -n default delete rs -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl -n default delete rs -l kubevirt.io No resources found + _kubectl -n default delete services -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl -n default delete services -l kubevirt.io No resources found + _kubectl -n default delete apiservices -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl -n default delete apiservices -l kubevirt.io No resources found + _kubectl -n default delete validatingwebhookconfiguration -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl -n default delete validatingwebhookconfiguration -l kubevirt.io No resources found + _kubectl -n default delete secrets -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl -n default delete secrets -l kubevirt.io No resources found + _kubectl -n default delete pv -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl -n default delete pv -l kubevirt.io No resources found + _kubectl -n default delete pvc -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl -n default delete pvc -l kubevirt.io No resources found + _kubectl -n default delete ds -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl -n default delete ds -l kubevirt.io No resources found + _kubectl -n default delete customresourcedefinitions -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl -n default delete customresourcedefinitions -l kubevirt.io No resources found + _kubectl -n default delete pods -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl -n default delete pods -l kubevirt.io No resources found + _kubectl -n default delete clusterrolebinding -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl -n default delete clusterrolebinding -l kubevirt.io No resources found + _kubectl -n default delete rolebinding -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl -n default delete rolebinding -l kubevirt.io No resources found + _kubectl -n default delete roles -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl -n default delete roles -l kubevirt.io No resources found + _kubectl -n default delete clusterroles -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl -n default delete clusterroles -l kubevirt.io No resources found + _kubectl -n default delete serviceaccounts -l kubevirt.io + export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl -n default delete serviceaccounts -l kubevirt.io No resources found ++ _kubectl -n default get crd offlinevirtualmachines.kubevirt.io ++ export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig ++ KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig ++ wc -l ++ cluster/k8s-1.10.4/.kubectl -n default get crd offlinevirtualmachines.kubevirt.io 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.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.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.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.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.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.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.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.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.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.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.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.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.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.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.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.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.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.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.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.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.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.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.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.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.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.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.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.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.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.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.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.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.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.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.10.4/.kubeconfig ++ KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig ++ wc -l ++ cluster/k8s-1.10.4/.kubectl -n kube-system get crd offlinevirtualmachines.kubevirt.io 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.10.4-release/go/src/kubevirt.io/kubevirt ++ OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out ++ VENDOR_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/vendor ++ CMD_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out/cmd ++ TESTS_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out/tests ++ APIDOCS_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out/apidocs ++ MANIFESTS_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out/manifests ++ MANIFEST_TEMPLATES_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out/templates/manifests ++ PYTHON_CLIENT_OUT_DIR=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out/client-python ++ KUBEVIRT_PROVIDER=k8s-1.10.4 ++ KUBEVIRT_NUM_NODES=2 ++ '[' -z kubevirt-functional-tests-k8s-1.10.4-release ']' ++ provider_prefix=kubevirt-functional-tests-k8s-1.10.4-release0 ++ job_prefix=kubevirt-functional-tests-k8s-1.10.4-release0 +++ kubevirt_version +++ '[' -n '' ']' +++ '[' -d /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/.git ']' ++++ git describe --always --tags +++ echo v0.7.0-189-g96d0165 ++ KUBEVIRT_VERSION=v0.7.0-189-g96d0165 + source cluster/k8s-1.10.4/provider.sh ++ set -e ++ image=k8s-1.10.4@sha256:09ac918cc16f13a5d0af51d4c98e3e25cbf4f97b7b32fe18ec61b32f04ca1009 ++ 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.10.4 ++ source hack/config-default.sh source hack/config-k8s-1.10.4.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.10.4.sh ++ source hack/config-provider-k8s-1.10.4.sh +++ master_ip=127.0.0.1 +++ docker_tag=devel +++ kubeconfig=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/cluster/k8s-1.10.4/.kubeconfig +++ kubectl=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/cluster/k8s-1.10.4/.kubectl +++ docker_prefix=localhost:33279/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.10.4-release ]] + [[ k8s-1.10.4-release =~ .*-dev ]] + [[ k8s-1.10.4-release =~ .*-release ]] + for manifest in '${MANIFESTS_OUT_DIR}/release/*' + [[ /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out/manifests/release/demo-content.yaml =~ .*demo.* ]] + continue + for manifest in '${MANIFESTS_OUT_DIR}/release/*' + [[ /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out/manifests/release/kubevirt.yaml =~ .*demo.* ]] + _kubectl create -f /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out/manifests/release/kubevirt.yaml + export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl create -f /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out/manifests/release/kubevirt.yaml clusterrole.rbac.authorization.k8s.io "kubevirt.io:admin" created clusterrole.rbac.authorization.k8s.io "kubevirt.io:edit" created clusterrole.rbac.authorization.k8s.io "kubevirt.io:view" created serviceaccount "kubevirt-apiserver" created clusterrolebinding.rbac.authorization.k8s.io "kubevirt-apiserver" created clusterrolebinding.rbac.authorization.k8s.io "kubevirt-apiserver-auth-delegator" created rolebinding.rbac.authorization.k8s.io "kubevirt-apiserver" created role.rbac.authorization.k8s.io "kubevirt-apiserver" created clusterrole.rbac.authorization.k8s.io "kubevirt-apiserver" created clusterrole.rbac.authorization.k8s.io "kubevirt-controller" created serviceaccount "kubevirt-controller" created serviceaccount "kubevirt-privileged" created clusterrolebinding.rbac.authorization.k8s.io "kubevirt-controller" created clusterrolebinding.rbac.authorization.k8s.io "kubevirt-controller-cluster-admin" created clusterrolebinding.rbac.authorization.k8s.io "kubevirt-privileged-cluster-admin" created clusterrole.rbac.authorization.k8s.io "kubevirt.io:default" created clusterrolebinding.rbac.authorization.k8s.io "kubevirt.io:default" created service "virt-api" created deployment.extensions "virt-api" created deployment.extensions "virt-controller" created daemonset.extensions "virt-handler" created customresourcedefinition.apiextensions.k8s.io "virtualmachineinstances.kubevirt.io" created customresourcedefinition.apiextensions.k8s.io "virtualmachineinstancereplicasets.kubevirt.io" created customresourcedefinition.apiextensions.k8s.io "virtualmachineinstancepresets.kubevirt.io" created customresourcedefinition.apiextensions.k8s.io "virtualmachines.kubevirt.io" created + _kubectl create -f /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out/manifests/testing -R + export KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + KUBECONFIG=cluster/k8s-1.10.4/.kubeconfig + cluster/k8s-1.10.4/.kubectl create -f /var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/go/src/kubevirt.io/kubevirt/_out/manifests/testing -R persistentvolumeclaim "disk-alpine" created persistentvolume "host-path-disk-alpine" created persistentvolumeclaim "disk-custom" created persistentvolume "host-path-disk-custom" created daemonset.extensions "disks-images-provider" created serviceaccount "kubevirt-testing" created clusterrolebinding.rbac.authorization.k8s.io "kubevirt-testing-cluster-admin" created + [[ k8s-1.10.4 =~ 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-7d79764579-dblhq 0/1 ContainerCreating 0 2s virt-api-7d79764579-hqpn2 0/1 ContainerCreating 0 2s virt-controller-7d57d96b65-b8vrz 0/1 ContainerCreating 0 2s virt-controller-7d57d96b65-cv6pb 0/1 ContainerCreating 0 2s virt-handler-2v7vl 0/1 ContainerCreating 0 2s virt-handler-q9bdc 0/1 ContainerCreating 0 2s' ']' + echo 'Waiting for kubevirt pods to enter the Running state ...' Waiting for kubevirt pods to enter the Running state ... + kubectl get pods -n kube-system --no-headers + grep -v Running + cluster/kubectl.sh get pods -n kube-system --no-headers virt-api-7d79764579-dblhq 0/1 ContainerCreating 0 2s virt-api-7d79764579-hqpn2 0/1 ContainerCreating 0 2s virt-controller-7d57d96b65-b8vrz 0/1 ContainerCreating 0 2s virt-controller-7d57d96b65-cv6pb 0/1 ContainerCreating 0 2s virt-handler-2v7vl 0/1 ContainerCreating 0 2s virt-handler-q9bdc 0/1 ContainerCreating 0 2s + sleep 30 + current_time=30 + '[' 30 -gt 300 ']' ++ kubectl get pods -n kube-system --no-headers ++ grep -v Running ++ cluster/kubectl.sh get pods -n kube-system --no-headers + '[' -n '' ']' + current_time=0 ++ kubectl get pods -n kube-system '-ocustom-columns=status:status.containerStatuses[*].ready' --no-headers ++ cluster/kubectl.sh get pods -n kube-system '-ocustom-columns=status:status.containerStatuses[*].ready' --no-headers ++ grep false + '[' -n false ']' + echo 'Waiting for KubeVirt containers to become ready ...' Waiting for KubeVirt containers to become ready ... + kubectl get pods -n kube-system '-ocustom-columns=status:status.containerStatuses[*].ready' --no-headers + grep false + cluster/kubectl.sh get pods -n kube-system '-ocustom-columns=status:status.containerStatuses[*].ready' --no-headers false + sleep 30 + current_time=30 + '[' 30 -gt 300 ']' ++ kubectl get pods -n kube-system '-ocustom-columns=status:status.containerStatuses[*].ready' --no-headers ++ grep false ++ cluster/kubectl.sh get pods -n kube-system '-ocustom-columns=status:status.containerStatuses[*].ready' --no-headers + '[' -n '' ']' + kubectl get pods -n kube-system + cluster/kubectl.sh get pods -n kube-system NAME READY STATUS RESTARTS AGE disks-images-provider-8wt7r 1/1 Running 0 1m disks-images-provider-nmksm 1/1 Running 0 1m etcd-node01 1/1 Running 0 8m kube-apiserver-node01 1/1 Running 0 8m kube-controller-manager-node01 1/1 Running 0 8m kube-dns-86f4d74b45-sq65b 3/3 Running 0 9m kube-flannel-ds-pbrhh 1/1 Running 0 9m kube-flannel-ds-vfp7w 1/1 Running 0 9m kube-proxy-26jhr 1/1 Running 0 9m kube-proxy-4lhjm 1/1 Running 0 9m kube-scheduler-node01 1/1 Running 0 8m virt-api-7d79764579-dblhq 1/1 Running 0 1m virt-api-7d79764579-hqpn2 1/1 Running 1 1m virt-controller-7d57d96b65-b8vrz 1/1 Running 0 1m virt-controller-7d57d96b65-cv6pb 1/1 Running 0 1m virt-handler-2v7vl 1/1 Running 0 1m virt-handler-q9bdc 1/1 Running 0 1m + for i in '${namespaces[@]}' + current_time=0 ++ kubectl get pods -n default --no-headers ++ cluster/kubectl.sh get pods -n default --no-headers ++ grep -v Running No resources found. + '[' -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 No resources found. + kubectl version + cluster/kubectl.sh version Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.4", GitCommit:"5ca598b4ba5abb89bb773071ce452e33fb66339d", GitTreeState:"clean", BuildDate:"2018-06-06T08:13:03Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.4", GitCommit:"5ca598b4ba5abb89bb773071ce452e33fb66339d", GitTreeState:"clean", BuildDate:"2018-06-06T08:00:59Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"} + ginko_params='--ginkgo.noColor --junit-output=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/junit.xml' + [[ k8s-1.10.4-release =~ windows.* ]] + FUNC_TEST_ARGS='--ginkgo.noColor --junit-output=/var/lib/swarm/workspace/kubevirt-functional-tests-k8s-1.10.4-release/junit.xml' + make functest hack/dockerized "hack/build-func-tests.sh" sha256:559a45ac63f40982ccce3a1b80cb62788566f2032c847ad9c45ee993eb9c48d4 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: 1533330111 Will run 148 of 148 specs Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T21:02:06.230472Z 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/testvmisqmsz/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:08.337132Z 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-03T21:02:08.337215Z 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/testvmisqmsz/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:10.443740Z 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-03T21:02:10.443826Z 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/testvmisqmsz/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 21:02:10 http: TLS handshake error from 10.244.1.1:52670: EOF level=error timestamp=2018-08-03T21:02:12.549374Z 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-03T21:02:12.549455Z 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/testvmisqmsz/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:15.708212Z 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-03T21:02:15.708298Z 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/testvmisqmsz/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:17.816835Z 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-03T21:02:17.816914Z 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/testvmisqmsz/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:18.864625Z 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-03T21:02:18.864693Z 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/testvmisqmsz/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 21:02:20 http: TLS handshake error from 10.244.1.1:52676: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=error timestamp=2018-08-03T21:02:11.425275Z 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-03T21:02:11.425409Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmisqmsz/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:13.526134Z 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-03T21:02:13.526234Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmisqmsz/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:14.577161Z 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-03T21:02:14.577250Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmisqmsz/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 21:02:16 http: TLS handshake error from 10.244.0.1:51480: EOF level=error timestamp=2018-08-03T21:02:16.685735Z 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-03T21:02:16.685966Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmisqmsz/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:19.845871Z 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-03T21:02:19.845994Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmisqmsz/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:20.892346Z 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-03T21:02:20.892424Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmisqmsz/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:21.977452Z 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-03T21:02:21.977532Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmisqmsz/console proto=HTTP/1.1 statusCode=400 contentLength=90 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:00:14.872357Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:00:14.872442Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmInformer" level=info timestamp=2018-08-03T21:00:14.872459Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer limitrangeInformer" level=info timestamp=2018-08-03T21:00:14.872473Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmiInformer" level=info timestamp=2018-08-03T21:00:14.872498Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer kubeVirtPodInformer" level=info timestamp=2018-08-03T21:00:14.872514Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer kubeVirtNodeInformer" level=info timestamp=2018-08-03T21:00:14.872528Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmiPresetInformer" level=info timestamp=2018-08-03T21:00:14.872542Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmirsInformer" level=info timestamp=2018-08-03T21:00:14.872642Z pos=vm.go:85 component=virt-controller service=http msg="Starting VirtualMachine controller." level=info timestamp=2018-08-03T21:00:14.877744Z pos=node.go:104 component=virt-controller service=http msg="Starting node controller." level=info timestamp=2018-08-03T21:00:14.877815Z pos=vmi.go:129 component=virt-controller service=http msg="Starting vmi controller." level=info timestamp=2018-08-03T21:00:14.877915Z pos=replicaset.go:111 component=virt-controller service=http msg="Starting VirtualMachineInstanceReplicaSet controller." level=info timestamp=2018-08-03T21:00:14.878108Z pos=preset.go:74 component=virt-controller service=http msg="Starting Virtual Machine Initializer." level=info timestamp=2018-08-03T21:01:52.194361Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisqmsz kind= uid=71f27085-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:01:52.206635Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisqmsz kind= uid=71f27085-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-2v7vl Pod phase: Running level=info timestamp=2018-08-03T21:00:19.712946Z pos=virt-handler.go:89 component=virt-handler hostname=node02 level=info timestamp=2018-08-03T21:00:19.722740Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:00:20.825151Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T21:00:20.826118Z pos=health.go:55 component=virt-handler 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:00:20.829461Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:02:09.536559Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=info timestamp=2018-08-03T21:00:26.766069Z pos=virt-handler.go:89 component=virt-handler hostname=node01 level=info timestamp=2018-08-03T21:00:26.913877Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:00:27.019262Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=info timestamp=2018-08-03T21:00:27.040666Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:00:27.024258Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:02:14.954498Z pos=health.go:55 component=virt-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-testvmisqmsz-5j6tx Pod phase: Pending • Failure [30.685 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 | 0xc4204ee600>: { 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-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=error timestamp=2018-08-03T21:02:40.846924Z 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-03T21:02:40.847021Z 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/testvmim8n7r/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:42.957775Z 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-03T21:02:42.957875Z 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/testvmim8n7r/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:46.113864Z 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-03T21:02:46.113962Z 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/testvmim8n7r/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:48.211041Z 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-03T21:02:48.211118Z 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/testvmim8n7r/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:50.317512Z 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-03T21:02:50.317595Z 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/testvmim8n7r/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 21:02:50 http: TLS handshake error from 10.244.1.1:52694: EOF level=error timestamp=2018-08-03T21:02:51.370184Z 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-03T21:02:51.370277Z 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/testvmim8n7r/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:52.434886Z 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-03T21:02:52.434993Z 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/testvmim8n7r/console proto=HTTP/1.1 statusCode=400 contentLength=90 Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=error timestamp=2018-08-03T21:02:39.718113Z 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-03T21:02:39.718235Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmim8n7r/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:41.820575Z 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-03T21:02:41.820663Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmim8n7r/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:43.938366Z 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-03T21:02:43.938457Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmim8n7r/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:44.983481Z 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-03T21:02:44.983550Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmim8n7r/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 21:02:46 http: TLS handshake error from 10.244.0.1:51622: EOF level=info timestamp=2018-08-03T21:02:46.716064Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:02:46.716970Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 level=error timestamp=2018-08-03T21:02:47.082479Z 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-03T21:02:47.082548Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmim8n7r/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:02:49.188359Z 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-03T21:02:49.188498Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmim8n7r/console proto=HTTP/1.1 statusCode=400 contentLength=90 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:00:14.872459Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer limitrangeInformer" level=info timestamp=2018-08-03T21:00:14.872473Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmiInformer" level=info timestamp=2018-08-03T21:00:14.872498Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer kubeVirtPodInformer" level=info timestamp=2018-08-03T21:00:14.872514Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer kubeVirtNodeInformer" level=info timestamp=2018-08-03T21:00:14.872528Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmiPresetInformer" level=info timestamp=2018-08-03T21:00:14.872542Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmirsInformer" level=info timestamp=2018-08-03T21:00:14.872642Z pos=vm.go:85 component=virt-controller service=http msg="Starting VirtualMachine controller." level=info timestamp=2018-08-03T21:00:14.877744Z pos=node.go:104 component=virt-controller service=http msg="Starting node controller." level=info timestamp=2018-08-03T21:00:14.877815Z pos=vmi.go:129 component=virt-controller service=http msg="Starting vmi controller." level=info timestamp=2018-08-03T21:00:14.877915Z pos=replicaset.go:111 component=virt-controller service=http msg="Starting VirtualMachineInstanceReplicaSet controller." level=info timestamp=2018-08-03T21:00:14.878108Z pos=preset.go:74 component=virt-controller service=http msg="Starting Virtual Machine Initializer." level=info timestamp=2018-08-03T21:01:52.194361Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisqmsz kind= uid=71f27085-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:01:52.206635Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisqmsz kind= uid=71f27085-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:02:22.826208Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim8n7r kind= uid=84515fad-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:02:22.826499Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim8n7r kind= uid=84515fad-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-2v7vl Pod phase: Running level=info timestamp=2018-08-03T21:00:19.712946Z pos=virt-handler.go:89 component=virt-handler hostname=node02 level=info timestamp=2018-08-03T21:00:19.722740Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:00:20.825151Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T21:00:20.826118Z pos=health.go:55 component=virt-handler 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:00:20.829461Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:02:09.536559Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=info timestamp=2018-08-03T21:00:26.766069Z pos=virt-handler.go:89 component=virt-handler hostname=node01 level=info timestamp=2018-08-03T21:00:26.913877Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:00:27.019262Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=info timestamp=2018-08-03T21:00:27.040666Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:00:27.024258Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:02:14.954498Z pos=health.go:55 component=virt-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-testvmim8n7r-qfd55 Pod phase: Pending • Failure [30.431 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 | 0xc42040f4d0>: { 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-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T21:03:08.057763Z 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/testvmimxfs2/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 21:03:10 http: TLS handshake error from 10.244.1.1:52706: EOF level=error timestamp=2018-08-03T21:03:13.295593Z 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-03T21:03:13.295680Z 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/testvmimxfs2/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:15.395849Z 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-03T21:03:15.395939Z 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/testvmimxfs2/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:16.457729Z 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-03T21:03:16.457810Z 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/testvmimxfs2/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:17.504598Z 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-03T21:03:17.504678Z 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/testvmimxfs2/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:19.606642Z 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-03T21:03:19.606728Z 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/testvmimxfs2/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 21:03:20 http: TLS handshake error from 10.244.1.1:52712: EOF level=error timestamp=2018-08-03T21:03:22.750675Z 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-03T21:03:22.750751Z 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/testvmimxfs2/console proto=HTTP/1.1 statusCode=400 contentLength=90 Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=error timestamp=2018-08-03T21:03:10.074727Z 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-03T21:03:10.075097Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmimxfs2/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:11.126827Z 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-03T21:03:11.126955Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmimxfs2/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:12.171906Z 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-03T21:03:12.171980Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmimxfs2/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:14.264233Z 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-03T21:03:14.264298Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmimxfs2/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 21:03:16 http: TLS handshake error from 10.244.0.1:51758: EOF level=error timestamp=2018-08-03T21:03:18.477496Z 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-03T21:03:18.477581Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmimxfs2/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:20.579213Z 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-03T21:03:20.579305Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmimxfs2/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:21.628227Z 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-03T21:03:21.628323Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmimxfs2/console proto=HTTP/1.1 statusCode=400 contentLength=90 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:00:14.872514Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer kubeVirtNodeInformer" level=info timestamp=2018-08-03T21:00:14.872528Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmiPresetInformer" level=info timestamp=2018-08-03T21:00:14.872542Z pos=virtinformers.go:107 component=virt-controller service=http msg="STARTING informer vmirsInformer" level=info timestamp=2018-08-03T21:00:14.872642Z pos=vm.go:85 component=virt-controller service=http msg="Starting VirtualMachine controller." level=info timestamp=2018-08-03T21:00:14.877744Z pos=node.go:104 component=virt-controller service=http msg="Starting node controller." level=info timestamp=2018-08-03T21:00:14.877815Z pos=vmi.go:129 component=virt-controller service=http msg="Starting vmi controller." level=info timestamp=2018-08-03T21:00:14.877915Z pos=replicaset.go:111 component=virt-controller service=http msg="Starting VirtualMachineInstanceReplicaSet controller." level=info timestamp=2018-08-03T21:00:14.878108Z pos=preset.go:74 component=virt-controller service=http msg="Starting Virtual Machine Initializer." level=info timestamp=2018-08-03T21:01:52.194361Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisqmsz kind= uid=71f27085-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:01:52.206635Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisqmsz kind= uid=71f27085-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:02:22.826208Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim8n7r kind= uid=84515fad-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:02:22.826499Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim8n7r kind= uid=84515fad-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:02:53.254125Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmimxfs2 kind= uid=9674a27f-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:02:53.254286Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmimxfs2 kind= uid=9674a27f-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:02:53.299942Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmimxfs2\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmimxfs2" Pod name: virt-handler-2v7vl Pod phase: Running level=info timestamp=2018-08-03T21:00:19.712946Z pos=virt-handler.go:89 component=virt-handler hostname=node02 level=info timestamp=2018-08-03T21:00:19.722740Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:00:20.825151Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T21:00:20.826118Z pos=health.go:55 component=virt-handler 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:00:20.829461Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:02:09.536559Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:14.277211Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=info timestamp=2018-08-03T21:00:26.766069Z pos=virt-handler.go:89 component=virt-handler hostname=node01 level=info timestamp=2018-08-03T21:00:26.913877Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:00:27.019262Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=info timestamp=2018-08-03T21:00:27.040666Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:00:27.024258Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:02:14.954498Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:19.694126Z pos=health.go:55 component=virt-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-testvmimxfs2-xdm5k Pod phase: Pending • Failure [30.429 seconds] Console /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:37 A new VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:65 with a serial console /root/go/src/kubevirt.io/kubevirt/tests/console_test.go:66 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 | 0xc420927b30>: { 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-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=error timestamp=2018-08-03T21:03:42.661480Z 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-03T21:03:42.661565Z 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/testvmi6sl5d/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:43.710968Z 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-03T21:03:43.711042Z 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/testvmi6sl5d/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:44.762269Z 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-03T21:03:44.762383Z 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/testvmi6sl5d/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:47.902026Z 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-03T21:03:47.902109Z 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/testvmi6sl5d/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:48.949803Z 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-03T21:03:48.949921Z 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/testvmi6sl5d/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 21:03:50 http: TLS handshake error from 10.244.1.1:52730: EOF level=error timestamp=2018-08-03T21:03:51.044763Z 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-03T21:03:51.044850Z 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/testvmi6sl5d/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:53.146055Z 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-03T21:03:53.146132Z 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/testvmi6sl5d/console proto=HTTP/1.1 statusCode=400 contentLength=90 Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=error timestamp=2018-08-03T21:03:38.381254Z 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-03T21:03:38.381364Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmi6sl5d/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:39.429017Z 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-03T21:03:39.429103Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmi6sl5d/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:40.479482Z 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-03T21:03:40.479573Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmi6sl5d/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:45.736186Z 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-03T21:03:45.736264Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmi6sl5d/console proto=HTTP/1.1 statusCode=400 contentLength=90 2018/08/03 21:03:46 http: TLS handshake error from 10.244.0.1:51894: EOF level=error timestamp=2018-08-03T21:03:46.777730Z 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-03T21:03:46.777800Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmi6sl5d/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:49.922837Z 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-03T21:03:49.923005Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmi6sl5d/console proto=HTTP/1.1 statusCode=400 contentLength=90 level=error timestamp=2018-08-03T21:03:52.017403Z 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-03T21:03:52.017484Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2/namespaces/kubevirt-test-default/virtualmachineinstances/testvmi6sl5d/console proto=HTTP/1.1 statusCode=400 contentLength=90 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:00:14.877815Z pos=vmi.go:129 component=virt-controller service=http msg="Starting vmi controller." level=info timestamp=2018-08-03T21:00:14.877915Z pos=replicaset.go:111 component=virt-controller service=http msg="Starting VirtualMachineInstanceReplicaSet controller." level=info timestamp=2018-08-03T21:00:14.878108Z pos=preset.go:74 component=virt-controller service=http msg="Starting Virtual Machine Initializer." level=info timestamp=2018-08-03T21:01:52.194361Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisqmsz kind= uid=71f27085-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:01:52.206635Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisqmsz kind= uid=71f27085-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:02:22.826208Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim8n7r kind= uid=84515fad-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:02:22.826499Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim8n7r kind= uid=84515fad-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:02:53.254125Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmimxfs2 kind= uid=9674a27f-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:02:53.254286Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmimxfs2 kind= uid=9674a27f-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:02:53.299942Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmimxfs2\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmimxfs2" level=info timestamp=2018-08-03T21:03:23.505142Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmimxfs2\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmimxfs2, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 9674a27f-9760-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmimxfs2" level=info timestamp=2018-08-03T21:03:23.509184Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmimxfs2\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmimxfs2, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 9674a27f-9760-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmimxfs2" level=info timestamp=2018-08-03T21:03:23.684024Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi6sl5d kind= uid=a897d627-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:03:23.684190Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi6sl5d kind= uid=a897d627-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:03:23.746807Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi6sl5d\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi6sl5d" Pod name: virt-handler-2v7vl Pod phase: Running level=info timestamp=2018-08-03T21:00:19.712946Z pos=virt-handler.go:89 component=virt-handler hostname=node02 level=info timestamp=2018-08-03T21:00:19.722740Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:00:20.825151Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T21:00:20.826118Z pos=health.go:55 component=virt-handler 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:00:20.829461Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:02:09.536559Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:14.277211Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=info timestamp=2018-08-03T21:00:26.766069Z pos=virt-handler.go:89 component=virt-handler hostname=node01 level=info timestamp=2018-08-03T21:00:26.913877Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:00:27.019262Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=info timestamp=2018-08-03T21:00:27.040666Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:00:27.024258Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:02:14.954498Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:19.694126Z pos=health.go:55 component=virt-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-testvmi6sl5d-8vkjr Pod phase: Pending • Failure [30.431 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 | 0xc42059b980>: { 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.218 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.225 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 ------------------------------ Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T21:06:03.321710Z 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:06:10 http: TLS handshake error from 10.244.1.1:52814: EOF 2018/08/03 21:06:20 http: TLS handshake error from 10.244.1.1:52820: EOF 2018/08/03 21:06:30 http: TLS handshake error from 10.244.1.1:52826: EOF level=info timestamp=2018-08-03T21:06:33.308408Z 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:06:40 http: TLS handshake error from 10.244.1.1:52832: EOF 2018/08/03 21:06:50 http: TLS handshake error from 10.244.1.1:52838: EOF 2018/08/03 21:07:00 http: TLS handshake error from 10.244.1.1:52844: EOF level=info timestamp=2018-08-03T21:07:03.325559Z 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:07:10 http: TLS handshake error from 10.244.1.1:52850: EOF 2018/08/03 21:07:20 http: TLS handshake error from 10.244.1.1:52856: EOF 2018/08/03 21:07:30 http: TLS handshake error from 10.244.1.1:52862: EOF level=info timestamp=2018-08-03T21:07:33.327046Z 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:07:40 http: TLS handshake error from 10.244.1.1:52868: EOF 2018/08/03 21:07:50 http: TLS handshake error from 10.244.1.1:52874: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T21:06:38.502101Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:06:46 http: TLS handshake error from 10.244.0.1:1026: EOF level=info timestamp=2018-08-03T21:06:53.972014Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:06:56 http: TLS handshake error from 10.244.0.1:52486: EOF level=info timestamp=2018-08-03T21:06:57.059694Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:07:06 http: TLS handshake error from 10.244.0.1:52510: EOF 2018/08/03 21:07:16 http: TLS handshake error from 10.244.0.1:52534: EOF level=info timestamp=2018-08-03T21:07:24.003137Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:07:26 http: TLS handshake error from 10.244.0.1:1027: EOF level=info timestamp=2018-08-03T21:07:27.083258Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:07:36 http: TLS handshake error from 10.244.0.1:52582: EOF level=info timestamp=2018-08-03T21:07:38.503293Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:07:38.504175Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:07:46 http: TLS handshake error from 10.244.0.1:52606: EOF level=info timestamp=2018-08-03T21:07:54.030920Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:02:53.299942Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmimxfs2\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmimxfs2" level=info timestamp=2018-08-03T21:03:23.505142Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmimxfs2\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmimxfs2, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 9674a27f-9760-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmimxfs2" level=info timestamp=2018-08-03T21:03:23.509184Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmimxfs2\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmimxfs2, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 9674a27f-9760-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmimxfs2" level=info timestamp=2018-08-03T21:03:23.684024Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi6sl5d kind= uid=a897d627-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:03:23.684190Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi6sl5d kind= uid=a897d627-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:03:23.746807Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi6sl5d\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi6sl5d" level=info timestamp=2018-08-03T21:03:54.152215Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5mxlw kind= uid=babadd4c-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:03:54.152403Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5mxlw kind= uid=babadd4c-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:03:54.204751Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi5mxlw\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi5mxlw" level=info timestamp=2018-08-03T21:04:24.150482Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi5mxlw\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi5mxlw, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: babadd4c-9760-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi5mxlw" level=info timestamp=2018-08-03T21:04:24.337128Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmidsfp9 kind= uid=ccbe694d-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:04:24.337282Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmidsfp9 kind= uid=ccbe694d-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:04:54.558599Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8tslx kind= uid=dec1fb6d-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:04:54.558726Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8tslx kind= uid=dec1fb6d-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:04:54.601742Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8tslx\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8tslx" Pod name: virt-handler-2v7vl Pod phase: Running level=info timestamp=2018-08-03T21:00:19.712946Z pos=virt-handler.go:89 component=virt-handler hostname=node02 level=info timestamp=2018-08-03T21:00:19.722740Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:00:20.825151Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T21:00:20.826118Z pos=health.go:55 component=virt-handler 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:00:20.829461Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:02:09.536559Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:14.277211Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:25.561895Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:32.559054Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:06:54.238481Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=info timestamp=2018-08-03T21:00:26.766069Z pos=virt-handler.go:89 component=virt-handler hostname=node01 level=info timestamp=2018-08-03T21:00:26.913877Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:00:27.019262Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=info timestamp=2018-08-03T21:00:27.040666Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:00:27.024258Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:02:14.954498Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:19.694126Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:30.975343Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.967852Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:06:59.645852Z pos=health.go:55 component=virt-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-testvmi8tslx-z84zd Pod phase: Pending • Failure in Spec Setup (BeforeEach) [180.443 seconds] VNC /root/go/src/kubevirt.io/kubevirt/tests/vnc_test.go:46 A new VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vnc_test.go:54 with VNC connection [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/vnc_test.go:62 should allow accessing the VNC device /root/go/src/kubevirt.io/kubevirt/tests/vnc_test.go:64 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T21:04:54.946036Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi8tslx kind=VirtualMachineInstance uid=dec1fb6d-9760-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi8tslx-z84zd" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T21:09:03.342168Z 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:09:10 http: TLS handshake error from 10.244.1.1:52922: EOF 2018/08/03 21:09:20 http: TLS handshake error from 10.244.1.1:52928: EOF 2018/08/03 21:09:30 http: TLS handshake error from 10.244.1.1:52934: EOF level=info timestamp=2018-08-03T21:09:33.334632Z 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:09:40 http: TLS handshake error from 10.244.1.1:52940: EOF 2018/08/03 21:09:50 http: TLS handshake error from 10.244.1.1:52946: EOF 2018/08/03 21:10:00 http: TLS handshake error from 10.244.1.1:52952: EOF level=info timestamp=2018-08-03T21:10:03.321628Z 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:10:10 http: TLS handshake error from 10.244.1.1:52958: EOF 2018/08/03 21:10:20 http: TLS handshake error from 10.244.1.1:52964: EOF 2018/08/03 21:10:30 http: TLS handshake error from 10.244.1.1:52970: EOF level=info timestamp=2018-08-03T21:10:33.310703Z 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:10:40 http: TLS handshake error from 10.244.1.1:52976: EOF 2018/08/03 21:10:50 http: TLS handshake error from 10.244.1.1:52982: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running 2018/08/03 21:09:36 http: TLS handshake error from 10.244.0.1:52870: EOF level=info timestamp=2018-08-03T21:09:38.505436Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:09:38.506641Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:09:46 http: TLS handshake error from 10.244.0.1:52894: EOF level=info timestamp=2018-08-03T21:09:54.150437Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:09:56 http: TLS handshake error from 10.244.0.1:52918: EOF level=info timestamp=2018-08-03T21:09:57.222346Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:10:06 http: TLS handshake error from 10.244.0.1:1030: EOF 2018/08/03 21:10:16 http: TLS handshake error from 10.244.0.1:52966: EOF level=info timestamp=2018-08-03T21:10:24.177484Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:10:26 http: TLS handshake error from 10.244.0.1:52990: EOF level=info timestamp=2018-08-03T21:10:27.247855Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:10:36 http: TLS handshake error from 10.244.0.1:1031: EOF 2018/08/03 21:10:46 http: TLS handshake error from 10.244.0.1:53038: EOF level=info timestamp=2018-08-03T21:10:54.207197Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:03:23.509184Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmimxfs2\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmimxfs2, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 9674a27f-9760-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmimxfs2" level=info timestamp=2018-08-03T21:03:23.684024Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi6sl5d kind= uid=a897d627-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:03:23.684190Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi6sl5d kind= uid=a897d627-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:03:23.746807Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi6sl5d\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi6sl5d" level=info timestamp=2018-08-03T21:03:54.152215Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5mxlw kind= uid=babadd4c-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:03:54.152403Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5mxlw kind= uid=babadd4c-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:03:54.204751Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi5mxlw\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi5mxlw" level=info timestamp=2018-08-03T21:04:24.150482Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi5mxlw\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi5mxlw, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: babadd4c-9760-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi5mxlw" level=info timestamp=2018-08-03T21:04:24.337128Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmidsfp9 kind= uid=ccbe694d-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:04:24.337282Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmidsfp9 kind= uid=ccbe694d-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:04:54.558599Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8tslx kind= uid=dec1fb6d-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:04:54.558726Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8tslx kind= uid=dec1fb6d-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:04:54.601742Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8tslx\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8tslx" level=info timestamp=2018-08-03T21:07:54.997023Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihgwp4 kind= uid=4a4f2995-9761-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:07:54.997193Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihgwp4 kind= uid=4a4f2995-9761-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-2v7vl Pod phase: Running level=info timestamp=2018-08-03T21:00:19.712946Z pos=virt-handler.go:89 component=virt-handler hostname=node02 level=info timestamp=2018-08-03T21:00:19.722740Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:00:20.825151Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T21:00:20.826118Z pos=health.go:55 component=virt-handler 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:00:20.829461Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:02:09.536559Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:14.277211Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:25.561895Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:32.559054Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:06:54.238481Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:08:31.350488Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.947835Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=info timestamp=2018-08-03T21:00:26.766069Z pos=virt-handler.go:89 component=virt-handler hostname=node01 level=info timestamp=2018-08-03T21:00:26.913877Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:00:27.019262Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=info timestamp=2018-08-03T21:00:27.040666Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:00:27.024258Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:02:14.954498Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:19.694126Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:30.975343Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.967852Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:06:59.645852Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:08:36.752066Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.356549Z pos=health.go:55 component=virt-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-testvmihgwp4-dp2ld Pod phase: Pending • Failure in Spec Setup (BeforeEach) [180.435 seconds] VNC /root/go/src/kubevirt.io/kubevirt/tests/vnc_test.go:46 A new VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vnc_test.go:54 should upgrade subresource connections if an origin header is given [BeforeEach] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 for vnc /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T21:07:55.372895Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmihgwp4 kind=VirtualMachineInstance uid=4a4f2995-9761-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmihgwp4-dp2ld" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T21:12:03.332806Z 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:12:10 http: TLS handshake error from 10.244.1.1:53030: EOF 2018/08/03 21:12:20 http: TLS handshake error from 10.244.1.1:53036: EOF 2018/08/03 21:12:30 http: TLS handshake error from 10.244.1.1:53042: EOF level=info timestamp=2018-08-03T21:12:33.343558Z 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:12:40 http: TLS handshake error from 10.244.1.1:53048: EOF 2018/08/03 21:12:50 http: TLS handshake error from 10.244.1.1:53054: EOF 2018/08/03 21:13:00 http: TLS handshake error from 10.244.1.1:53060: EOF level=info timestamp=2018-08-03T21:13:03.345747Z 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:13:10 http: TLS handshake error from 10.244.1.1:53066: EOF 2018/08/03 21:13:20 http: TLS handshake error from 10.244.1.1:53072: EOF 2018/08/03 21:13:30 http: TLS handshake error from 10.244.1.1:53078: EOF level=info timestamp=2018-08-03T21:13:33.347851Z 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:13:40 http: TLS handshake error from 10.244.1.1:53084: EOF 2018/08/03 21:13:50 http: TLS handshake error from 10.244.1.1:53090: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running 2018/08/03 21:12:36 http: TLS handshake error from 10.244.0.1:53302: EOF level=info timestamp=2018-08-03T21:12:38.434721Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:12:38.435797Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:12:46 http: TLS handshake error from 10.244.0.1:53326: EOF level=info timestamp=2018-08-03T21:12:54.330576Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:12:56 http: TLS handshake error from 10.244.0.1:53350: EOF level=info timestamp=2018-08-03T21:12:57.399174Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:13:06 http: TLS handshake error from 10.244.0.1:53374: EOF 2018/08/03 21:13:16 http: TLS handshake error from 10.244.0.1:53398: EOF level=info timestamp=2018-08-03T21:13:24.361415Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:13:26 http: TLS handshake error from 10.244.0.1:53422: EOF level=info timestamp=2018-08-03T21:13:27.429874Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:13:36 http: TLS handshake error from 10.244.0.1:53446: EOF 2018/08/03 21:13:46 http: TLS handshake error from 10.244.0.1:53470: EOF level=info timestamp=2018-08-03T21:13:54.392493Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:03:23.746807Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi6sl5d\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi6sl5d" level=info timestamp=2018-08-03T21:03:54.152215Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5mxlw kind= uid=babadd4c-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:03:54.152403Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5mxlw kind= uid=babadd4c-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:03:54.204751Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi5mxlw\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi5mxlw" level=info timestamp=2018-08-03T21:04:24.150482Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi5mxlw\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi5mxlw, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: babadd4c-9760-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi5mxlw" level=info timestamp=2018-08-03T21:04:24.337128Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmidsfp9 kind= uid=ccbe694d-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:04:24.337282Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmidsfp9 kind= uid=ccbe694d-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:04:54.558599Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8tslx kind= uid=dec1fb6d-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:04:54.558726Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8tslx kind= uid=dec1fb6d-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:04:54.601742Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8tslx\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8tslx" level=info timestamp=2018-08-03T21:07:54.997023Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihgwp4 kind= uid=4a4f2995-9761-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:07:54.997193Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihgwp4 kind= uid=4a4f2995-9761-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:10:55.252816Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmihgwp4\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmihgwp4, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 4a4f2995-9761-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmihgwp4" level=info timestamp=2018-08-03T21:10:55.437697Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmicjl4l kind= uid=b5dc1da0-9761-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:10:55.437845Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmicjl4l kind= uid=b5dc1da0-9761-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-2v7vl Pod phase: Running level=info timestamp=2018-08-03T21:00:19.712946Z pos=virt-handler.go:89 component=virt-handler hostname=node02 level=info timestamp=2018-08-03T21:00:19.722740Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:00:20.825151Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=error timestamp=2018-08-03T21:00:20.826118Z pos=health.go:55 component=virt-handler 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:00:20.829461Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:02:09.536559Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:14.277211Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:25.561895Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:32.559054Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:06:54.238481Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:08:31.350488Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.947835Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:03.720273Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.119687Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=info timestamp=2018-08-03T21:00:26.766069Z pos=virt-handler.go:89 component=virt-handler hostname=node01 level=info timestamp=2018-08-03T21:00:26.913877Z pos=virtinformers.go:107 component=virt-handler msg="STARTING informer configMapInformer" level=info timestamp=2018-08-03T21:00:27.019262Z pos=vm.go:208 component=virt-handler msg="Starting virt-handler controller." level=info timestamp=2018-08-03T21:00:27.040666Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:00:27.024258Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:02:14.954498Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:19.694126Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:30.975343Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.967852Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:06:59.645852Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:08:36.752066Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.356549Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:09.130061Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.522467Z pos=health.go:55 component=virt-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-testvmicjl4l-5mltg Pod phase: Pending • Failure in Spec Setup (BeforeEach) [180.444 seconds] VNC /root/go/src/kubevirt.io/kubevirt/tests/vnc_test.go:46 A new VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vnc_test.go:54 should upgrade subresource connections if an origin header is given [BeforeEach] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 for serial console /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.005s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T21:10:55.812535Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmicjl4l kind=VirtualMachineInstance uid=b5dc1da0-9761-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmicjl4l-5mltg" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T21:18:03.331083Z 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:18:10 http: TLS handshake error from 10.244.1.1:53246: EOF 2018/08/03 21:18:20 http: TLS handshake error from 10.244.1.1:53252: EOF 2018/08/03 21:18:30 http: TLS handshake error from 10.244.1.1:53258: EOF level=info timestamp=2018-08-03T21:18:33.333577Z 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:18:40 http: TLS handshake error from 10.244.1.1:53264: EOF 2018/08/03 21:18:50 http: TLS handshake error from 10.244.1.1:53270: EOF 2018/08/03 21:19:00 http: TLS handshake error from 10.244.1.1:53276: EOF level=info timestamp=2018-08-03T21:19:03.343555Z 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:19:10 http: TLS handshake error from 10.244.1.1:53282: EOF 2018/08/03 21:19:20 http: TLS handshake error from 10.244.1.1:53288: EOF 2018/08/03 21:19:30 http: TLS handshake error from 10.244.1.1:53294: EOF level=info timestamp=2018-08-03T21:19:33.344137Z 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:19:40 http: TLS handshake error from 10.244.1.1:53300: EOF 2018/08/03 21:19:50 http: TLS handshake error from 10.244.1.1:53306: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running 2018/08/03 21:18:36 http: TLS handshake error from 10.244.0.1:54166: EOF 2018/08/03 21:18:46 http: TLS handshake error from 10.244.0.1:54190: EOF level=info timestamp=2018-08-03T21:18:54.697369Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:18:56 http: TLS handshake error from 10.244.0.1:54214: EOF level=info timestamp=2018-08-03T21:18:57.748449Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:19:06 http: TLS handshake error from 10.244.0.1:54238: EOF 2018/08/03 21:19:16 http: TLS handshake error from 10.244.0.1:54262: EOF level=info timestamp=2018-08-03T21:19:24.733431Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:19:26 http: TLS handshake error from 10.244.0.1:54286: EOF level=info timestamp=2018-08-03T21:19:27.775878Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:19:36 http: TLS handshake error from 10.244.0.1:54310: EOF level=info timestamp=2018-08-03T21:19:38.395365Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:19:38.396329Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:19:46 http: TLS handshake error from 10.244.0.1:54334: EOF level=info timestamp=2018-08-03T21:19:54.769632Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:03:54.152403Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5mxlw kind= uid=babadd4c-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:03:54.204751Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi5mxlw\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi5mxlw" level=info timestamp=2018-08-03T21:04:24.150482Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi5mxlw\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi5mxlw, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: babadd4c-9760-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi5mxlw" level=info timestamp=2018-08-03T21:04:24.337128Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmidsfp9 kind= uid=ccbe694d-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:04:24.337282Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmidsfp9 kind= uid=ccbe694d-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:04:54.558599Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8tslx kind= uid=dec1fb6d-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:04:54.558726Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8tslx kind= uid=dec1fb6d-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:04:54.601742Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8tslx\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8tslx" level=info timestamp=2018-08-03T21:07:54.997023Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihgwp4 kind= uid=4a4f2995-9761-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:07:54.997193Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihgwp4 kind= uid=4a4f2995-9761-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:10:55.252816Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmihgwp4\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmihgwp4, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 4a4f2995-9761-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmihgwp4" level=info timestamp=2018-08-03T21:10:55.437697Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmicjl4l kind= uid=b5dc1da0-9761-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:10:55.437845Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmicjl4l kind= uid=b5dc1da0-9761-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:13:55.877968Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixjxwd kind= uid=21691a02-9762-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:13:55.878155Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixjxwd kind= uid=21691a02-9762-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:00:20.826118Z pos=health.go:55 component=virt-handler 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:00:20.829461Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:02:09.536559Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:14.277211Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:25.561895Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:32.559054Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:06:54.238481Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:08:31.350488Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.947835Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:03.720273Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.119687Z pos=health.go:55 component=virt-handler reason="tun device does not 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:45.235913Z pos=health.go:55 component=virt-handler reason="tun device does not 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:34.143836Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:48.788121Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.894111Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=info timestamp=2018-08-03T21:00:27.040666Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:00:27.024258Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:02:14.954498Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:19.694126Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:30.975343Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.967852Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:06:59.645852Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:08:36.752066Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.356549Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:09.130061Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.522467Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.636725Z pos=health.go:55 component=virt-handler reason="tun device does not 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:39.542878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:54.185448Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.285186Z pos=health.go:55 component=virt-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-testvmixjxwd-8hvj6 Pod phase: Pending • Failure [360.442 seconds] RegistryDisk /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:41 Starting and stopping the same VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:90 with ephemeral registry disk /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:91 should success multiple times [It] /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:92 Timed out after 180.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1034 ------------------------------ STEP: Starting the VirtualMachineInstance level=info timestamp=2018-08-03T21:13:56.308041Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmixjxwd kind=VirtualMachineInstance uid=21691a02-9762-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmixjxwd-8hvj6" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running 2018/08/03 21:20:20 http: TLS handshake error from 10.244.1.1:53324: EOF 2018/08/03 21:20:30 http: TLS handshake error from 10.244.1.1:53330: EOF level=info timestamp=2018-08-03T21:20:33.346977Z 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:20:40 http: TLS handshake error from 10.244.1.1:53336: EOF 2018/08/03 21:20:50 http: TLS handshake error from 10.244.1.1:53342: EOF 2018/08/03 21:21:00 http: TLS handshake error from 10.244.1.1:53348: EOF level=info timestamp=2018-08-03T21:21:03.345817Z 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:21:10 http: TLS handshake error from 10.244.1.1:53354: EOF 2018/08/03 21:21:20 http: TLS handshake error from 10.244.1.1:53360: EOF 2018/08/03 21:21:30 http: TLS handshake error from 10.244.1.1:53366: EOF level=info timestamp=2018-08-03T21:21:33.278424Z 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:21:33.295965Z 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:21:33.317064Z 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:21:40 http: TLS handshake error from 10.244.1.1:53372: EOF 2018/08/03 21:21:50 http: TLS handshake error from 10.244.1.1:53378: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running 2018/08/03 21:20:46 http: TLS handshake error from 10.244.0.1:54478: EOF level=info timestamp=2018-08-03T21:20:54.831132Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:20:56 http: TLS handshake error from 10.244.0.1:54502: EOF level=info timestamp=2018-08-03T21:20:57.870083Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:21:06 http: TLS handshake error from 10.244.0.1:54526: EOF 2018/08/03 21:21:16 http: TLS handshake error from 10.244.0.1:54550: EOF level=info timestamp=2018-08-03T21:21:24.864538Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:21:26 http: TLS handshake error from 10.244.0.1:54574: EOF level=info timestamp=2018-08-03T21:21:27.898641Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:21:36 http: TLS handshake error from 10.244.0.1:54598: EOF level=info timestamp=2018-08-03T21:21:38.401715Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:21:38.402514Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:21:46 http: TLS handshake error from 10.244.0.1:54622: EOF level=info timestamp=2018-08-03T21:21:54.894524Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:21:56 http: TLS handshake error from 10.244.0.1:54646: EOF Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:04:24.150482Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi5mxlw\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi5mxlw, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: babadd4c-9760-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi5mxlw" level=info timestamp=2018-08-03T21:04:24.337128Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmidsfp9 kind= uid=ccbe694d-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:04:24.337282Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmidsfp9 kind= uid=ccbe694d-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:04:54.558599Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8tslx kind= uid=dec1fb6d-9760-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:04:54.558726Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi8tslx kind= uid=dec1fb6d-9760-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:04:54.601742Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi8tslx\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi8tslx" level=info timestamp=2018-08-03T21:07:54.997023Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihgwp4 kind= uid=4a4f2995-9761-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:07:54.997193Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihgwp4 kind= uid=4a4f2995-9761-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:10:55.252816Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmihgwp4\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmihgwp4, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 4a4f2995-9761-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmihgwp4" level=info timestamp=2018-08-03T21:10:55.437697Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmicjl4l kind= uid=b5dc1da0-9761-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:10:55.437845Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmicjl4l kind= uid=b5dc1da0-9761-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:13:55.877968Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixjxwd kind= uid=21691a02-9762-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:13:55.878155Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixjxwd kind= uid=21691a02-9762-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:19:56.322497Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifnxtb kind= uid=f8408712-9762-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:19:56.322658Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifnxtb kind= uid=f8408712-9762-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-2v7vl Pod phase: Running level=info timestamp=2018-08-03T21:00:20.829461Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains" level=error timestamp=2018-08-03T21:02:09.536559Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:14.277211Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:25.561895Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:32.559054Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:06:54.238481Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:08:31.350488Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.947835Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:03.720273Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.119687Z pos=health.go:55 component=virt-handler reason="tun device does not 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:45.235913Z pos=health.go:55 component=virt-handler reason="tun device does not 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:34.143836Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:48.788121Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.894111Z pos=health.go:55 component=virt-handler reason="tun device does not 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:32.008911Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:00:27.024258Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:02:14.954498Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:19.694126Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:30.975343Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.967852Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:06:59.645852Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:08:36.752066Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.356549Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:09.130061Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.522467Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.636725Z pos=health.go:55 component=virt-handler reason="tun device does not 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:39.542878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:54.185448Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.285186Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.395483Z pos=health.go:55 component=virt-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-testvmifnxtb-vhhvf Pod phase: Pending • Failure [120.440 seconds] RegistryDisk /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:41 Starting a VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:111 with ephemeral registry disk /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:112 should not modify the spec on status update [It] /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:113 Timed out after 60.003s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1034 ------------------------------ STEP: Starting the VirtualMachineInstance level=info timestamp=2018-08-03T21:19:56.700755Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmifnxtb kind=VirtualMachineInstance uid=f8408712-9762-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmifnxtb-vhhvf" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running 2018/08/03 21:21:20 http: TLS handshake error from 10.244.1.1:53360: EOF 2018/08/03 21:21:30 http: TLS handshake error from 10.244.1.1:53366: EOF level=info timestamp=2018-08-03T21:21:33.278424Z 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:21:33.295965Z 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:21:33.317064Z 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:21:40 http: TLS handshake error from 10.244.1.1:53372: EOF 2018/08/03 21:21:50 http: TLS handshake error from 10.244.1.1:53378: EOF 2018/08/03 21:22:00 http: TLS handshake error from 10.244.1.1:53384: EOF level=info timestamp=2018-08-03T21:22:03.346996Z 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:22:10 http: TLS handshake error from 10.244.1.1:53390: EOF 2018/08/03 21:22:20 http: TLS handshake error from 10.244.1.1:53396: EOF 2018/08/03 21:22:30 http: TLS handshake error from 10.244.1.1:53402: EOF level=info timestamp=2018-08-03T21:22:33.334383Z 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:22:40 http: TLS handshake error from 10.244.1.1:53408: EOF 2018/08/03 21:22:50 http: TLS handshake error from 10.244.1.1:53414: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running 2018/08/03 21:21:46 http: TLS handshake error from 10.244.0.1:54622: EOF level=info timestamp=2018-08-03T21:21:54.894524Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:21:56 http: TLS handshake error from 10.244.0.1:54646: EOF level=info timestamp=2018-08-03T21:21:57.933456Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:22:06 http: TLS handshake error from 10.244.0.1:54670: EOF 2018/08/03 21:22:16 http: TLS handshake error from 10.244.0.1:54694: EOF level=info timestamp=2018-08-03T21:22:24.926085Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:22:26 http: TLS handshake error from 10.244.0.1:54718: EOF level=info timestamp=2018-08-03T21:22:27.960033Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:22:36 http: TLS handshake error from 10.244.0.1:54742: EOF level=info timestamp=2018-08-03T21:22:38.403634Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:22:38.404737Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:22:46 http: TLS handshake error from 10.244.0.1:54766: EOF level=info timestamp=2018-08-03T21:22:54.957196Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:22:56 http: TLS handshake error from 10.244.0.1:54790: EOF Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:10:55.437845Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmicjl4l kind= uid=b5dc1da0-9761-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:13:55.877968Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixjxwd kind= uid=21691a02-9762-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:13:55.878155Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixjxwd kind= uid=21691a02-9762-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:19:56.322497Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifnxtb kind= uid=f8408712-9762-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:19:56.322658Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifnxtb kind= uid=f8408712-9762-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:56.760844Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirb7vz kind= uid=4009f527-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.760990Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirb7vz kind= uid=4009f527-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:56.771052Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi6848m kind= uid=400b9329-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.771107Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi6848m kind= uid=400b9329-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:56.799437Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqwllw kind= uid=400de131-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.799533Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqwllw kind= uid=400de131-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:56.820887Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih7kxd kind= uid=4010e29f-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.820957Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih7kxd kind= uid=4010e29f-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:56.841947Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivgf8x kind= uid=4014424f-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.842052Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivgf8x kind= uid=4014424f-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:02:09.536559Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:14.277211Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:25.561895Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:32.559054Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:06:54.238481Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:08:31.350488Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.947835Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:03.720273Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.119687Z pos=health.go:55 component=virt-handler reason="tun device does not 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:45.235913Z pos=health.go:55 component=virt-handler reason="tun device does not 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:34.143836Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:48.788121Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.894111Z pos=health.go:55 component=virt-handler reason="tun device does not 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:32.008911Z pos=health.go:55 component=virt-handler reason="tun device does not 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:53.130481Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:00:27.024258Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:02:14.954498Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:03:19.694126Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:30.975343Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.967852Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:06:59.645852Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:08:36.752066Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.356549Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:09.130061Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.522467Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.636725Z pos=health.go:55 component=virt-handler reason="tun device does not 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:39.542878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:54.185448Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.285186Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.395483Z pos=health.go:55 component=virt-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-testvmi6848m-kscp4 Pod phase: Pending Pod name: virt-launcher-testvmih7kxd-vspzj Pod phase: Pending Pod name: virt-launcher-testvmiqwllw-s5ktn Pod phase: Pending Pod name: virt-launcher-testvmirb7vz-q6tdb Pod phase: Pending Pod name: virt-launcher-testvmivgf8x-j7fmz Pod phase: Pending • Failure [61.333 seconds] RegistryDisk /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:41 Starting multiple VMIs /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:129 with ephemeral registry disk /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:130 should success [It] /root/go/src/kubevirt.io/kubevirt/tests/registry_disk_test.go:131 Timed out after 30.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1030 ------------------------------ STEP: Starting a VirtualMachineInstance STEP: Starting a VirtualMachineInstance STEP: Starting a VirtualMachineInstance STEP: Starting a VirtualMachineInstance STEP: Starting a VirtualMachineInstance level=info timestamp=2018-08-03T21:21:57.214167Z pos=utils.go:255 component=tests namespace=kubevirt-test-default name=testvmirb7vz kind=VirtualMachineInstance uid=4009f527-9763-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmirb7vz-q6tdb" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T21:24:03.349924Z 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:24:10 http: TLS handshake error from 10.244.1.1:53462: EOF 2018/08/03 21:24:20 http: TLS handshake error from 10.244.1.1:53468: EOF 2018/08/03 21:24:30 http: TLS handshake error from 10.244.1.1:53474: EOF level=info timestamp=2018-08-03T21:24:33.370911Z 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:24:40 http: TLS handshake error from 10.244.1.1:53480: EOF 2018/08/03 21:24:50 http: TLS handshake error from 10.244.1.1:53486: EOF 2018/08/03 21:25:00 http: TLS handshake error from 10.244.1.1:53492: EOF level=info timestamp=2018-08-03T21:25:03.330904Z 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:25:10 http: TLS handshake error from 10.244.1.1:53498: EOF 2018/08/03 21:25:20 http: TLS handshake error from 10.244.1.1:53504: EOF 2018/08/03 21:25:30 http: TLS handshake error from 10.244.1.1:53510: EOF level=info timestamp=2018-08-03T21:25:33.343672Z 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:25:40 http: TLS handshake error from 10.244.1.1:53516: EOF 2018/08/03 21:25:50 http: TLS handshake error from 10.244.1.1:53522: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T21:24:38.407612Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:24:46 http: TLS handshake error from 10.244.0.1:55054: EOF level=info timestamp=2018-08-03T21:24:55.092637Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:24:56 http: TLS handshake error from 10.244.0.1:55078: EOF level=info timestamp=2018-08-03T21:24:58.100333Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:25:06 http: TLS handshake error from 10.244.0.1:55102: EOF 2018/08/03 21:25:16 http: TLS handshake error from 10.244.0.1:55126: EOF level=info timestamp=2018-08-03T21:25:25.135956Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:25:26 http: TLS handshake error from 10.244.0.1:55150: EOF level=info timestamp=2018-08-03T21:25:28.131598Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:25:36 http: TLS handshake error from 10.244.0.1:55174: EOF 2018/08/03 21:25:46 http: TLS handshake error from 10.244.0.1:55198: EOF level=info timestamp=2018-08-03T21:25:55.164510Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:25:56 http: TLS handshake error from 10.244.0.1:55222: EOF level=info timestamp=2018-08-03T21:25:58.157366Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:13:55.878155Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixjxwd kind= uid=21691a02-9762-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:19:56.322497Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifnxtb kind= uid=f8408712-9762-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:19:56.322658Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifnxtb kind= uid=f8408712-9762-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:56.760844Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirb7vz kind= uid=4009f527-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.760990Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirb7vz kind= uid=4009f527-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:56.771052Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi6848m kind= uid=400b9329-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.771107Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi6848m kind= uid=400b9329-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:56.799437Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqwllw kind= uid=400de131-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.799533Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqwllw kind= uid=400de131-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:56.820887Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih7kxd kind= uid=4010e29f-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.820957Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih7kxd kind= uid=4010e29f-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:56.841947Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivgf8x kind= uid=4014424f-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.842052Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivgf8x kind= uid=4014424f-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:22:58.699157Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihwkz8 kind= uid=64f47249-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:22:58.699299Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihwkz8 kind= uid=64f47249-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:03:14.277211Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:25.561895Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:32.559054Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:06:54.238481Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:08:31.350488Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.947835Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:03.720273Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.119687Z pos=health.go:55 component=virt-handler reason="tun device does not 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:45.235913Z pos=health.go:55 component=virt-handler reason="tun device does not 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:34.143836Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:48.788121Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.894111Z pos=health.go:55 component=virt-handler reason="tun device does not 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:32.008911Z pos=health.go:55 component=virt-handler reason="tun device does not 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:53.130481Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.333789Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:03:19.694126Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:04:30.975343Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:05:37.967852Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:06:59.645852Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:08:36.752066Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.356549Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:09.130061Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.522467Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.636725Z pos=health.go:55 component=virt-handler reason="tun device does not 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:39.542878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:54.185448Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.285186Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.395483Z pos=health.go:55 component=virt-handler reason="tun device does not 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:58.508118Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.708179Z pos=health.go:55 component=virt-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-testvmihwkz8-q92zj Pod phase: Pending • Failure [181.039 seconds] CloudInit UserData /root/go/src/kubevirt.io/kubevirt/tests/vmi_userdata_test.go:46 A new VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_userdata_test.go:80 with cloudInitNoCloud userDataBase64 source /root/go/src/kubevirt.io/kubevirt/tests/vmi_userdata_test.go:81 should have cloud-init data [It] /root/go/src/kubevirt.io/kubevirt/tests/vmi_userdata_test.go:82 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ STEP: Starting a VirtualMachineInstance STEP: Waiting the VirtualMachineInstance start level=info timestamp=2018-08-03T21:22:59.140284Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmihwkz8 kind=VirtualMachineInstance uid=64f47249-9763-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmihwkz8-q92zj" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T21:27:03.321071Z 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:10 http: TLS handshake error from 10.244.1.1:53570: EOF 2018/08/03 21:27:20 http: TLS handshake error from 10.244.1.1:53576: EOF 2018/08/03 21:27:30 http: TLS handshake error from 10.244.1.1:53582: EOF level=info timestamp=2018-08-03T21:27:33.320242Z 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:40 http: TLS handshake error from 10.244.1.1:53588: EOF 2018/08/03 21:27:50 http: TLS handshake error from 10.244.1.1:53594: EOF 2018/08/03 21:28:00 http: TLS handshake error from 10.244.1.1:53600: EOF level=info timestamp=2018-08-03T21:28:03.336109Z 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:28:10 http: TLS handshake error from 10.244.1.1:53606: EOF 2018/08/03 21:28:20 http: TLS handshake error from 10.244.1.1:53612: EOF 2018/08/03 21:28:30 http: TLS handshake error from 10.244.1.1:53618: EOF level=info timestamp=2018-08-03T21:28:33.357249Z 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:28:40 http: TLS handshake error from 10.244.1.1:53624: EOF 2018/08/03 21:28:50 http: TLS handshake error from 10.244.1.1:53630: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T21:27:38.395337Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:27:46 http: TLS handshake error from 10.244.0.1:55486: EOF level=info timestamp=2018-08-03T21:27:55.287794Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:27:56 http: TLS handshake error from 10.244.0.1:55510: EOF level=info timestamp=2018-08-03T21:27:58.281871Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:28:06 http: TLS handshake error from 10.244.0.1:55534: EOF 2018/08/03 21:28:16 http: TLS handshake error from 10.244.0.1:55558: EOF level=info timestamp=2018-08-03T21:28:25.311822Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:28:26 http: TLS handshake error from 10.244.0.1:55582: EOF level=info timestamp=2018-08-03T21:28:28.309149Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:28:36 http: TLS handshake error from 10.244.0.1:55606: EOF 2018/08/03 21:28:46 http: TLS handshake error from 10.244.0.1:55630: EOF level=info timestamp=2018-08-03T21:28:55.336303Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:28:56 http: TLS handshake error from 10.244.0.1:55654: EOF level=info timestamp=2018-08-03T21:28:58.339793Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:21:56.760844Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirb7vz kind= uid=4009f527-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.760990Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirb7vz kind= uid=4009f527-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:56.771052Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi6848m kind= uid=400b9329-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.771107Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi6848m kind= uid=400b9329-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:56.799437Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqwllw kind= uid=400de131-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.799533Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqwllw kind= uid=400de131-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:56.820887Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih7kxd kind= uid=4010e29f-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.820957Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih7kxd kind= uid=4010e29f-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:56.841947Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivgf8x kind= uid=4014424f-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.842052Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivgf8x kind= uid=4014424f-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:22:58.699157Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihwkz8 kind= uid=64f47249-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:22:58.699299Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihwkz8 kind= uid=64f47249-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:25:59.132672Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim5jbf kind= uid=d0811b05-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:25:59.132855Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim5jbf kind= uid=d0811b05-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:25:59.179087Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmim5jbf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmim5jbf" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:05:32.559054Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:06:54.238481Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:08:31.350488Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.947835Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:03.720273Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.119687Z pos=health.go:55 component=virt-handler reason="tun device does not 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:45.235913Z pos=health.go:55 component=virt-handler reason="tun device does not 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:34.143836Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:48.788121Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.894111Z pos=health.go:55 component=virt-handler reason="tun device does not 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:32.008911Z pos=health.go:55 component=virt-handler reason="tun device does not 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:53.130481Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.333789Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:49.653880Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:39.835572Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:05:37.967852Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:06:59.645852Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:08:36.752066Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.356549Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:09.130061Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.522467Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.636725Z pos=health.go:55 component=virt-handler reason="tun device does not 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:39.542878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:54.185448Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.285186Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.395483Z pos=health.go:55 component=virt-handler reason="tun device does not 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:58.508118Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.708179Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:55.023095Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:45.196978Z pos=health.go:55 component=virt-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-testvmim5jbf-4r8mv Pod phase: Pending • Failure [180.449 seconds] CloudInit UserData /root/go/src/kubevirt.io/kubevirt/tests/vmi_userdata_test.go:46 A new VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_userdata_test.go:80 with cloudInitNoCloud userDataBase64 source /root/go/src/kubevirt.io/kubevirt/tests/vmi_userdata_test.go:81 with injected ssh-key /root/go/src/kubevirt.io/kubevirt/tests/vmi_userdata_test.go:92 should have ssh-key under authorized keys [It] /root/go/src/kubevirt.io/kubevirt/tests/vmi_userdata_test.go:93 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ STEP: Starting a VirtualMachineInstance STEP: Waiting the VirtualMachineInstance start level=info timestamp=2018-08-03T21:25:59.576667Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmim5jbf kind=VirtualMachineInstance uid=d0811b05-9763-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmim5jbf-4r8mv" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running 2018/08/03 21:30:20 http: TLS handshake error from 10.244.1.1:53684: EOF 2018/08/03 21:30:30 http: TLS handshake error from 10.244.1.1:53690: EOF level=info timestamp=2018-08-03T21:30:33.354983Z 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:40 http: TLS handshake error from 10.244.1.1:53696: EOF 2018/08/03 21:30:50 http: TLS handshake error from 10.244.1.1:53702: EOF 2018/08/03 21:31:00 http: TLS handshake error from 10.244.1.1:53708: EOF level=info timestamp=2018-08-03T21:31:03.322059Z 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:31:10 http: TLS handshake error from 10.244.1.1:53714: EOF 2018/08/03 21:31:20 http: TLS handshake error from 10.244.1.1:53720: EOF 2018/08/03 21:31:30 http: TLS handshake error from 10.244.1.1:53726: EOF level=info timestamp=2018-08-03T21:31:33.278520Z 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:31:33.295903Z 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:31:33.376929Z 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:31:40 http: TLS handshake error from 10.244.1.1:53732: EOF 2018/08/03 21:31:50 http: TLS handshake error from 10.244.1.1:53738: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T21:30:55.451378Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:30:56 http: TLS handshake error from 10.244.0.1:55942: EOF level=info timestamp=2018-08-03T21:30:58.473964Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:31:06 http: TLS handshake error from 10.244.0.1:55966: EOF 2018/08/03 21:31:16 http: TLS handshake error from 10.244.0.1:55990: EOF level=info timestamp=2018-08-03T21:31:25.499215Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:31:26 http: TLS handshake error from 10.244.0.1:56014: EOF level=info timestamp=2018-08-03T21:31:28.498981Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:31:36 http: TLS handshake error from 10.244.0.1:56038: EOF level=info timestamp=2018-08-03T21:31:38.448990Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:31:38.449979Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:31:46 http: TLS handshake error from 10.244.0.1:56062: EOF level=info timestamp=2018-08-03T21:31:55.531825Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:31:56 http: TLS handshake error from 10.244.0.1:56086: EOF level=info timestamp=2018-08-03T21:31:58.530572Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:21:56.799437Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqwllw kind= uid=400de131-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.799533Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqwllw kind= uid=400de131-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:56.820887Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih7kxd kind= uid=4010e29f-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.820957Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih7kxd kind= uid=4010e29f-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:56.841947Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivgf8x kind= uid=4014424f-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.842052Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivgf8x kind= uid=4014424f-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:22:58.699157Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihwkz8 kind= uid=64f47249-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:22:58.699299Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihwkz8 kind= uid=64f47249-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:25:59.132672Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim5jbf kind= uid=d0811b05-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:25:59.132855Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim5jbf kind= uid=d0811b05-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:25:59.179087Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmim5jbf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmim5jbf" level=info timestamp=2018-08-03T21:28:59.403245Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmim5jbf\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmim5jbf, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: d0811b05-9763-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmim5jbf" level=info timestamp=2018-08-03T21:28:59.585968Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqltdl kind= uid=3c0fd9de-9764-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:28:59.586101Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqltdl kind= uid=3c0fd9de-9764-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:28:59.628791Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiqltdl\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiqltdl" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:08:31.350488Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.947835Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:03.720273Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.119687Z pos=health.go:55 component=virt-handler reason="tun device does not 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:45.235913Z pos=health.go:55 component=virt-handler reason="tun device does not 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:34.143836Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:48.788121Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.894111Z pos=health.go:55 component=virt-handler reason="tun device does not 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:32.008911Z pos=health.go:55 component=virt-handler reason="tun device does not 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:53.130481Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.333789Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:49.653880Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:39.835572Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.891405Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.631127Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:08:36.752066Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.356549Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:12:09.130061Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.522467Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.636725Z pos=health.go:55 component=virt-handler reason="tun device does not 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:39.542878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:54.185448Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.285186Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.395483Z pos=health.go:55 component=virt-handler reason="tun device does not 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:58.508118Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.708179Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:55.023095Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:45.196978Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.247809Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.983248Z pos=health.go:55 component=virt-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-testvmiqltdl-cwzjw Pod phase: Pending • Failure [180.444 seconds] CloudInit UserData /root/go/src/kubevirt.io/kubevirt/tests/vmi_userdata_test.go:46 A new VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_userdata_test.go:80 with cloudInitNoCloud userData source /root/go/src/kubevirt.io/kubevirt/tests/vmi_userdata_test.go:118 should process provided cloud-init data [It] /root/go/src/kubevirt.io/kubevirt/tests/vmi_userdata_test.go:119 Timed out after 90.003s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ STEP: Starting a VirtualMachineInstance STEP: Waiting the VirtualMachineInstance start level=info timestamp=2018-08-03T21:28:59.976991Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmiqltdl kind=VirtualMachineInstance uid=3c0fd9de-9764-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmiqltdl-cwzjw" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T21:33:03.332298Z 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:10 http: TLS handshake error from 10.244.1.1:53786: EOF 2018/08/03 21:33:20 http: TLS handshake error from 10.244.1.1:53792: EOF 2018/08/03 21:33:30 http: TLS handshake error from 10.244.1.1:53798: EOF level=info timestamp=2018-08-03T21:33:33.323548Z 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:40 http: TLS handshake error from 10.244.1.1:53804: EOF 2018/08/03 21:33:50 http: TLS handshake error from 10.244.1.1:53810: EOF 2018/08/03 21:34:00 http: TLS handshake error from 10.244.1.1:53816: EOF level=info timestamp=2018-08-03T21:34:03.323673Z 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:34:10 http: TLS handshake error from 10.244.1.1:53822: EOF 2018/08/03 21:34:20 http: TLS handshake error from 10.244.1.1:53828: EOF 2018/08/03 21:34:30 http: TLS handshake error from 10.244.1.1:53834: EOF level=info timestamp=2018-08-03T21:34:33.350783Z 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:34:40 http: TLS handshake error from 10.244.1.1:53840: EOF 2018/08/03 21:34:50 http: TLS handshake error from 10.244.1.1:53846: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T21:33:55.657418Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:33:56 http: TLS handshake error from 10.244.0.1:56374: EOF level=info timestamp=2018-08-03T21:33:58.658292Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:34:06 http: TLS handshake error from 10.244.0.1:56398: EOF 2018/08/03 21:34:16 http: TLS handshake error from 10.244.0.1:56422: EOF level=info timestamp=2018-08-03T21:34:25.686353Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:34:26 http: TLS handshake error from 10.244.0.1:56446: EOF level=info timestamp=2018-08-03T21:34:28.683287Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:34:36 http: TLS handshake error from 10.244.0.1:56470: EOF level=info timestamp=2018-08-03T21:34:38.454061Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:34:38.455114Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:34:46 http: TLS handshake error from 10.244.0.1:56494: EOF level=info timestamp=2018-08-03T21:34:55.722135Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:34:56 http: TLS handshake error from 10.244.0.1:56518: EOF level=info timestamp=2018-08-03T21:34:58.712660Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:21:56.820887Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih7kxd kind= uid=4010e29f-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.820957Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmih7kxd kind= uid=4010e29f-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:21:56.841947Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivgf8x kind= uid=4014424f-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.842052Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivgf8x kind= uid=4014424f-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:22:58.699157Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihwkz8 kind= uid=64f47249-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:22:58.699299Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihwkz8 kind= uid=64f47249-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:25:59.132672Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim5jbf kind= uid=d0811b05-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:25:59.132855Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim5jbf kind= uid=d0811b05-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:25:59.179087Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmim5jbf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmim5jbf" level=info timestamp=2018-08-03T21:28:59.403245Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmim5jbf\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmim5jbf, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: d0811b05-9763-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmim5jbf" level=info timestamp=2018-08-03T21:28:59.585968Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqltdl kind= uid=3c0fd9de-9764-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:28:59.586101Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqltdl kind= uid=3c0fd9de-9764-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:28:59.628791Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiqltdl\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiqltdl" level=info timestamp=2018-08-03T21:32:00.035853Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikg68m kind= uid=a79e73df-9764-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:32:00.036022Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikg68m kind= uid=a79e73df-9764-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:12:03.720273Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.119687Z pos=health.go:55 component=virt-handler reason="tun device does not 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:45.235913Z pos=health.go:55 component=virt-handler reason="tun device does not 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:34.143836Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:48.788121Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.894111Z pos=health.go:55 component=virt-handler reason="tun device does not 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:32.008911Z pos=health.go:55 component=virt-handler reason="tun device does not 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:53.130481Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.333789Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:49.653880Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:39.835572Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.891405Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.631127Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.862218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:41.604703Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:12:09.130061Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.522467Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.636725Z pos=health.go:55 component=virt-handler reason="tun device does not 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:39.542878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:54.185448Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.285186Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.395483Z pos=health.go:55 component=virt-handler reason="tun device does not 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:58.508118Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.708179Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:55.023095Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:45.196978Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.247809Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.983248Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.211229Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:46.942432Z pos=health.go:55 component=virt-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-testvmikg68m-x5d49 Pod phase: Pending • Failure [180.448 seconds] CloudInit UserData /root/go/src/kubevirt.io/kubevirt/tests/vmi_userdata_test.go:46 A new VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/tests/vmi_userdata_test.go:80 should take user-data from k8s secret [It] /root/go/src/kubevirt.io/kubevirt/tests/vmi_userdata_test.go:162 Timed out after 90.003s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ STEP: Creating a user-data secret STEP: Starting a VirtualMachineInstance STEP: Waiting the VirtualMachineInstance start level=info timestamp=2018-08-03T21:32:00.472531Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmikg68m kind=VirtualMachineInstance uid=a79e73df-9764-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmikg68m-x5d49" • ------------------------------ • [SLOW TEST:5.947 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:5.721 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:5.608 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:5.736 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-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T21:34:33.350783Z 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:34:40 http: TLS handshake error from 10.244.1.1:53840: EOF 2018/08/03 21:34:50 http: TLS handshake error from 10.244.1.1:53846: EOF 2018/08/03 21:35:00 http: TLS handshake error from 10.244.1.1:53852: EOF level=info timestamp=2018-08-03T21:35:03.353102Z 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:35:10 http: TLS handshake error from 10.244.1.1:53858: EOF 2018/08/03 21:35:20 http: TLS handshake error from 10.244.1.1:53864: EOF 2018/08/03 21:35:30 http: TLS handshake error from 10.244.1.1:53870: EOF level=info timestamp=2018-08-03T21:35:33.360993Z 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:35:40 http: TLS handshake error from 10.244.1.1:53876: EOF 2018/08/03 21:35:50 http: TLS handshake error from 10.244.1.1:53882: EOF 2018/08/03 21:36:00 http: TLS handshake error from 10.244.1.1:53888: EOF level=info timestamp=2018-08-03T21:36:03.345921Z 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:10 http: TLS handshake error from 10.244.1.1:53894: EOF 2018/08/03 21:36:20 http: TLS handshake error from 10.244.1.1:53900: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T21:35:23.200564Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:35:23.208937Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:35:23.369160Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:35:23.378312Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:35:23.385997Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:35:25.750961Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:35:26 http: TLS handshake error from 10.244.0.1:56590: EOF level=info timestamp=2018-08-03T21:35:28.746781Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:35:36 http: TLS handshake error from 10.244.0.1:56614: EOF 2018/08/03 21:35:46 http: TLS handshake error from 10.244.0.1:56638: EOF level=info timestamp=2018-08-03T21:35:55.783084Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:35:56 http: TLS handshake error from 10.244.0.1:56662: EOF level=info timestamp=2018-08-03T21:35:58.774410Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:36:06 http: TLS handshake error from 10.244.0.1:56686: EOF 2018/08/03 21:36:16 http: TLS handshake error from 10.244.0.1:56710: EOF Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:21:56.841947Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivgf8x kind= uid=4014424f-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:21:56.842052Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivgf8x kind= uid=4014424f-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:22:58.699157Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihwkz8 kind= uid=64f47249-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:22:58.699299Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihwkz8 kind= uid=64f47249-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:25:59.132672Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim5jbf kind= uid=d0811b05-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:25:59.132855Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim5jbf kind= uid=d0811b05-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:25:59.179087Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmim5jbf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmim5jbf" level=info timestamp=2018-08-03T21:28:59.403245Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmim5jbf\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmim5jbf, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: d0811b05-9763-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmim5jbf" level=info timestamp=2018-08-03T21:28:59.585968Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqltdl kind= uid=3c0fd9de-9764-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:28:59.586101Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqltdl kind= uid=3c0fd9de-9764-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:28:59.628791Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiqltdl\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiqltdl" level=info timestamp=2018-08-03T21:32:00.035853Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikg68m kind= uid=a79e73df-9764-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:32:00.036022Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikg68m kind= uid=a79e73df-9764-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:35:23.494828Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7l5g9 kind= uid=20e37695-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:35:23.495004Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7l5g9 kind= uid=20e37695-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:12:03.720273Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.119687Z pos=health.go:55 component=virt-handler reason="tun device does not 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:45.235913Z pos=health.go:55 component=virt-handler reason="tun device does not 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:34.143836Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:48.788121Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.894111Z pos=health.go:55 component=virt-handler reason="tun device does not 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:32.008911Z pos=health.go:55 component=virt-handler reason="tun device does not 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:53.130481Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.333789Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:49.653880Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:39.835572Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.891405Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.631127Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.862218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:41.604703Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:12:09.130061Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.522467Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.636725Z pos=health.go:55 component=virt-handler reason="tun device does not 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:39.542878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:54.185448Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.285186Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.395483Z pos=health.go:55 component=virt-handler reason="tun device does not 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:58.508118Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.708179Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:55.023095Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:45.196978Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.247809Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.983248Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.211229Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:46.942432Z pos=health.go:55 component=virt-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-testvmi7l5g9-5tztg Pod phase: Pending • Failure in Spec Setup (BeforeEach) [60.259 seconds] Expose /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:53 Expose service on a VM /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:61 Expose ClusterIP service [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:68 Should expose a Cluster IP service on a VMI and connect to it /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:71 Timed out after 30.003s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1030 ------------------------------ level=info timestamp=2018-08-03T21:35:23.908893Z pos=utils.go:255 component=tests namespace=kubevirt-test-default name=testvmi7l5g9 kind=VirtualMachineInstance uid=20e37695-9765-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi7l5g9-5tztg" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T21:35:33.360993Z 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:35:40 http: TLS handshake error from 10.244.1.1:53876: EOF 2018/08/03 21:35:50 http: TLS handshake error from 10.244.1.1:53882: EOF 2018/08/03 21:36:00 http: TLS handshake error from 10.244.1.1:53888: EOF level=info timestamp=2018-08-03T21:36:03.345921Z 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:10 http: TLS handshake error from 10.244.1.1:53894: EOF 2018/08/03 21:36:20 http: TLS handshake error from 10.244.1.1:53900: EOF 2018/08/03 21:36:30 http: TLS handshake error from 10.244.1.1:53906: EOF level=info timestamp=2018-08-03T21:36:33.373314Z 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:40 http: TLS handshake error from 10.244.1.1:53912: EOF 2018/08/03 21:36:50 http: TLS handshake error from 10.244.1.1:53918: EOF 2018/08/03 21:37:00 http: TLS handshake error from 10.244.1.1:53924: EOF level=info timestamp=2018-08-03T21:37:03.346703Z 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:37:10 http: TLS handshake error from 10.244.1.1:53930: EOF 2018/08/03 21:37:20 http: TLS handshake error from 10.244.1.1:53936: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T21:35:58.774410Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:36:06 http: TLS handshake error from 10.244.0.1:56686: EOF 2018/08/03 21:36:16 http: TLS handshake error from 10.244.0.1:56710: EOF level=info timestamp=2018-08-03T21:36:25.813513Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:36:26 http: TLS handshake error from 10.244.0.1:56734: EOF level=info timestamp=2018-08-03T21:36:28.805778Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:36:36 http: TLS handshake error from 10.244.0.1:56758: EOF level=info timestamp=2018-08-03T21:36:38.405243Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:36:38.406166Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:36:46 http: TLS handshake error from 10.244.0.1:56782: EOF level=info timestamp=2018-08-03T21:36:55.842776Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:36:56 http: TLS handshake error from 10.244.0.1:56806: EOF level=info timestamp=2018-08-03T21:36:58.834188Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:37:06 http: TLS handshake error from 10.244.0.1:56830: EOF 2018/08/03 21:37:16 http: TLS handshake error from 10.244.0.1:56854: EOF Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:22:58.699157Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihwkz8 kind= uid=64f47249-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:22:58.699299Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihwkz8 kind= uid=64f47249-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:25:59.132672Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim5jbf kind= uid=d0811b05-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:25:59.132855Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim5jbf kind= uid=d0811b05-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:25:59.179087Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmim5jbf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmim5jbf" level=info timestamp=2018-08-03T21:28:59.403245Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmim5jbf\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmim5jbf, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: d0811b05-9763-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmim5jbf" level=info timestamp=2018-08-03T21:28:59.585968Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqltdl kind= uid=3c0fd9de-9764-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:28:59.586101Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqltdl kind= uid=3c0fd9de-9764-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:28:59.628791Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiqltdl\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiqltdl" level=info timestamp=2018-08-03T21:32:00.035853Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikg68m kind= uid=a79e73df-9764-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:32:00.036022Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikg68m kind= uid=a79e73df-9764-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:35:23.494828Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7l5g9 kind= uid=20e37695-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:35:23.495004Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7l5g9 kind= uid=20e37695-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:36:23.751763Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmif2nrm kind= uid=44ce377a-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:36:23.751918Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmif2nrm kind= uid=44ce377a-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:13:24.119687Z pos=health.go:55 component=virt-handler reason="tun device does not 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:45.235913Z pos=health.go:55 component=virt-handler reason="tun device does not 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:34.143836Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:48.788121Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.894111Z pos=health.go:55 component=virt-handler reason="tun device does not 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:32.008911Z pos=health.go:55 component=virt-handler reason="tun device does not 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:53.130481Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.333789Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:49.653880Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:39.835572Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.891405Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.631127Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.862218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:41.604703Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.447001Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:13:29.522467Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.636725Z pos=health.go:55 component=virt-handler reason="tun device does not 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:39.542878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:54.185448Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.285186Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.395483Z pos=health.go:55 component=virt-handler reason="tun device does not 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:58.508118Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.708179Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:55.023095Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:45.196978Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.247809Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.983248Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.211229Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:46.942432Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.779129Z pos=health.go:55 component=virt-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-testvmi7l5g9-5tztg Pod phase: Pending Pod name: virt-launcher-testvmif2nrm-bk47f Pod phase: Pending • Failure in Spec Setup (BeforeEach) [60.432 seconds] Expose /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:53 Expose service on a VM /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:61 Expose ClusterIP service with string target-port [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:98 Should expose a ClusterIP service and connect to the vm on port 80 /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:101 Timed out after 30.006s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1030 ------------------------------ level=info timestamp=2018-08-03T21:36:24.143961Z pos=utils.go:255 component=tests namespace=kubevirt-test-default name=testvmif2nrm kind=VirtualMachineInstance uid=44ce377a-9765-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmif2nrm-bk47f" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T21:36:33.373314Z 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:40 http: TLS handshake error from 10.244.1.1:53912: EOF 2018/08/03 21:36:50 http: TLS handshake error from 10.244.1.1:53918: EOF 2018/08/03 21:37:00 http: TLS handshake error from 10.244.1.1:53924: EOF level=info timestamp=2018-08-03T21:37:03.346703Z 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:37:10 http: TLS handshake error from 10.244.1.1:53930: EOF 2018/08/03 21:37:20 http: TLS handshake error from 10.244.1.1:53936: EOF 2018/08/03 21:37:30 http: TLS handshake error from 10.244.1.1:53942: EOF level=info timestamp=2018-08-03T21:37:33.352449Z 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:37:40 http: TLS handshake error from 10.244.1.1:53948: EOF 2018/08/03 21:37:50 http: TLS handshake error from 10.244.1.1:53954: EOF 2018/08/03 21:38:00 http: TLS handshake error from 10.244.1.1:53960: EOF level=info timestamp=2018-08-03T21:38:03.325629Z 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:38:10 http: TLS handshake error from 10.244.1.1:53966: EOF 2018/08/03 21:38:20 http: TLS handshake error from 10.244.1.1:53972: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T21:36:58.834188Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:37:06 http: TLS handshake error from 10.244.0.1:56830: EOF 2018/08/03 21:37:16 http: TLS handshake error from 10.244.0.1:56854: EOF level=info timestamp=2018-08-03T21:37:25.880757Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:37:26 http: TLS handshake error from 10.244.0.1:56878: EOF level=info timestamp=2018-08-03T21:37:28.861659Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:37:36 http: TLS handshake error from 10.244.0.1:56902: EOF level=info timestamp=2018-08-03T21:37:38.407404Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:37:38.408134Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:37:46 http: TLS handshake error from 10.244.0.1:56926: EOF level=info timestamp=2018-08-03T21:37:55.911263Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:37:56 http: TLS handshake error from 10.244.0.1:56950: EOF level=info timestamp=2018-08-03T21:37:58.892248Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:38:06 http: TLS handshake error from 10.244.0.1:56974: EOF 2018/08/03 21:38:16 http: TLS handshake error from 10.244.0.1:56998: EOF Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:25:59.132672Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim5jbf kind= uid=d0811b05-9763-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:25:59.132855Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim5jbf kind= uid=d0811b05-9763-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:25:59.179087Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmim5jbf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmim5jbf" level=info timestamp=2018-08-03T21:28:59.403245Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmim5jbf\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmim5jbf, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: d0811b05-9763-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmim5jbf" level=info timestamp=2018-08-03T21:28:59.585968Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqltdl kind= uid=3c0fd9de-9764-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:28:59.586101Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqltdl kind= uid=3c0fd9de-9764-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:28:59.628791Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiqltdl\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiqltdl" level=info timestamp=2018-08-03T21:32:00.035853Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikg68m kind= uid=a79e73df-9764-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:32:00.036022Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikg68m kind= uid=a79e73df-9764-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:35:23.494828Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7l5g9 kind= uid=20e37695-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:35:23.495004Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7l5g9 kind= uid=20e37695-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:36:23.751763Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmif2nrm kind= uid=44ce377a-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:36:23.751918Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmif2nrm kind= uid=44ce377a-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:37:24.187527Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibfmgc kind= uid=68d3702f-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:37:24.187681Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibfmgc kind= uid=68d3702f-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:14:45.235913Z pos=health.go:55 component=virt-handler reason="tun device does not 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:34.143836Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:48.788121Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.894111Z pos=health.go:55 component=virt-handler reason="tun device does not 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:32.008911Z pos=health.go:55 component=virt-handler reason="tun device does not 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:53.130481Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.333789Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:49.653880Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:39.835572Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.891405Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.631127Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.862218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:41.604703Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.447001Z pos=health.go:55 component=virt-handler reason="tun device does not 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:46.173315Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:14:50.636725Z pos=health.go:55 component=virt-handler reason="tun device does not 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:39.542878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:54.185448Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.285186Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.395483Z pos=health.go:55 component=virt-handler reason="tun device does not 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:58.508118Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.708179Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:55.023095Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:45.196978Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.247809Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.983248Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.211229Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:46.942432Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.779129Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.503419Z pos=health.go:55 component=virt-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-testvmi7l5g9-5tztg Pod phase: Pending Pod name: virt-launcher-testvmibfmgc-hldl6 Pod phase: Pending Pod name: virt-launcher-testvmif2nrm-bk47f Pod phase: Pending • Failure in Spec Setup (BeforeEach) [60.635 seconds] Expose /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:53 Expose service on a VM /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:61 Expose NodePort service [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:124 Should expose a NodePort service on a VMI and connect to it /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:129 Timed out after 30.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1030 ------------------------------ level=info timestamp=2018-08-03T21:37:24.567794Z pos=utils.go:255 component=tests namespace=kubevirt-test-default name=testvmibfmgc kind=VirtualMachineInstance uid=68d3702f-9765-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmibfmgc-hldl6" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T21:37:33.352449Z 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:37:40 http: TLS handshake error from 10.244.1.1:53948: EOF 2018/08/03 21:37:50 http: TLS handshake error from 10.244.1.1:53954: EOF 2018/08/03 21:38:00 http: TLS handshake error from 10.244.1.1:53960: EOF level=info timestamp=2018-08-03T21:38:03.325629Z 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:38:10 http: TLS handshake error from 10.244.1.1:53966: EOF 2018/08/03 21:38:20 http: TLS handshake error from 10.244.1.1:53972: EOF 2018/08/03 21:38:30 http: TLS handshake error from 10.244.1.1:53978: EOF level=info timestamp=2018-08-03T21:38:33.355152Z 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:38:40 http: TLS handshake error from 10.244.1.1:53984: EOF 2018/08/03 21:38:50 http: TLS handshake error from 10.244.1.1:53990: EOF 2018/08/03 21:39:00 http: TLS handshake error from 10.244.1.1:53996: EOF level=info timestamp=2018-08-03T21:39:03.341879Z 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:10 http: TLS handshake error from 10.244.1.1:54002: EOF 2018/08/03 21:39:20 http: TLS handshake error from 10.244.1.1:54008: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T21:37:55.911263Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:37:56 http: TLS handshake error from 10.244.0.1:56950: EOF level=info timestamp=2018-08-03T21:37:58.892248Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:38:06 http: TLS handshake error from 10.244.0.1:56974: EOF 2018/08/03 21:38:16 http: TLS handshake error from 10.244.0.1:56998: EOF level=info timestamp=2018-08-03T21:38:25.939607Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:38:26 http: TLS handshake error from 10.244.0.1:57022: EOF level=info timestamp=2018-08-03T21:38:28.919332Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:38:36 http: TLS handshake error from 10.244.0.1:57046: EOF 2018/08/03 21:38:46 http: TLS handshake error from 10.244.0.1:57070: EOF level=info timestamp=2018-08-03T21:38:55.968638Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:38:56 http: TLS handshake error from 10.244.0.1:57094: EOF level=info timestamp=2018-08-03T21:38:58.947758Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:39:06 http: TLS handshake error from 10.244.0.1:57118: EOF 2018/08/03 21:39:16 http: TLS handshake error from 10.244.0.1:57142: EOF Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:28:59.403245Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmim5jbf\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmim5jbf, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: d0811b05-9763-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmim5jbf" level=info timestamp=2018-08-03T21:28:59.585968Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqltdl kind= uid=3c0fd9de-9764-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:28:59.586101Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqltdl kind= uid=3c0fd9de-9764-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:28:59.628791Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiqltdl\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiqltdl" level=info timestamp=2018-08-03T21:32:00.035853Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikg68m kind= uid=a79e73df-9764-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:32:00.036022Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikg68m kind= uid=a79e73df-9764-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:35:23.494828Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7l5g9 kind= uid=20e37695-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:35:23.495004Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7l5g9 kind= uid=20e37695-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:36:23.751763Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmif2nrm kind= uid=44ce377a-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:36:23.751918Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmif2nrm kind= uid=44ce377a-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:37:24.187527Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibfmgc kind= uid=68d3702f-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:37:24.187681Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibfmgc kind= uid=68d3702f-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:38:24.821812Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixflhd kind= uid=8cf7ac93-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:38:24.821984Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixflhd kind= uid=8cf7ac93-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:38:24.866907Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmixflhd\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmixflhd" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:16:34.143836Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:48.788121Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.894111Z pos=health.go:55 component=virt-handler reason="tun device does not 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:32.008911Z pos=health.go:55 component=virt-handler reason="tun device does not 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:53.130481Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.333789Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:49.653880Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:39.835572Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.891405Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.631127Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.862218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:41.604703Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.447001Z pos=health.go:55 component=virt-handler reason="tun device does not 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:46.173315Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:38:58.665965Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:16:39.542878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:54.185448Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.285186Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.395483Z pos=health.go:55 component=virt-handler reason="tun device does not 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:58.508118Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.708179Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:55.023095Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:45.196978Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.247809Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.983248Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.211229Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:46.942432Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.779129Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.503419Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.989011Z pos=health.go:55 component=virt-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-testvmi7l5g9-5tztg Pod phase: Pending Pod name: virt-launcher-testvmibfmgc-hldl6 Pod phase: Pending Pod name: virt-launcher-testvmif2nrm-bk47f Pod phase: Pending Pod name: virt-launcher-testvmixflhd-mwxkc Pod phase: Pending • Failure in Spec Setup (BeforeEach) [60.836 seconds] Expose /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:53 Expose UDP service on a VMI /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:166 Expose ClusterIP UDP service [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:173 Should expose a ClusterIP service on a VMI and connect to it /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:177 Timed out after 30.005s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1030 ------------------------------ level=info timestamp=2018-08-03T21:38:25.200301Z pos=utils.go:255 component=tests namespace=kubevirt-test-default name=testvmixflhd kind=VirtualMachineInstance uid=8cf7ac93-9765-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmixflhd-mwxkc" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T21:38:33.355152Z 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:38:40 http: TLS handshake error from 10.244.1.1:53984: EOF 2018/08/03 21:38:50 http: TLS handshake error from 10.244.1.1:53990: EOF 2018/08/03 21:39:00 http: TLS handshake error from 10.244.1.1:53996: EOF level=info timestamp=2018-08-03T21:39:03.341879Z 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:10 http: TLS handshake error from 10.244.1.1:54002: EOF 2018/08/03 21:39:20 http: TLS handshake error from 10.244.1.1:54008: EOF 2018/08/03 21:39:30 http: TLS handshake error from 10.244.1.1:54014: EOF level=info timestamp=2018-08-03T21:39:33.326165Z 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:40 http: TLS handshake error from 10.244.1.1:54020: EOF 2018/08/03 21:39:50 http: TLS handshake error from 10.244.1.1:54026: EOF 2018/08/03 21:40:00 http: TLS handshake error from 10.244.1.1:54032: EOF level=info timestamp=2018-08-03T21:40:03.362733Z 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:40:10 http: TLS handshake error from 10.244.1.1:54038: EOF 2018/08/03 21:40:20 http: TLS handshake error from 10.244.1.1:54044: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T21:38:58.947758Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:39:06 http: TLS handshake error from 10.244.0.1:57118: EOF 2018/08/03 21:39:16 http: TLS handshake error from 10.244.0.1:57142: EOF level=info timestamp=2018-08-03T21:39:25.998795Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:39:26 http: TLS handshake error from 10.244.0.1:57166: EOF level=info timestamp=2018-08-03T21:39:28.975695Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:39:36 http: TLS handshake error from 10.244.0.1:57190: EOF level=info timestamp=2018-08-03T21:39:38.409346Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:39:38.410212Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:39:46 http: TLS handshake error from 10.244.0.1:57214: EOF level=info timestamp=2018-08-03T21:39:56.029012Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:39:56 http: TLS handshake error from 10.244.0.1:57238: EOF level=info timestamp=2018-08-03T21:39:59.006682Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:40:06 http: TLS handshake error from 10.244.0.1:57262: EOF 2018/08/03 21:40:16 http: TLS handshake error from 10.244.0.1:57286: EOF Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:28:59.628791Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiqltdl\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiqltdl" level=info timestamp=2018-08-03T21:32:00.035853Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikg68m kind= uid=a79e73df-9764-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:32:00.036022Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikg68m kind= uid=a79e73df-9764-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:35:23.494828Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7l5g9 kind= uid=20e37695-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:35:23.495004Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7l5g9 kind= uid=20e37695-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:36:23.751763Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmif2nrm kind= uid=44ce377a-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:36:23.751918Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmif2nrm kind= uid=44ce377a-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:37:24.187527Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibfmgc kind= uid=68d3702f-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:37:24.187681Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibfmgc kind= uid=68d3702f-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:38:24.821812Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixflhd kind= uid=8cf7ac93-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:38:24.821984Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixflhd kind= uid=8cf7ac93-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:38:24.866907Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmixflhd\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmixflhd" level=info timestamp=2018-08-03T21:39:25.656503Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi88j4h kind= uid=b13a7d29-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:39:25.656658Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi88j4h kind= uid=b13a7d29-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:39:25.693701Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi88j4h\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi88j4h" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:16:34.143836Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:48.788121Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.894111Z pos=health.go:55 component=virt-handler reason="tun device does not 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:32.008911Z pos=health.go:55 component=virt-handler reason="tun device does not 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:53.130481Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.333789Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:49.653880Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:39.835572Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.891405Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.631127Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.862218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:41.604703Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.447001Z pos=health.go:55 component=virt-handler reason="tun device does not 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:46.173315Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:38:58.665965Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:16:39.542878Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:17:54.185448Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.285186Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.395483Z pos=health.go:55 component=virt-handler reason="tun device does not 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:58.508118Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.708179Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:55.023095Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:45.196978Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.247809Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.983248Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.211229Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:46.942432Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.779129Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.503419Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.989011Z pos=health.go:55 component=virt-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-testvmi7l5g9-5tztg Pod phase: Pending Pod name: virt-launcher-testvmi88j4h-6l8pt Pod phase: Pending Pod name: virt-launcher-testvmibfmgc-hldl6 Pod phase: Pending Pod name: virt-launcher-testvmif2nrm-bk47f Pod phase: Pending Pod name: virt-launcher-testvmixflhd-mwxkc Pod phase: Pending • Failure in Spec Setup (BeforeEach) [61.033 seconds] Expose /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:53 Expose UDP service on a VMI /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:166 Expose NodePort UDP service [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:205 Should expose a NodePort service on a VMI and connect to it /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:210 Timed out after 30.005s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1030 ------------------------------ level=info timestamp=2018-08-03T21:39:26.046563Z pos=utils.go:255 component=tests namespace=kubevirt-test-default name=testvmi88j4h kind=VirtualMachineInstance uid=b13a7d29-9765-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi88j4h-6l8pt" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running 2018/08/03 21:40:50 http: TLS handshake error from 10.244.1.1:54062: EOF 2018/08/03 21:41:00 http: TLS handshake error from 10.244.1.1:54068: EOF level=info timestamp=2018-08-03T21:41:03.358419Z 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:41:10 http: TLS handshake error from 10.244.1.1:54074: EOF 2018/08/03 21:41:20 http: TLS handshake error from 10.244.1.1:54080: EOF 2018/08/03 21:41:30 http: TLS handshake error from 10.244.1.1:54086: EOF level=info timestamp=2018-08-03T21:41:33.278924Z 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:41:33.296092Z 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:41:33.328783Z 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:41:40 http: TLS handshake error from 10.244.1.1:54092: EOF 2018/08/03 21:41:50 http: TLS handshake error from 10.244.1.1:54098: EOF 2018/08/03 21:42:00 http: TLS handshake error from 10.244.1.1:54104: EOF level=info timestamp=2018-08-03T21:42:03.328602Z 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:42:10 http: TLS handshake error from 10.244.1.1:54110: EOF 2018/08/03 21:42:20 http: TLS handshake error from 10.244.1.1:54116: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running 2018/08/03 21:41:16 http: TLS handshake error from 10.244.0.1:57430: EOF level=info timestamp=2018-08-03T21:41:26.110715Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:41:26 http: TLS handshake error from 10.244.0.1:57454: EOF level=info timestamp=2018-08-03T21:41:29.092626Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:41:36 http: TLS handshake error from 10.244.0.1:57478: EOF level=info timestamp=2018-08-03T21:41:38.445524Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:41:38.446268Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:41:46 http: TLS handshake error from 10.244.0.1:57502: EOF level=info timestamp=2018-08-03T21:41:56.143171Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:41:56 http: TLS handshake error from 10.244.0.1:57526: EOF level=info timestamp=2018-08-03T21:41:59.116168Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:42:06 http: TLS handshake error from 10.244.0.1:57550: EOF 2018/08/03 21:42:16 http: TLS handshake error from 10.244.0.1:57574: EOF level=info timestamp=2018-08-03T21:42:26.175431Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:42:26 http: TLS handshake error from 10.244.0.1:57598: EOF Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:38:24.821812Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixflhd kind= uid=8cf7ac93-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:38:24.821984Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmixflhd kind= uid=8cf7ac93-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:38:24.866907Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmixflhd\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmixflhd" level=info timestamp=2018-08-03T21:39:25.656503Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi88j4h kind= uid=b13a7d29-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:39:25.656658Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi88j4h kind= uid=b13a7d29-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:39:25.693701Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi88j4h\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi88j4h" level=error timestamp=2018-08-03T21:40:26.700451Z pos=vm.go:459 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqz6m8xsfcw kind= uid=d59d7e45-9765-11e8-9925-525500d15501 msg="Cant find the matching VM for VirtualMachineInstance: testvmiqz6m8xsfcw" level=info timestamp=2018-08-03T21:40:26.700663Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqz6m8xsfcw kind= uid=d59d7e45-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:40:26.700765Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqz6m8xsfcw kind= uid=d59d7e45-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=error timestamp=2018-08-03T21:40:26.713586Z pos=vm.go:459 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqz6m8ggfd4 kind= uid=d59de12d-9765-11e8-9925-525500d15501 msg="Cant find the matching VM for VirtualMachineInstance: testvmiqz6m8ggfd4" level=info timestamp=2018-08-03T21:40:26.713742Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqz6m8ggfd4 kind= uid=d59de12d-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:40:26.713834Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqz6m8ggfd4 kind= uid=d59de12d-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=error timestamp=2018-08-03T21:40:26.734439Z pos=replicaset.go:230 component=virt-controller service=http namespace=kubevirt-test-default name=replicasetv2jfj kind= uid=d59b6ee5-9765-11e8-9925-525500d15501 reason="Operation cannot be fulfilled on virtualmachineinstancereplicasets.kubevirt.io \"replicasetv2jfj\": the object has been modified; please apply your changes to the latest version and try again" msg="Updating the replicaset status failed." level=info timestamp=2018-08-03T21:40:26.734623Z pos=replicaset.go:137 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstancereplicasets.kubevirt.io \"replicasetv2jfj\": the object has been modified; please apply your changes to the latest version and try again" msg="re-enqueuing VirtualMachineInstanceReplicaSet kubevirt-test-default/replicasetv2jfj" level=info timestamp=2018-08-03T21:40:26.896846Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiqz6m8ggfd4\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiqz6m8ggfd4" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:19:29.894111Z pos=health.go:55 component=virt-handler reason="tun device does not 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:32.008911Z pos=health.go:55 component=virt-handler reason="tun device does not 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:53.130481Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.333789Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:49.653880Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:39.835572Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.891405Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.631127Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.862218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:41.604703Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.447001Z pos=health.go:55 component=virt-handler reason="tun device does not 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:46.173315Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:38:58.665965Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.641743Z pos=health.go:55 component=virt-handler reason="tun device does not 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:57.701858Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:19:35.285186Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.395483Z pos=health.go:55 component=virt-handler reason="tun device does not 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:58.508118Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.708179Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:55.023095Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:45.196978Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.247809Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.983248Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.211229Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:46.942432Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.779129Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.503419Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.989011Z pos=health.go:55 component=virt-handler reason="tun device does not 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:42.958098Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.021114Z pos=health.go:55 component=virt-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-testvmi7l5g9-5tztg Pod phase: Pending Pod name: virt-launcher-testvmi88j4h-6l8pt Pod phase: Pending Pod name: virt-launcher-testvmibfmgc-hldl6 Pod phase: Pending Pod name: virt-launcher-testvmif2nrm-bk47f Pod phase: Pending Pod name: virt-launcher-testvmiqz6m8ggfd4-9sckw Pod phase: Pending Pod name: virt-launcher-testvmiqz6m8xsfcw-h4g8w Pod phase: Pending Pod name: virt-launcher-testvmixflhd-mwxkc Pod phase: Pending • Failure in Spec Setup (BeforeEach) [121.420 seconds] Expose /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:53 Expose service on a VMI replica set /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:253 Expose ClusterIP service [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:286 Should create a ClusterIP service on VMRS and connect to it /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:290 Timed out after 120.000s. Expected : 0 to equal : 2 /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:271 ------------------------------ STEP: Creating a VMRS object with 2 replicas STEP: Start the replica set STEP: Checking the number of ready replicas Service cluster-ip-vm successfully exposed for virtualmachine testvmi9hddg VM testvmi9hddg was scheduled to start Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T21:42:33.358181Z 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:42:40 http: TLS handshake error from 10.244.1.1:54128: EOF 2018/08/03 21:42:50 http: TLS handshake error from 10.244.1.1:54134: EOF 2018/08/03 21:43:00 http: TLS handshake error from 10.244.1.1:54140: EOF level=info timestamp=2018-08-03T21:43:03.354907Z 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:43:10 http: TLS handshake error from 10.244.1.1:54146: EOF 2018/08/03 21:43:20 http: TLS handshake error from 10.244.1.1:54152: EOF 2018/08/03 21:43:30 http: TLS handshake error from 10.244.1.1:54158: EOF level=info timestamp=2018-08-03T21:43:33.349652Z 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:43:40 http: TLS handshake error from 10.244.1.1:54164: EOF 2018/08/03 21:43:50 http: TLS handshake error from 10.244.1.1:54170: EOF 2018/08/03 21:44:00 http: TLS handshake error from 10.244.1.1:54176: EOF level=info timestamp=2018-08-03T21:44:03.340023Z 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:44:10 http: TLS handshake error from 10.244.1.1:54182: EOF 2018/08/03 21:44:20 http: TLS handshake error from 10.244.1.1:54188: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T21:42:59.173817Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:43:06 http: TLS handshake error from 10.244.0.1:57694: EOF 2018/08/03 21:43:16 http: TLS handshake error from 10.244.0.1:57718: EOF level=info timestamp=2018-08-03T21:43:26.236647Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:43:26 http: TLS handshake error from 10.244.0.1:57742: EOF level=info timestamp=2018-08-03T21:43:29.213716Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:43:36 http: TLS handshake error from 10.244.0.1:57766: EOF 2018/08/03 21:43:46 http: TLS handshake error from 10.244.0.1:57790: EOF 2018/08/03 21:43:56 http: TLS handshake error from 10.244.0.1:57814: EOF level=info timestamp=2018-08-03T21:43:56.265862Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:43:59.243379Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:44:06 http: TLS handshake error from 10.244.0.1:57838: EOF 2018/08/03 21:44:16 http: TLS handshake error from 10.244.0.1:57862: EOF 2018/08/03 21:44:26 http: TLS handshake error from 10.244.0.1:57886: EOF level=info timestamp=2018-08-03T21:44:26.294568Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:39:25.656658Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi88j4h kind= uid=b13a7d29-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:39:25.693701Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi88j4h\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi88j4h" level=error timestamp=2018-08-03T21:40:26.700451Z pos=vm.go:459 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqz6m8xsfcw kind= uid=d59d7e45-9765-11e8-9925-525500d15501 msg="Cant find the matching VM for VirtualMachineInstance: testvmiqz6m8xsfcw" level=info timestamp=2018-08-03T21:40:26.700663Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqz6m8xsfcw kind= uid=d59d7e45-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:40:26.700765Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqz6m8xsfcw kind= uid=d59d7e45-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=error timestamp=2018-08-03T21:40:26.713586Z pos=vm.go:459 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqz6m8ggfd4 kind= uid=d59de12d-9765-11e8-9925-525500d15501 msg="Cant find the matching VM for VirtualMachineInstance: testvmiqz6m8ggfd4" level=info timestamp=2018-08-03T21:40:26.713742Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqz6m8ggfd4 kind= uid=d59de12d-9765-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:40:26.713834Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiqz6m8ggfd4 kind= uid=d59de12d-9765-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=error timestamp=2018-08-03T21:40:26.734439Z pos=replicaset.go:230 component=virt-controller service=http namespace=kubevirt-test-default name=replicasetv2jfj kind= uid=d59b6ee5-9765-11e8-9925-525500d15501 reason="Operation cannot be fulfilled on virtualmachineinstancereplicasets.kubevirt.io \"replicasetv2jfj\": the object has been modified; please apply your changes to the latest version and try again" msg="Updating the replicaset status failed." level=info timestamp=2018-08-03T21:40:26.734623Z pos=replicaset.go:137 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstancereplicasets.kubevirt.io \"replicasetv2jfj\": the object has been modified; please apply your changes to the latest version and try again" msg="re-enqueuing VirtualMachineInstanceReplicaSet kubevirt-test-default/replicasetv2jfj" level=info timestamp=2018-08-03T21:40:26.896846Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiqz6m8ggfd4\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiqz6m8ggfd4" level=info timestamp=2018-08-03T21:42:28.192801Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9hddg kind= uid=1e05d2ac-9766-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:42:28.192955Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9hddg kind= uid=1e05d2ac-9766-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=error timestamp=2018-08-03T21:42:28.214378Z pos=vm.go:201 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9hddg kind= uid=1dfaad60-9766-11e8-9925-525500d15501 reason="Operation cannot be fulfilled on virtualmachines.kubevirt.io \"testvmi9hddg\": 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-03T21:42:28.214471Z pos=vm.go:111 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachines.kubevirt.io \"testvmi9hddg\": the object has been modified; please apply your changes to the latest version and try again" msg="re-enqueuing VirtualMachine kubevirt-test-default/testvmi9hddg" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:21:32.008911Z pos=health.go:55 component=virt-handler reason="tun device does not 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:53.130481Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.333789Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:49.653880Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:39.835572Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.891405Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.631127Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.862218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:41.604703Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.447001Z pos=health.go:55 component=virt-handler reason="tun device does not 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:46.173315Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:38:58.665965Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.641743Z pos=health.go:55 component=virt-handler reason="tun device does not 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:57.701858Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:28.187225Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:21:37.395483Z pos=health.go:55 component=virt-handler reason="tun device does not 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:58.508118Z pos=health.go:55 component=virt-handler reason="tun device does not 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:52.708179Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:55.023095Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:45.196978Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.247809Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.983248Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.211229Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:46.942432Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.779129Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.503419Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.989011Z pos=health.go:55 component=virt-handler reason="tun device does not 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:42.958098Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.021114Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:33.500844Z pos=health.go:55 component=virt-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-testvmi7l5g9-5tztg Pod phase: Pending Pod name: virt-launcher-testvmi88j4h-6l8pt Pod phase: Pending Pod name: virt-launcher-testvmi9hddg-h82mq Pod phase: Pending Pod name: virt-launcher-testvmibfmgc-hldl6 Pod phase: Pending Pod name: virt-launcher-testvmif2nrm-bk47f Pod phase: Pending Pod name: virt-launcher-testvmiqz6m8ggfd4-9sckw Pod phase: Pending Pod name: virt-launcher-testvmiqz6m8xsfcw-h4g8w Pod phase: Pending Pod name: virt-launcher-testvmixflhd-mwxkc Pod phase: Pending • Failure in Spec Setup (BeforeEach) [121.680 seconds] Expose /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:53 Expose service on an VM /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:318 Expose ClusterIP service [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:362 Connect to ClusterIP services that was set when VM was offline /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:363 Timed out after 120.000s. Expected : false to be true /root/go/src/kubevirt.io/kubevirt/tests/expose_test.go:349 ------------------------------ STEP: Creating an VM object STEP: Creating the VM STEP: Exposing a service on the VM using virtctl STEP: Calling the start command STEP: Getting the status of the VMI •••• Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running 2018/08/03 21:46:00 http: TLS handshake error from 10.244.1.1:54256: EOF level=info timestamp=2018-08-03T21:46:03.330089Z 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:46:10 http: TLS handshake error from 10.244.1.1:54262: EOF 2018/08/03 21:46:20 http: TLS handshake error from 10.244.1.1:54268: EOF 2018/08/03 21:46:30 http: TLS handshake error from 10.244.1.1:54274: EOF level=info timestamp=2018-08-03T21:46:33.375413Z 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:46:40 http: TLS handshake error from 10.244.1.1:54280: EOF 2018/08/03 21:46:50 http: TLS handshake error from 10.244.1.1:54286: EOF 2018/08/03 21:47:00 http: TLS handshake error from 10.244.1.1:54292: EOF level=info timestamp=2018-08-03T21:47:03.346582Z 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:47:10 http: TLS handshake error from 10.244.1.1:54298: EOF 2018/08/03 21:47:20 http: TLS handshake error from 10.244.1.1:54304: EOF 2018/08/03 21:47:30 http: TLS handshake error from 10.244.1.1:54310: EOF level=info timestamp=2018-08-03T21:47:33.330792Z 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:47:40 http: TLS handshake error from 10.244.1.1:54316: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running 2018/08/03 21:46:36 http: TLS handshake error from 10.244.0.1:58198: EOF level=info timestamp=2018-08-03T21:46:38.389708Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:46:38.390713Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:46:46 http: TLS handshake error from 10.244.0.1:58222: EOF 2018/08/03 21:46:56 http: TLS handshake error from 10.244.0.1:58246: EOF level=info timestamp=2018-08-03T21:46:56.467998Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:46:59.430616Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:47:06 http: TLS handshake error from 10.244.0.1:58270: EOF 2018/08/03 21:47:16 http: TLS handshake error from 10.244.0.1:58294: EOF 2018/08/03 21:47:26 http: TLS handshake error from 10.244.0.1:58318: EOF level=info timestamp=2018-08-03T21:47:26.496253Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:47:29.461383Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:47:36 http: TLS handshake error from 10.244.0.1:58342: EOF level=info timestamp=2018-08-03T21:47:38.392258Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:47:38.393180Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:44:30.234464Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmif2nrm\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmif2nrm, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 44ce377a-9765-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmif2nrm" level=info timestamp=2018-08-03T21:44:30.434180Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmixflhd\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmixflhd, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 8cf7ac93-9765-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmixflhd" level=info timestamp=2018-08-03T21:44:44.917937Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilq7q8 kind= uid=6f861c43-9766-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:44:44.919075Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilq7q8 kind= uid=6f861c43-9766-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:44:44.926818Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmic2ctl kind= uid=6f8778c2-9766-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:44:44.926898Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmic2ctl kind= uid=6f8778c2-9766-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:44:44.943797Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwmzp6 kind= uid=6f88b23d-9766-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:44:44.943896Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwmzp6 kind= uid=6f88b23d-9766-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:44:44.971636Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmijslnz kind= uid=6f8aedfc-9766-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:44:44.971720Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmijslnz kind= uid=6f8aedfc-9766-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:44:45.018212Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmic2ctl\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmic2ctl" level=info timestamp=2018-08-03T21:44:45.122551Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiwmzp6\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiwmzp6" level=info timestamp=2018-08-03T21:44:45.924921Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmic2ctl\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmic2ctl" level=info timestamp=2018-08-03T21:44:46.323314Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiwmzp6\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiwmzp6" level=info timestamp=2018-08-03T21:44:47.122627Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiwmzp6\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiwmzp6" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:24:47.333789Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:49.653880Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:39.835572Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.891405Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.631127Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.862218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:41.604703Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.447001Z pos=health.go:55 component=virt-handler reason="tun device does not 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:46.173315Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:38:58.665965Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.641743Z pos=health.go:55 component=virt-handler reason="tun device does not 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:57.701858Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:28.187225Z pos=health.go:55 component=virt-handler reason="tun device does not 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:06.404981Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.205414Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:24:52.708179Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:26:55.023095Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:28:45.196978Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.247809Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.983248Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.211229Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:46.942432Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.779129Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.503419Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.989011Z pos=health.go:55 component=virt-handler reason="tun device does not 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:42.958098Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.021114Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:33.500844Z pos=health.go:55 component=virt-handler reason="tun device does not 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:11.715230Z pos=health.go:55 component=virt-handler reason="tun device does not 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:08.504317Z pos=health.go:55 component=virt-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-testvmic2ctl-mjb4n Pod phase: Pending Pod name: virt-launcher-testvmijslnz-578q7 Pod phase: Pending Pod name: virt-launcher-testvmilq7q8-zjdxz Pod phase: Pending Pod name: virt-launcher-testvmiwmzp6-wwtgv Pod phase: Pending ------------------------------ • Failure in Spec Setup (BeforeEach) [180.968 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 should be able to reach [BeforeEach] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 the Inbound VirtualMachineInstance /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.005s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T21:44:45.375585Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmilq7q8 kind=VirtualMachineInstance uid=6f861c43-9766-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmilq7q8-zjdxz" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running 2018/08/03 21:49:00 http: TLS handshake error from 10.244.1.1:54364: EOF level=info timestamp=2018-08-03T21:49:03.360386Z 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:49:10 http: TLS handshake error from 10.244.1.1:54370: EOF 2018/08/03 21:49:20 http: TLS handshake error from 10.244.1.1:54376: EOF 2018/08/03 21:49:30 http: TLS handshake error from 10.244.1.1:54382: EOF level=info timestamp=2018-08-03T21:49:33.348173Z 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:49:40 http: TLS handshake error from 10.244.1.1:54388: EOF 2018/08/03 21:49:50 http: TLS handshake error from 10.244.1.1:54394: EOF 2018/08/03 21:50:00 http: TLS handshake error from 10.244.1.1:54400: EOF level=info timestamp=2018-08-03T21:50:03.357489Z 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:50:10 http: TLS handshake error from 10.244.1.1:54406: EOF 2018/08/03 21:50:20 http: TLS handshake error from 10.244.1.1:54412: EOF 2018/08/03 21:50:30 http: TLS handshake error from 10.244.1.1:54418: EOF level=info timestamp=2018-08-03T21:50:33.346813Z 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:50:40 http: TLS handshake error from 10.244.1.1:54424: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T21:49:29.579928Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:49:36 http: TLS handshake error from 10.244.0.1:58630: EOF level=info timestamp=2018-08-03T21:49:38.394575Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:49:38.395478Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:49:46 http: TLS handshake error from 10.244.0.1:58654: EOF 2018/08/03 21:49:56 http: TLS handshake error from 10.244.0.1:58678: EOF level=info timestamp=2018-08-03T21:49:56.642535Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:49:59.609978Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:50:06 http: TLS handshake error from 10.244.0.1:58702: EOF 2018/08/03 21:50:16 http: TLS handshake error from 10.244.0.1:58726: EOF 2018/08/03 21:50:26 http: TLS handshake error from 10.244.0.1:58750: EOF level=info timestamp=2018-08-03T21:50:26.672375Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:50:29.641273Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:50:36 http: TLS handshake error from 10.244.0.1:58774: EOF 2018/08/03 21:50:46 http: TLS handshake error from 10.244.0.1:58798: EOF Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:44:45.122551Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiwmzp6\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiwmzp6" level=info timestamp=2018-08-03T21:44:45.924921Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmic2ctl\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmic2ctl" level=info timestamp=2018-08-03T21:44:46.323314Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiwmzp6\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiwmzp6" level=info timestamp=2018-08-03T21:44:47.122627Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiwmzp6\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiwmzp6" level=info timestamp=2018-08-03T21:47:45.886465Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmic2ctl\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmic2ctl, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 6f8778c2-9766-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmic2ctl" level=info timestamp=2018-08-03T21:47:45.909990Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmijslnz\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmijslnz, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 6f8aedfc-9766-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmijslnz" level=info timestamp=2018-08-03T21:47:45.920907Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmilq7q8\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmilq7q8, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 6f861c43-9766-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmilq7q8" level=info timestamp=2018-08-03T21:47:46.627221Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9xsgt kind= uid=dbd4d7f2-9766-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:47:46.627412Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi9xsgt kind= uid=dbd4d7f2-9766-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:47:46.637236Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihw6rx kind= uid=dbd6837e-9766-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:47:46.637359Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihw6rx kind= uid=dbd6837e-9766-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:47:46.646490Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivxrfp kind= uid=dbd7c451-9766-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:47:46.646634Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivxrfp kind= uid=dbd7c451-9766-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:47:46.686240Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi95rcf kind= uid=dbd8eda5-9766-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:47:46.686346Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi95rcf kind= uid=dbd8eda5-9766-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:28:39.835572Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.891405Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.631127Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.862218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:41.604703Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.447001Z pos=health.go:55 component=virt-handler reason="tun device does not 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:46.173315Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:38:58.665965Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.641743Z pos=health.go:55 component=virt-handler reason="tun device does not 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:57.701858Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:28.187225Z pos=health.go:55 component=virt-handler reason="tun device does not 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:06.404981Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.205414Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.269273Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.673971Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:28:45.196978Z pos=health.go:55 component=virt-handler reason="tun device does not 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:47.247809Z pos=health.go:55 component=virt-handler reason="tun device does not 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:30.983248Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.211229Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:46.942432Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.779129Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.503419Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.989011Z pos=health.go:55 component=virt-handler reason="tun device does not 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:42.958098Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.021114Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:33.500844Z pos=health.go:55 component=virt-handler reason="tun device does not 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:11.715230Z pos=health.go:55 component=virt-handler reason="tun device does not 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:08.504317Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:34.570067Z pos=health.go:55 component=virt-handler reason="tun device does not 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.975494Z pos=health.go:55 component=virt-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-testvmi95rcf-krw9r Pod phase: Pending Pod name: virt-launcher-testvmi9xsgt-hcj8v Pod phase: Pending Pod name: virt-launcher-testvmihw6rx-gjnzj Pod phase: Pending Pod name: virt-launcher-testvmivxrfp-98kn4 Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.698 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 should be able to reach [BeforeEach] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 the Inbound VirtualMachineInstance with pod network connectivity explicitly set /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T21:47:47.054215Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi9xsgt kind=VirtualMachineInstance uid=dbd4d7f2-9766-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi9xsgt-hcj8v" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running 2018/08/03 21:52:00 http: TLS handshake error from 10.244.1.1:54472: EOF level=info timestamp=2018-08-03T21:52:03.332985Z 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:52:10 http: TLS handshake error from 10.244.1.1:54478: EOF 2018/08/03 21:52:20 http: TLS handshake error from 10.244.1.1:54484: EOF 2018/08/03 21:52:30 http: TLS handshake error from 10.244.1.1:54490: EOF level=info timestamp=2018-08-03T21:52:33.366712Z 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:52:40 http: TLS handshake error from 10.244.1.1:54496: EOF 2018/08/03 21:52:50 http: TLS handshake error from 10.244.1.1:54502: EOF 2018/08/03 21:53:00 http: TLS handshake error from 10.244.1.1:54508: EOF level=info timestamp=2018-08-03T21:53:03.348933Z 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:53:10 http: TLS handshake error from 10.244.1.1:54514: EOF 2018/08/03 21:53:20 http: TLS handshake error from 10.244.1.1:54520: EOF 2018/08/03 21:53:30 http: TLS handshake error from 10.244.1.1:54526: EOF level=info timestamp=2018-08-03T21:53:33.365781Z 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:53:40 http: TLS handshake error from 10.244.1.1:54532: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T21:52:29.761173Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:52:36 http: TLS handshake error from 10.244.0.1:59062: EOF level=info timestamp=2018-08-03T21:52:38.417321Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:52:38.418078Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:52:46 http: TLS handshake error from 10.244.0.1:59086: EOF 2018/08/03 21:52:56 http: TLS handshake error from 10.244.0.1:59110: EOF level=info timestamp=2018-08-03T21:52:56.830741Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:52:59.791336Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:53:06 http: TLS handshake error from 10.244.0.1:59134: EOF 2018/08/03 21:53:16 http: TLS handshake error from 10.244.0.1:59158: EOF 2018/08/03 21:53:26 http: TLS handshake error from 10.244.0.1:59182: EOF level=info timestamp=2018-08-03T21:53:26.860461Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:53:29.812827Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:53:36 http: TLS handshake error from 10.244.0.1:59206: EOF 2018/08/03 21:53:46 http: TLS handshake error from 10.244.0.1:59230: EOF Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:47:46.637359Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihw6rx kind= uid=dbd6837e-9766-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:47:46.646490Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivxrfp kind= uid=dbd7c451-9766-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:47:46.646634Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmivxrfp kind= uid=dbd7c451-9766-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:47:46.686240Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi95rcf kind= uid=dbd8eda5-9766-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:47:46.686346Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi95rcf kind= uid=dbd8eda5-9766-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:50:47.612029Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmivxrfp\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmivxrfp" level=info timestamp=2018-08-03T21:50:47.626597Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmivxrfp\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmivxrfp, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: dbd7c451-9766-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmivxrfp" level=info timestamp=2018-08-03T21:50:48.325009Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisxrp5 kind= uid=48219803-9767-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:50:48.325178Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisxrp5 kind= uid=48219803-9767-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:50:48.333768Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmish828 kind= uid=482319f4-9767-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:50:48.333917Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmish828 kind= uid=482319f4-9767-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:50:48.344292Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi2kjng kind= uid=482459c6-9767-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:50:48.344419Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi2kjng kind= uid=482459c6-9767-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:50:48.357968Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmir65kl kind= uid=4825ee08-9767-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:50:48.358068Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmir65kl kind= uid=4825ee08-9767-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:29:41.891405Z pos=health.go:55 component=virt-handler reason="tun device does not 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:25.631127Z pos=health.go:55 component=virt-handler reason="tun device does not 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:35.862218Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:41.604703Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.447001Z pos=health.go:55 component=virt-handler reason="tun device does not 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:46.173315Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:38:58.665965Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.641743Z pos=health.go:55 component=virt-handler reason="tun device does not 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:57.701858Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:28.187225Z pos=health.go:55 component=virt-handler reason="tun device does not 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:06.404981Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.205414Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.269273Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.673971Z pos=health.go:55 component=virt-handler reason="tun device does not 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:55.087074Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:31:30.983248Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.211229Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:34:46.942432Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.779129Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.503419Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.989011Z pos=health.go:55 component=virt-handler reason="tun device does not 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:42.958098Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.021114Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:33.500844Z pos=health.go:55 component=virt-handler reason="tun device does not 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:11.715230Z pos=health.go:55 component=virt-handler reason="tun device does not 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:08.504317Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:34.570067Z pos=health.go:55 component=virt-handler reason="tun device does not 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.975494Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:00.380193Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.740984Z pos=health.go:55 component=virt-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-testvmi2kjng-hdsk4 Pod phase: Pending Pod name: virt-launcher-testvmir65kl-76sf7 Pod phase: Pending Pod name: virt-launcher-testvmish828-jcjqw Pod phase: Pending Pod name: virt-launcher-testvmisxrp5-c98vl Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.685 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 should be able to reach [BeforeEach] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 the Inbound VirtualMachineInstance with custom MAC address /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T21:50:48.822188Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmisxrp5 kind=VirtualMachineInstance uid=48219803-9767-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmisxrp5-c98vl" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running 2018/08/03 21:55:00 http: TLS handshake error from 10.244.1.1:54580: EOF level=info timestamp=2018-08-03T21:55:03.334792Z 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:55:10 http: TLS handshake error from 10.244.1.1:54586: EOF 2018/08/03 21:55:20 http: TLS handshake error from 10.244.1.1:54592: EOF 2018/08/03 21:55:30 http: TLS handshake error from 10.244.1.1:54598: EOF level=info timestamp=2018-08-03T21:55:33.362530Z 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:55:40 http: TLS handshake error from 10.244.1.1:54604: EOF 2018/08/03 21:55:50 http: TLS handshake error from 10.244.1.1:54610: EOF 2018/08/03 21:56:00 http: TLS handshake error from 10.244.1.1:54616: EOF level=info timestamp=2018-08-03T21:56:03.364750Z 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:56:10 http: TLS handshake error from 10.244.1.1:54622: EOF 2018/08/03 21:56:20 http: TLS handshake error from 10.244.1.1:54628: EOF 2018/08/03 21:56:30 http: TLS handshake error from 10.244.1.1:54634: EOF level=info timestamp=2018-08-03T21:56:33.335481Z 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:56:40 http: TLS handshake error from 10.244.1.1:54640: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T21:55:29.916604Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:55:36 http: TLS handshake error from 10.244.0.1:59494: EOF 2018/08/03 21:55:46 http: TLS handshake error from 10.244.0.1:59518: EOF 2018/08/03 21:55:56 http: TLS handshake error from 10.244.0.1:59542: EOF level=info timestamp=2018-08-03T21:55:56.998497Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:55:59.946146Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:56:06 http: TLS handshake error from 10.244.0.1:59566: EOF 2018/08/03 21:56:16 http: TLS handshake error from 10.244.0.1:59590: EOF 2018/08/03 21:56:26 http: TLS handshake error from 10.244.0.1:59614: EOF level=info timestamp=2018-08-03T21:56:27.032137Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:56:29.972237Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:56:36 http: TLS handshake error from 10.244.0.1:59638: EOF level=info timestamp=2018-08-03T21:56:38.429178Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:56:38.430032Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:56:46 http: TLS handshake error from 10.244.0.1:59662: EOF Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:50:48.357968Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmir65kl kind= uid=4825ee08-9767-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:50:48.358068Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmir65kl kind= uid=4825ee08-9767-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:53:50.009282Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5xxvx kind= uid=b46c80b4-9767-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:53:50.009544Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5xxvx kind= uid=b46c80b4-9767-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:53:50.016498Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirzrjt kind= uid=b46dbb02-9767-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:53:50.016596Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirzrjt kind= uid=b46dbb02-9767-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:53:50.030234Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikrm6b kind= uid=b46fcfb3-9767-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:53:50.030316Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmikrm6b kind= uid=b46fcfb3-9767-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:53:50.072130Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilqt8b kind= uid=b4746238-9767-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:53:50.072230Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilqt8b kind= uid=b4746238-9767-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:53:50.228196Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmirzrjt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmirzrjt" level=info timestamp=2018-08-03T21:53:50.628749Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmikrm6b\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmikrm6b" level=info timestamp=2018-08-03T21:53:52.228593Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmilqt8b\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmilqt8b" level=info timestamp=2018-08-03T21:53:52.628363Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmilqt8b\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmilqt8b" level=info timestamp=2018-08-03T21:53:53.029895Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmilqt8b\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmilqt8b" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:34:41.604703Z pos=health.go:55 component=virt-handler reason="tun device does not 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:24.447001Z pos=health.go:55 component=virt-handler reason="tun device does not 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:46.173315Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:38:58.665965Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.641743Z pos=health.go:55 component=virt-handler reason="tun device does not 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:57.701858Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:28.187225Z pos=health.go:55 component=virt-handler reason="tun device does not 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:06.404981Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.205414Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.269273Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.673971Z pos=health.go:55 component=virt-handler reason="tun device does not 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:55.087074Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.441067Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.806614Z pos=health.go:55 component=virt-handler reason="tun device does not 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:26.846574Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:34:46.942432Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:36:29.779129Z pos=health.go:55 component=virt-handler reason="tun device does not 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:51.503419Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.989011Z pos=health.go:55 component=virt-handler reason="tun device does not 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:42.958098Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.021114Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:33.500844Z pos=health.go:55 component=virt-handler reason="tun device does not 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:11.715230Z pos=health.go:55 component=virt-handler reason="tun device does not 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:08.504317Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:34.570067Z pos=health.go:55 component=virt-handler reason="tun device does not 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.975494Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:00.380193Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.740984Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.764066Z pos=health.go:55 component=virt-handler reason="tun device does not 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:10.824493Z pos=health.go:55 component=virt-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-testvmi5xxvx-4stwj Pod phase: Pending Pod name: virt-launcher-testvmikrm6b-wp4pw Pod phase: Pending Pod name: virt-launcher-testvmilqt8b-bsp9x Pod phase: Pending Pod name: virt-launcher-testvmirzrjt-4wngj Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.709 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 should be able to reach [BeforeEach] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 the internet /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T21:53:50.445484Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi5xxvx kind=VirtualMachineInstance uid=b46c80b4-9767-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi5xxvx-4stwj" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T21:58:03.336050Z 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:58:10 http: TLS handshake error from 10.244.1.1:54694: EOF 2018/08/03 21:58:20 http: TLS handshake error from 10.244.1.1:54700: EOF 2018/08/03 21:58:30 http: TLS handshake error from 10.244.1.1:54706: EOF level=info timestamp=2018-08-03T21:58:33.364981Z 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:58:40 http: TLS handshake error from 10.244.1.1:54712: EOF 2018/08/03 21:58:50 http: TLS handshake error from 10.244.1.1:54718: EOF 2018/08/03 21:59:00 http: TLS handshake error from 10.244.1.1:54724: EOF level=info timestamp=2018-08-03T21:59:03.364426Z 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:59:10 http: TLS handshake error from 10.244.1.1:54730: EOF 2018/08/03 21:59:20 http: TLS handshake error from 10.244.1.1:54736: EOF 2018/08/03 21:59:30 http: TLS handshake error from 10.244.1.1:54742: EOF level=info timestamp=2018-08-03T21:59:33.337774Z 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:59:40 http: TLS handshake error from 10.244.1.1:54748: EOF 2018/08/03 21:59:50 http: TLS handshake error from 10.244.1.1:54754: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T21:58:30.096535Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:58:36 http: TLS handshake error from 10.244.0.1:59926: EOF 2018/08/03 21:58:46 http: TLS handshake error from 10.244.0.1:59950: EOF 2018/08/03 21:58:56 http: TLS handshake error from 10.244.0.1:59974: EOF level=info timestamp=2018-08-03T21:58:57.177042Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:59:00.128085Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:59:06 http: TLS handshake error from 10.244.0.1:59998: EOF 2018/08/03 21:59:16 http: TLS handshake error from 10.244.0.1:60022: EOF 2018/08/03 21:59:26 http: TLS handshake error from 10.244.0.1:60046: EOF level=info timestamp=2018-08-03T21:59:27.205304Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T21:59:30.161598Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 21:59:36 http: TLS handshake error from 10.244.0.1:60070: EOF level=info timestamp=2018-08-03T21:59:38.433612Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T21:59:38.434454Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 21:59:46 http: TLS handshake error from 10.244.0.1:60094: EOF Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:53:50.228196Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmirzrjt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmirzrjt" level=info timestamp=2018-08-03T21:53:50.628749Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmikrm6b\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmikrm6b" level=info timestamp=2018-08-03T21:53:52.228593Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmilqt8b\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmilqt8b" level=info timestamp=2018-08-03T21:53:52.628363Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmilqt8b\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmilqt8b" level=info timestamp=2018-08-03T21:53:53.029895Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmilqt8b\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmilqt8b" level=info timestamp=2018-08-03T21:56:50.985811Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi5xxvx\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi5xxvx, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: b46c80b4-9767-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi5xxvx" level=info timestamp=2018-08-03T21:56:51.723565Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7vjb7 kind= uid=20bbbcc4-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:56:51.723722Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7vjb7 kind= uid=20bbbcc4-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:56:51.732284Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiht2x7 kind= uid=20bd3559-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:56:51.732421Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiht2x7 kind= uid=20bd3559-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:56:51.742980Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig87x4 kind= uid=20be7d85-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:56:51.743072Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig87x4 kind= uid=20be7d85-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:56:51.775125Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibjrp9 kind= uid=20c0de66-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:56:51.775203Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibjrp9 kind= uid=20c0de66-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:56:51.781971Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi7vjb7\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi7vjb7" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:37:46.173315Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:38:58.665965Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.641743Z pos=health.go:55 component=virt-handler reason="tun device does not 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:57.701858Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:28.187225Z pos=health.go:55 component=virt-handler reason="tun device does not 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:06.404981Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.205414Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.269273Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.673971Z pos=health.go:55 component=virt-handler reason="tun device does not 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:55.087074Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.441067Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.806614Z pos=health.go:55 component=virt-handler reason="tun device does not 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:26.846574Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:57:49.289586Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:59:42.710016Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:37:51.503419Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.989011Z pos=health.go:55 component=virt-handler reason="tun device does not 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:42.958098Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.021114Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:33.500844Z pos=health.go:55 component=virt-handler reason="tun device does not 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:11.715230Z pos=health.go:55 component=virt-handler reason="tun device does not 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:08.504317Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:34.570067Z pos=health.go:55 component=virt-handler reason="tun device does not 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.975494Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:00.380193Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.740984Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.764066Z pos=health.go:55 component=virt-handler reason="tun device does not 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:10.824493Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:57:28.230055Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.674769Z pos=health.go:55 component=virt-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-testvmi7vjb7-cst25 Pod phase: Pending Pod name: virt-launcher-testvmibjrp9-v5wv8 Pod phase: Pending Pod name: virt-launcher-testvmig87x4-dz2bn Pod phase: Pending Pod name: virt-launcher-testvmiht2x7-vqjs7 Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.701 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 should be reachable via the propagated IP from a Pod [BeforeEach] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 on the same node from Pod /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T21:56:52.143509Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi7vjb7 kind=VirtualMachineInstance uid=20bbbcc4-9768-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi7vjb7-cst25" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running 2018/08/03 22:01:20 http: TLS handshake error from 10.244.1.1:54808: EOF 2018/08/03 22:01:30 http: TLS handshake error from 10.244.1.1:54814: EOF level=info timestamp=2018-08-03T22:01:33.279484Z 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:01:33.296749Z 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:01:33.338391Z 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:01:40 http: TLS handshake error from 10.244.1.1:54820: EOF 2018/08/03 22:01:50 http: TLS handshake error from 10.244.1.1:54826: EOF 2018/08/03 22:02:00 http: TLS handshake error from 10.244.1.1:54832: EOF level=info timestamp=2018-08-03T22:02:03.373866Z 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:02:10 http: TLS handshake error from 10.244.1.1:54838: EOF 2018/08/03 22:02:20 http: TLS handshake error from 10.244.1.1:54844: EOF 2018/08/03 22:02:30 http: TLS handshake error from 10.244.1.1:54850: EOF level=info timestamp=2018-08-03T22:02:33.370001Z 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:02:40 http: TLS handshake error from 10.244.1.1:54856: EOF 2018/08/03 22:02:50 http: TLS handshake error from 10.244.1.1:54862: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T22:01:38.327863Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:01:38.328825Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:01:46 http: TLS handshake error from 10.244.0.1:60382: EOF 2018/08/03 22:01:56 http: TLS handshake error from 10.244.0.1:60406: EOF level=info timestamp=2018-08-03T22:01:57.352223Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:02:00.310403Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:02:06 http: TLS handshake error from 10.244.0.1:60430: EOF 2018/08/03 22:02:16 http: TLS handshake error from 10.244.0.1:60454: EOF 2018/08/03 22:02:26 http: TLS handshake error from 10.244.0.1:60478: EOF level=info timestamp=2018-08-03T22:02:27.380684Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:02:30.339370Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:02:36 http: TLS handshake error from 10.244.0.1:60502: EOF level=info timestamp=2018-08-03T22:02:38.330192Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:02:38.331126Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:02:46 http: TLS handshake error from 10.244.0.1:60526: EOF Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:56:51.742980Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig87x4 kind= uid=20be7d85-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:56:51.743072Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmig87x4 kind= uid=20be7d85-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:56:51.775125Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibjrp9 kind= uid=20c0de66-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:56:51.775203Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmibjrp9 kind= uid=20c0de66-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:56:51.781971Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi7vjb7\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi7vjb7" level=info timestamp=2018-08-03T21:59:52.668405Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmibjrp9\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmibjrp9" level=info timestamp=2018-08-03T21:59:52.720160Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiht2x7\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmiht2x7, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 20bd3559-9768-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiht2x7" level=info timestamp=2018-08-03T21:59:53.422844Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitdktw kind= uid=8d08a4ea-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:59:53.422989Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmitdktw kind= uid=8d08a4ea-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:59:53.437819Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifxzpn kind= uid=8d0a1b4d-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:59:53.437916Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifxzpn kind= uid=8d0a1b4d-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:59:53.441649Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi868hw kind= uid=8d0bde2e-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:59:53.441698Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi868hw kind= uid=8d0bde2e-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:59:53.451585Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7cwzk kind= uid=8d0d4815-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:59:53.451673Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7cwzk kind= uid=8d0d4815-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:38:58.665965Z pos=health.go:55 component=virt-handler reason="tun device does not 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:37.641743Z pos=health.go:55 component=virt-handler reason="tun device does not 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:57.701858Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:28.187225Z pos=health.go:55 component=virt-handler reason="tun device does not 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:06.404981Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.205414Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.269273Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.673971Z pos=health.go:55 component=virt-handler reason="tun device does not 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:55.087074Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.441067Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.806614Z pos=health.go:55 component=virt-handler reason="tun device does not 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:26.846574Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:57:49.289586Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:59:42.710016Z pos=health.go:55 component=virt-handler reason="tun device does not 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:40.401628Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:40:42.958098Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.021114Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:33.500844Z pos=health.go:55 component=virt-handler reason="tun device does not 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:11.715230Z pos=health.go:55 component=virt-handler reason="tun device does not 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:08.504317Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:34.570067Z pos=health.go:55 component=virt-handler reason="tun device does not 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.975494Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:00.380193Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.740984Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.764066Z pos=health.go:55 component=virt-handler reason="tun device does not 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:10.824493Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:57:28.230055Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.674769Z pos=health.go:55 component=virt-handler reason="tun device does not 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:44.103744Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.795776Z pos=health.go:55 component=virt-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-testvmi7cwzk-c54cp Pod phase: Pending Pod name: virt-launcher-testvmi868hw-648d8 Pod phase: Pending Pod name: virt-launcher-testvmifxzpn-r2lpc Pod phase: Pending Pod name: virt-launcher-testvmitdktw-l6sb8 Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.682 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 should be reachable via the propagated IP from a Pod [BeforeEach] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 on a different node from Pod /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T21:59:53.918894Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmitdktw kind=VirtualMachineInstance uid=8d08a4ea-9768-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmitdktw-l6sb8" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T22:04:03.371138Z 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:04:10 http: TLS handshake error from 10.244.1.1:54910: EOF 2018/08/03 22:04:20 http: TLS handshake error from 10.244.1.1:54916: EOF 2018/08/03 22:04:30 http: TLS handshake error from 10.244.1.1:54922: EOF level=info timestamp=2018-08-03T22:04:33.339595Z 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:04:40 http: TLS handshake error from 10.244.1.1:54928: EOF 2018/08/03 22:04:50 http: TLS handshake error from 10.244.1.1:54934: EOF 2018/08/03 22:05:00 http: TLS handshake error from 10.244.1.1:54940: EOF level=info timestamp=2018-08-03T22:05:03.340047Z 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:05:10 http: TLS handshake error from 10.244.1.1:54946: EOF 2018/08/03 22:05:20 http: TLS handshake error from 10.244.1.1:54952: EOF 2018/08/03 22:05:30 http: TLS handshake error from 10.244.1.1:54958: EOF level=info timestamp=2018-08-03T22:05:33.379971Z 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:05:40 http: TLS handshake error from 10.244.1.1:54964: EOF 2018/08/03 22:05:50 http: TLS handshake error from 10.244.1.1:54970: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T22:04:30.455196Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:04:36 http: TLS handshake error from 10.244.0.1:60790: EOF level=info timestamp=2018-08-03T22:04:38.332512Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:04:38.333483Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:04:46 http: TLS handshake error from 10.244.0.1:60814: EOF 2018/08/03 22:04:56 http: TLS handshake error from 10.244.0.1:60838: EOF level=info timestamp=2018-08-03T22:04:57.535642Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:05:00.481586Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:05:06 http: TLS handshake error from 10.244.0.1:60862: EOF 2018/08/03 22:05:16 http: TLS handshake error from 10.244.0.1:60886: EOF 2018/08/03 22:05:26 http: TLS handshake error from 10.244.0.1:60910: EOF level=info timestamp=2018-08-03T22:05:27.563238Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:05:30.508102Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:05:36 http: TLS handshake error from 10.244.0.1:60934: EOF 2018/08/03 22:05:46 http: TLS handshake error from 10.244.0.1:60958: EOF Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T21:59:53.437819Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifxzpn kind= uid=8d0a1b4d-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:59:53.437916Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmifxzpn kind= uid=8d0a1b4d-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:59:53.441649Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi868hw kind= uid=8d0bde2e-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:59:53.441698Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi868hw kind= uid=8d0bde2e-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T21:59:53.451585Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7cwzk kind= uid=8d0d4815-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T21:59:53.451673Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7cwzk kind= uid=8d0d4815-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:02:54.904030Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwtddj kind= uid=f934804a-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:02:54.904304Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwtddj kind= uid=f934804a-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:02:54.912398Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmif5f8k kind= uid=f9361263-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:02:54.912499Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmif5f8k kind= uid=f9361263-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:02:54.924751Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirjmjv kind= uid=f937cc4a-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:02:54.924852Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirjmjv kind= uid=f937cc4a-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:02:54.945446Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiktv2f kind= uid=f9396a5a-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:02:54.945559Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiktv2f kind= uid=f9396a5a-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:02:55.317036Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmif5f8k\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmif5f8k" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:41:57.701858Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:43:28.187225Z pos=health.go:55 component=virt-handler reason="tun device does not 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:06.404981Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.205414Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.269273Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.673971Z pos=health.go:55 component=virt-handler reason="tun device does not 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:55.087074Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.441067Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.806614Z pos=health.go:55 component=virt-handler reason="tun device does not 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:26.846574Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:57:49.289586Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:59:42.710016Z pos=health.go:55 component=virt-handler reason="tun device does not 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:40.401628Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:03:32.995613Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:05:03.853403Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:43:33.500844Z pos=health.go:55 component=virt-handler reason="tun device does not 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:11.715230Z pos=health.go:55 component=virt-handler reason="tun device does not 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:08.504317Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:34.570067Z pos=health.go:55 component=virt-handler reason="tun device does not 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.975494Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:00.380193Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.740984Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.764066Z pos=health.go:55 component=virt-handler reason="tun device does not 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:10.824493Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:57:28.230055Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.674769Z pos=health.go:55 component=virt-handler reason="tun device does not 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:44.103744Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.795776Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:03:54.981470Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:05:25.842533Z pos=health.go:55 component=virt-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-testvmif5f8k-cfxhc Pod phase: Pending Pod name: virt-launcher-testvmiktv2f-vjplp Pod phase: Pending Pod name: virt-launcher-testvmirjmjv-tc2d4 Pod phase: Pending Pod name: virt-launcher-testvmiwtddj-2dxkq Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.497 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 should be reachable via the propagated IP from a Pod [BeforeEach] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 on the same node from Node /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T22:02:55.327459Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmiwtddj kind=VirtualMachineInstance uid=f934804a-9768-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmiwtddj-2dxkq" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T22:07:03.369249Z 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:07:10 http: TLS handshake error from 10.244.1.1:55018: EOF 2018/08/03 22:07:20 http: TLS handshake error from 10.244.1.1:55024: EOF 2018/08/03 22:07:30 http: TLS handshake error from 10.244.1.1:55030: EOF level=info timestamp=2018-08-03T22:07:33.362839Z 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:07:40 http: TLS handshake error from 10.244.1.1:55036: EOF 2018/08/03 22:07:50 http: TLS handshake error from 10.244.1.1:55042: EOF 2018/08/03 22:08:00 http: TLS handshake error from 10.244.1.1:55048: EOF level=info timestamp=2018-08-03T22:08:03.364282Z 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:08:10 http: TLS handshake error from 10.244.1.1:55054: EOF 2018/08/03 22:08:20 http: TLS handshake error from 10.244.1.1:55060: EOF 2018/08/03 22:08:30 http: TLS handshake error from 10.244.1.1:55066: EOF level=info timestamp=2018-08-03T22:08:33.374735Z 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:08:40 http: TLS handshake error from 10.244.1.1:55072: EOF 2018/08/03 22:08:50 http: TLS handshake error from 10.244.1.1:55078: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running 2018/08/03 22:07:36 http: TLS handshake error from 10.244.0.1:32990: EOF level=info timestamp=2018-08-03T22:07:38.466588Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:07:38.467367Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:07:46 http: TLS handshake error from 10.244.0.1:33014: EOF 2018/08/03 22:07:56 http: TLS handshake error from 10.244.0.1:33038: EOF level=info timestamp=2018-08-03T22:07:57.734123Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:08:00.669415Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:08:06 http: TLS handshake error from 10.244.0.1:33062: EOF 2018/08/03 22:08:16 http: TLS handshake error from 10.244.0.1:33086: EOF 2018/08/03 22:08:26 http: TLS handshake error from 10.244.0.1:33110: EOF level=info timestamp=2018-08-03T22:08:27.757826Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:08:30.701563Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:08:36 http: TLS handshake error from 10.244.0.1:33134: EOF 2018/08/03 22:08:46 http: TLS handshake error from 10.244.0.1:33158: EOF 2018/08/03 22:08:56 http: TLS handshake error from 10.244.0.1:33182: EOF Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T22:02:54.912398Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmif5f8k kind= uid=f9361263-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:02:54.912499Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmif5f8k kind= uid=f9361263-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:02:54.924751Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirjmjv kind= uid=f937cc4a-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:02:54.924852Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmirjmjv kind= uid=f937cc4a-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:02:54.945446Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiktv2f kind= uid=f9396a5a-9768-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:02:54.945559Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiktv2f kind= uid=f9396a5a-9768-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:02:55.317036Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmif5f8k\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmif5f8k" level=info timestamp=2018-08-03T22:05:56.616813Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisj5rh kind= uid=6583fa82-9769-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:56.617008Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisj5rh kind= uid=6583fa82-9769-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:05:56.625875Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvminqpj4 kind= uid=65858c2a-9769-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:56.626081Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvminqpj4 kind= uid=65858c2a-9769-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:05:56.636258Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7785j kind= uid=6587179a-9769-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:56.636369Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7785j kind= uid=6587179a-9769-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:05:56.661666Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmidh9xp kind= uid=65887abe-9769-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:56.661780Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmidh9xp kind= uid=65887abe-9769-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:43:28.187225Z pos=health.go:55 component=virt-handler reason="tun device does not 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:06.404981Z pos=health.go:55 component=virt-handler reason="tun device does not 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:03.205414Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.269273Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.673971Z pos=health.go:55 component=virt-handler reason="tun device does not 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:55.087074Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.441067Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.806614Z pos=health.go:55 component=virt-handler reason="tun device does not 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:26.846574Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:57:49.289586Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:59:42.710016Z pos=health.go:55 component=virt-handler reason="tun device does not 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:40.401628Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:03:32.995613Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:05:03.853403Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:07:08.449082Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:45:11.715230Z pos=health.go:55 component=virt-handler reason="tun device does not 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:08.504317Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:48:34.570067Z pos=health.go:55 component=virt-handler reason="tun device does not 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.975494Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:00.380193Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.740984Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.764066Z pos=health.go:55 component=virt-handler reason="tun device does not 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:10.824493Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:57:28.230055Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.674769Z pos=health.go:55 component=virt-handler reason="tun device does not 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:44.103744Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.795776Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:03:54.981470Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:05:25.842533Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:07:30.448675Z pos=health.go:55 component=virt-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-testvmi7785j-5dfgk Pod phase: Pending Pod name: virt-launcher-testvmidh9xp-tj5v4 Pod phase: Pending Pod name: virt-launcher-testvminqpj4-lndhn Pod phase: Pending Pod name: virt-launcher-testvmisj5rh-j7lmg Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.719 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 should be reachable via the propagated IP from a Pod [BeforeEach] /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92 on a different node from Node /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46 Timed out after 90.003s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T22:05:57.038382Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmisj5rh kind=VirtualMachineInstance uid=6583fa82-9769-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmisj5rh-j7lmg" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running 2018/08/03 22:10:20 http: TLS handshake error from 10.244.1.1:55132: EOF 2018/08/03 22:10:30 http: TLS handshake error from 10.244.1.1:55138: EOF level=info timestamp=2018-08-03T22:10:33.359605Z 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:10:40 http: TLS handshake error from 10.244.1.1:55144: EOF 2018/08/03 22:10:50 http: TLS handshake error from 10.244.1.1:55150: EOF 2018/08/03 22:11:00 http: TLS handshake error from 10.244.1.1:55156: EOF level=info timestamp=2018-08-03T22:11:03.374025Z 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:11:10 http: TLS handshake error from 10.244.1.1:55162: EOF 2018/08/03 22:11:20 http: TLS handshake error from 10.244.1.1:55168: EOF 2018/08/03 22:11:30 http: TLS handshake error from 10.244.1.1:55174: EOF level=info timestamp=2018-08-03T22:11:33.279717Z 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:11:33.296727Z 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:11:33.372976Z 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:11:40 http: TLS handshake error from 10.244.1.1:55180: EOF 2018/08/03 22:11:50 http: TLS handshake error from 10.244.1.1:55186: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running 2018/08/03 22:10:46 http: TLS handshake error from 10.244.0.1:33446: EOF 2018/08/03 22:10:56 http: TLS handshake error from 10.244.0.1:33470: EOF level=info timestamp=2018-08-03T22:10:57.928760Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:11:00.846868Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:11:06 http: TLS handshake error from 10.244.0.1:33494: EOF 2018/08/03 22:11:16 http: TLS handshake error from 10.244.0.1:33518: EOF 2018/08/03 22:11:26 http: TLS handshake error from 10.244.0.1:33542: EOF level=info timestamp=2018-08-03T22:11:27.965794Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:11:30.877548Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:11:36 http: TLS handshake error from 10.244.0.1:33566: EOF level=info timestamp=2018-08-03T22:11:38.476615Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:11:38.478591Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:11:46 http: TLS handshake error from 10.244.0.1:33590: EOF 2018/08/03 22:11:56 http: TLS handshake error from 10.244.0.1:33614: EOF level=info timestamp=2018-08-03T22:11:57.996163Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T22:05:56.636258Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7785j kind= uid=6587179a-9769-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:56.636369Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi7785j kind= uid=6587179a-9769-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:05:56.661666Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmidh9xp kind= uid=65887abe-9769-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:05:56.661780Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmidh9xp kind= uid=65887abe-9769-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:08:57.612701Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmisj5rh\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmisj5rh, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 6583fa82-9769-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmisj5rh" level=info timestamp=2018-08-03T22:08:58.321162Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwsk6h kind= uid=d1d1a2a3-9769-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:08:58.321370Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwsk6h kind= uid=d1d1a2a3-9769-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:08:58.328856Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiznkvj kind= uid=d1d32b98-9769-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:08:58.329003Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiznkvj kind= uid=d1d32b98-9769-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:08:58.340155Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmicj7rt kind= uid=d1d47273-9769-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:08:58.340228Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmicj7rt kind= uid=d1d47273-9769-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:08:58.350870Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmimgzkg kind= uid=d1d5ff47-9769-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:08:58.350975Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmimgzkg kind= uid=d1d5ff47-9769-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:08:58.542375Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmicj7rt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmicj7rt" level=info timestamp=2018-08-03T22:08:58.742627Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiwsk6h\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiwsk6h" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:47:03.205414Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.269273Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.673971Z pos=health.go:55 component=virt-handler reason="tun device does not 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:55.087074Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.441067Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.806614Z pos=health.go:55 component=virt-handler reason="tun device does not 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:26.846574Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:57:49.289586Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:59:42.710016Z pos=health.go:55 component=virt-handler reason="tun device does not 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:40.401628Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:03:32.995613Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:05:03.853403Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:07:08.449082Z pos=health.go:55 component=virt-handler reason="tun device does not 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:57.617169Z pos=health.go:55 component=virt-handler reason="tun device does not 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:33.140454Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:48:34.570067Z pos=health.go:55 component=virt-handler reason="tun device does not 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.975494Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:00.380193Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.740984Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.764066Z pos=health.go:55 component=virt-handler reason="tun device does not 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:10.824493Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:57:28.230055Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.674769Z pos=health.go:55 component=virt-handler reason="tun device does not 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:44.103744Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.795776Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:03:54.981470Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:05:25.842533Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:07:30.448675Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:09:40.941784Z pos=health.go:55 component=virt-handler reason="tun device does not 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:16.464752Z pos=health.go:55 component=virt-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-testvmicj7rt-8lh44 Pod phase: Pending Pod name: virt-launcher-testvmimgzkg-g5dq7 Pod phase: Pending Pod name: virt-launcher-testvmiwsk6h-k72wj Pod phase: Pending Pod name: virt-launcher-testvmiznkvj-pg52k Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.691 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 with a service matching the vmi exposed [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:272 should be able to reach the vmi based on labels specified on the vmi /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:292 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T22:08:58.736286Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmiwsk6h kind=VirtualMachineInstance uid=d1d1a2a3-9769-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmiwsk6h-k72wj" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running level=info timestamp=2018-08-03T22:13:03.380567Z 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:13:10 http: TLS handshake error from 10.244.1.1:55234: EOF 2018/08/03 22:13:20 http: TLS handshake error from 10.244.1.1:55240: EOF 2018/08/03 22:13:30 http: TLS handshake error from 10.244.1.1:55246: EOF level=info timestamp=2018-08-03T22:13:33.379782Z 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:13:40 http: TLS handshake error from 10.244.1.1:55252: EOF 2018/08/03 22:13:50 http: TLS handshake error from 10.244.1.1:55258: EOF 2018/08/03 22:14:00 http: TLS handshake error from 10.244.1.1:55264: EOF level=info timestamp=2018-08-03T22:14:03.345006Z 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:14:10 http: TLS handshake error from 10.244.1.1:55270: EOF 2018/08/03 22:14:20 http: TLS handshake error from 10.244.1.1:55276: EOF 2018/08/03 22:14:30 http: TLS handshake error from 10.244.1.1:55282: EOF level=info timestamp=2018-08-03T22:14:33.385940Z 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:14:40 http: TLS handshake error from 10.244.1.1:55288: EOF 2018/08/03 22:14:50 http: TLS handshake error from 10.244.1.1:55294: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running 2018/08/03 22:13:46 http: TLS handshake error from 10.244.0.1:33878: EOF 2018/08/03 22:13:56 http: TLS handshake error from 10.244.0.1:33902: EOF level=info timestamp=2018-08-03T22:13:58.140834Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:14:01.035582Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:14:06 http: TLS handshake error from 10.244.0.1:33926: EOF 2018/08/03 22:14:16 http: TLS handshake error from 10.244.0.1:33950: EOF 2018/08/03 22:14:26 http: TLS handshake error from 10.244.0.1:33974: EOF level=info timestamp=2018-08-03T22:14:28.167455Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:14:31.064225Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:14:36 http: TLS handshake error from 10.244.0.1:33998: EOF level=info timestamp=2018-08-03T22:14:38.481851Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:14:38.483135Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:14:46 http: TLS handshake error from 10.244.0.1:34022: EOF 2018/08/03 22:14:56 http: TLS handshake error from 10.244.0.1:34046: EOF level=info timestamp=2018-08-03T22:14:58.197518Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T22:08:58.329003Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiznkvj kind= uid=d1d32b98-9769-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:08:58.340155Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmicj7rt kind= uid=d1d47273-9769-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:08:58.340228Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmicj7rt kind= uid=d1d47273-9769-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:08:58.350870Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmimgzkg kind= uid=d1d5ff47-9769-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:08:58.350975Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmimgzkg kind= uid=d1d5ff47-9769-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:08:58.542375Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmicj7rt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmicj7rt" level=info timestamp=2018-08-03T22:08:58.742627Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmiwsk6h\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmiwsk6h" level=info timestamp=2018-08-03T22:12:00.009053Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmix7m7t kind= uid=3e1d2442-976a-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:12:00.009222Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmix7m7t kind= uid=3e1d2442-976a-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:12:00.015733Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisgprc kind= uid=3e1eadda-976a-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:12:00.015826Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmisgprc kind= uid=3e1eadda-976a-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:12:00.026734Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiltsqn kind= uid=3e201d53-976a-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:12:00.026825Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiltsqn kind= uid=3e201d53-976a-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:12:00.047518Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigpkvn kind= uid=3e21475e-976a-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:12:00.047587Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigpkvn kind= uid=3e21475e-976a-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:49:50.673971Z pos=health.go:55 component=virt-handler reason="tun device does not 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:55.087074Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.441067Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.806614Z pos=health.go:55 component=virt-handler reason="tun device does not 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:26.846574Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:57:49.289586Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:59:42.710016Z pos=health.go:55 component=virt-handler reason="tun device does not 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:40.401628Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:03:32.995613Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:05:03.853403Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:07:08.449082Z pos=health.go:55 component=virt-handler reason="tun device does not 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:57.617169Z pos=health.go:55 component=virt-handler reason="tun device does not 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:33.140454Z pos=health.go:55 component=virt-handler reason="tun device does not 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:39.895856Z pos=health.go:55 component=virt-handler reason="tun device does not 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:48.667926Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:49:55.975494Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:52:00.380193Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.740984Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.764066Z pos=health.go:55 component=virt-handler reason="tun device does not 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:10.824493Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:57:28.230055Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.674769Z pos=health.go:55 component=virt-handler reason="tun device does not 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:44.103744Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.795776Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:03:54.981470Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:05:25.842533Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:07:30.448675Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:09:40.941784Z pos=health.go:55 component=virt-handler reason="tun device does not 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:16.464752Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:13:23.223800Z pos=health.go:55 component=virt-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-testvmigpkvn-ls2gk Pod phase: Pending Pod name: virt-launcher-testvmiltsqn-blpjh Pod phase: Pending Pod name: virt-launcher-testvmisgprc-7khbc Pod phase: Pending Pod name: virt-launcher-testvmix7m7t-wggp6 Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.701 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 with a service matching the vmi exposed [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:272 should fail to reach the vmi if an invalid servicename is used /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:303 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T22:12:00.551749Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmix7m7t kind=VirtualMachineInstance uid=3e1d2442-976a-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmix7m7t-wggp6" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running 2018/08/03 22:16:10 http: TLS handshake error from 10.244.1.1:55342: EOF 2018/08/03 22:16:20 http: TLS handshake error from 10.244.1.1:55348: EOF 2018/08/03 22:16:30 http: TLS handshake error from 10.244.1.1:55354: EOF level=info timestamp=2018-08-03T22:16:33.345290Z 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:16:40 http: TLS handshake error from 10.244.1.1:55360: EOF 2018/08/03 22:16:50 http: TLS handshake error from 10.244.1.1:55366: EOF 2018/08/03 22:17:00 http: TLS handshake error from 10.244.1.1:55372: EOF level=info timestamp=2018-08-03T22:17:03.393797Z 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:17:10 http: TLS handshake error from 10.244.1.1:55378: EOF 2018/08/03 22:17:20 http: TLS handshake error from 10.244.1.1:55384: EOF 2018/08/03 22:17:30 http: TLS handshake error from 10.244.1.1:55390: EOF level=info timestamp=2018-08-03T22:17:33.360755Z 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:17:40 http: TLS handshake error from 10.244.1.1:55396: EOF 2018/08/03 22:17:50 http: TLS handshake error from 10.244.1.1:55402: EOF 2018/08/03 22:18:00 http: TLS handshake error from 10.244.1.1:55408: EOF Pod name: virt-api-7d79764579-hqpn2 Pod phase: Running 2018/08/03 22:16:56 http: TLS handshake error from 10.244.0.1:34334: EOF level=info timestamp=2018-08-03T22:16:58.322412Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:17:01.197869Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:17:06 http: TLS handshake error from 10.244.0.1:34358: EOF 2018/08/03 22:17:16 http: TLS handshake error from 10.244.0.1:34382: EOF 2018/08/03 22:17:26 http: TLS handshake error from 10.244.0.1:34406: EOF level=info timestamp=2018-08-03T22:17:28.352268Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:17:31.227137Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:17:36 http: TLS handshake error from 10.244.0.1:34430: EOF level=info timestamp=2018-08-03T22:17:38.310234Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:17:38.311194Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:17:46 http: TLS handshake error from 10.244.0.1:34454: EOF 2018/08/03 22:17:56 http: TLS handshake error from 10.244.0.1:34478: EOF level=info timestamp=2018-08-03T22:17:58.390510Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:18:01.255750Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T22:12:00.026734Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiltsqn kind= uid=3e201d53-976a-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:12:00.026825Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiltsqn kind= uid=3e201d53-976a-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:12:00.047518Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigpkvn kind= uid=3e21475e-976a-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:12:00.047587Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmigpkvn kind= uid=3e21475e-976a-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:15:00.979941Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmigpkvn\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmigpkvn, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 3e21475e-976a-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmigpkvn" level=info timestamp=2018-08-03T22:15:01.708098Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin4j4k kind= uid=aa6a5fb7-976a-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:15:01.708273Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmin4j4k kind= uid=aa6a5fb7-976a-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:15:01.717761Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilrlzt kind= uid=aa6c03a5-976a-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:15:01.717880Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmilrlzt kind= uid=aa6c03a5-976a-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:15:01.730039Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi2nkzt kind= uid=aa6d6a53-976a-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:15:01.730190Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi2nkzt kind= uid=aa6d6a53-976a-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:15:01.752955Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5mlmj kind= uid=aa6f1d69-976a-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:15:01.753043Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5mlmj kind= uid=aa6f1d69-976a-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:15:01.758135Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmin4j4k\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmin4j4k" level=info timestamp=2018-08-03T22:15:01.943442Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmilrlzt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmilrlzt" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:51:55.087074Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.441067Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:55:10.806614Z pos=health.go:55 component=virt-handler reason="tun device does not 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:26.846574Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:57:49.289586Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:59:42.710016Z pos=health.go:55 component=virt-handler reason="tun device does not 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:40.401628Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:03:32.995613Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:05:03.853403Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:07:08.449082Z pos=health.go:55 component=virt-handler reason="tun device does not 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:57.617169Z pos=health.go:55 component=virt-handler reason="tun device does not 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:33.140454Z pos=health.go:55 component=virt-handler reason="tun device does not 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:39.895856Z pos=health.go:55 component=virt-handler reason="tun device does not 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:48.667926Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:16:38.430958Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:53:05.740984Z pos=health.go:55 component=virt-handler reason="tun device does not 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:21.764066Z pos=health.go:55 component=virt-handler reason="tun device does not 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:10.824493Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:57:28.230055Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.674769Z pos=health.go:55 component=virt-handler reason="tun device does not 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:44.103744Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.795776Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:03:54.981470Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:05:25.842533Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:07:30.448675Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:09:40.941784Z pos=health.go:55 component=virt-handler reason="tun device does not 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:16.464752Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:13:23.223800Z pos=health.go:55 component=virt-handler reason="tun device does not 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:31.997096Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:17:21.755145Z pos=health.go:55 component=virt-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-testvmi2nkzt-kr6gt Pod phase: Pending Pod name: virt-launcher-testvmi5mlmj-vkgtk Pod phase: Pending Pod name: virt-launcher-testvmilrlzt-ldvfr Pod phase: Pending Pod name: virt-launcher-testvmin4j4k-cf6jw Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.695 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 with a subdomain and a headless service given [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:319 should be able to reach the vmi via its unique fully qualified domain name /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:342 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T22:15:02.126214Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmin4j4k kind=VirtualMachineInstance uid=aa6a5fb7-976a-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmin4j4k-cf6jw" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running 2018/08/03 22:19:20 http: TLS handshake error from 10.244.1.1:55456: EOF 2018/08/03 22:19:30 http: TLS handshake error from 10.244.1.1:55462: EOF level=info timestamp=2018-08-03T22:19:33.362936Z 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:19:40 http: TLS handshake error from 10.244.1.1:55468: EOF 2018/08/03 22:19:50 http: TLS handshake error from 10.244.1.1:55474: EOF 2018/08/03 22:20:00 http: TLS handshake error from 10.244.1.1:55480: EOF level=info timestamp=2018-08-03T22:20:03.348413Z 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:20:10 http: TLS handshake error from 10.244.1.1:55486: EOF 2018/08/03 22:20:20 http: TLS handshake error from 10.244.1.1:55492: EOF 2018/08/03 22:20:30 http: TLS handshake error from 10.244.1.1:55498: EOF level=info timestamp=2018-08-03T22:20:33.369125Z 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:20:40 http: TLS handshake error from 10.244.1.1:55504: EOF 2018/08/03 22:20:50 http: TLS handshake error from 10.244.1.1:55510: EOF 2018/08/03 22:21:00 http: TLS handshake error from 10.244.1.1:55516: EOF level=info timestamp=2018-08-03T22:21:03.349090Z 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-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T22:19:38.313792Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:19:46 http: TLS handshake error from 10.244.0.1:34742: EOF 2018/08/03 22:19:56 http: TLS handshake error from 10.244.0.1:34766: EOF level=info timestamp=2018-08-03T22:19:58.525585Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:20:01.411629Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:20:06 http: TLS handshake error from 10.244.0.1:34790: EOF 2018/08/03 22:20:16 http: TLS handshake error from 10.244.0.1:34814: EOF 2018/08/03 22:20:26 http: TLS handshake error from 10.244.0.1:34838: EOF level=info timestamp=2018-08-03T22:20:28.557347Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:20:31.440478Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:20:36 http: TLS handshake error from 10.244.0.1:34862: EOF 2018/08/03 22:20:46 http: TLS handshake error from 10.244.0.1:34886: EOF 2018/08/03 22:20:56 http: TLS handshake error from 10.244.0.1:34910: EOF level=info timestamp=2018-08-03T22:20:58.587271Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:21:01.466183Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T22:15:01.730190Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi2nkzt kind= uid=aa6d6a53-976a-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:15:01.752955Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5mlmj kind= uid=aa6f1d69-976a-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:15:01.753043Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5mlmj kind= uid=aa6f1d69-976a-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:15:01.758135Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmin4j4k\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmin4j4k" level=info timestamp=2018-08-03T22:15:01.943442Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmilrlzt\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmilrlzt" level=info timestamp=2018-08-03T22:18:03.416885Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4wvrk kind= uid=16b902f4-976b-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:18:03.417061Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4wvrk kind= uid=16b902f4-976b-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:18:03.430316Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmijq66v kind= uid=16baa76a-976b-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:18:03.430505Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmijq66v kind= uid=16baa76a-976b-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:18:03.442904Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwvlsv kind= uid=16bcf0fb-976b-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:18:03.442972Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmiwvlsv kind= uid=16bcf0fb-976b-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:18:03.467622Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4z7bd kind= uid=16bf128c-976b-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:18:03.467717Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4z7bd kind= uid=16bf128c-976b-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:18:03.470770Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi4wvrk\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi4wvrk" level=info timestamp=2018-08-03T22:18:04.035545Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmijq66v\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmijq66v" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:55:10.806614Z pos=health.go:55 component=virt-handler reason="tun device does not 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:26.846574Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:57:49.289586Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:59:42.710016Z pos=health.go:55 component=virt-handler reason="tun device does not 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:40.401628Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:03:32.995613Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:05:03.853403Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:07:08.449082Z pos=health.go:55 component=virt-handler reason="tun device does not 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:57.617169Z pos=health.go:55 component=virt-handler reason="tun device does not 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:33.140454Z pos=health.go:55 component=virt-handler reason="tun device does not 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:39.895856Z pos=health.go:55 component=virt-handler reason="tun device does not 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:48.667926Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:16:38.430958Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.629661Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:20:16.406402Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:56:10.824493Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:57:28.230055Z pos=health.go:55 component=virt-handler reason="tun device does not 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:50.674769Z pos=health.go:55 component=virt-handler reason="tun device does not 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:44.103744Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.795776Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:03:54.981470Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:05:25.842533Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:07:30.448675Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:09:40.941784Z pos=health.go:55 component=virt-handler reason="tun device does not 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:16.464752Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:13:23.223800Z pos=health.go:55 component=virt-handler reason="tun device does not 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:31.997096Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:17:21.755145Z pos=health.go:55 component=virt-handler reason="tun device does not 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:02.363217Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:20:49.149479Z pos=health.go:55 component=virt-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-testvmi4wvrk-sgbc4 Pod phase: Pending Pod name: virt-launcher-testvmi4z7bd-wbpj9 Pod phase: Pending Pod name: virt-launcher-testvmijq66v-qhrtq Pod phase: Pending Pod name: virt-launcher-testvmiwvlsv-4mhmm Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.709 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 VirtualMachineInstance with custom interface model [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:368 should expose the right device type to the guest /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:369 Timed out after 90.003s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T22:18:03.835137Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi4wvrk kind=VirtualMachineInstance uid=16b902f4-976b-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi4wvrk-sgbc4" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running 2018/08/03 22:22:20 http: TLS handshake error from 10.244.1.1:55564: EOF 2018/08/03 22:22:30 http: TLS handshake error from 10.244.1.1:55570: EOF level=info timestamp=2018-08-03T22:22:33.383385Z 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:22:40 http: TLS handshake error from 10.244.1.1:55576: EOF 2018/08/03 22:22:50 http: TLS handshake error from 10.244.1.1:55582: EOF 2018/08/03 22:23:00 http: TLS handshake error from 10.244.1.1:55588: EOF level=info timestamp=2018-08-03T22:23:03.382992Z 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:23:10 http: TLS handshake error from 10.244.1.1:55594: EOF 2018/08/03 22:23:20 http: TLS handshake error from 10.244.1.1:55600: EOF 2018/08/03 22:23:30 http: TLS handshake error from 10.244.1.1:55606: EOF level=info timestamp=2018-08-03T22:23:33.370866Z 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:23:40 http: TLS handshake error from 10.244.1.1:55612: EOF 2018/08/03 22:23:50 http: TLS handshake error from 10.244.1.1:55618: EOF 2018/08/03 22:24:00 http: TLS handshake error from 10.244.1.1:55624: EOF level=info timestamp=2018-08-03T22:24:03.398615Z 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-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T22:22:38.515577Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:22:46 http: TLS handshake error from 10.244.0.1:35174: EOF 2018/08/03 22:22:56 http: TLS handshake error from 10.244.0.1:35198: EOF level=info timestamp=2018-08-03T22:22:58.703698Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:23:01.568470Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:23:06 http: TLS handshake error from 10.244.0.1:35222: EOF 2018/08/03 22:23:16 http: TLS handshake error from 10.244.0.1:35246: EOF 2018/08/03 22:23:26 http: TLS handshake error from 10.244.0.1:35270: EOF level=info timestamp=2018-08-03T22:23:28.736509Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:23:31.600125Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:23:36 http: TLS handshake error from 10.244.0.1:35294: EOF 2018/08/03 22:23:46 http: TLS handshake error from 10.244.0.1:35318: EOF 2018/08/03 22:23:56 http: TLS handshake error from 10.244.0.1:35342: EOF level=info timestamp=2018-08-03T22:23:58.766640Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:24:01.628714Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T22:18:03.467622Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4z7bd kind= uid=16bf128c-976b-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:18:03.467717Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi4z7bd kind= uid=16bf128c-976b-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:18:03.470770Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi4wvrk\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi4wvrk" level=info timestamp=2018-08-03T22:18:04.035545Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmijq66v\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmijq66v" level=info timestamp=2018-08-03T22:21:04.359851Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi4wvrk\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi4wvrk" level=info timestamp=2018-08-03T22:21:04.408711Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi4z7bd\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi4z7bd, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 16bf128c-976b-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi4z7bd" level=info timestamp=2018-08-03T22:21:05.115129Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5z2sf kind= uid=83054630-976b-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:21:05.115288Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5z2sf kind= uid=83054630-976b-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:21:05.126441Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim5wc6 kind= uid=83075413-976b-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:21:05.126531Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim5wc6 kind= uid=83075413-976b-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:21:05.140839Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmimk9r7 kind= uid=8309d645-976b-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:21:05.140965Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmimk9r7 kind= uid=8309d645-976b-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:21:05.170766Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim5qw9 kind= uid=830aeeae-976b-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:21:05.170838Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim5qw9 kind= uid=830aeeae-976b-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:21:05.340025Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi5z2sf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi5z2sf" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T21:57:49.289586Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T21:59:42.710016Z pos=health.go:55 component=virt-handler reason="tun device does not 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:40.401628Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:03:32.995613Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:05:03.853403Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:07:08.449082Z pos=health.go:55 component=virt-handler reason="tun device does not 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:57.617169Z pos=health.go:55 component=virt-handler reason="tun device does not 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:33.140454Z pos=health.go:55 component=virt-handler reason="tun device does not 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:39.895856Z pos=health.go:55 component=virt-handler reason="tun device does not 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:48.667926Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:16:38.430958Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.629661Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:20:16.406402Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.150808Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.579279Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T21:58:50.674769Z pos=health.go:55 component=virt-handler reason="tun device does not 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:44.103744Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.795776Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:03:54.981470Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:05:25.842533Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:07:30.448675Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:09:40.941784Z pos=health.go:55 component=virt-handler reason="tun device does not 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:16.464752Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:13:23.223800Z pos=health.go:55 component=virt-handler reason="tun device does not 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:31.997096Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:17:21.755145Z pos=health.go:55 component=virt-handler reason="tun device does not 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:02.363217Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:20:49.149479Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:22:28.895250Z pos=health.go:55 component=virt-handler reason="tun device does not 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:38.322253Z pos=health.go:55 component=virt-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-testvmi5z2sf-p82df Pod phase: Pending Pod name: virt-launcher-testvmim5qw9-hsgrb Pod phase: Pending Pod name: virt-launcher-testvmim5wc6-nd4bb Pod phase: Pending Pod name: virt-launcher-testvmimk9r7-6rgd5 Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.710 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 VirtualMachineInstance with default interface model [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:382 should expose the right device type to the guest /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:383 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T22:21:05.553180Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmi5z2sf kind=VirtualMachineInstance uid=83054630-976b-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmi5z2sf-p82df" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running 2018/08/03 22:25:20 http: TLS handshake error from 10.244.1.1:55672: EOF 2018/08/03 22:25:30 http: TLS handshake error from 10.244.1.1:55678: EOF level=info timestamp=2018-08-03T22:25:33.413277Z 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:25:40 http: TLS handshake error from 10.244.1.1:55684: EOF 2018/08/03 22:25:50 http: TLS handshake error from 10.244.1.1:55690: EOF 2018/08/03 22:26:00 http: TLS handshake error from 10.244.1.1:55696: EOF level=info timestamp=2018-08-03T22:26:03.366696Z 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:26:10 http: TLS handshake error from 10.244.1.1:55702: EOF 2018/08/03 22:26:20 http: TLS handshake error from 10.244.1.1:55708: EOF 2018/08/03 22:26:30 http: TLS handshake error from 10.244.1.1:55714: EOF level=info timestamp=2018-08-03T22:26:33.373150Z 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:26:40 http: TLS handshake error from 10.244.1.1:55720: EOF 2018/08/03 22:26:50 http: TLS handshake error from 10.244.1.1:55726: EOF 2018/08/03 22:27:00 http: TLS handshake error from 10.244.1.1:55732: EOF level=info timestamp=2018-08-03T22:27:03.367104Z 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-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T22:25:58.889621Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:26:01.746014Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:26:06 http: TLS handshake error from 10.244.0.1:35654: EOF 2018/08/03 22:26:16 http: TLS handshake error from 10.244.0.1:35678: EOF 2018/08/03 22:26:26 http: TLS handshake error from 10.244.0.1:35702: EOF level=info timestamp=2018-08-03T22:26:28.922347Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:26:31.783613Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:26:36 http: TLS handshake error from 10.244.0.1:35726: EOF level=info timestamp=2018-08-03T22:26:38.359808Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:26:38.360691Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:26:46 http: TLS handshake error from 10.244.0.1:35750: EOF 2018/08/03 22:26:56 http: TLS handshake error from 10.244.0.1:35774: EOF level=info timestamp=2018-08-03T22:26:58.952272Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:27:01.815835Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:27:06 http: TLS handshake error from 10.244.0.1:35798: EOF Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T22:21:05.170766Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim5qw9 kind= uid=830aeeae-976b-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:21:05.170838Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmim5qw9 kind= uid=830aeeae-976b-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:21:05.340025Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi5z2sf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi5z2sf" level=info timestamp=2018-08-03T22:24:06.066101Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmim5qw9\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmim5qw9" level=info timestamp=2018-08-03T22:24:06.070702Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi5z2sf\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi5z2sf" level=info timestamp=2018-08-03T22:24:06.097845Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmi5z2sf\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmi5z2sf, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 83054630-976b-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmi5z2sf" level=info timestamp=2018-08-03T22:24:06.245149Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmimk9r7\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmimk9r7, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 8309d645-976b-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmimk9r7" level=info timestamp=2018-08-03T22:24:06.824071Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmijw45g kind= uid=ef541d7d-976b-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:24:06.824240Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmijw45g kind= uid=ef541d7d-976b-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:24:06.841001Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmic54q8 kind= uid=ef55fe4a-976b-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:24:06.841141Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmic54q8 kind= uid=ef55fe4a-976b-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:24:06.855381Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihbz4s kind= uid=ef5855be-976b-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:24:06.855446Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihbz4s kind= uid=ef5855be-976b-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:24:06.867665Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmif6qgh kind= uid=ef5b151a-976b-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:24:06.867774Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmif6qgh kind= uid=ef5b151a-976b-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T22:01:40.401628Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:03:32.995613Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:05:03.853403Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:07:08.449082Z pos=health.go:55 component=virt-handler reason="tun device does not 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:57.617169Z pos=health.go:55 component=virt-handler reason="tun device does not 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:33.140454Z pos=health.go:55 component=virt-handler reason="tun device does not 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:39.895856Z pos=health.go:55 component=virt-handler reason="tun device does not 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:48.667926Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:16:38.430958Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.629661Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:20:16.406402Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.150808Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.579279Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:25:16.584591Z pos=health.go:55 component=virt-handler reason="tun device does not 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:39.789810Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T22:00:44.103744Z pos=health.go:55 component=virt-handler reason="tun device does not 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:41.795776Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:03:54.981470Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:05:25.842533Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:07:30.448675Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:09:40.941784Z pos=health.go:55 component=virt-handler reason="tun device does not 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:16.464752Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:13:23.223800Z pos=health.go:55 component=virt-handler reason="tun device does not 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:31.997096Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:17:21.755145Z pos=health.go:55 component=virt-handler reason="tun device does not 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:02.363217Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:20:49.149479Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:22:28.895250Z pos=health.go:55 component=virt-handler reason="tun device does not 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:38.322253Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:25:49.326085Z pos=health.go:55 component=virt-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-testvmic54q8-9f4lw Pod phase: Pending Pod name: virt-launcher-testvmif6qgh-62dqb Pod phase: Pending Pod name: virt-launcher-testvmihbz4s-t2897 Pod phase: Pending Pod name: virt-launcher-testvmijw45g-skvkp Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.694 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 VirtualMachineInstance with custom MAC address [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:402 should configure custom MAC address /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:403 Timed out after 90.004s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T22:24:07.246200Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmijw45g kind=VirtualMachineInstance uid=ef541d7d-976b-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmijw45g-skvkp" Pod name: disks-images-provider-8wt7r Pod phase: Running copy all images to host mount directory Pod name: disks-images-provider-nmksm Pod phase: Running copy all images to host mount directory Pod name: virt-api-7d79764579-dblhq Pod phase: Running 2018/08/03 22:28:20 http: TLS handshake error from 10.244.1.1:55780: EOF 2018/08/03 22:28:30 http: TLS handshake error from 10.244.1.1:55786: EOF level=info timestamp=2018-08-03T22:28:33.370191Z 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:28:40 http: TLS handshake error from 10.244.1.1:55792: EOF 2018/08/03 22:28:50 http: TLS handshake error from 10.244.1.1:55798: EOF 2018/08/03 22:29:00 http: TLS handshake error from 10.244.1.1:55804: EOF level=info timestamp=2018-08-03T22:29:03.380300Z 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:29:10 http: TLS handshake error from 10.244.1.1:55810: EOF 2018/08/03 22:29:20 http: TLS handshake error from 10.244.1.1:55816: EOF 2018/08/03 22:29:30 http: TLS handshake error from 10.244.1.1:55822: EOF level=info timestamp=2018-08-03T22:29:33.353415Z 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:29:40 http: TLS handshake error from 10.244.1.1:55828: EOF 2018/08/03 22:29:50 http: TLS handshake error from 10.244.1.1:55834: EOF 2018/08/03 22:30:00 http: TLS handshake error from 10.244.1.1:55840: EOF level=info timestamp=2018-08-03T22:30:03.379098Z 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-api-7d79764579-hqpn2 Pod phase: Running level=info timestamp=2018-08-03T22:28:59.076013Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:29:01.931725Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:29:06 http: TLS handshake error from 10.244.0.1:36086: EOF 2018/08/03 22:29:16 http: TLS handshake error from 10.244.0.1:36110: EOF 2018/08/03 22:29:26 http: TLS handshake error from 10.244.0.1:36134: EOF level=info timestamp=2018-08-03T22:29:29.101721Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:29:31.969771Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:29:36 http: TLS handshake error from 10.244.0.1:36158: EOF level=info timestamp=2018-08-03T22:29:38.364640Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/openapi/v2 proto=HTTP/2.0 statusCode=404 contentLength=19 level=info timestamp=2018-08-03T22:29:38.365475Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/swagger.json proto=HTTP/2.0 statusCode=404 contentLength=19 2018/08/03 22:29:46 http: TLS handshake error from 10.244.0.1:36182: EOF 2018/08/03 22:29:56 http: TLS handshake error from 10.244.0.1:36206: EOF level=info timestamp=2018-08-03T22:29:59.131989Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 level=info timestamp=2018-08-03T22:30:01.994441Z pos=filter.go:46 component=virt-api remoteAddress=10.244.0.1 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha2 proto=HTTP/2.0 statusCode=200 contentLength=136 2018/08/03 22:30:06 http: TLS handshake error from 10.244.0.1:36230: EOF Pod name: virt-controller-7d57d96b65-b8vrz Pod phase: Running level=info timestamp=2018-08-03T21:00:26.824546Z pos=application.go:177 component=virt-controller service=http action=listening interface=0.0.0.0 port=8182 Pod name: virt-controller-7d57d96b65-cv6pb Pod phase: Running level=info timestamp=2018-08-03T22:24:06.855381Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihbz4s kind= uid=ef5855be-976b-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:24:06.855446Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmihbz4s kind= uid=ef5855be-976b-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:24:06.867665Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmif6qgh kind= uid=ef5b151a-976b-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:24:06.867774Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmif6qgh kind= uid=ef5b151a-976b-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:27:07.790666Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmic54q8\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachineinstances/kubevirt-test-default/testvmic54q8, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: ef55fe4a-976b-11e8-9925-525500d15501, UID in object meta: " msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmic54q8" level=info timestamp=2018-08-03T22:27:07.807216Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmijw45g\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmijw45g" level=info timestamp=2018-08-03T22:27:08.515313Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmij4drl kind= uid=5ba04dfa-976c-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:27:08.515510Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmij4drl kind= uid=5ba04dfa-976c-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:27:08.525946Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5jmwt kind= uid=5ba1a47c-976c-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:27:08.526065Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5jmwt kind= uid=5ba1a47c-976c-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:27:08.537950Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmimrbs2 kind= uid=5ba33a84-976c-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:27:08.538055Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmimrbs2 kind= uid=5ba33a84-976c-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:27:08.566706Z pos=preset.go:142 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5vnnq kind= uid=5ba51ce3-976c-11e8-9925-525500d15501 msg="Initializing VirtualMachineInstance" level=info timestamp=2018-08-03T22:27:08.566898Z pos=preset.go:171 component=virt-controller service=http namespace=kubevirt-test-default name=testvmi5vnnq kind= uid=5ba51ce3-976c-11e8-9925-525500d15501 msg="Marking VirtualMachineInstance as initialized" level=info timestamp=2018-08-03T22:27:09.567091Z pos=vmi.go:157 component=virt-controller service=http reason="Operation cannot be fulfilled on virtualmachineinstances.kubevirt.io \"testvmij4drl\": the object has been modified; please apply your changes to the latest version and try again" msg="reenqueuing VirtualMachineInstance kubevirt-test-default/testvmij4drl" Pod name: virt-handler-2v7vl Pod phase: Running level=error timestamp=2018-08-03T22:05:03.853403Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:07:08.449082Z pos=health.go:55 component=virt-handler reason="tun device does not 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:57.617169Z pos=health.go:55 component=virt-handler reason="tun device does not 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:33.140454Z pos=health.go:55 component=virt-handler reason="tun device does not 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:39.895856Z pos=health.go:55 component=virt-handler reason="tun device does not 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:48.667926Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:16:38.430958Z pos=health.go:55 component=virt-handler reason="tun device does not 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:29.629661Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:20:16.406402Z pos=health.go:55 component=virt-handler reason="tun device does not 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:56.150808Z pos=health.go:55 component=virt-handler reason="tun device does not 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:05.579279Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:25:16.584591Z pos=health.go:55 component=virt-handler reason="tun device does not 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:39.789810Z pos=health.go:55 component=virt-handler reason="tun device does not 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:31.725887Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:29:37.897391Z pos=health.go:55 component=virt-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-q9bdc Pod phase: Running level=error timestamp=2018-08-03T22:03:54.981470Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:05:25.842533Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:07:30.448675Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:09:40.941784Z pos=health.go:55 component=virt-handler reason="tun device does not 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:16.464752Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:13:23.223800Z pos=health.go:55 component=virt-handler reason="tun device does not 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:31.997096Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:17:21.755145Z pos=health.go:55 component=virt-handler reason="tun device does not 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:02.363217Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:20:49.149479Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:22:28.895250Z pos=health.go:55 component=virt-handler reason="tun device does not 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:38.322253Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:25:49.326085Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:27:12.530338Z pos=health.go:55 component=virt-handler reason="tun device does not show up in /proc/misc, is the module loaded?" msg="Check for mandatory device /dev/net/tun failed" level=error timestamp=2018-08-03T22:29:04.469302Z pos=health.go:55 component=virt-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-testvmi5jmwt-xnhxm Pod phase: Pending Pod name: virt-launcher-testvmi5vnnq-jf6k6 Pod phase: Pending Pod name: virt-launcher-testvmij4drl-bnx7b Pod phase: Pending Pod name: virt-launcher-testvmimrbs2-r6r82 Pod phase: Pending • Failure in Spec Setup (BeforeEach) [181.698 seconds] Networking /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:48 VirtualMachineInstance with custom MAC address in non-conventional format [BeforeEach] /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:414 should configure custom MAC address /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:415 Timed out after 90.005s. Timed out waiting for VMI to enter Running phase Expected : false to equal : true /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 ------------------------------ level=info timestamp=2018-08-03T22:27:08.968047Z pos=utils.go:244 component=tests namespace=kubevirt-test-default name=testvmij4drl kind=VirtualMachineInstance uid=5ba04dfa-976c-11e8-9925-525500d15501 msg="Created virtual machine pod virt-launcher-testvmij4drl-bnx7b" panic: test timed out after 1h30m0s goroutine 14873 [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(0xc4205b20f0, 0x12ad0d7, 0x9, 0x1339680, 0x47fa16) /gimme/.gimme/versions/go1.10.linux.amd64/src/testing/testing.go:825 +0x301 testing.runTests.func1(0xc4205b2000) /gimme/.gimme/versions/go1.10.linux.amd64/src/testing/testing.go:1063 +0x64 testing.tRunner(0xc4205b2000, 0xc420aa1df8) /gimme/.gimme/versions/go1.10.linux.amd64/src/testing/testing.go:777 +0xd0 testing.runTests(0xc4207627c0, 0x1bc0e20, 0x1, 0x1, 0x412009) /gimme/.gimme/versions/go1.10.linux.amd64/src/testing/testing.go:1061 +0x2c4 testing.(*M).Run(0xc420a18100, 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 7 [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 10 [select]: kubevirt.io/kubevirt/vendor/github.com/onsi/gomega/internal/asyncassertion.(*AsyncAssertion).match(0xc420792800, 0x13c29a0, 0xc4206292e0, 0x412801, 0xc420629300, 0x1, 0x1, 0xc420629300) /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(0xc420792800, 0x13c29a0, 0xc4206292e0, 0xc420629300, 0x1, 0x1, 0x13ba800) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/gomega/internal/asyncassertion/async_assertion.go:48 +0x62 kubevirt.io/kubevirt/tests.waitForVMIStart(0x13b9580, 0xc420a13b80, 0x5a, 0x0, 0x0, 0x0) /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1024 +0x703 kubevirt.io/kubevirt/tests.WaitForSuccessfulVMIStart(0x13b9580, 0xc420a13b80, 0xc4207cb120, 0xa206ae) /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1047 +0x43 kubevirt.io/kubevirt/tests.WaitUntilVMIReady(0xc420a13b80, 0x1339658, 0x1c06250) /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1052 +0x3b kubevirt.io/kubevirt/tests_test.glob..func18.4() /root/go/src/kubevirt.io/kubevirt/tests/vmi_networking_test.go:135 +0x72b kubevirt.io/kubevirt/tests.BeforeAll.func1() /root/go/src/kubevirt.io/kubevirt/tests/utils.go:1334 +0x3f kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*runner).runSync(0xc42054ab40, 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(0xc42054ab40, 0xc4206fd100, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:64 +0x13e kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*SetupNode).Run(0xc42000e8d0, 0x13b5fc0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/leafnodes/setup_nodes.go:15 +0x7f kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/spec.(*Spec).runSample(0xc4203885a0, 0x0, 0x13b5fc0, 0xc420057500) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/spec/spec.go:181 +0x1f1 kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/spec.(*Spec).Run(0xc4203885a0, 0x13b5fc0, 0xc420057500) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/spec/spec.go:138 +0xff kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).runSpec(0xc4209b0140, 0xc4203885a0, 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(0xc4209b0140, 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(0xc4209b0140, 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(0xc4200ceb40, 0x7f9f7361ede8, 0xc4205b20f0, 0x12af51b, 0xb, 0xc420762800, 0x2, 0x2, 0x13d0ca0, 0xc420057500, ...) /root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/suite/suite.go:62 +0x27c kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo.RunSpecsWithCustomReporters(0x13b6d00, 0xc4205b20f0, 0x12af51b, 0xb, 0xc4207627e0, 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, 0xc4205b20f0, 0x12af51b, 0xb, 0xc42076a8a0, 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(0xc4205b20f0) /root/go/src/kubevirt.io/kubevirt/tests/tests_suite_test.go:43 +0xaa testing.tRunner(0xc4205b20f0, 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 11 [chan receive, 90 minutes]: kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).registerForInterrupts(0xc4209b0140, 0xc420922d80) /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 12 [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(0xc42047cf50, 0xc420922e40) /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 26 [IO wait]: internal/poll.runtime_pollWait(0x7f9f73602f00, 0x72, 0xc420580850) /gimme/.gimme/versions/go1.10.linux.amd64/src/runtime/netpoll.go:173 +0x57 internal/poll.(*pollDesc).wait(0xc420564198, 0x72, 0xffffffffffffff00, 0x13b7ca0, 0x1ad8640) /gimme/.gimme/versions/go1.10.linux.amd64/src/internal/poll/fd_poll_runtime.go:85 +0x9b internal/poll.(*pollDesc).waitRead(0xc420564198, 0xc420a78000, 0x8000, 0x8000) /gimme/.gimme/versions/go1.10.linux.amd64/src/internal/poll/fd_poll_runtime.go:90 +0x3d internal/poll.(*FD).Read(0xc420564180, 0xc420a78000, 0x8000, 0x8000, 0x0, 0x0, 0x0) /gimme/.gimme/versions/go1.10.linux.amd64/src/internal/poll/fd_unix.go:157 +0x17d net.(*netFD).Read(0xc420564180, 0xc420a78000, 0x8000, 0x8000, 0x0, 0x8, 0x7ffb) /gimme/.gimme/versions/go1.10.linux.amd64/src/net/fd_unix.go:202 +0x4f net.(*conn).Read(0xc420390000, 0xc420a78000, 0x8000, 0x8000, 0x0, 0x0, 0x0) /gimme/.gimme/versions/go1.10.linux.amd64/src/net/net.go:176 +0x6a crypto/tls.(*block).readFromUntil(0xc4200f3e60, 0x7f9f735b7cc8, 0xc420390000, 0x5, 0xc420390000, 0x0) /gimme/.gimme/versions/go1.10.linux.amd64/src/crypto/tls/conn.go:493 +0x96 crypto/tls.(*Conn).readRecord(0xc4204fc000, 0x133b617, 0xc4204fc120, 0x20) /gimme/.gimme/versions/go1.10.linux.amd64/src/crypto/tls/conn.go:595 +0xe0 crypto/tls.(*Conn).Read(0xc4204fc000, 0xc42042b000, 0x1000, 0x1000, 0x0, 0x0, 0x0) /gimme/.gimme/versions/go1.10.linux.amd64/src/crypto/tls/conn.go:1156 +0x100 bufio.(*Reader).Read(0xc420946cc0, 0xc4203422d8, 0x9, 0x9, 0xc42054b0d8, 0xc4206b6880, 0xc420580d10) /gimme/.gimme/versions/go1.10.linux.amd64/src/bufio/bufio.go:216 +0x238 io.ReadAtLeast(0x13b4e00, 0xc420946cc0, 0xc4203422d8, 0x9, 0x9, 0x9, 0xc420580ce0, 0xc420580ce0, 0x406614) /gimme/.gimme/versions/go1.10.linux.amd64/src/io/io.go:309 +0x86 io.ReadFull(0x13b4e00, 0xc420946cc0, 0xc4203422d8, 0x9, 0x9, 0xc42054b080, 0xc420580d10, 0xc400006e01) /gimme/.gimme/versions/go1.10.linux.amd64/src/io/io.go:327 +0x58 kubevirt.io/kubevirt/vendor/golang.org/x/net/http2.readFrameHeader(0xc4203422d8, 0x9, 0x9, 0x13b4e00, 0xc420946cc0, 0x0, 0xc400000000, 0x7baa0d, 0xc420580fb0) /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(0xc4203422a0, 0xc420594b40, 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(0xc420580fb0, 0x133a5d8, 0xc4204787b0) /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(0xc4200d7ba0) /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