Jira (PUP-2922) Acceptance test is using an invalid regex

2015-03-31 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-2922 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Acceptance test is using an invalid regex  
 
 
 
 
 
 
 
 
 
 
I retested it too and did not see the issue... closing 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-408) Puppet package acceptance is sufficient for a smoke test

2015-03-31 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-408 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet package acceptance is sufficient for a smoke test  
 
 
 
 
 
 
 
 
 
 
 
The ability to test the msi packages on vcloud windows templates A Beaker that uses the service scripts for starting and stopping puppet master
 
These are covered in current CI 
 
A test that checks puppet agent service scripts?
 
This is not tested to the best of my knowledge, but should be. 
 
An acceptance test for puppetmaster-passenger on Debian
 
We added that at some point to the old pipelines, and should be handled in PUP-4234 (so that we're running all acceptance tests against passenger) 
 
Man tests for puppet and facter
 
So puppet's main man page has been broken for awhile, see PUP-3251. We should really fix that, and add an acceptance test to verify. 
In summary, I think the only thing that is missing and isn't ticketed is the agent service scripts. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-408) Puppet package acceptance is sufficient for a smoke test

2015-03-31 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper assigned an issue to Kurt Wall 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-408 
 
 
 
  Puppet package acceptance is sufficient for a smoke test  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Assignee:
 
 Josh Cooper Kurt Wall 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4237) Add puppet_gem provider for managing puppet-agent gems

2015-03-31 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-4237 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add puppet_gem provider for managing puppet-agent gems  
 
 
 
 
 
 
 
 
 
 
This caused spec failures on Windows https://jenkins.puppetlabs.com/view/Puppet/view/Stable/job/Puppet-Specs-Windows-stable/631/ 
 
 
 
 
 
 
C:\work\puppet [stable +4 ~0 -0 !]> bundle exec rspec .\spec\integration\provider\package_spec.rb 
 
 
 
 
Run options: exclude {:broken=>true, :benchmark=>true} 
 
 
 
 
.F.. 
 
 
 
 
  
 
 
 
 
Failures: 
 
 
 
 
  
 
 
 
 
  1) Package provider puppet_gem should be able to get a list of existing packages 
 
 
 
 
 Failure/Error: expect(package.properties[:provider]).to eq(provider.name) 
 
 
 
 
  
 
 
 
 
   expected: :puppet_gem 
 
 
 

Jira (PDB-1362) puppetdb crashes after upgrade

2015-03-31 Thread Pete Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pete Brown commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
Just letting you know I upgraded PuppetDB on my live server and it worked without a hitch. 
It seems to have been suffering from the memory bloat that 2.3.1 fixed. Thanks for that.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1362) puppetdb crashes after upgrade

2015-03-31 Thread Pete Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pete Brown commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
Sorry missed you last comment. Here is the curl request 
root@puppet:~# curl -X GET http://localhost:8080/v4/facts/pip_version [  { "value" : "1.5.4", "name" : "pip_version", "environment" : "development", "certname" : "puppet.pivit.net.au" } 
,  { "value" : false, "name" : "pip_version", "environment" : "development", "certname" : "dhcp.pivit.net.au" } 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1362) puppetdb crashes after upgrade

2015-03-31 Thread Pete Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pete Brown commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
I booted up my puppetmaster and it didn't have a duplicate fact for pip_version I was running a couple of other nodes last time so I have booted up a test dhcp server and it added the extra pip_version fact. 
While I have it running is there anything else you would like me to check? 
Results from the queries. puppetdb=# select * from fact_paths where path='pip_version'; id | value_type_id | depth | name | path 


-
-


---
 98 | 0 | 0 | pip_version | pip_version 180 | 3 | 0 | pip_version | pip_version (2 rows) 
puppetdb=# select * from value_types; id | type ---

+
 0 | string 1 | integer 2 | float 3 | boolean 4 | null 5 | json (6 rows) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1362) puppetdb crashes after upgrade

2015-03-31 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
The output of curl -X GET http://localhost:8080/v4/facts/pip_version 
would also show the different types if you manage to replicate the problem on your dev environment. 
As for your live puppet master (production I assume) attempting an upgrade will be safe since the migrations take place within a transaction, and assuming I understand the problem, the fact that 
 
 
 
 
 
 
 select path,count(1) from fact_paths group by path having count(1) > 1;
 
 
 
 
 
 
 
 returns nothing means the migration should succeed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1362) puppetdb crashes after upgrade

2015-03-31 Thread Pete Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pete Brown commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
Just booting it up now. 
I ran those queries on my live puppet master and it seems like it doesn't have any duplicates. Can I assume from that it would be safe to upgrade it to latest PuppetDB? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1362) puppetdb crashes after upgrade

2015-03-31 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
Pete Brown If it weren't too much trouble that would certainly help confirm. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4330) Remove Puppet dependency on facter/util/plist.

2015-03-31 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-4330 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Remove Puppet dependency on facter/util/plist.  
 
 
 
 
 
 
 
 
 
 
Michael Smith  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1363) Puppetdb broken because of forced check for tables in public schema

2015-03-31 Thread Chuck Schweizer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chuck Schweizer commented on  PDB-1363 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppetdb broken because of forced check for tables in public schema  
 
 
 
 
 
 
 
 
 
 
Postgres Error 
 
 
 
 
 
 
2015-03-31 22:50:37 UTC|puppetdb|39489|CREATE TABLE|10.0.0.50|puppet ERROR:  relation "certnames" already exists 
 
 
 
 
2015-03-31 22:50:37 UTC|puppetdb|39489|CREATE TABLE|10.0.0.50|puppet STATEMENT:  CREATE TABLE certnames (name TEXT PRIMARY KEY)
 
 
 
 
 
 
 
PuppetDB Error 
 
 
 
 
 
 
2015-03-31 22:39:57,606 INFO  [c.p.p.s.migrate] Applying database migration version 1 
 
 
 
 
2015-03-31 22:39:57,622 ERROR [c.p.p.s.migrate] Caught SQLException during migration 
 
 
 
 
java.sql.BatchUpdateException: Batch entry 0 CREATE TABLE certnames (name TEXT PRIMARY KEY) was aborted.  Call getNextException to see the cause. 
 
 
 
 
at org.postgresql.jdbc2.AbstractJdbc2Statement$BatchResultHandler.handleError(AbstractJdbc2Statement.java:2746) ~[puppetdb.jar:na]
 
 
 
 
 
 
 
PuppetDB debug 
 
 
 
 
 
 

Jira (PDB-1363) Puppetdb broken because of forced check for tables in public schema

2015-03-31 Thread Chuck Schweizer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chuck Schweizer commented on  PDB-1363 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppetdb broken because of forced check for tables in public schema  
 
 
 
 
 
 
 
 
 
 
Sorry should have been a little more specific. The change makes it so that only the public schema is searched for existing puppetdb tables. The end result in my environment is that puppetdb always tries to create the tables since they don't exist in the public schema and then fails to create them because they already exist.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-893) CentOS 7.1.1503 breaks /etc/redhat-release

2015-03-31 Thread Steven Merrill (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Merrill commented on  FACT-893 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: CentOS 7.1.1503 breaks /etc/redhat-release  
 
 
 
 
 
 
 
 
 
 
Looks like this is also being fixed upstream with a small patch that will be pushed out via yum: http://lists.centos.org/pipermail/centos-announce/2015-April/021010.html. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1364) Address 2.3.1 release failure / Release 2.3.2

2015-03-31 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1364 
 
 
 
  Address 2.3.1 release failure / Release 2.3.2  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 The 2.3.1 release has two issues that need to be corrected for a 2.3.2 ASAP. Before addressing the following, we will need to revert or otherwise address the commits that went into stable today (Tuesday.)* (PDB-1362)Pete Brown reported a failure when migration was attempted with a fact path string associated with multiple types. In his case he had nodes with facts pip_version of different types (may int and string). This seems likely to occur on infrastructures with a mix of facter versions. We have replicated it and it is addressed by [~rob.browning]'s PR here:https://github.com/puppetlabs/puppetdb/pull/1332* ( PDB_1363 PDB-1363 ) Chuck Schweizer reported an issue with the check for the schema_migrations table:https://tickets.puppetlabs.com/browse/PDB-1363to address this we should probably revert the commit and deal with it in master if we want to. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1205) facts gc is too slow

2015-03-31 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-1205 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facts gc is too slow  
 
 
 
 
 
 
 
 
 
 
Chuck Schweizer Really appreciate you taking the time, that's a very valuable datapoint. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1362) puppetdb crashes after upgrade

2015-03-31 Thread Pete Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pete Brown commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
Dammit. 
I just destroyed and rebuilt my dev puppet server and used the new version of puppetdb. 
I can try and build it with the old version and see how it goes and let you know what I find. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1362) puppetdb crashes after upgrade

2015-03-31 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
the type ids can be correlated with the types in the output of 
select * from value_types; 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1362) puppetdb crashes after upgrade

2015-03-31 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
Pete Brown sorry, didn't see your comment before I posted mine. What does the query 
select * from fact_paths where path='pip_version'; 
return? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1362) puppetdb crashes after upgrade

2015-03-31 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
Alternatively, a module may be assigning null values on some nodes for facts that don't apply. I'd expect that to cause the same. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1362) puppetdb crashes after upgrade

2015-03-31 Thread Pete Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pete Brown commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
I use Vagrant for my development environment and I tend to destroy and rebuild it pretty regularly, sometimes every day. I also manage versions of facter with puppet so everything gets upgraded not long after new versions get rolled out. 
I do have two "environments" with stankevich-python installed (for puppetboard) but they are not used in separate environments and they are at the same version. 
Does that help? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1364) Address 2.3.1 release failure / Release 2.3.2

2015-03-31 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1364 
 
 
 
  Address 2.3.1 release failure / Release 2.3.2  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/03/31 7:16 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
The 2.3.1 release has two issues that need to be corrected for a 2.3.2 ASAP. Before addressing the following, we will need to revert or otherwise address the commits that went into stable today (Tuesday.) 
 

(PDB-1362)Pete Brown reported a failure when migration was attempted with a fact path string associated with multiple types. In his case he had nodes with facts pip_version of different types (may int and string). This seems likely to occur on infrastructures with a mix of facter versions. We have replicated it and it is addressed by Rob Browning's PR here: https://github.com/puppetlabs/puppetdb/pull/1332
 
 
 

(PDB_1363) Chuck Schweizer reported an issue with the check for the schema_migrations table: https://tickets.puppetlabs.com/browse/PDB-1363
 
 
to address this we should probably revert the commit and deal with it in master if we want to. 
 
 
 
 
 
 
 
 
 
 
 
  

Jira (PDB-1364) Address 2.3.1 release failure / Release 2.3.2

2015-03-31 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1364 
 
 
 
  Address 2.3.1 release failure / Release 2.3.2  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Sprint:
 
 PuppetDB 2015-04-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1363) Puppetdb broken because of forced check for tables in public schema

2015-03-31 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning commented on  PDB-1363 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppetdb broken because of forced check for tables in public schema  
 
 
 
 
 
 
 
 
 
 
Does it fail with an SQLException by any chance? And thanks for the report. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1362) puppetdb crashes after upgrade

2015-03-31 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
Pete Brown Yeah, new installs should be fine. 
My guess is the main risk is when migrating folks have a mix of facter versions across their infrastructure, or a mix of module versions where the module generates custom facts. Old versions of facter stringified all fact values, whereas new ones use more varied types. The same is true of modules, since only strings used to be supported. 
So for instance if you have puppetlabs-python from a year ago somewhere, in addition to one installed yesterday in another place, you could easily hit this issue with the pip_version fact. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (HI-14) Allow access to structured data

2015-03-31 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  HI-14 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow access to structured data  
 
 
 
 
 
 
 
 
 
 
This: https://github.com/puppetlabs/pre-docs/pull/34/files (a single documentation file) and this https://github.com/puppetlabs/hiera/pull/231/files (the README.md) describes the features. It would be good to update this ticket's description as well so that the description is more easily found. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1362) puppetdb crashes after upgrade

2015-03-31 Thread Pete Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pete Brown commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
Awesome! Thanks Wyatt Alt! Happy to help. 
I am going to guess this won't affect new installs? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1362) puppetdb crashes after upgrade

2015-03-31 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
Pete Brown yep, I think that's the issue. We've got a fix up for review here: https://github.com/puppetlabs/puppetdb/pull/1332, and we'll get it out in a new release in the next day or two. Thanks again for the quick report and debugging assistance. 
Wyatt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4330) Remove Puppet dependency on facter/util/plist.

2015-03-31 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  PUP-4330 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Remove Puppet dependency on facter/util/plist.  
 
 
 
 
 
 
 
 
 
 
Josh, did you have anything more on this? Kylo thumbsed up it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4330) Remove Puppet dependency on facter/util/plist.

2015-03-31 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley assigned an issue to QA 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4330 
 
 
 
  Remove Puppet dependency on facter/util/plist.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Status:
 
 Ready for  Merge  Test 
 
 
 

Assignee:
 
 Josh Cooper QA 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4231) File resources with defined content don't output contents with ensure=>present

2015-03-31 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  PUP-4231 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: File resources with defined content don't output contents with ensure=>present  
 
 
 
 
 
 
 
 
 
 
I plan to write spec tests, similar to https://github.com/puppetlabs/puppet/pull/3752, to cover ensure => :present. Currently none exist. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4231) File resources with defined content don't output contents with ensure=>present

2015-03-31 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith assigned an issue to Michael Smith 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4231 
 
 
 
  File resources with defined content don't output contents with ensure=>present  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Assignee:
 
 Michael Smith 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1362) puppetdb crashes after upgrade

2015-03-31 Thread Pete Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pete Brown commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
Looks like pip_version is culprit 
puppetdb=# select path,count(1) from fact_paths group by path having count(1) > 1; path | count 

+
-- pip_version | 2 (1 row) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-927) puppet apply on Windows always uses *nix style newlines from templates

2015-03-31 Thread Rob Reynolds (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Reynolds updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-927 
 
 
 
  puppet apply on Windows always uses *nix style newlines from templates  
 
 
 
 
 
 
 
 
 
 
Master? 
On Tuesday, March 31, 2015, Ethan Brown (JIRA)  
–  Rob Reynolds Developer, Puppet Labs 
*PuppetConf 2015  is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount  * --save $349! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-927) puppet apply on Windows always uses *nix style newlines from templates

2015-03-31 Thread Rob Reynolds (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Reynolds updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-927 
 
 
 
  puppet apply on Windows always uses *nix style newlines from templates  
 
 
 
 
 
 
 
 
 
 
Master? 
On Tuesday, March 31, 2015, Ethan Brown (JIRA)  
–  Rob Reynolds Developer, Puppet Labs 
*PuppetConf 2015  is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount  * --save $349! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-927) puppet apply on Windows always uses *nix style newlines from templates

2015-03-31 Thread Rob Reynolds (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Reynolds updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-927 
 
 
 
  puppet apply on Windows always uses *nix style newlines from templates  
 
 
 
 
 
 
 
 
 
 
Master? 
On Tuesday, March 31, 2015, Ethan Brown (JIRA)  
–  Rob Reynolds Developer, Puppet Labs 
*PuppetConf 2015  is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount  * --save $349! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1362) puppetdb crashes after upgrade

2015-03-31 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
@Pete Brown I just used that id because it's the one in the stack trace. It looks like it's no longer applicable though.  
We've managed to replicate your error message by having two facts on different hosts with the same name but different types. 
Could you check if that's your case using this query? 
select path,count(1) from fact_paths group by path having count(1) > 1; 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-894) Prepend ~/.puppetlabs/opt/facter/facts.d to external search path for non-root

2015-03-31 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  FACT-894 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Prepend ~/.puppetlabs/opt/facter/facts.d to external search path for non-root  
 
 
 
 
 
 
 
 
 
 
Can't update this for cfacter (on Windows) due to CFACT-272. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4196) agent command line options ignored running under systemd

2015-03-31 Thread Melissa Stone (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Melissa Stone updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4196 
 
 
 
  agent command line options ignored running under systemd  
 
 
 
 
 
 
 
 
 

Change By:
 
 Melissa Stone 
 
 
 

Sprint:
 
 RE 2015-04-22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4196) agent command line options ignored running under systemd

2015-03-31 Thread Melissa Stone (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Melissa Stone updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4196 
 
 
 
  agent command line options ignored running under systemd  
 
 
 
 
 
 
 
 
 

Change By:
 
 Melissa Stone 
 
 
 

Story Points:
 
 5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-894) Prepend ~/.puppetlabs/opt/facter/facts.d to external search path for non-root

2015-03-31 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  FACT-894 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Prepend ~/.puppetlabs/opt/facter/facts.d to external search path for non-root  
 
 
 
 
 
 
 
 
 
 
Also going to put up a PR against cfacter. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-96) Deprecate 'facter --puppet'

2015-03-31 Thread Nicholas Fagerlund (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicholas Fagerlund commented on  FACT-96 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Deprecate 'facter --puppet'  
 
 
 
 
 
 
 
 
 
 
Kylo Ginsberg ...no, I don't think so. Come to think of it, I don't think we document the command line tool at all on the website. (!?!?!!?) 
But! If you run facter --help on the cli, you'll get help text. And that help text lists the --puppet option WITHOUT any mention of its deprecation. That documentation lives in lib/facter/application.rb.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4241) Acceptance test for Puppet Preview

2015-03-31 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson commented on  PUP-4241 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Acceptance test for Puppet Preview  
 
 
 
 
 
 
 
 
 
 
Hailee Kenney henrik reminded me we should test that the output diff files are created. i can take another look at this in the am. 
i think we should also add at least one test where --migrate is not used to see if preview still works, this was a mini-regression yesterday and might not be adequately covered by units. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4231) File resources with defined content don't output contents with ensure=>present

2015-03-31 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4231 
 
 
 
  File resources with defined content don't output contents with ensure=>present  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Sprint:
 
 Client 2015-04-15 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 

Story Points:
 
 1 
 
 
 

Scope Change Reason:
 
 Community PR 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 fr

Jira (PUP-4231) File resources with defined content don't output contents with ensure=>present

2015-03-31 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4231 
 
 
 
  File resources with defined content don't output contents with ensure=>present  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Fix Version/s:
 
 PUP 4.1.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.


Jira (PDB-1362) puppetdb crashes after upgrade

2015-03-31 Thread Pete Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pete Brown commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
Here you go. Should they all be empty? 
puppetdb=# select 1 from facts where fact_value_id=452 limit 1; ?column? -- (0 rows) 
puppetdb=# select * from fact_values where id=452; id | path_id | value_type_id | value_hash | value_integer | value_float | value_string | value_boolean | value_json ---


---
-


--
-


---



-
--- (0 rows) 
puppetdb=# select * from fact_paths where id in (select path_id from fact_values where id=452); id | value_type_id | depth | name | path ---


-
-



- (0 rows) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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+u

Jira (PUP-4239) add acceptance for hash and array lookup()

2015-03-31 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4239 
 
 
 
  add acceptance for hash and array lookup()  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-927) puppet apply on Windows always uses *nix style newlines from templates

2015-03-31 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown commented on  PUP-927 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet apply on Windows always uses *nix style newlines from templates  
 
 
 
 
 
 
 
 
 
 
Merged to master in https://github.com/puppetlabs/puppet/commit/a7b5072437a0a30e067d16d86144a44b293b4d91 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1362) puppetdb crashes after upgrade

2015-03-31 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
Well, thanks for ruling that out anyway. Would you mind giving the outputs of the following queries? 
select 1 from facts where fact_value_id=452 limit 1; 
select * from fact_values where id=452, 
select * from fact_paths where id in (select path_id from fact_values where id=452); 
Thanks for the help. Wyatt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1205) facts gc is too slow

2015-03-31 Thread Chuck Schweizer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chuck Schweizer commented on  PDB-1205 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facts gc is too slow  
 
 
 
 
 
 
 
 
 
 
I manually fixed the schema issue in the JAR file and I can CONFIRM that the performance issue with fact replacement is fixed in my 38,000 node environment. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4355) Update per-user directories to ~/.puppetlabs

2015-03-31 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg assigned an issue to Kylo Ginsberg 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4355 
 
 
 
  Update per-user directories to ~/.puppetlabs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4361) Puppet 4 Language fixes/enhancements

2015-03-31 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4361 
 
 
 
  Puppet 4 Language fixes/enhancements  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Scrum Team:
 
 Language 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4361) Puppet 4 Language fixes/enhancements

2015-03-31 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4361 
 
 
 
  Puppet 4 Language fixes/enhancements  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Summary:
 
 This is a catch-all for bug Puppet 4 Language  fixes/enhancements  that arise from Puppet 4 Parser changes 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4361) This is a catch-all for bug fixes/enhancements that arise from Puppet 4 Parser changes

2015-03-31 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4361 
 
 
 
  This is a catch-all for bug fixes/enhancements that arise from Puppet 4 Parser changes  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Epic 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/03/31 4:48 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Steve Barlow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

Jira (PDB-1362) puppetdb crashes after upgrade

2015-03-31 Thread Pete Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pete Brown commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
On a side note I was able to downgrade to 2.3.0 and it works again. 
I ran these two queries delete from fact_values where id not in (select distinct fact_value_id from facts); delete from fact_paths where id not in (select path_id from fact_values); and started up puppetdb but it's still not starting 
These are the errors I got in the logs this time 
2015-04-01 09:35:21,808 INFO [c.p.p.c.services] PuppetDB version 2.3.1 2015-04-01 09:35:21,956 INFO [c.p.p.s.migrate] Applying database migration version 28 2015-04-01 09:35:21,988 ERROR [c.p.p.s.migrate] Caught SQLException during migration java.sql.BatchUpdateException: Batch entry 5 DELETE FROM fact_paths t1 WHERE t1.id <> (SELECT MIN(t2.id) FROM fact_paths t2 WHERE t1.path = t2.path) was aborted. Call getNextException to see the cause. at org.postgresql.jdbc2.AbstractJdbc2Statement$BatchResultHandler.handleError(AbstractJdbc2Statement.java:2746) ~[puppetdb.jar:na] at org.postgresql.core.v3.QueryExecutorImpl$1.handleError(QueryExecutorImpl.java:457) ~[puppetdb.jar:na] at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1887) ~[puppetdb.jar:na] at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:405) ~[puppetdb.jar:na] at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2893) ~[puppetdb.jar:na] at com.jolbox.bonecp.StatementHandle.executeBatch(StatementHandle.java:469) ~[puppetdb.jar:na] at clojure.java.jdbc$do_commands$fn__7301.invoke(jdbc.clj:188) ~[na:na] at clojure.java.jdbc.internal$transaction_STAR_.invoke(internal.clj:223) [na:na] at clojure.java.jdbc$do_commands.doInvoke(jdbc.clj:187) ~[na:na] at clojure.lang.RestFn.invoke(RestFn.java:3894) [puppetdb.jar:na] at com.puppetlabs.puppetdb.scf.migrate$lift_fact_paths_into_facts.invoke(migrate.clj:968) ~[na:na] at com.puppetlabs.puppetdb.scf.migrate$migrate_BANG_$fn_20902$fn_20915.invoke(migrate.clj:1063) ~[na:na] at com.puppetlabs.puppetdb.scf.migrate$migrate_BANG_$fn__20902.invoke(migrate.clj:1062) [na:na] at clojure.java.jdbc.internal$transaction_STAR_.invoke(internal.clj:204) [na:na] at com.puppetlabs.puppetdb.scf.migrate$migrate_BANG_.invoke(migrate.clj:1059) [na:na] at com.puppetlabs.puppetdb.cli.services$start_puppetdb$fn__21109.invoke(services.clj:292) [na:na] at clojure.java.jdbc.internal$with_connection_STAR_.invoke(internal.clj:186) [na:na] at com.puppetlabs.puppetdb.cli.services$start_puppetdb.invoke(services.clj:290) [na:na] at com.puppetlabs.puppetdb.cli.services$reify_21157$service_fnk18232auto_positional$reify_21168.start(services.clj:366) [na:na] at puppetlabs.trapperkeeper.services$eval18068$fn_18082$G18058_18085.invoke(services.clj:10) [na:na] at puppetlabs.trapperkeeper.services$eval18068$fn_18082$G18057_18089.invoke(services.clj:10) [na:na] at puppetlabs.trapperkeeper.internal$run_lifecycle_fn_BANG_.invoke(internal.clj:154) [na:na] at puppetlabs.trapperkeeper.internal$run_lifecycle_fns.invoke(internal.clj:182) [na:na] at puppetlabs.trapperkeeper.internal$build_app_STAR_$reify__18905.start(internal.clj:449) [na:na] at puppetlabs.trapperkeeper.internal$boot_services_STAR_$fn__18917.invoke(internal.clj:473) [na:na] at puppetlabs.trapperkeeper.internal$boot_services_STAR_.invoke(internal.clj:471) [na:na] at puppetlabs.trapperkeeper.core$boot_with_cli_data.invoke(core.clj:113) [na:na] at puppetlabs.trapperkeeper.core$run.invoke(core.clj:144) [na:na] at puppetlabs.trapperkeeper.core$main.doInvoke(core.clj:159) [na:na] at clojure.lang.RestFn.applyTo(RestFn.java:137) [puppetdb.jar:na] at clojure.core$apply.invoke(core.clj:624) [puppetdb.jar:na] at com.puppetlabs.puppetdb.cli.services$_main.doInvoke(serv

Jira (PDB-1362) puppetdb crashes after upgrade

2015-03-31 Thread Pete Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pete Brown commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
Hi Wyatt. 
Damn. Sorry I forgot to add that. 
Operating system is Ubuntu 14.04, PostgresSQL version is 9.3. I manage my Dev environment with the same code as my live server and I just noticed postgresql-contrib wasn't installed and pg_trgm isn't setup on the puppetdb database. I added that and added the extension to the puppetdb database but upgrade still doesn't work. 
I shall try your suggested fix and let you know how it goes. 
PostgreSQL logs have this in it which seems pretty relevant. 2015-04-01 08:44:53 AEST ERROR: update or delete on table "fact_paths" violates foreign key constraint "fact_values_path_id_fk" on table "fact_values" 2015-04-01 08:44:53 AEST DETAIL: Key (id)=(452) is still referenced from table "fact_values". 2015-04-01 08:44:53 AEST STATEMENT: DELETE FROM fact_paths t1 WHERE t1.id <> (SELECT MIN(t2.id) FROM fact_paths t2 WHERE t1.path = t2.path) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1205) facts gc is too slow

2015-03-31 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-1205 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facts gc is too slow  
 
 
 
 
 
 
 
 
 
 
Chuck Schweizer yes, thanks for reporting that. We'll get a fix out as quick as we can. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1362) puppetdb crashes after upgrade

2015-03-31 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
@PeteBrown my guess is that running the following two queries on a 2.3.0 database will permit the upgrade: 
 
 
 
 
 
 
delete from fact_values where id not in (select distinct fact_value_id from facts); 
 
 
 
 
delete from fact_paths where id not in (select path_id from fact_values);
 
 
 
 
 
 
 
if you're up for trying it we'd be interested to know if it does the trick. Otherwise thanks for reporting this issue – we're on it and will keep you posted. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1205) facts gc is too slow

2015-03-31 Thread Chuck Schweizer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chuck Schweizer commented on  PDB-1205 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facts gc is too slow  
 
 
 
 
 
 
 
 
 
 
Wyatt Alt, Looks like puppetDB 2.3.1 breaks in my environment because we don't use the public schema. 
https://tickets.puppetlabs.com/browse/PDB-1363?jql=project%20%3D%20PDB 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1363) Puppetdb broken because of forced check for tables in public schema

2015-03-31 Thread Chuck Schweizer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chuck Schweizer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1363 
 
 
 
  Puppetdb broken because of forced check for tables in public schema  
 
 
 
 
 
 
 
 
 

Change By:
 
 Chuck Schweizer 
 
 
 

Summary:
 
 Puppetdb    broken because of forced check for tables in public schema 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1363) Puppetdb

2015-03-31 Thread Chuck Schweizer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chuck Schweizer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1363 
 
 
 
  Puppetdb   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PDB 2.3.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/03/31 4:19 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Chuck Schweizer 
 
 
 
 
 
 
 
 
 
 
The following commit breaks puppetdb in my environment because we do not use the PUBLIC schema. 
https://github.com/puppetlabs/puppetdb/commit/53210f67eb8b2223cfb719ae484313b8cec55042#diff-11e61c2a3b3f71dacf7007d803e71b3d 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 

Jira (PUP-2400) Add acceptance tests for mount type

2015-03-31 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall assigned an issue to John Duarte 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2400 
 
 
 
  Add acceptance tests for mount type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

Assignee:
 
 Kurt Wall John Duarte 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1362) puppetdb crashes after upgrade

2015-03-31 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-1362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 
 
Pete Brown can you tell us what the operating system is and how many nodes you have? Also is there anything in your postgres logs that you can correlate to the crash? 
Wyatt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2400) Add acceptance tests for mount type

2015-03-31 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall commented on  PUP-2400 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add acceptance tests for mount type  
 
 
 
 
 
 
 
 
 
 
Fails on Windows 2012r2 x86_64: 
 
 
 
 
 
 
sayk41asu149l8o.delivery.puppetlabs.net (agent-2012r2-x86_64-rubyx64) 16:08:37$ env PATH=":${PATH}" cmd /c gem source --clear-all 
 
 
 
 
env: cmd: No such file or directory 
 
 
 
 
  
 
 
 
 
sayk41asu149l8o.delivery.puppetlabs.net (agent-2012r2-x86_64-rubyx64) executed in 0.10 seconds 
 
 
 
 
Exited: 127 
 
 
 
 
# 
 
 
 
 
 env PATH=":${PATH}" cmd /c gem source --clear-all 
 
 
 
 
Last 10 lines of output were: 
 
 
 
 
	env: cmd: No such file or directory>
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  

Jira (PUP-2400) Add acceptance tests for mount type

2015-03-31 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall commented on  PUP-2400 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add acceptance tests for mount type  
 
 
 
 
 
 
 
 
 
 
Passes on Debian 7 
Failing on F20: 
 
 
 
 
 
 
 51 fw8f9sy6cq8ivdv.delivery.puppetlabs.net (agent) 15:27:40$ umount /pl872469 
 
 
 
 
 52 umount: /pl872469: mountpoint not found 
 
 
 
 
 53 
 
 
 
 
 54 fw8f9sy6cq8ivdv.delivery.puppetlabs.net (agent) executed in 0.03 seconds 
 
 
 
 
 55 Exited: 32 
 
 
 
 
 56 # 
 
 
 
 
 57  umount /pl872469 
 
 
 
 
 58 Last 10 lines of output were: 
 
 
 
 
 59 umount: /pl872469: mountpoint not found>
 
 
 
 
 
 
 
 
 
 
 
 
 
  

Jira (PDB-1362) puppetdb crashes after upgrade

2015-03-31 Thread Pete Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pete Brown created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1362 
 
 
 
  puppetdb crashes after upgrade  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PDB 2.3.1, PDB 2.3.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/03/31 4:00 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Pete Brown 
 
 
 
 
 
 
 
 
 
 
Hi Gang, 
I just upgraded to PuppetDB 2.3.1 from 2.3.0 in my development environment and PuppetDB crashed on restart. 
If you need more information let me know. 
The resulting log messages. 2015-04-01 08:44:51,294 INFO [o.e.j.u.log] Logging initialized @24441ms 2015-04-01 08:44:52,110 INFO [p.t.s.w.jetty9-core] Removing buggy security provider SunPKCS11-NSS version 1.7 2015-04-01 08:44:52,636 INFO [p.t.s.w.jetty9-service] Initializing web server(s). 2015-04-01 08:44:52,642 INFO [p.t.s.w.jetty9-service] Starting web server(s). 2015-04-01 08:44:52,818 INFO [p.t.s.w.jetty9-core] Starting web server. 2015-04-01 08:44:52,822 INFO [o.e.j.s.Server] jetty-9.2.z-SNAPSHOT 2015-04-01 08:44:52,874 INFO [o.e.j.s.ServerConnector] Started ServerConnector@66ace155 {HTTP/1.1}{localhost:8080} 2015-04-01 08:44:53,150 INFO [o.e.j.s.ServerConnector] Started ServerConnector@7f17e429{SSL-HTTP/1.1}{0.0.0.0:8081} 2015-04-01 08:44:53,151 INFO [o.e.j.s.Server] Started @26300ms 2015-04-01 08:44:53,228 INFO [c.p.p.c.services] PuppetDB version 2.3.1 2015-04-01 08:44:53,362 INFO [c.p.p.s.migrate] Applying database migration version 28 2015-04-01 08:44:53,396 ERROR [c.p.p.s.migrate] Caught SQLException during migration java.sql.BatchUpdateException: Batch entry 5 DELETE FROM fact_paths t1 WHERE t1.id <> (SELECT MIN(t2.id) FROM fac

Jira (PUP-927) puppet apply on Windows always uses *nix style newlines from templates

2015-03-31 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown commented on  PUP-927 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet apply on Windows always uses *nix style newlines from templates  
 
 
 
 
 
 
 
 
 
 
Verifying with Rob's repo https://github.com/ferventcoder/puppet-simple_templates - existing files have the following checksums 
 
 
 
 
 
 
2411f8af978939a25884d8e13ceb8b38 - crlf_newlines.txt 
 
 
 
 
1751c05b07f0f4bc472fd04e6b9a5a5f - mixed_newlines.txt 
 
 
 
 
2a8909a71df8f1216074d1bd295b8e8b - unix_newlines.txt 
 
 
 
 
  
 
 
 
 
2411f8af978939a25884d8e13ceb8b38 - crlf_newlines.erb 
 
 
 
 
1751c05b07f0f4bc472fd04e6b9a5a5f - mixed_newlines.erb 
 
 
 
 
2a8909a71df8f1216074d1bd295b8e8b - unix_newlines.erb
 
 
 
 
 
 
 
Tests are executed against the sample module Rob has provided with 
 
 
 
 
 
 
bundle exec puppet apply --modulepath="../test-modules" -e "include simple_templates"
 
 
 
 
  

Jira (FACT-96) Deprecate 'facter --puppet'

2015-03-31 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  FACT-96 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Deprecate 'facter --puppet'  
 
 
 
 
 
 
 
 
 
 
 
it doesn't pretty-print facts, though there was an idea for that
 
puppet facts find will now pretty print (see 

PUP-3706
). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-96) Deprecate 'facter --puppet'

2015-03-31 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  FACT-96 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Deprecate 'facter --puppet'  
 
 
 
 
 
 
 
 
 
 
Nicholas Fagerlund do we have a docs-only deprecation in facter 2 docs? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4360) create puppetversion acceptance test

2015-03-31 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson assigned an issue to QA 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4360 
 
 
 
  create puppetversion acceptance test  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Assignee:
 
 Eric Sorenson QA 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4360) create puppetversion acceptance test

2015-03-31 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4360 
 
 
 
  create puppetversion acceptance test  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Reporter:
 
 QA Eric Thompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4360) create puppetversion acceptance test

2015-03-31 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 QA created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4360 
 
 
 
  create puppetversion acceptance test  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 

Components:
 

 QA 
 
 
 

Created:
 

 2015/03/31 3:50 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 QA 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

Jira (PUP-4359) puppetversion fact is missing

2015-03-31 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4359 
 
 
 
  puppetversion fact is missing  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Fix Version/s:
 
 CFACT 1.0.0 
 
 
 

Fix Version/s:
 
 PUP 4.0.1 
 
 
 

Key:
 
 CFACT PUP - 256 4359 
 
 
 

Project:
 
 Native Facter Puppet 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-891) dynamic library support cannot determine first_load on AIX

2015-03-31 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-891 
 
 
 
  dynamic library support cannot determine first_load on AIX  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Fix Version/s:
 
 FACT 3.1.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.


Jira (FACT-892) load_average resolver is not really posix

2015-03-31 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-892 
 
 
 
  load_average resolver is not really posix  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Fix Version/s:
 
 FACT 3.1.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.


Jira (FACT-890) Native facter support for aix

2015-03-31 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-890 
 
 
 
  Native facter support for aix  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Fix Version/s:
 
 FACT 3.1.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.


Jira (PUP-3968) Cache the zypper list-updates output

2015-03-31 Thread Melissa Stone (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Melissa Stone updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3968 
 
 
 
  Cache the zypper list-updates output  
 
 
 
 
 
 
 
 
 

Change By:
 
 Melissa Stone 
 
 
 

Sprint:
 
 RE 2015-04-08 
 
 
 

Story Points:
 
 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4044) AIO acceptance tests copies multiple versions of repo configs to the SUT

2015-03-31 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4044 
 
 
 
  AIO acceptance tests copies multiple versions of repo configs to the SUT  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4358) Multiple updates should not run at the same time

2015-03-31 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4358 
 
 
 
  Multiple updates should not run at the same time  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/03/31 3:24 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Alex Dreyer 
 
 
 
 
 
 
 
 
 
 
Multiple updates should not be run at the same time. Before an update starts it should check for an existing update running. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-4357) As a user I want to know when the module storage for my local forge does not match the database

2015-03-31 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4357 
 
 
 
  As a user I want to know when the module storage for my local forge does not match the database  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Story 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/03/31 3:21 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Alex Dreyer 
 
 
 
 
 
 
 
 
 
 
Updates should check for this state, log it and update A request for a module that finds it in the database but not on disk should result in a 500 and log at critical level. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (FACT-865) Native facter lost the output from stderr in external (and custom?) facts

2015-03-31 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-865 
 
 
 
  Native facter lost the output from stderr in external (and custom?) facts  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4308) puppet-agent 1.0.0 2015-04-01 Release

2015-03-31 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4308 
 
 
 
  puppet-agent 1.0.0 2015-04-01 Release  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4292) puppet 4.0.0 2015-04-01 Release

2015-03-31 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4292 
 
 
 
  puppet 4.0.0 2015-04-01 Release  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-893) CentOS 7.1.1503 breaks /etc/redhat-release

2015-03-31 Thread Peter Meier (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier commented on  FACT-893 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: CentOS 7.1.1503 breaks /etc/redhat-release  
 
 
 
 
 
 
 
 
 
 
I decided to add this task only to cfacter (given that's the future of facter) CFACT-271 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-865) Native facter lost the output from stderr in external (and custom?) facts

2015-03-31 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-865 
 
 
 
  Native facter lost the output from stderr in external (and custom?) facts  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 
 
 
 
 
 
 
 Fix output, and restore the original behavior from the acceptance test {{runs_external_facts_once.rb}}.We don't want to just dump output like facter does; this seems to make sense as a log warning. risk assessment: mediumprobability: medium (custom and external fact debugging)severity: medium (hard to debug)highest test layer: unit integration?  (some acceptance above, ensure log has warnings?  unit integration test?) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4203) Add ':uninstall_options' to gem provider

2015-03-31 Thread Melissa Stone (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Melissa Stone updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4203 
 
 
 
  Add ':uninstall_options' to gem provider  
 
 
 
 
 
 
 
 
 

Change By:
 
 Melissa Stone 
 
 
 

Affects Version/s:
 
 PUP 3.7.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-896) Solaris: undefined reference to symbol 'inet_ntop@@SUNW_1.7' when building Facter

2015-03-31 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-896 
 
 
 
  Solaris: undefined reference to symbol 'inet_ntop@@SUNW_1.7' when building Facter  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Fix Version/s:
 
 FACT 3.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 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 (FACT-895) Solaris: "'getloadavg' was not declared in this scope" when building Facter

2015-03-31 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-895 
 
 
 
  Solaris: "'getloadavg' was not declared in this scope" when building Facter  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Fix Version/s:
 
 FACT 3.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 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-735) Status unchanged when "Could not apply complete catalog"

2015-03-31 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-735 
 
 
 
  Status unchanged when "Could not apply complete catalog"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4241) Acceptance test for Puppet Preview

2015-03-31 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney assigned an issue to Hailee Kenney 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4241 
 
 
 
  Acceptance test for Puppet Preview  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hailee Kenney 
 
 
 

Assignee:
 
 Hailee Kenney 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-830) xendomains returning empty on debian hosts

2015-03-31 Thread Melissa Stone (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Melissa Stone updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-830 
 
 
 
  xendomains returning empty on debian hosts  
 
 
 
 
 
 
 
 
 

Change By:
 
 Melissa Stone 
 
 
 

Fix Version/s:
 
 FACT 2.4.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3238) puppet reports "end of file reached" if server closes HTTP connection

2015-03-31 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3238 
 
 
 
  puppet reports "end of file reached" if server closes HTTP connection  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4198) Add install_options feature to pip provider

2015-03-31 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4198 
 
 
 
  Add install_options feature to pip provider  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-893) CentOS 7.1.1503 breaks /etc/redhat-release

2015-03-31 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-893 
 
 
 
  CentOS 7.1.1503 breaks /etc/redhat-release  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Fix Version/s:
 
 FACT 2.4.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-893) CentOS 7.1.1503 breaks /etc/redhat-release

2015-03-31 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-893 
 
 
 
  CentOS 7.1.1503 breaks /etc/redhat-release  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Sprint:
 
 Client 2015-04-15 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-893) CentOS 7.1.1503 breaks /etc/redhat-release

2015-03-31 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-893 
 
 
 
  CentOS 7.1.1503 breaks /etc/redhat-release  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Story Points:
 
 1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-893) CentOS 7.1.1503 breaks /etc/redhat-release

2015-03-31 Thread Peter Meier (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier commented on  FACT-893 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: CentOS 7.1.1503 breaks /etc/redhat-release  
 
 
 
 
 
 
 
 
 
 
We should also make sure, that we might revisite the whole thing and prefering /etc/os-release for CentOS, RedHat, ... > 7. /etc/os-release seems to be present since 7.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.


Jira (PDB-1124) PuppetDB high CPU usage

2015-03-31 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-1124 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PuppetDB high CPU usage  
 
 
 
 
 
 
 
 
 
 
Anton Fomenko Can you see if the issue persists on PuppetDB 2.3.1 (released today)? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4340) source_attribute acceptance test failing intermittently

2015-03-31 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  PUP-4340 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: source_attribute acceptance test failing intermittently  
 
 
 
 
 
 
 
 
 
 
Appears to have made it through CI. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4340) source_attribute acceptance test failing intermittently

2015-03-31 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith assigned an issue to QA 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4340 
 
 
 
  source_attribute acceptance test failing intermittently  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 QA 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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   3   >