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

2017-07-13 Thread Bernhard Schmidt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bernhard Schmidt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP- 
 
 
 
  Append "source_permissions=use" to 3.x file_metadata requests  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bernhard Schmidt 
 
 
 
 
 
 
 
 
 
 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/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

2017-07-13 Thread Bernhard Schmidt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bernhard Schmidt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP- 
 
 
 
  Append "source_permissions=use" to 3.x file_metadata requests  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bernhard Schmidt 
 
 
 

Sub-team:
 
 emerald 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


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

2017-07-13 Thread Bernhard Schmidt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bernhard Schmidt assigned an issue to Jeremy Barlow 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP- 
 
 
 
  Append "source_permissions=use" to 3.x file_metadata requests  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bernhard Schmidt 
 
 
 

Assignee:
 
 Erik Dasher Jeremy Barlow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


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

2017-07-13 Thread Bernhard Schmidt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bernhard Schmidt moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP- 
 
 
 
  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  
 
 
 

Project:
 
 Puppet  Server 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 


Jira (PUP-2023) Debian/Ubuntu service provider improvements

2014-03-24 Thread Bernhard Schmidt (JIRA)
Title: Message Title










 

 Bernhard Schmidt created an issue


















 Puppet /  PUP-2023



  Debian/Ubuntu service provider improvements 










Issue Type:

  Improvement




Affects Versions:


 3.4.3




Assignee:

 Kylo Ginsberg




Components:


 Types and Providers




Created:


 24/Mar/14 9:00 AM




Priority:

  Normal




Reporter:

 Bernhard Schmidt










Currently on Debian the debian service provider is selected, which uses standard SysV /etc/init/* for start/stop and update-rc.d to enable/disable services. 
The Debian CTTE has decided in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727708#6734 that the default init implementation for Jessie (Debian 8.0) on Linux platforms is going to be systemd. At the same time at least sysvinit, upstart and openrc are going to be available for users to choose.
This will also affect Ubuntu in the long run, since Marc Shuttleworth has announced Ubuntu switching to SystemD as well, which will most likely have a transition period too.
The systemd supports most Debian packages being controlled by /etc/init.d/* (using redirection functions) it is definitely not the recommended way and will spectacularly fail for services that do not have a standard init script anymore.
I don't have a good and tested solution for that. Hardcoding Debian 8.0 to systemd will also break things. I can think of two options: