Bad Key Store behavior, permissions denied when use become

[karloff10]

Hi, i just want to report that the behavior of the key store is not intuitive and cost a lot of 'try & error' run to find the underlying problem.

What is the Problem? All my jobs which use become: true run into permission denied.

What i did:

• Add SSH-Key with Username as Key Store Object and use it inside the Inventory
• Add a Login with Password with (the optional) Username and the Password also use it inside the inventory

What is the workaround? Remove from the Key Store object Login with password the Username. If you enter any username it will always fail. Just enter the password with an empty username.

I think this should be fixed, or at least it should be written somewhere that you are not allowed to enter usernames in the username field, if you plan the use the become feature.
For the record: i use latest stable release on an arch linux