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

Splunk plugin fails test connection when upgraded past 1.8.2 rollback restores

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • splunk-devops-plugin
    • Aws ec2/Redhat: 3.10.0-1127.19.1.el7.x86_64
      Jenkins: Jenkins 2.249.1
      Plugins: splunk-devops-plugin (1.8.2 and 1.9.4)
      Java: openjdk version "1.8.0_262"

      Upgrading the working splunk-devops-plugin from (1.8.2) to (1.9.4) breaks the connection, rollback to 1.8.2 restores it.

      Test:

      Upgrade plugin press "Test Connection" (splunk for Jenkins configuration) get error

      Token:XXXXXX response:Forbidden

      Rollback to version 1.8.2

      Test connection success.

      In a an adhoc Jenkins instance created to debug this we updated all plugins to the latest version with the latest Jenkins.

      We also set the the variables http.proxyHost http.proxyPort https.proxyHost http.nonProxyHosts (per recent release notes)

       

      In the Jenkins log we see the following.

      com.splunk.splunkjenkins.utils.LogConsumer$SplunkClientError: Forbidden, http event collector token is invalid, status code:403

       

       

            fengxx Ted Xiao
            jim_zarakis Jim Zarakis
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: