Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Cloud-init v. 0.7.9 running 'modules:config' at Fri, 22 Jun 2018 15:59:27 +0000. Up 84.00 seconds.
- /var/lib/cloud/instance/scripts/part-003: line 50: /etc/etcd/etcd.conf: No such file or directory
- /var/lib/cloud/instance/scripts/part-003: line 63: /etc/etcd/etcd.conf: No such file or directory
- /var/lib/cloud/instance/scripts/part-004: line 9: /etc/kubernetes/kube_openstack_config: No such file or directory
- Cloud-init v. 0.7.9 running 'modules:final' at Fri, 22 Jun 2018 15:59:29 +0000. Up 86.20 seconds.
- 2018-06-22 15:59:29,655 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-004 [1]
- 2018-06-22 15:59:50,236 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-005 [1]
- Physical volume "/dev/disk/by-id/virtio-95b2bd1e-ff8b-4dc4-a" successfully created.
- Volume group "docker" successfully created
- New size given (1280 extents) not larger than existing size (69887 extents)
- INFO: DATA_SIZE=40%FREE is smaller than MIN_DATA_SIZE=2G. Will create data volume of size specified by MIN_DATA_SIZE.
- Using default stripesize 64.00 KiB.
- Rounding up size to full physical extent 8.00 MiB
- Thin pool volume with chunk size 512.00 KiB can address at most 126.50 TiB of data.
- Logical volume "docker-pool" created.
- Logical volume docker/docker-pool changed.
- configuring kubernetes (master)
- sed: can't read /etc/kubernetes/config: No such file or directory
- sed: can't read /etc/kubernetes/apiserver: No such file or directory
- sed: can't read /etc/kubernetes/controller-manager: No such file or directory
- sed: can't read /etc/kubernetes/scheduler: No such file or directory
- sed: can't read /etc/kubernetes/kubelet: No such file or directory
- 2018-06-22 16:10:40,923 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-007 [2]
- starting services
- activating service etcd
- Failed to enable unit: Unit file etcd.service does not exist.
- Failed to start etcd.service: Unit etcd.service not found.
- activating service docker
- activating service kube-apiserver
- Failed to enable unit: Unit file kube-apiserver.service does not exist.
- Failed to start kube-apiserver.service: Unit kube-apiserver.service not found.
- activating service kube-controller-manager
- Failed to enable unit: Unit file kube-controller-manager.service does not exist.
- Failed to start kube-controller-manager.service: Unit kube-controller-manager.service not found.
- activating service kube-scheduler
- Failed to enable unit: Unit file kube-scheduler.service does not exist.
- Failed to start kube-scheduler.service: Unit kube-scheduler.service not found.
- activating service kubelet
- Failed to enable unit: Unit file kubelet.service does not exist.
- Failed to start kubelet.service: Unit kubelet.service not found.
- activating service kube-proxy
- Failed to enable unit: Unit file kube-proxy.service does not exist.
- Failed to start kube-proxy.service: Unit kube-proxy.service not found.
- 2018-06-22 16:10:41,290 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-009 [5]
- /var/lib/cloud/instance/scripts/part-010: line 9: /etc/sysconfig/flanneld: No such file or directory
- 2018-06-22 16:10:41,306 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-010 [1]
- sed: can't read /etc/sysconfig/flanneld: No such file or directory
- creating /usr/local/bin/flannel-config
- Created symlink /etc/systemd/system/multi-user.target.wants/flannel-config.service → /etc/systemd/system/flannel-config.service.
- Failed to start flannel-config.service: Unit etcd.service not found.
- 2018-06-22 16:10:41,513 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-014 [5]
- activating service flanneld
- Failed to enable unit: Unit file flanneld.service does not exist.
- Failed to start flanneld.service: Unit flanneld.service not found.
- 2018-06-22 16:10:41,563 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-015 [5]
- Writing File: /srv/kubernetes/kube-system-namespace.json
- Writing File: /usr/local/bin/kube-system-namespace
- Writing File: /etc/systemd/system/kube-system-namespace.service
- Created symlink /etc/systemd/system/multi-user.target.wants/kube-system-namespace.service → /etc/systemd/system/kube-system-namespace.service.
- Failed to start kube-system-namespace.service: Unit kubelet.service not found.
- 2018-06-22 16:10:41,814 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-016 [5]
- Writing File: /etc/kubernetes/manifests/kube-coredns.yaml
- Waiting for Kubernetes API...
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement