-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Dev
My jenkins job used to work fine , but as a monthly ami refresh, means on aws ec2, on which jenkins is running, we do a ami refresh of that ec2 after 2 months.
after that, problem started.
Then we tried to roll back to older ami(though the recent ami was not avaiable) ,but still the issue was same.
So, it doesn't looks like an ami issue.
But our main concern is, we are not able to see the errors in jenkins pipeline, it will just stuck at one at some docker test cases.
we though, its an memory or cpu issues, we checked that in slave node, using htop and free-m, all looked good.
Then we thought, it jdk mismacth issue between master and slave, even after matching those jdk version, its the same issue.
we are using ec2 plugin for managing aws ec2 nodes on the go in jenkins.
So, our main concern is , we are doing hit and try as we don't have error, So, mainly we want to know the error.
our jenkins inside ec2 is running on docker, when we do docker logs container id, then this logs visible, but no help, will attach the log file.
I checked my slave agent logs, it was all fine, I have no idea where to check things.
Jenkins version:
REST API
Jenkins 2.330
to add my investigation in it:
Our jenkins run on Docker container, and this Docker container runs on EC2 and EC2 is based on an AMI, and that AMi gets expired after 2 months and jenkins stops working and then , we get a new ami, that we add in ASG, so, our jenkins ec2 gets a new AMI and then DOcker container runs and jenkins comes up.
But this issue started after this ami refresh
****************
There is hopefully, no change in AMI side, it would be same.
We have tried taking old ami , which was base AMI for jenkins, still issue was same.
though, now we are back to ami issue persist.
we have upgraded java version in slave nodes to 11, but still the issue is same.
we have upgraded amazon ec2 plugin, but still the issue is same from .66 to .68, as that was available in updates in manage plugins.
we have tried by macthing slave and master jdk as 11, that also stuck at same place and with both slave and master at jdk 8, that job also stuck