/vagrant/artifacts/tls/admin.pem: no such file or directory #244
Comments
|
How should i deal with it? Thank you. |
|
Are you running this on Windows? |
|
yes, your OS？ |
|
MacOS. Can you repeat the setup and share the entire log here? The TLS artifacts should've been generated when provisioning the master node. |
|
{ kubernetes-vagrant-coreos-cluster } master » vagrant up Error in configuration:
|
|
Do you want these? I hope that my understanding is right. |
|
The master was not provisioned correctly. Can you log into the machine and check logs? If some unit failed, it should show up as soon as you log. You can use |
|
I am having similar issues on windows with exact same error. I then tried login to master and after login the output of create and journalctl commands were core@master ~ $ ls May 13 02:08:26 localhost kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' |
|
Also, the deployment is working correctly on windows for the branch tag 1.5.7 |
|
So the apiserver is not running. I need more logs. |
|
How can i generate more detailed log? |
|
Did someone found a workaround for this problem? |
|
thats the log i got from the master: |
|
Hello, [Unit] output of system status kube-certs Jun 18 08:25:03 master make-certs.sh[2141]: --restricted Jun 18 08:25:03 master make-certs.sh[2141]: -abefhkmnptuvxBCHP or -o option |
|
Found the issue: the two shell scripts (in my case) was still in Windows Format, even if I deleted the git directory, run those git global commands and doing git clone again.. I don't know why. |
|
@TheFausap open PR please. |
|
@pires Sorry but I never did before :-) How can I do that ? |
|
@TheFausap Could you at least update which files had an were malformed? I am facing the same issue |
|
Sorry for the delay, today I will open the PR. |
|
@TheFausap Any word on that PR? Or the files that were malformed? |
|
Hi, I am too facing the issue for the latest release tag 1.7.4 |
|
This resolved for me after I uninstalled minikube. |
|
This might caused by make-certs.sh fails. Line ending conversion is forced by .gitattributes below. https://git-scm.com/docs/gitattributes
|
|
Hi, I got the same issue, as you said, i tried to run : $ vagrant ssh master after i use journal, following error has been found: Dec 06 20:00:19 master sshd[2014]: pam_unix(sshd:session): session opened for user core by (uid=0) How can i solve this? Thank you. |
|
As i described above, i used the stable coreos channel, but after i change to alpha, it is ok now. I am not sure what was wrong. |
==> master:
==> master: Switched to context "local".
==> master: Remote command execution finished.
==> master: Configuring Kubernetes DNS...
==> master: Executing remote command "/opt/bin/kubectl create -f /home/core/dns-controller.yaml"...
==> master:
==> master:
**```
==> master: Error in configuration:
==> master: * unable to read client-cert /vagrant/artifacts/tls/admin.pem for default-admin due to open /vagrant/artifacts/tls/admin.pem: no such file or directory
==> master: * unable to read client-key /vagrant/artifacts/tls/admin-key.pem for default-admin due to open /vagrant/artifacts/tls/admin-key.pem: no such file or directory
==> master: * unable to read certificate-authority /vagrant/artifacts/tls/ca.pem for default-cluster due to open /vagrant/artifacts/tls/ca.pem: no such file or directory
==> master: Remote command execution finished.
The remote command "/opt/bin/kubectl create -f /home/core/dns-controller.yaml" returned a failed exit
code or an exception. The error output is shown below:
Error in configuration:
The text was updated successfully, but these errors were encountered: