Jira (PUP-1763) Puppet run continues despite failed Pluginsync

17 views
Skip to first unread message

R.I.Pienaar (JIRA)

unread,
Mar 5, 2015, 6:49:23 AM3/5/15
to puppe...@googlegroups.com
R.I.Pienaar commented on Bug PUP-1763
 
Re: Puppet run continues despite failed Pluginsync

I think this is quite an important issue. If pluginsync has issues you really can't know what versions of providers/facts/etc are used to apply your catalog and quite bad things can happen.

Ideally I'd say pluginsync failures should just prevent the catalog from being applied all together with some indication in last_run_summary.yaml and reports that this happened. If not the default behaviour then a setting to cause this to happen would be really good.
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Atlassian logo

Kylo Ginsberg (JIRA)

unread,
Mar 30, 2015, 6:27:18 PM3/30/15
to puppe...@googlegroups.com
Kylo Ginsberg updated an issue
 
Puppet / Bug PUP-1763
Change By: Kylo Ginsberg
Scrum Team: Client Platform
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Atlassian logo

Josh Cooper (JIRA)

unread,
Dec 11, 2015, 6:24:02 PM12/11/15
to puppe...@googlegroups.com
Josh Cooper commented on Bug PUP-1763
 
Re: Puppet run continues despite failed Pluginsync

If the master doesn't have at least one module/lib directory, pluginsync will fail (and I think the same is true for facts.d for pluginfactsync) due to PUP-2608. So that needs to be fixed before this ticket can be.
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Atlassian logo

John Duarte (JIRA)

unread,
May 15, 2017, 6:17:04 PM5/15/17
to puppe...@googlegroups.com
John Duarte updated an issue
 
Change By: John Duarte
Labels: triaged
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Atlassian logo

John Duarte (JIRA)

unread,
May 15, 2017, 6:18:04 PM5/15/17
to puppe...@googlegroups.com
John Duarte updated an issue
Change By: John Duarte
Team: Agent

Moses Mendoza (JIRA)

unread,
May 18, 2017, 1:46:02 PM5/18/17
to puppe...@googlegroups.com
Moses Mendoza updated an issue
Change By: Moses Mendoza
Labels: triaged

Josh Cooper (Jira)

unread,
Jun 5, 2020, 5:47:03 PM6/5/20
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Epic Link: PUP- 7539 10539
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Josh Cooper (Jira)

unread,
Jul 13, 2020, 11:58:04 AM7/13/20
to puppe...@googlegroups.com
Josh Cooper assigned an issue to Josh Cooper
Change By: Josh Cooper
Assignee: Josh Cooper

Josh Cooper (Jira)

unread,
Jul 13, 2020, 11:59:03 AM7/13/20
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Sprint: Platform Core KANBAN

Josh Cooper (Jira)

unread,
Jul 15, 2020, 4:12:04 PM7/15/20
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Fix Version/s: PUP 6.18.0
Fix Version/s: PUP 5.5.22

Josh Cooper (Jira)

unread,
Jul 16, 2020, 1:16:03 PM7/16/20
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Release Notes: Bug Fix
Release Notes Summary: Previously, if a puppet agent failed to pluginsync, it would continue trying to request a catalog and apply it with the possibly incorrect fact and plugin versions, leading to obscure errors or worse, data corruption. The puppet agent will now abort the run if pluginsync fails.

Josh Cooper (Jira)

unread,
Jul 29, 2020, 10:15:03 AM7/29/20
to puppe...@googlegroups.com
Josh Cooper commented on Bug PUP-1763

Josh Cooper (Jira)

unread,
Jul 29, 2020, 10:16:02 AM7/29/20
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Release Notes Summary: Previously, if a puppet agent failed to pluginsync, it would continue trying to request a catalog and apply it with the possibly incorrect fact and plugin versions, leading to obscure errors or worse, data corruption. The puppet This release adds a new setting `ignore_plugin_errors` which defaults to true preserving the existing behavior. If set to false, then the agent will now abort the run if pluginsync fails.

Josh Cooper (Jira)

unread,
Jul 29, 2020, 10:19:03 AM7/29/20
to puppe...@googlegroups.com
Josh Cooper commented on Bug PUP-1763
 
Re: Puppet run continues despite failed Pluginsync

In puppet 7, the `ignore_plugin_errors` setting's default value will change from true to false, and the setting will be removed. See PUP-10598.

Josh Cooper (Jira)

unread,
Aug 5, 2020, 12:52:03 PM8/5/20
to puppe...@googlegroups.com
Josh Cooper commented on Bug PUP-1763

Passed CI in 81e3bdf38bbfb1ec

Josh Cooper (Jira)

unread,
Aug 5, 2020, 12:52:03 PM8/5/20
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Release Notes Summary: Previously, if puppet agent failed to agents ignored pluginsync , it would continue trying to request a catalog errors and would apply it with the catalog with possibly incorrect fact facts and plugin versions, leading to obscure errors or worse, data corruption. This release adds a new setting `ignore_plugin_errors` which defaults to true preserving the existing behavior . If set to false, then the agent will abort the run if pluginsync fails. The setting defaults to true so the old behavior is preserved. In Puppet 7, the default value will be switched to false.

Claire Cadman (Jira)

unread,
Aug 13, 2020, 9:50:04 AM8/13/20
to puppe...@googlegroups.com
Claire Cadman updated an issue
Change By: Claire Cadman
Labels: doc_reviewed
Reply all
Reply to author
Forward
0 new messages