-
Bug
-
Resolution: Fixed
-
Major
We have configured Octane / Jenkins integration by installing ALM Octane plugin in Jenkins. The connection works for a day and then drops.
Jenkins is setup as a CI server in Octane, we have found that if we run a pipeline everyday with a Jenkins build that the connection between Jenkins and Octane drops and the Jenkins plugin for Octane cannot get a new connection to the Octane server.
A few things we have noticed:
The issue only happens if we run a build once a day, if we have a pipeline running every hour the issue does not seem to happen. We believe that the plugin may not be managing the sessions (cookies/tokens) with Octane correctly and that by running a build every hour might be keeping the session "alive"
When this happens our only fix seems to be restarting the Jenkins server which we think might make the plugin renegotiate the session with Octane
We tried the newest plugin 5.9 to see if it might resolve the issue but it did not
[JENKINS-59754] Jenkins Micro Focus Application Automation Tools Plugin losing connection with Octane after running pipelines
Radi Berkovich
added a comment - HI.
I need more information - what is not working after some time?
In log file , I see that relogins are succedded.
The best will be , if you encounter you problem - take logs file and give me the time it happen, so it will be easier to search relevant log rows.
Thanks.
Radi.
Radi Berkovich
added a comment - HI.
I need more information - what is not working after some time?
In log file , I see that relogins are succedded.
The best will be , if you encounter you problem - take logs file and give me the time it happen, so it will be easier to search relevant log rows.
Thanks.
Radi.
Hello Radi,
What happens is if they go more than a few hours without running a build It will not run a build from Octane. At the time that this is happening if you check Octane it does not show the Jenkins CI server as connected during that period, even though we can ping the jenkins server from Octane at the time that Octane is saying that it cannot get to jenkins.
The log files that we sent had a period in there where it could not connect but that is the weird thing, the plugin seems to think that it is creating a new session but we do not think that this is actually happening..... And as soon as Jenkins is restarted the issue goes away
Thanks
Radi Berkovich
added a comment - Hi.
Unfortunately we did not succeeded to reproduce the issue in our environment.
Can I create plugin version with additional log message and you will use it for several days?
Thanks.
Radi Berkovich
added a comment - Hi.
Unfortunately we did not succeeded to reproduce the issue in our environment.
Can I create plugin version with additional log message and you will use it for several days?
Thanks. Yes that would be fine, send us the modified plugin and we can install that and get the logs
Radi Berkovich
added a comment - Please use v5.9.2-beta :
http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/hp-application-automation-tools-plugin/5.9.2-beta/hp-application-automation-tools-plugin-5.9.2-beta.hpi
Radi Berkovich
added a comment - please update me if you already used 5.9.2
. Radi Berkovich
added a comment - If you still didn't installed previous link, please you this :
(its the same code, it just official beta version)
Radi Berkovich
added a comment - If you still didn't installed previous link, please you this :
(its the same code, it just official beta version)
http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/hp-application-automation-tools-plugin/5.9.3-beta/hp-application-automation-tools-plugin-5.9.3-beta.hpi
Radi Berkovich
added a comment - any updates? Official version 6.0 is released .
Please check if issue is reproduced on this version.
Radi Berkovich
added a comment - - edited Official version 6.0 is released .
Please check if issue is reproduced on this version. 
I actually see that relogin succedded - "having successful RE-LOGIN".
Please explain what happen with plugin when it "drop" the connection, what exactly happen.