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

Getting 'TypeError: Cannot read property 'private_key' of undefined' when running playbook #24

Closed
vsayer opened this issue May 26, 2015 · 3 comments
Labels

Comments

@vsayer
Copy link

vsayer commented May 26, 2015

Hi,

I'm getting semaphore to crash when running a playbook.

Steps to reproduce:

  1. Add identity: populated name, private key (copied from ~/.ssh/id_rsa), public key (copied from ~/.ssh/id_rsa.pub); password was not entered (what is that field for?)
  2. Add Playbook: populated name, playbook location (used ssh://user@ip_address/path/to/playbook.git), identity used was above identity from 1. vault password wasn't entered (what is this for?)
  3. Add a host group and host; doubt that this affects the bug although it's not clear which host group your playbook would use if your playbook is group generic.
  4. Add job under created playbook: some path under the git repository specified above)
  5. On run job, I get this: "TypeError: Cannot read property 'private_key' of undefined" and semaphore subsequently crashes.

If you could also a HOWTO for a test playbook flow, that would help the end user use this. Thanks

@vsayer
Copy link
Author

vsayer commented May 26, 2015

Also, it appears at the git clone step, semaphore is updating my keys to require a passphrase. Is that correct? If so, what's the workaround if I have no passphrase set for my keys?

@rmessner
Copy link
Contributor

rmessner commented Jun 6, 2015

Hi,

I'm having the same issue.
In my case, it didn't save the identity, that's why when you try to start a job, you got the "TypeError: Cannot read property 'private_key' of undefined".

I worked around this by editing again the playbook, you can see that the identity is not set, select it and save again. This should be working.

@matejkramny matejkramny added the bug label Sep 9, 2015
@matejkramny
Copy link
Contributor

This issue is that either the key is null/undefined in the database or the _id is not leading to a key.

You can edit the database.

If your question is still relevant, what is the log output?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants