Advertisement
Guest User

Untitled

a guest
Jun 22nd, 2018
260
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.43 KB | None | 0 0
  1. Cloud-init v. 0.7.9 running 'modules:config' at Fri, 22 Jun 2018 15:59:27 +0000. Up 84.00 seconds.
  2. /var/lib/cloud/instance/scripts/part-003: line 50: /etc/etcd/etcd.conf: No such file or directory
  3. /var/lib/cloud/instance/scripts/part-003: line 63: /etc/etcd/etcd.conf: No such file or directory
  4. /var/lib/cloud/instance/scripts/part-004: line 9: /etc/kubernetes/kube_openstack_config: No such file or directory
  5. Cloud-init v. 0.7.9 running 'modules:final' at Fri, 22 Jun 2018 15:59:29 +0000. Up 86.20 seconds.
  6. 2018-06-22 15:59:29,655 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-004 [1]
  7. 2018-06-22 15:59:50,236 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-005 [1]
  8. Physical volume "/dev/disk/by-id/virtio-95b2bd1e-ff8b-4dc4-a" successfully created.
  9. Volume group "docker" successfully created
  10. New size given (1280 extents) not larger than existing size (69887 extents)
  11. INFO: DATA_SIZE=40%FREE is smaller than MIN_DATA_SIZE=2G. Will create data volume of size specified by MIN_DATA_SIZE.
  12. Using default stripesize 64.00 KiB.
  13. Rounding up size to full physical extent 8.00 MiB
  14. Thin pool volume with chunk size 512.00 KiB can address at most 126.50 TiB of data.
  15. Logical volume "docker-pool" created.
  16. Logical volume docker/docker-pool changed.
  17. configuring kubernetes (master)
  18.  
  19.  
  20.  
  21.  
  22.  
  23. sed: can't read /etc/kubernetes/config: No such file or directory
  24. sed: can't read /etc/kubernetes/apiserver: No such file or directory
  25. sed: can't read /etc/kubernetes/controller-manager: No such file or directory
  26. sed: can't read /etc/kubernetes/scheduler: No such file or directory
  27. sed: can't read /etc/kubernetes/kubelet: No such file or directory
  28. 2018-06-22 16:10:40,923 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-007 [2]
  29. starting services
  30. activating service etcd
  31. Failed to enable unit: Unit file etcd.service does not exist.
  32. Failed to start etcd.service: Unit etcd.service not found.
  33. activating service docker
  34. activating service kube-apiserver
  35. Failed to enable unit: Unit file kube-apiserver.service does not exist.
  36. Failed to start kube-apiserver.service: Unit kube-apiserver.service not found.
  37. activating service kube-controller-manager
  38. Failed to enable unit: Unit file kube-controller-manager.service does not exist.
  39. Failed to start kube-controller-manager.service: Unit kube-controller-manager.service not found.
  40. activating service kube-scheduler
  41. Failed to enable unit: Unit file kube-scheduler.service does not exist.
  42. Failed to start kube-scheduler.service: Unit kube-scheduler.service not found.
  43. activating service kubelet
  44. Failed to enable unit: Unit file kubelet.service does not exist.
  45. Failed to start kubelet.service: Unit kubelet.service not found.
  46. activating service kube-proxy
  47. Failed to enable unit: Unit file kube-proxy.service does not exist.
  48. Failed to start kube-proxy.service: Unit kube-proxy.service not found.
  49. 2018-06-22 16:10:41,290 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-009 [5]
  50. /var/lib/cloud/instance/scripts/part-010: line 9: /etc/sysconfig/flanneld: No such file or directory
  51. 2018-06-22 16:10:41,306 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-010 [1]
  52. sed: can't read /etc/sysconfig/flanneld: No such file or directory
  53. creating /usr/local/bin/flannel-config
  54. Created symlink /etc/systemd/system/multi-user.target.wants/flannel-config.service → /etc/systemd/system/flannel-config.service.
  55. Failed to start flannel-config.service: Unit etcd.service not found.
  56. 2018-06-22 16:10:41,513 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-014 [5]
  57. activating service flanneld
  58. Failed to enable unit: Unit file flanneld.service does not exist.
  59. Failed to start flanneld.service: Unit flanneld.service not found.
  60. 2018-06-22 16:10:41,563 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-015 [5]
  61. Writing File: /srv/kubernetes/kube-system-namespace.json
  62. Writing File: /usr/local/bin/kube-system-namespace
  63. Writing File: /etc/systemd/system/kube-system-namespace.service
  64. Created symlink /etc/systemd/system/multi-user.target.wants/kube-system-namespace.service → /etc/systemd/system/kube-system-namespace.service.
  65. Failed to start kube-system-namespace.service: Unit kubelet.service not found.
  66. 2018-06-22 16:10:41,814 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-016 [5]
  67. Writing File: /etc/kubernetes/manifests/kube-coredns.yaml
  68. Waiting for Kubernetes API...
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement