https://www.puppet.com/community logo
Join Slack
Powered by
This message was deleted.
# bolt
s
This message was deleted.
y
I’d check the transport options in the bolt documentation
z
Hi Yury, thank you for the quick reply. Can you tell me where I can find the bolt documentation?
c
z
Wow, impressed how quick you guys are...let me read this document...Thanks a lot!
y
@CVQuesty++
z
Thank you Yury....let me read yours too....
Hi, I found these lines in bolt-defaults.yaml:
inventory-config: pcp: job-poll-interval: 15 job-poll-timeout: 30
But it seems not working....any idea?
I also tried disconnect-timeout, but no luck....
t
if you use native ssh, you can set ssh options and let ssh do the timeout.
z
Hi tuxmea, thank you! My problem is that bolt can ssh to this machine, but the command running on this machine won't finish.
t
how about ssh connection timeout? that terminates inactive sessions.
z
Let me first clarify one thing: my original statement was not accurate. The bolt actually will return, after 3 minutes. I didn't wait long enough before and kill the bolt command. So at least it will return! Now my question is: is this 3 minutes built in somewhere? Can I specify a shorter time?
Hi tuxmea, I tried connection timeout 30 seconds, but it will still wait for 3 minutes to return the bolt command.
c
that really sounds like some latency on your network the way you’re describing it.
z
Hi, I did another test....this time the command is to start clearcase (/usr/atria/etc/atria_start start). Very interesting: if I manually run this command on one machine, it finished quickly. But when I used bolt to run on this machine, the bolt command never returns (I waited for 10 minutes).....
So final question: any way to tell bolt command to finish after certain time such as 5 minutes?
Continuing my test. For this problematic machine, I tried "ssh thisHostnmae myCommand" and it won't return. Then I added "-t" option: ssh -t thisHostname myCommand, and it returns. So my question is: what is the bolt equivalent option as ssh's -t option?
In bolt-defaults.yaml, I tried: ssh-command: ['ssh', '-t']
y
tty: true
is the default as far as I see
Are you really using ssh with bolt? Any chance your setup uses PCP with Puppet Enterprise instead?
z
Hello Yury, I don't know if I am really using ssh with bolt or not 🙂....
In bolt-defaults.yaml, I have this puppetdb section:
puppetdb: server_urls: ["https://foreman.example.com:8081"] cacert: /etc/puppetlabs/puppet/ssl/certs/ca.pem cert: /etc/puppetlabs/puppet/ssl/certs/foreman.example.com.pem key: /etc/puppetlabs/puppet/ssl/private_keys/foreman.example.com.pem
So I think you are right, I am using Puppet ....so how to achieve tty: true in puppet?
Guess what? After I specify "tty: true" in bolt-defaults.yaml, it works!!! Thank you very much!!! So it seems the tty default is false?
y
That’s really confusing as the documentation says it should be true by default.. 🤔 but anyway it’s great that it works for you now!
z
Glad you pointed tty out! Thank you so much!
Open in Slack
PreviousNext
Powered by