Oh, I suppose that explains it. Well ssh favors the rsa key too, but ssh doesn't give up if the first key doesn't work. If the ssh slaves plugin, or the credentials plugin, or whatever actually controls this is stopping after trying the first key then that's a pretty significant regression. I'll try to verify that it actually works like that, and create a bug for it if so.
Eric ________________________________ From: [email protected] [[email protected]] on behalf of Stephen Connolly [[email protected]] Sent: Friday, May 03, 2013 5:04 PM To: [email protected] Subject: Re: can't start slaves anymore, ssh auth failing - FIXED It favours rsa if present On Friday, 3 May 2013, Haszlakiewicz, Eric wrote: Well, I finally managed to get it working. I deleted all the existing credentials, and added a new one. I then had to go edit each of my node configurations and explicitly specify the new credential configuration. Also, using the "From the Jenkins master ~/.ssh" under Manage Credentials didn't work at all. I had to explicitly specify the path to the .ssh/id_dsa key file. ugh, what a pain. Eric > -----Original Message----- > From: [email protected]<UrlBlockedError.aspx> > [mailto:jenkinsci-<UrlBlockedError.aspx> > [email protected]<UrlBlockedError.aspx>] On Behalf Of Haszlakiewicz, Eric > > -----Original Message----- > > From: [email protected]<UrlBlockedError.aspx> > > [mailto:jenkinsci-<UrlBlockedError.aspx> On Friday, 3 > > May 2013, Jonathan Rogers wrote: > > Stephen Connolly wrote: > > > On Thursday, 2 May 2013, JonathanRRogers wrote: > > > 0.23 and 0.24 have a race condition where there is a 10-15% chance > > > that you will loose your credentials after rebooting the first time > > > post installation. > > > > > > 0.25 should be fine. > > > > Are you saying that upgrading from 0.22 to 0.25 is transparent? > > > > Should be... The plugin will pickup your credentials from your slave > > configuration and add them to the credentials store, consolidating > > where that makes sense. IOW the upgrade should result in everything > > still working as before > > > > If it doesn't then that's a bug, but nobody has alerted me to issues > > with that upgrade path. > > I seem to have ended up with 9 entries on the Manage Credentials page, > most with "From a file on Jenkins master" selected, but with no way to > indicate the file to use. > Is this what happens when that race condition is hit? > I guess I'll try upgrading again, then removing and re-adding some > credentials. > > Eric -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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/groups/opt_out.
