Jira (PUP-7777) Append "source_permissions=use" to 3.x file_metadata requests

4 views
Skip to first unread message

Bernhard Schmidt (JIRA)

unread,
Jul 13, 2017, 3:38:03 PM7/13/17
to puppe...@googlegroups.com
Bernhard Schmidt moved an issue
 
Puppet / Bug PUP-7777
Append "source_permissions=use" to 3.x file_metadata requests
Change By: Bernhard Schmidt
Fix Version/s: SERVER 2.1.0
Affects Version/s: SERVER 2.1.0
Affects Version/s: PUP 4.8.2
Component/s: Puppet Server
Component/s: Server
Key: SERVER PUP - 1890 7777
Project: Puppet  Server
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Atlassian logo

Bernhard Schmidt (JIRA)

unread,
Jul 13, 2017, 3:40:02 PM7/13/17
to puppe...@googlegroups.com
Bernhard Schmidt updated an issue
This is a clone of SERVER-684, I'm hitting the very same issue with a Debian Stretch server (4.8.2) and a Debian Jessie agent (3.7.2). After upgrading the agent to 4.8.2 as well source_permissions => use starts to work.

---

The file_metadata endpoint has a query parameter called {{source_permissions}} with possible values {{ignore}}, {{use}}, or {{use_when_creating}}.

The 3.x agent and master defaulted to {{use}}, but this changed in 4.x to {{ignore}}.  In addition, 3.x agents "rely" on this default value matching on both sides and therefore don't bother specifying a value when making requests.

This is problematic for 3.x agents talking to a 4.x master, as the default value has changed and the agent doesn't explicitly specify it. For comparison, the 4.x agents explicitly specify the value when making the request.

This behavior will break external executable facts (they won't be executable on the agent) for 3.x agents talking to 4.x master. 

We should modify the {{legacy_routes_service}} to reconcile this difference and append {{source_permissions=use}} to file_metadata requests made to the old URLs (unless of course it's already specified, which agent 3.x agents won't).

We already have failing acceptance tests in CI for this: https://jenkins.puppetlabs.com/job/platform_puppet-server_integration-system_no-conditional_puppet3-compat_master/18/

Bernhard Schmidt (JIRA)

unread,
Jul 13, 2017, 3:40:02 PM7/13/17
to puppe...@googlegroups.com

Bernhard Schmidt (JIRA)

unread,
Jul 13, 2017, 3:40:03 PM7/13/17
to puppe...@googlegroups.com
Bernhard Schmidt assigned an issue to Jeremy Barlow
Change By: Bernhard Schmidt
Assignee: Erik Dasher Jeremy Barlow

Karen Van der Veer (JIRA)

unread,
Jul 13, 2017, 5:16:02 PM7/13/17
to puppe...@googlegroups.com
Karen Van der Veer updated an issue
Change By: Karen Van der Veer
Component/s: Server
Component/s: Puppet Server

Jeremy Barlow (JIRA)

unread,
Jul 13, 2017, 5:17:02 PM7/13/17
to puppe...@googlegroups.com
Jeremy Barlow assigned an issue to Unassigned
Change By: Jeremy Barlow
Assignee: Jeremy Barlow

Karen Van der Veer (JIRA)

unread,
Jul 13, 2017, 5:19:02 PM7/13/17
to puppe...@googlegroups.com

Josh Cooper (JIRA)

unread,
Jul 14, 2017, 2:09:02 AM7/14/17
to puppe...@googlegroups.com
Josh Cooper commented on Bug PUP-7777
 
Re: Append "source_permissions=use" to 3.x file_metadata requests

This is an issue because the default value of source_permissions changed between 3.x and 4.0.

Josh Cooper (JIRA)

unread,
Oct 1, 2019, 12:49:03 AM10/1/19
to puppe...@googlegroups.com
Josh Cooper updated an issue
 
Change By: Josh Cooper
Team: Coremunity
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Josh Cooper (Jira)

unread,
May 4, 2020, 11:34:03 PM5/4/20
to puppe...@googlegroups.com
Josh Cooper commented on Bug PUP-7777
 
Re: Append "source_permissions=use" to 3.x file_metadata requests

Puppet 3 and 4 are EOL, closing as won't fix

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages