date:20150610

Jira (PUP-1827) Permission denied when installing modules on Windows

2015-06-10 Thread Chris Nappin (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Nappin commented on  PUP-1827 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Permission denied when installing modules on Windows  
 
 
 
 
 
 
 
 
 
 
Hi, 
 I just wanted to add that I think I've just hit this issue with Puppet 3.8.1. I'm attempting to install Puppet Forge modules to a shared vagrant source directory, as a solution to installing Puppet Modules without setting up a full Puppet Master or Ruby development environment. I'm using: 
 

Windows 7 (host)
 

Vagrant 1.7.2
 

Windows 2008 R2 (guest - the joshbeard/windows_2008_r2 base box)
 

Puppet 3.8.1 (.msi installed directly on the guest VM)
 
 
I'm opening PowerShell as Administrator, then running: 
puppet module install puppetlabs-windows --modulepath C:\vagrant\provision\modules 
The output is as follows: 
 
 
 
 
 
 
PS C:\vagrant\provision\modules puppet module install puppetlabs-windows --modulepath C:\vagrant\provision\modules 
 
 
 
 
Notice: Preparing to install into C:/vagrant/provision/modules ... 
 
 
 
 
Notice: Downloading from https://forgeapi.puppetlabs.com ... 
 
 
 
 
Failed to add /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Root Certificate Authority 2011 
 
 
 
 
Failed to add /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Root Certificate Authority 2011

Jira (PDB-1531) Upgrade to tk-metrics

2015-06-10 Thread Ryan Senior (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1531 
 
 
 
  Upgrade to tk-metrics  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Sprint:
 
 PuppetDB2015-07-01 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDB-1530) Upgrade to latest clojure.java.jdbc

2015-06-10 Thread Ryan Senior (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1530 
 
 
 
  Upgrade to latest clojure.java.jdbc  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Sprint:
 
 PuppetDB2015-07-01 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDB-7) investigate moving puppetdb acceptance testing to use vsphere

2015-06-10 Thread Ryan Senior (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-7 
 
 
 
  investigate moving puppetdb acceptance testing to use vsphere  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Sprint:
 
 PuppetDB2015-07- 01 15 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDB-1601) benchmark tool should send only one catalog/factset per node in untimed mode

2015-06-10 Thread Ryan Senior (JIRA)

Title: Message Title

Ryan Senior commented on PDB-1601

Re: benchmark tool should send only one catalog/factset per node in untimed mode

Wyatt Alt AJ Roetker We can chat about this, but what you're describing as wasted data, since it's overridden by a subsequent message, was totally the intent of the feature. The tool was originally for benchmarking/load testing real load (or close to it). This specific feature was to help answer the question, how long does it take PuppetDB to consume 10,000 commands. Prior to that, benchmark only let you run for a specific duration, which is difficult to compare apples to apples.
I understand what you're looking for though. We've begun to use the benchmark tool to load test data, and if your only goal is to get some dummy data in a database, it is a waste. Could you just pass in -N 1 to get the behavior you want without removing the current behavior?

Add Comment

This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDB-1605) puppet query to puppetdb fails on invalid cache + missing data

2015-06-10 Thread Kenneth Barber (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber commented on  PDB-1605 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: puppet query to puppetdb fails on invalid cache + missing data  
 
 
 
 
 
 
 
 
 
 
404 responses are kind of normal but this time they indicate a smell ... I think what is abnormal is that the Puppet master is even making a request to PuppetDB in the absence of a file - the workflow should be that it's received the original facts via the catalog POST submission (which returns a catalog in exchange for facts) and it uses them straight away from the cache. Thats the problem that we need to be concerned about, and it's not a PDB problem I think. 
In particular there is an edge case here - when PDB has old data, and the master fact cache is removed - this means potentially the first puppet run would be using PDB as a source of truth for facts ... however I can't reproduce this effect at all. The new facts seem to work, and it ignores the call to PDB. The erroneous call to PDB seems to be for no purpose, and may have no side-effect after all. More weight to add to the fact that it shouldn't be occurring at all, especially if the data is ignored. 
FWIW, I cannot reproduce this with 4.1.0, when deleting its fact cache file: ```rm ~/.puppetlabs/opt/puppet/cache/yaml/facts/kb.local.yaml```. I'm not sure then it matters to chase this particular erroneous call concern too much, short from proving it has no bad side-effects to data integrity, since a later version of Puppet has this solved. One could always bisect and backport a fix (if its a clean patch) to 3.x I guess. I think perhaps the bigger story was that there was always a workflow issue of some kind, and it's now solved potentially, but I have no idea if this was intentional or accidental . 
As far as reducing the level of the 404 calls, there is one issue I would consider - they sometimes indicate startup delays. A 404 can be a missing piece of data, or the fact that PuppetDB hasn't fully started. Unfortunately we really should return 503's for apps 'still starting' ideally (or maybe use that new status endpoint, but thats 2 hits and racy). Sometimes a 404 also indicates you're pointing at the wrong web service, although thats a little rarer. One difference however, is that a 404 on missing data does return a JSON response, we could inspect that to delineate. 
In normal usage, the only time we ever call PuppetDB in the terminus (outside of resource collection) is going to be when users are using the inventory service or indirector REST service, normally called via 'puppet facts find --terminus rest kb.local' (and the like). In that case 404's do return a warning on the master, but no data on the client. So outside of this weird bug/anomaly, that's the other place we expect to see this 404 warning in particular under 'normalish' conditions. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (PDB-1607) PR (186): Release 4.3.0 of module - kbarber

2015-06-10 Thread gepetto-bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1607 
 
 
 
  PR (186): Release 4.3.0 of module - kbarber  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/06/10 6:51 AM 
 
 
 

Labels:
 

 github module 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
Release 4.3.0 of module 
 

Author: Ken Barber k...@bob.sh
 

Company: Puppet Labs Inc.
 

Github ID: kbarber
 

Pull Request 186 Discussion
 

Pull Request 186 File Diff
 
 
Pull Request Description 
 
This updates the CHANGELOG and the metadata.json ready for a new release. 
Signed-off-by: Ken Barber k...@bob.sh 
 
(webhooks-id:

Jira (PUP-1827) Permission denied when installing modules on Windows

2015-06-10 Thread Rob Reynolds (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Reynolds commented on  PUP-1827 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Permission denied when installing modules on Windows  
 
 
 
 
 
 
 
 
 
 
Chris Nappin can you run icacls on the two folders and post your output here? I'm guessing the modulepath you are attempting to use is a shared folder from your host operating system, so it doesn't understand the permissions. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDB-1607) PR (186): Release 4.3.0 of module - kbarber

2015-06-10 Thread gepetto-bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1607 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (186): Release 4.3.0 of module - kbarber  
 
 
 
 
 
 
 
 
 
 
kbarber commented: 
Blocked on PR-135 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDB-1607) PR (186): Release 4.3.0 of module - kbarber

2015-06-10 Thread Kenneth Barber (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber assigned an issue to Kenneth Barber 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1607 
 
 
 
  PR (186): Release 4.3.0 of module - kbarber  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Assignee:
 
 KennethBarber 
 
 
 

Sprint:
 
 PuppetDB2015-06-17 
 
 
 

Story Points:
 
 1 
 
 
 

Scope Change Reason:
 
 BlocksworkonPDB-1455 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 

Fix Version/s:
 
 PDBmodule-4.3.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

Jira (PDB-1523) Update puppetlabs-puppetdb module (master branch) with AIO changes

2015-06-10 Thread Kenneth Barber (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1523 
 
 
 
  Update puppetlabs-puppetdb module (master branch) with AIO changes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Summary:
 
 Updatepuppetlabs-puppetdbmodule (masterbranch) withAIOchanges 
 
 
 
 
 
 
 
 
 
 OncewehaveupdatedtothelatestEZBake(PDB-1455)thePuppetDBmodulewillnolongerwork bydefault,therelease5 . 0.0howevershouldwork. Thisticketcoverstheworktoupdatethemoduletosupportthenewpaths andchoicesbydefault (wheninanAIOsetup).  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-4386) Windows Group resource reports errors incorrectly when specifying an invalid group member

2015-06-10 Thread Ethan Brown (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown commented on  PUP-4386 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Windows Group resource reports errors incorrectly when specifying an invalid group member  
 
 
 
 
 
 
 
 
 
 
There are two separate approaches up for review. 
4010 - throws an exception in the Windows group provider that the corresponding type must catch 4024 - performs validation on values if the provider has a member_valid? method available 
Both have to implement some sanity checking is the types is_to_s given that can be called from the resource_harness message building - https://github.com/puppetlabs/puppet/blob/stable/lib/puppet/transaction/resource_harness.rb#L147 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDB-1606) PR (1445): (maint) Update fs to 1.4.5, matching kitchensink - rbrw

2015-06-10 Thread Kenneth Barber (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1606 
 
 
 
  PR (1445): (maint) Update fs to 1.4.5, matching kitchensink - rbrw  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Sprint:
 
 PuppetDB2015-06-17 
 
 
 

Story Points:
 
 1 
 
 
 

Scope Change Reason:
 
 Noticedthatwewererunningoldversioncomparedtokitchensink,minormaintonly 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 

Fix Version/s:
 
 PDB3.0.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google

Jira (PUP-3774) puppet fails to manipulate user's group membership if group name has space in it

2015-06-10 Thread Kylo Ginsberg (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3774 
 
 
 
  puppet fails to manipulate user's group membership if group name has space in it  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Fix Version/s:
 
 PUP4.2.0 
 
 
 

Fix Version/s:
 
 PUP4.3.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

1 2 >

1 - 100 of 161 matches

Mail list logo