Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CHEF 15] Bootstrapping a server now causes 'No such file or directory' all of a sudden. #8534

Closed
breisig opened this issue May 14, 2019 · 4 comments

Comments

Projects
None yet
3 participants
@breisig
Copy link

commented May 14, 2019

I have upgraded from Chef client 14.xx to Chef Infra Client: 15.0.293 and tried bootstrapping a server as normal [had to replace -x on the command line with --connection-user and --connection-password] but now I keep getting the follow error message when attempting to boostrap a server.

Performing legacy client registration with the validation key at /home/test/.chef/mychefserver.pem..."
Delete your validation key in order to use your user credentials for client registration instead.
Connecting to test.mytestsite.com
ERROR: Errno::ENOENT: No such file or directory @ rb_sysopen - /tmp/d20190514-10948-1pq02vu/test.mytestsite.com.pem

@marcparadise

This comment has been minimized.

Copy link
Member

commented May 14, 2019

Thanks for reporting this @breisig. Could you let us know what your workstation OS/version is, and the OS/version of the node you're bootstrapping? It would also help to know which cloud provider for the target node, or if the target node is internal/local.

@breisig

This comment has been minimized.

Copy link
Author

commented May 14, 2019

@marcparadise Both the workstation and bootstrapped server is using the latest CentOS 7.6 64bit. The target server is just an internal VM running on a fresh CentOS 7.6 minimal image [with all patches].

@marcparadise

This comment has been minimized.

Copy link
Member

commented May 15, 2019

Thanks, I'll see if I can get the same to occur.

Would you be able to include the redacted CLI and its output when run with -VV? (Note two Vs and not three - two will not give the stack trace I'm hoping for - ref #8433 for the curious...)

@dheerajd-msys

This comment has been minimized.

Copy link
Contributor

commented May 17, 2019

@breisig Until you confirm with the complete stacktrace I would like to say that I was getting the similar error from Windows workstation with chef v15 here chef/knife-ec2#575. In my knife.rb there was an entry for validation_key which is old process for client registration. Deleting the entry and file from the path resolved my error. Could you please cross-verify if you are doing the same.

Thanks,

btm added a commit that referenced this issue May 17, 2019

Only set client_pem in bootstrap_context when validatorless
We should only set bootstrap_context.client_pem if we're a validatorless
bootstrap.

Fixes #8534

Signed-off-by: Bryan McLellan <btm@loftninjas.org>

@btm btm closed this in #8567 May 20, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.