Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Overriding slaveConnectTimeout is not honoured #903

Open
commodity729 opened this issue Aug 18, 2023 · 1 comment
Open

Overriding slaveConnectTimeout is not honoured #903

commodity729 opened this issue Aug 18, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@commodity729
Copy link

Describe the bug

I'm provisioning jenkins where I override agent.connectTimeout setting. By default it says that value is 100 (in seconds according to VALUES_SUMMARY.md file. When I set any other value, like 500 I still see the following:

2023-08-18 08:53:15.482+0000 [id=7218] WARNING o.c.j.p.k.KubernetesLauncher#launch: Error in provisioning; agent=KubernetesSlave name: default-flslt, template=PodTemplate{id='-jenkins-slave-7543208ce3d913bc458bd901ee0a225a', name='default', slaveConnectTimeout=100, .........

No matter what I set when overriding agent.connectTimeout , I still see slaveConnectTimeout=100 in logs. Looks like a bug to me.

Version of Helm and Kubernetes

- Helm: Terraform Kubernetes provider helm 2.10.1
- Kubernetes: 1.27

Chart version

jenkins-4.4.2

What happened?

No response

What you expected to happen?

It has to override slaveConnectTimeout value

How to reproduce it

Deploy chart and try to override agent.slaveConnectTimeout value

Anything else we need to know?

Please investigate :) Thanks

@commodity729 commodity729 added the bug Something isn't working label Aug 18, 2023
@YakovHerz
Copy link

Hi

try using agent.connectTimeout instead of agent.slaveConnectTimeout

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants