When you create a user via chef-server-ctl add-user with --filename pointed at invalid path, the user is created, but the key is not put on the filesystem.

[tylercloke]

root@vagrant:~# chef-server-ctl user-create test test test test@test.com testtest --filename /<invalid_folder>/file.key
ERROR: Errno::ENOENT: No such file or directory - /path/to/file.key
root@vagrant:~# chef-server-ctl user-create test test test test@test.com testtest --filename /<valid_folder>/file.key
ERROR: Conflict
Response: User 'wtf' already exists

So it creates the user just fine, and you get a conflict when you try to re-create it (valid), but you won't have the key on your filesystem. There are other ways to get the key, but that's annoying.

[stevendanna]

Thanks @tylercloke. With the newest changes to knife-opc, you can get the key with the user-edit command and adding

"private_key": true

to the user data. I agree this is annoying, I think we should probably do something like:

1. Check if we can write into the directory before issuing the API request, fail with an error if we cannot.
2. Write the key to STDERR if the write to the file fails.

We'll probably want to follow whatever best-practices chef-client uses when writing credentials as well.

[jmink]

This has been addressed in the linked PR

[marcparadise]

This is fixed in current knife-opc, so bumping the rev in omnibus should resolve it

[Abhsubba]

you may created the org or user my mistake, but every problem has some solution.its simple

sudo -s
chef-server-ctl org-delete learndevops

learndevops is my org-name you may have different.

this will delete the old one so you can create new user or org name.