Jira (PUP-9717) Puppet 6 client exits on start when it cannot connect to puppetserver

[Siebrand Mazeland (JIRA)]

Siebrand Mazeland updated an issue

Puppet / PUP-9717 Puppet 6 client exits on start when it cannot connect to puppetserver Change By: Siebrand Mazeland Summary: Puppet 6 client exist exits on start when it cannot connect to puppetserver Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-9717 Puppet 6 client exits on start when it cannot connect to puppetserver

Change By: Josh Cooper Team: Coremunity

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-9717 Puppet 6 client exits on start when it cannot connect to puppetserver

Change By: Josh Cooper Fix Version/s: PUP 6.5.0

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper commented on PUP-9717

Re: Puppet 6 client exits on start when it cannot connect to puppetserver Before 6.4, the agent would rescue all StandardErrors during key generation, csr submission, cert retrieval, and wait for waitforcert seconds until retrying. In 6.4.0, only rescues some errors, which is a bug.

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-9717

Puppet 6 client exits on start when it cannot connect to puppetserver

Change By: Josh Cooper Sprint: Coremunity Hopper

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-9717 Puppet 6 client exits on start when it cannot connect to puppetserver

Change By: Josh Cooper Fix Version/s: PUP 6.4.3

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-9717 Puppet 6 client exits on start when it cannot connect to puppetserver

Change By: Josh Cooper Sprint: Coremunity Hopper Platform Core KANBAN

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper assigned an issue to Josh Cooper

Puppet / PUP-9717 Puppet 6 client exits on start when it cannot connect to puppetserver

Change By: Josh Cooper Assignee: Josh Cooper

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-9717 Puppet 6 client exits on start when it cannot connect to puppetserver

Change By: Josh Cooper Fix Version/s: PUP 6.5.0 Fix Version/s: PUP 6.6.0

Add Comment

[Siebrand Mazeland (JIRA)]

Siebrand Mazeland updated an issue

Puppet / PUP-9717 Puppet 6 client exits on start when it cannot connect to puppetserver

Change By: Siebrand Mazeland *Puppet Version: 6.4.2* *Puppet Server Version: 6.3.0* *OS Name/Version: CentOS 7.6* In previous versions of puppet, I would spin up instances in AWS, regardless of the puppetservere being available, and have runinterval at 20 seconds. Whenever the base packages were installed, I'd update the puppet configuration to a runinterval of every 30 minutes. Since I've started version 6 clients, this "trick" no longer works. The puppet client will try to connect to the puppetserver when it starts, and if it doesn't it will exit. That's quite disastrous for my deployment strategy. Steps to reproduce: Pre-requisites: Have the above puppet server and client versions on a single machine. Have puppetserver and client stopped. 1. Start puppet client. *Desired Behavior:* A. puppet client starts, regardless of a connection is possible with the puppetserver. It will re-try each runinterval. *Actual Behavior:* - puppet client exits with below message in /var/log/ message messages : {noformat} May 22 15:08:05 bas-t-1 systemd: Started Puppet agent. May 22 15:08:07 bas-t-1 puppet-agent[12580]: Could not run: Failed to open TCP connection to bas-t-1.t.dam.loc:8140 (Connection refused - connect(2) for "bas-t-1.t.dam.loc" port 8140) May 22 15:08:07 bas-t-1 systemd: puppet.service: main process exited, code=exited, status=1/FAILURE May 22 15:08:07 bas-t-1 systemd: Unit puppet.service entered failed state. May 22 15:08:07 bas-t-1 systemd: puppet.service failed.{noformat} puppet.conf: {noformat} [main] server = bas-t-1.t.dam.loc environment = production runinterval = 20s hiera_config = /etc/puppetlabs/puppet/hiera.yaml [master] dns_alt_names = bas-t-1.t.dam.loc{noformat}

Add Comment

[Kris Bosland (JIRA)]

Kris Bosland commented on PUP-9717

Re: Puppet 6 client exits on start when it cannot connect to puppetserver Merged to 6.4.x at ebed29d.

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-9717

Puppet 6 client exits on start when it cannot connect to puppetserver

Change By: Josh Cooper Release Notes Summary: Restores the behavior present in < 6.4 whereby non-onetime puppet runs will wait and retry if an error is encountered while bootstrapping the SSL subsystem. The wait interval is controlled by the existing `waitforcert` setting. Onetime puppet runs (such as `puppet agent --test/--onetime`) will not retry, and instead exit when the first error occurs. Release Notes: Bug Fix

Add Comment

[Octavian Larion (JIRA)]

Octavian Larion commented on PUP-9717

Re: Puppet 6 client exits on start when it cannot connect to puppetserver This has been promoted to master and is included in the 6.6.0 release, closing the ticket.

Add Comment

[Jean Bond (JIRA)]

Jean Bond updated an issue

Puppet / PUP-9717

Puppet 6 client exits on start when it cannot connect to puppetserver

Change By: Jean Bond Labels: resolved-issue-added

Add Comment