Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-41975

Multiple servers configuration ssh : jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Major Major
    • publish-over-ssh-plugin
    • Jenkins ver. 2.19.4 on Linux u3 3.13.0-105-generic #152-Ubuntu SMP Fri Dec 2 15:37:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
      (Vagrant machine)

      default connection ssh works but when you have two ssh servers, you put the each rsa private key in each server and the default key is blank. You test it and you have:
      Failed to connect or change directory
      jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [ora10g@FR-8L3GXW1B]. Message [Auth fail].
      You supress Remote Directory. Same bad result.
      And you put a default rsa private key and a specific rsa private key : Same bad result

        1. error 1a.JPG
          error 1a.JPG
          82 kB
        2. error 1b.JPG
          error 1b.JPG
          104 kB
        3. error 1c.JPG
          error 1c.JPG
          37 kB
        4. error 1d.JPG
          error 1d.JPG
          77 kB

          [JENKINS-41975] Multiple servers configuration ssh : jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config

          Bryan Peterson added a comment -

          We are seeing the same issue, including trying to remove the passphrase from the advanced config options for the specific server.

          All other servers using the default key works just fine, just the one that requires a special key.

          Workaround: Allow the default key access to the server.

          Bryan Peterson added a comment - We are seeing the same issue, including trying to remove the passphrase from the advanced config options for the specific server. All other servers using the default key works just fine, just the one that requires a special key. Workaround: Allow the default key access to the server.

          Alex Earl added a comment -

          I'm not sure I understand the issue, can you please describe what is going wrong?

          Alex Earl added a comment - I'm not sure I understand the issue, can you please describe what is going wrong?

          Gavin McDonald added a comment -

          For your information, all publish-over-ssh component type JENKINS issues related to the Publish Over SSH plugin have been transferred to Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues

          Here is the direct link to this issue in Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues/125
          And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-ssh-plugin/issues?q=%22JENKINS-41975%22

          (Note: this is an automated bulk comment)

          Gavin McDonald added a comment - For your information, all publish-over-ssh component type JENKINS issues related to the Publish Over SSH plugin have been transferred to Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues Here is the direct link to this issue in Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues/125 And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-ssh-plugin/issues?q=%22JENKINS-41975%22 (Note: this is an automated bulk comment)

          Gavin McDonald added a comment -

          Closing ticket, please use the corresponding Github Issue as linked above.

          Gavin McDonald added a comment - Closing ticket, please use the corresponding Github Issue as linked above.

            Unassigned Unassigned
            pviltard Pascal VILTARD
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: