You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 4, 2021. It is now read-only.
I tried to spin up a new single-node cluster but it fails prematurely within the cloudinit unit with the error:
● coreos-cloudinit-791973373.service - Unit generated and executed by coreos-cloudinit on behalf of user
Loaded: loaded (/run/systemd/transient/coreos-cloudinit-791973373.service; transient)
Transient: yes
Active: failed (Result: exit-code) since Tue 2019-10-22 17:29:20 UTC; 14min ago
Process: 1318 ExecStart=/bin/bash /var/lib/coreos-cloudinit/scripts/791973373 (code=exited, status=1/FAILURE)
Main PID: 1318 (code=exited, status=1/FAILURE)
Oct 22 17:29:20 localhost systemd[1]: Started Unit generated and executed by coreos-cloudinit on behalf of user.
Oct 22 17:29:20 localhost bash[1318]: Failed to enable unit: Unit file etcd2.service does not exist.
Oct 22 17:29:20 localhost systemd[1]: coreos-cloudinit-791973373.service: Main process exited, code=exited, status=1/FAILURE
Oct 22 17:29:20 localhost systemd[1]: coreos-cloudinit-791973373.service: Failed with result 'exit-code'.
And also the multi-node seam to have the same problem:
e1:
● user-cloudinit@var-lib-coreos\x2dvagrant-vagrantfile\x2duser\x2ddata.service - Load cloud-config from /var/lib/coreos-vagrant/vagrantfile-user-data
Loaded: loaded (/usr/lib/systemd/system/user-cloudinit@.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2019-10-22 18:05:00 UTC; 11min ago
Process: 1112 ExecStart=/usr/bin/coreos-cloudinit --from-file=/var/lib/coreos-vagrant/vagrantfile-user-data (code=exited, status=1/FAILURE)
Main PID: 1112 (code=exited, status=1/FAILURE)
Oct 22 18:04:59 e1 coreos-cloudinit[1112]: 2019/10/22 18:04:59 Wrote drop-in unit "20-cloudinit.conf"
Oct 22 18:04:59 e1 coreos-cloudinit[1112]: 2019/10/22 18:04:59 Ensuring runtime unit file "etcd2.service" is unmasked
Oct 22 18:04:59 e1 coreos-cloudinit[1112]: 2019/10/22 18:04:59 Ensuring runtime unit file "fleet.service" is unmasked
Oct 22 18:04:59 e1 coreos-cloudinit[1112]: 2019/10/22 18:04:59 Ensuring runtime unit file "locksmithd.service" is unmasked
Oct 22 18:04:59 e1 coreos-cloudinit[1112]: 2019/10/22 18:04:59 Masking unit file "locksmithd.service"
Oct 22 18:05:00 e1 coreos-cloudinit[1112]: 2019/10/22 18:05:00 Calling unit command "start" on "etcd2.service"
Oct 22 18:05:00 e1 coreos-cloudinit[1112]: 2019/10/22 18:05:00 Failed to apply cloud-config: Unit etcd2.service not found.
Oct 22 18:05:00 e1 systemd[1]: user-cloudinit@var-lib-coreos\x2dvagrant-vagrantfile\x2duser\x2ddata.service: Main process exited, code=exited, status=1/FAILURE
Oct 22 18:05:00 e1 systemd[1]: user-cloudinit@var-lib-coreos\x2dvagrant-vagrantfile\x2duser\x2ddata.service: Failed with result 'exit-code'.
Oct 22 18:05:00 e1 systemd[1]: Failed to start Load cloud-config from /var/lib/coreos-vagrant/vagrantfile-user-data.
And all worker nodes:
● coreos-cloudinit-362193141.service - Unit generated and executed by coreos-cloudinit on behalf of user
Loaded: loaded (/run/systemd/transient/coreos-cloudinit-362193141.service; transient)
Transient: yes
Active: failed (Result: exit-code) since Tue 2019-10-22 18:11:19 UTC; 7min ago
Process: 1308 ExecStart=/bin/bash /var/lib/coreos-cloudinit/scripts/362193141 (code=exited, status=1/FAILURE)
Main PID: 1308 (code=exited, status=1/FAILURE)
Oct 22 18:06:22 w1 bash[1308]: TEMPLATE: /etc/systemd/system/flanneld.service.d/40-ExecStartPre-symlink.conf.conf
Oct 22 18:06:22 w1 bash[1308]: TEMPLATE: /etc/systemd/system/docker.service.d/40-flannel.conf
Oct 22 18:06:22 w1 bash[1308]: TEMPLATE: /etc/kubernetes/cni/docker_opts_cni.env
Oct 22 18:06:22 w1 bash[1308]: TEMPLATE: /etc/kubernetes/cni/net.d/10-flannel.conf
Oct 22 18:06:22 w1 bash[1308]: Created symlink /etc/systemd/system/update-engine.service → /dev/null.
Oct 22 18:06:23 w1 bash[1308]: Created symlink /etc/systemd/system/multi-user.target.wants/flanneld.service → /usr/lib/systemd/system/flanneld.service.
Oct 22 18:11:19 w1 bash[1308]: Job for flanneld.service failed because a timeout was exceeded.
Oct 22 18:11:19 w1 bash[1308]: See "systemctl status flanneld.service" and "journalctl -xe" for details.
Oct 22 18:11:19 w1 systemd[1]: coreos-cloudinit-362193141.service: Main process exited, code=exited, status=1/FAILURE
Oct 22 18:11:19 w1 systemd[1]: coreos-cloudinit-362193141.service: Failed with result 'exit-code'.
● update-engine.service
Loaded: masked (Reason: Unit update-engine.service is masked.)
Active: failed (Result: exit-code) since Tue 2019-10-22 18:06:22 UTC; 11min ago
Main PID: 699 (code=exited, status=1/FAILURE)
Oct 22 18:06:12 localhost systemd[1]: Starting Update Engine...
Oct 22 18:06:13 localhost update_engine[699]: I1022 18:06:13.402832 699 main.cc:89] CoreOS Update Engine starting
Oct 22 18:06:13 localhost systemd[1]: Started Update Engine.
Oct 22 18:06:13 localhost update_engine[699]: I1022 18:06:13.429944 699 update_check_scheduler.cc:74] Next update check in 6m10s
Oct 22 18:06:22 w1 systemd[1]: Stopping Update Engine...
Oct 22 18:06:22 w1 systemd[1]: update-engine.service: Main process exited, code=exited, status=1/FAILURE
Oct 22 18:06:22 w1 systemd[1]: update-engine.service: Failed with result 'exit-code'.
Oct 22 18:06:22 w1 systemd[1]: Stopped Update Engine.
The text was updated successfully, but these errors were encountered:
agowa
changed the title
single-node cluster etcd2.service does not exist
vagrant example cluster fails to deploy
Oct 22, 2019
agowa
changed the title
vagrant example cluster fails to deploy
vagrant example cluster are failing to deploy
Oct 22, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I tried to spin up a new single-node cluster but it fails prematurely within the cloudinit unit with the error:
I followed the instructions at: https://coreos.com/kubernetes/docs/1.6.1/kubernetes-on-vagrant-single.html
And also the multi-node seam to have the same problem:
e1:
And all worker nodes:
The text was updated successfully, but these errors were encountered: