03, 2013 5:04 PM
To: jenkinsci-users@googlegroups.com
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
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 configuratio
Hmmm, not sure as once it has tried to transition to the new config it
saves the new config so that it can be applied. I'll have a look through
the code again. Most likely it will be Tuesday before I can take a look
though
On 3 May 2013 22:34, Les Mikesell wrote:
> On Fri, May 3, 2013 at 2:19 P
On Fri, May 3, 2013 at 2:19 PM, Les Mikesell wrote:
>> If it doesn't then that's a bug, but nobody has alerted me to issues with
>> that upgrade path.
>
> Can you describe what is "supposed" to happen in this upgrade?I
> just did an rpm update from a 1.5.00-1.1 (non LTS) to LTS 1.509.1-1
> a
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
> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> 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% ch
On Fri, May 3, 2013 at 2:15 AM, Stephen Connolly
wrote:
>
>> 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
On Friday, 3 May 2013, Jonathan Rogers wrote:
> Stephen Connolly wrote:
> >
> >
> > On Thursday, 2 May 2013, JonathanRRogers wrote:
> >
> > On Thursday, May 2, 2013 2:50:44 PM UTC-4, LesMikesell wrote:
> >
> > On Thu, May 2, 2013 at 1:26 PM, Kevin Fleming (BLOOMBERG/ 731
> > LE
Stephen Connolly wrote:
>
>
> On Thursday, 2 May 2013, JonathanRRogers wrote:
>
> On Thursday, May 2, 2013 2:50:44 PM UTC-4, LesMikesell wrote:
>
> On Thu, May 2, 2013 at 1:26 PM, Kevin Fleming (BLOOMBERG/ 731
> LEXIN)
> wrote:
> > This change would not have bee
On Thursday, 2 May 2013, JonathanRRogers wrote:
> On Thursday, May 2, 2013 2:50:44 PM UTC-4, LesMikesell wrote:
>>
>> On Thu, May 2, 2013 at 1:26 PM, Kevin Fleming (BLOOMBERG/ 731 LEXIN)
>> wrote:
>> > This change would not have been in the Jenkins changelog, because it
>> wasn't
>> > technically
.com
> > [mailto:jenkinsci-
> > us...@googlegroups.com ] On Behalf Of CHAVANNE Robert
> > Sent: Thursday, May 02, 2013 10:43 AM
> > To: jenkinsci-users@googlegroups.com
> > Subject: Re: can't start slaves anymore, ssh auth failing
> >
> > Hello Eri
On Thursday, May 2, 2013 2:50:44 PM UTC-4, LesMikesell wrote:
>
> On Thu, May 2, 2013 at 1:26 PM, Kevin Fleming (BLOOMBERG/ 731 LEXIN)
> > wrote:
> > This change would not have been in the Jenkins changelog, because it
> wasn't
> > technically a Jenkins change. It's a change in the SSH Slaves p
On Thu, May 2, 2013 at 1:26 PM, Kevin Fleming (BLOOMBERG/ 731 LEXIN)
wrote:
> This change would not have been in the Jenkins changelog, because it wasn't
> technically a Jenkins change. It's a change in the SSH Slaves plugin.
Shouldn't something note when the things distributed with the core
pack
This change would not have been in the Jenkins changelog, because it wasn't
technically a Jenkins change. It's a change in the SSH Slaves plugin.
- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: May 2 2013 14:13:22
> -Original Messa
> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
>
> Ensure you are on ssh-slaves 0.25 or newer as 0.23 and 0.24 can forget the
> credentials any time you reboot due to a race condition
I actually rolled back to 0.22 to get things working, but I'll try upgr
or
the pointer.
Eric
> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of CHAVANNE Robert
> Sent: Thursday, May 02, 2013 10:43 AM
> To: jenkinsci-users@googlegroups.com
> Subject: Re: can't start slave
You should also take a look at the tool locations on your slaves. My
configurations were messed up with, for instance, maven configured with the
JDK path and so on.
Le jeudi 2 mai 2013 17:43:09 UTC+2, CHAVANNE Robert a écrit :
>
> Hello Eric,
> We had the same kind of problem.
> I think you sh
Ensure you are on ssh-slaves 0.25 or newer as 0.23 and 0.24 can forget the
credentials any time you reboot due to a race condition
On 2 May 2013 16:43, CHAVANNE Robert wrote:
> Hello Eric,
> We had the same kind of problem.
> I think you should take a look at "manage Credentials" in manage Jenk
Hello Eric,
We had the same kind of problem.
I think you should take a look at "manage Credentials" in manage Jenkins.
We had to create credential to fix the issue.
I hope it can help.
Regards,
Robert
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users
19 matches
Mail list logo
