date:20140918

Jira (PUP-3301) concat type/provider broken since 3.7.1

2014-09-18 Thread Andreas Roth (JIRA)

Title: Message Title










 

 Andreas Roth created an issue


















 Puppet /  PUP-3301



  concat type/provider broken since 3.7.1 










Issue Type:

  Bug




Affects Versions:


 3.7.1




Assignee:

 Kylo Ginsberg




Components:


 Types and Providers




Created:


 18/Sep/14 12:39 AM




Environment:


(K)Ubuntu 14.04 AMD64 with latest updates, ruby 1.9.3p484




Priority:

  Normal




Reporter:

 Andreas Roth










I set up a GIT repository at https://github.com/aroth-arsoft/puppet-type-concat with my concat type+provider.
When i'm running the run_concat_test script using puppet version 3.7.0 (or before) the script creates two files: /tmp/concat_test2 which contains concat1 concat2 concat3
and /tmp/concat_test_redir  concat1 concat2 concat2_1 concat2_1_1 concat2_1_2 concat2_1_3 uptime=1:01 hours concat2_3a concat2_3b concat3
If i run the same script with puppet 3.7.1 the /tmp/concat_test_redir file is empty and the /tmp/concat_test2 is correct.

Jira (PDB-881) Resources endpoint should include defined type resources

2014-09-18 Thread Kenneth Barber (JIRA)

Title: Message Title










 

 Kenneth Barber commented on an issue


















  Re: Resources endpoint should include defined type resources 










Puppet would need to expose this first in the catalog. I'm presuming this ticket would be a noop of they did that as we'll just gladly accept the resource, however it would need some more design thought.












   

 Add Comment

























 PuppetDB /  PDB-881



  Resources endpoint should include defined type resources 







 Much like resources.txt (https://tickets.puppetlabs.com/browse/PUP-1102) PuppetDB's Resources endpoint should include defined type resources.   If anyone would find the time to include this, that'd be great.















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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-3302) Puppet resource broken when directory environments enabled

2014-09-18 Thread Chris Spence (JIRA)

Title: Message Title

Chris Spence created an issue

Puppet / PUP-3302

Puppet resource broken when directory environments enabled

Issue Type:

Bug

Affects Versions:

3.7.1

Assignee:

Unassigned

Created:

18/Sep/14 6:15 AM

Priority:

Normal

Reporter:

Chris Spence

puppet resource file /usr/share/puppet-dashboard-mirror ensure=directory source=/usr/share/puppet-dashboard recurse=true ignore='*/log/' Error: /File[/usr/share/puppet-dashboard-mirror]: Failed to generate additional resources using 'eval_generate': Could not find a directory environment named 'none' anywhere in the path: /platform/puppet/environment. Does the directory exist? Error: /File[/usr/share/puppet-dashboard-mirror]: Could not evaluate: Could not retrieve file metadata for file:/usr/share/puppet-dashboard: Could not find a directory environment named 'none' anywhere in the path: /platform/puppet/environment. Does the directory exist? Wrapped exception: Could not find a directory environment named 'none' anywhere in the path: /platform/puppet/environment. Does the directory exist? Error: Could not run: Could not retrieve file metadata for file:/usr/share/puppet-dashboard: Could not find a directory environment named 'none' anywhere in the path: /platform/puppet/environment. Does the directory exist? Wrapped exception: Could not find a directory environment named 'none' anywhere in the path: /platform/puppet/environment. Does the directory exist?

Jira (PUP-1199) Puppet should be able to manage files that are set to immutable

2014-09-18 Thread Julien Pivotto (JIRA)

Title: Message Title










 

 Julien Pivotto commented on an issue


















  Re: Puppet should be able to manage files that are set to immutable 










garrett honeycutt I do not agree. If I set a immutable flag, then I expect that puppet is not able to modify the file. This should of course never happen but sometimes it is an easy way to modify a file, then ensure the catalog is failing so you remember that you need to fix it.












   

 Add Comment

























 Puppet /  PUP-1199



  Puppet should be able to manage files that are set to immutable 







 Puppet should be able to override files it manages that are made immutable with chattr/chflags, perhaps by updating the File resource and determining what environment it's being run on.















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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-3302) Puppet resource broken when directory environments enabled

2014-09-18 Thread Chris Spence (JIRA)

Title: Message Title










 

 Chris Spence updated an issue


















 Puppet /  PUP-3302



  Puppet resource broken when directory environments enabled 










Change By:

 Chris Spence









 # Whenrunning puppetresource ,thecommandfailsforwantofa'none'environment{quote}puppetresource file/usr/share/puppet-dashboard-mirrorensure=directorysource=/usr/share/puppet-dashboardrecurse=trueignore='* */ log / *'Error:/File[/usr/share/puppet-dashboard-mirror]:Failedtogenerateadditionalresourcesusing'eval_generate':Couldnotfindadirectoryenvironmentnamed'none'anywhereinthepath:/platform/puppet/environment.Doesthedirectoryexist?Error:/File[/usr/share/puppet-dashboard-mirror]:Couldnotevaluate:Couldnotretrievefilemetadataforfile:/usr/share/puppet-dashboard:Couldnotfindadirectoryenvironmentnamed'none'anywhereinthepath:/platform/puppet/environment.Doesthedirectoryexist?Wrappedexception:Couldnotfindadirectoryenvironmentnamed'none'anywhereinthepath:/platform/puppet/environment.Doesthedirectoryexist?Error:Couldnotrun:Couldnotretrievefilemetadataforfile:/usr/share/puppet-dashboard:Couldnotfindadirectoryenvironmentnamed'none'anywhereinthepath:/platform/puppet/environment.Doesthedirectoryexist?Wrappedexception:Couldnotfindadirectoryenvironmentnamed'none'anywhereinthepath:/platform/puppet/environment.Doesthedirectoryexist? {quote}Notealso-whenalargenumberofdirectoryenvironmentsexist,thevalid_directoriesroutinein/usr/lib/ruby/site_ruby/1.8/puppet/environments.rbtakesalotoftimetostattheenvironmentdirectoryandworkoutwhetherallthedirectoriesarevalid(Icurrentlyhave224environmentsandthedelaybetweene.g.apuppetagent-t--debugandthecommandevenstartingtodisplaydebugoutputissomethinglike10s(ymmvdependingonIOetc)












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (PUP-1199) Puppet should be able to manage files that are set to immutable

2014-09-18 Thread garrett honeycutt (JIRA)

Title: Message Title










 

 garrett honeycutt commented on an issue


















  Re: Puppet should be able to manage files that are set to immutable 










Julien, I understand your use case, though if Puppet was able to manage the immutability flag, nothing would change for you unless you specifically used it in your code.












   

 Add Comment

























 Puppet /  PUP-1199



  Puppet should be able to manage files that are set to immutable 







 Puppet should be able to override files it manages that are made immutable with chattr/chflags, perhaps by updating the File resource and determining what environment it's being run on.















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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-882) Build a performance testing CI solution using something like Gatling

2014-09-18 Thread Kenneth Barber (JIRA)

Title: Message Title










 

 Kenneth Barber created an issue


















 PuppetDB /  PDB-882



  Build a performance testing CI solution using something like Gatling 










Issue Type:

  Improvement




Assignee:


 Unassigned




Created:


 18/Sep/14 8:49 AM




Priority:

  Normal




Reporter:

 Kenneth Barber










Chris Price has already cut a lot of ground on this, we should implement a similar solution to start to build up our performance related CI story.
The initial work should be in building up the environment, and running the most basic of perf test to begin with. Later we can build up our library of tests, but the build work is the hardest hill to climb for now.












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (PUP-3277) Fix up PE Puppet Acceptance Tests

2014-09-18 Thread Joshua Partlow (JIRA)

Title: Message Title










 

 Joshua Partlow assigned an issue to Joshua Partlow


















 Puppet /  PUP-3277



  Fix up PE Puppet Acceptance Tests 










Change By:

 Joshua Partlow




Assignee:

 JoshuaPartlow












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 107 matches

Mail list logo