Jira (PUP-7456) When agent gets its environment set by an ENC and cannot connect to the master it will pluginsync from the production environment ( possibly removing custom facts, etc... )

[Nick Walker (JIRA)]

Nick Walker updated an issue

Puppet / PUP-7456 When agent gets its environment set by an ENC and cannot connect to the master it will pluginsync from the production environment ( possibly removing custom facts, etc... ) Change By: Nick Walker Summary: When agent gets its environment set by an ENC and cannot connect to the master it will pluginsync from the production environment  ( possibly removing custom facts, etc... ) Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Geoff Nichols (JIRA)]

Geoff Nichols updated an issue

Puppet / PUP-7456 When agent gets its environment set by an ENC and cannot connect to the master it will pluginsync from the production environment ( possibly removing custom facts, etc... )

Change By: Geoff Nichols Sprint: Agent Triage

Add Comment

[Geoff Nichols (JIRA)]

[Geoff Nichols (JIRA)]

Geoff Nichols updated an issue

Puppet / PUP-7456 When agent gets its environment set by an ENC and cannot connect to the master it will pluginsync from the production environment ( possibly removing custom facts, etc... )

Change By: Geoff Nichols Sprint: Agent Grooming

Add Comment

[Ethan Brown (JIRA)]

Ethan Brown updated an issue

Puppet / PUP-7456 When agent gets its environment set by an ENC and cannot connect to the master it will pluginsync from the production environment ( possibly removing custom facts, etc... )

Change By: Ethan Brown Labels: tcse  triaged

Add Comment

[Geoff Nichols (JIRA)]

Geoff Nichols updated an issue

Puppet / PUP-7456 When agent gets its environment set by an ENC and cannot connect to the master it will pluginsync from the production environment ( possibly removing custom facts, etc... )

Change By: Geoff Nichols Sprint: Agent Grooming  2017-06-21

Add Comment

[Geoff Nichols (JIRA)]

[Geoff Nichols (JIRA)]

Geoff Nichols commented on PUP-7456

Re: When agent gets its environment set by an ENC and cannot connect to the master it will pluginsync from the production environment ( possibly removing custom facts, etc... ) This may be resolved as part of a related effort (see PUP-7662).

Add Comment

[Geoff Nichols (JIRA)]

Geoff Nichols updated an issue

Puppet / PUP-7456

When agent gets its environment set by an ENC and cannot connect to the master it will pluginsync from the production environment ( possibly removing custom facts, etc... )

Change By: Geoff Nichols Sprint: Agent Grooming

Add Comment

[Josh Cooper (Jira)]

Josh Cooper updated an issue

Puppet / PUP-7456 When agent gets its environment set by an ENC and cannot connect to the master it will pluginsync from the production environment ( possibly removing custom facts, etc... )

Change By: Josh Cooper Epic Link: PUP- 7539 7563

Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

[Josh Cooper (Jira)]

Josh Cooper commented on PUP-7456

Re: When agent gets its environment set by an ENC and cannot connect to the master it will pluginsync from the production environment ( possibly removing custom facts, etc... ) This error occurs because puppet logs a warning if it can't pluginsync, but doesn't abort the run. See PUP-1763. That's because there's a bug in puppetserver that causes it to fail the pluginsync request if it doesn't have at least one module installed, see PUP-2608. So we need to fix the latter issue first and then agents can differentiate between "the server doesn't have any modules" vs "the server encountered an error when trying to generate plugin metadata", as can often occur due to file permissions in the codedir. I'm going to close this as a dup of PUP-1763.

Add Comment