Hi Ivan, That's correct. I think it works when slave has different home location with different user. my doubt was it slaves status were idle after upgrading jenkins in new master server.
Thanks, Om Prasad Surapu On Wednesday, May 27, 2020 at 10:07:15 PM UTC+5:30, Ivan Fernandez Calvo wrote: > > Do you mean you have the same agent connected to two different masters > with different versions of the core and using the same user with the same > home? if so, this is a miracle that works, you are sharing same files > between two different instances of Jenkins core that also are in different > versions. If you want to connect those instances to both masters (not > recommended because you shared resources in a predictable way) you should > use different users at least. > > El miércoles, 27 de mayo de 2020, 15:10:52 (UTC+2), Om Prasad Surapu > escribió: >> >> Hi All, >> >> We have a jenkins master running with 2.13 version on EC2 instance. As >> part of Upgrade, we took AMI of existing jenkins master and provisioned >> instance and upgraded jenkins to higher version. >> >> After upgrade, all the slave nodes status showing as Idle but few days >> later they are offline suddenly. But same slave nodes status as Idle on Old >> jenkins master. It was AMI of Old jenkins server so keys were already >> copied and can do ssh from new jenkins master to slave node. >> >> Has anyone seen similar issue? >> >> Thanks, >> Om >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/199f8e5c-6ca0-4239-b5f1-aca3165bbb87%40googlegroups.com.
