|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Look, this is quite simple. Every time I try to set up a VM to use as a slave to reproduce this issue, I singularly fail to reproduce the issue.
I suspect the root cause is that I just install Java the "right way". So for example, I have set up CentOS 6.5 and installed java with yum install java-1.7.0-openjdk and connected as a slave and... oh look ssh-agent works.
I really want to get to the bottom of this issue.
If you want this issue solved I suggest you do the following: produce a step by step for a slave that has this issue from installing the OS through configuring and connecting the slave and finally testing the ssh-agent with a simple job.
I have done this about 10-15 times already, all with no luck. I do not consider my inability to reproduce this issue in the "the bug is not real" category, rather I consider there must be some key step that I am missing when I set up the slave OS... be it some additional package I don't install, or the way I configure Java, etc.
If there is a VM image that I can play with locally (and it's much easier if I have the step-by-step to create that image myself as that lets me play with alternative steps to try and break the reproducibility and find the root cause) I do not see how to make progress on this issue.