Jira (PUP-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren commented on PUP-4486 Re: Add a JSON data provider I seem to recall that we settled for a solution that uses a predetermined and unchangeable name and location for the json file that backs this provider. Henrik Lindberg, do you have any preferences? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4485) Add a 'hiera' data provider
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-4485 Add a 'hiera' data provider Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-4486 Add a JSON data provider Change By: Thomas Hallgren Comment: I seem to recall that we settled for a solution that uses a predetermined and unchangeable name and location for the json files that backs this provider. [~henrik.lindberg], do you have any preferences? I need two locations, one for env and one for the module. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren commented on PUP-4486 Re: Add a JSON data provider Regarding file location for the JSON data that backs this provider. I assume that the provider will not be bound but rather instantiated by the Hiera data provider mentioned in PUP-4485. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4485) Add a 'hiera' data provider
Title: Message Title Thomas Hallgren commented on PUP-4485 Re: Add a 'hiera' data provider "The data should be cached for each compilation", does that include the hiera.yaml itself (in one sense, it's configuration, not data. Then again, everything is data)? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4951) "puppet module build" too picky about SemVer
Title: Message Title Andreas Kotes created an issue Puppet / PUP-4951 "puppet module build" too picky about SemVer Issue Type: Bug Assignee: Unassigned Created: 2015/07/29 6:03 AM Priority: Normal Reporter: Andreas Kotes Parsing the metadata.json uses SemVer from lib/semver.rb (why not use Semantic everywhere?) which is unaccepting of SemVer 2.0: "A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version." "Build metadata MAY be denoted by appending a plus sign and a series of dot separated identifiers immediately following the patch or pre-release version." .. while the RegEx used is /^v?(\d+)\.(\d+)\.(\d+)(-[0-9A-Za-z-]*|)$/ .. Semantic 1.4.1 fares somewhat better. Add Comment
Jira (PUP-4485) Add a 'hiera' data provider
Title: Message Title Henrik Lindberg commented on PUP-4485 Re: Add a 'hiera' data provider The hiera.yaml content in itself without any interpretation of its content can have the same lifecycle as the environment. Each compilation must have its own configuration instance where variables/paths etc. have been resolved since variables change between compilations. The instantiated configuration can have the same lifecycle as the compiler. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-2864) yum provider can't handle installonly packages
Title: Message Title
Cenek Zach commented on PUP-2864
Re: yum provider can't handle installonly packages
It works, if you add the version to the package name:
package { 'kernel-ml-3.14.4-1.el6.elrepo' : ensure => installed, }
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-1824) PQL: Specification and Query Design
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1824 PQL: Specification and Query Design Issue Type: Task Assignee: Unassigned Created: 2015/07/29 6:50 AM Fix Versions: PDB 3.1.0 Priority: Normal Reporter: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are s
Jira (PDB-1825) PQL: Puppet DSL Function
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1825 PQL: Puppet DSL Function Issue Type: Task Assignee: Unassigned Created: 2015/07/29 6:52 AM Fix Versions: PDB 3.1.0 Priority: Normal Reporter: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed t
Jira (PDB-1826) PQL: Prototype needs to include from, subquery & extract capability
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1826 PQL: Prototype needs to include from, subquery & extract capability Issue Type: Task Assignee: Unassigned Created: 2015/07/29 6:54 AM Fix Versions: PDB 3.1.0 Priority: Normal Reporter: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You receive
Jira (PDB-1801) PQL Initial Service Prototype
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1801 PQL Initial Service Prototype Change By: Kenneth Barber Summary: PQL Initial Service Prototype Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1825) PQL: Puppet Function
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1825 PQL: Puppet Function Change By: Kenneth Barber Summary: PQL: Puppet DSL Function Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1826) PQL: Prototype needs to include from, subquery & extract capability
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1826 PQL: Prototype needs to include from, subquery & extract capability Change By: Kenneth Barber Story Points: 3 5 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1826) PQL: Prototype needs to include from, subquery capability
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1826 PQL: Prototype needs to include from, subquery capability Change By: Kenneth Barber Summary: PQL: Prototype needs to include from, subquery & extract capability Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1827) PQL: Prototype - include extract capability
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1827 PQL: Prototype - include extract capability Issue Type: Task Assignee: Unassigned Created: 2015/07/29 7:06 AM Fix Versions: PDB 3.1.0 Priority: Normal Reporter: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because y
Jira (PUP-283) Improve agent error reporting
Title: Message Title E Salberg commented on PUP-283 Re: Improve agent error reporting Updating here even though this may need its own ticket (I already opened a case with Support): We're also seeing the same behavior (green checkmark / no alerts in the Console or Tagmail) in cases of Classifier conflicts (e.g. one node pinned to two different node groups that set the same variables to different values - myvariable="yes" and myvariable="no"). The node is not using a cached catalog and the run continues, so the node doesn't even enter Unresponsive state - conflicts could just be there forever. The only indications are on the Node page and a 400 error in the Puppet run log (which doesn't alert anywhere). It definitely seems to be related to the same logging functionality, so I wanted to make sure it was a known issue before the development is over. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1827) PQL: Prototype - include subquery & extract capability
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1827 PQL: Prototype - include subquery & extract capability Change By: Kenneth Barber Summary: PQL: Prototype - include subquery & extract capability Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1827) PQL: Prototype - include subquery & extract capability
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1827 PQL: Prototype - include subquery & extract capability Change By: Kenneth Barber Sprint: PuppetDB 2015-08- 26 12 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1826) PQL: Prototype needs to include from & subquery capability
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1826 PQL: Prototype needs to include from & subquery capability Change By: Kenneth Barber Summary: PQL: Prototype needs to include from , & subquery capability Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg commented on PUP-4486 Re: Add a JSON data provider I don't think that the hiera specific providers (e.g. Json, Yaml) should be bound the same way as the function/hiera environment/module-providers. The protocol is slightly different. I do think they should be injected though as it should be possible to plugin other providers. Since the backends are mentioned by symbolic name in hiera.yaml, there needs to be a way to lookup the "json", the "yaml", etc. Those that extend with a plugin must be able to specify this mapping. This means using a multibinding with the symbolic name as the key. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4485) Add a 'hiera' data provider
Title: Message Title
Thomas Hallgren commented on PUP-4485
Re: Add a 'hiera' data provider
Some thoughts around the format of the hiera.yaml file.
Why is it possible to specify several types in one backend and then have them share paths? Does the paths in question then include the extension (.json and .yaml)? Should the extension be optional?
I would be more in favor of this simpler format:
---
:version: 4
:hierarchy:
- { backend: 'yaml1'
type: yaml,
datadir: 'some path',
paths:
- "path"
- "path"
}
Jira (PDB-1807) PR (1547): (maint) Add access to packaging repo - melissa
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1807 PR (1547): (maint) Add access to packaging repo - melissa Change By: Steve Barlow Sprint: PuppetDB 2015-07-29 , PuppetDB 2015-08-12 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1790) Show that sync works in the face of node expiration
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1790 Show that sync works in the face of node expiration Change By: Steve Barlow Sprint: PuppetDB 2015-07-29 , PuppetDB 2015-08-12 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1313) Test sync of divergent states
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1313 Test sync of divergent states Change By: Steve Barlow Sprint: PuppetDB 2015-07-15, PuppetDB 2015-07-29 , PuppetDB 2015-08-12 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1699) scope event-counts and legacy query engine retirement
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1699 scope event-counts and legacy query engine retirement Change By: Steve Barlow Sprint: PuppetDB 2015-07-01, PuppetDB 2015-07-15, PuppetDB 2015-07-29 , PuppetDB 2015-08-12 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1526) Provide test packages to ops for sync logging feedback
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1526 Provide test packages to ops for sync logging feedback Change By: Steve Barlow Sprint: PuppetDB 2015-07-01, PuppetDB 2015-07-15, PuppetDB 2015-07-29 , PuppetDB 2015-08-12 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1721) Possible Memory leak with PuppetDB?
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1721 Possible Memory leak with PuppetDB? Change By: Steve Barlow Sprint: PuppetDB 2015-07-29 , PuppetDB 2015-08-12 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1810) Filesync Service: Add new git sha1 field
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1810 Filesync Service: Add new git sha1 field Change By: Steve Barlow Sprint: PuppetDB 2015-08-12 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1676) PuppetDB module needs better documentation on SSL generation
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1676 PuppetDB module needs better documentation on SSL generation Change By: Steve Barlow Sprint: PuppetDB 2015-08-12 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1677) PuppetDB module does not work as advertised
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1677 PuppetDB module does not work as advertised Change By: Steve Barlow Sprint: PuppetDB 2015-08-12 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1677) PuppetDB module does not work as advertised
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1677 PuppetDB module does not work as advertised Change By: Steve Barlow Story Points: 8 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1123) Facter explodes with invalid locales
Title: Message Title Branan Riley commented on FACT-1123 Re: Facter explodes with invalid locales I'll work on the merge-up today. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4890) Add catalog_id to catalog
Title: Message Title Branan Riley assigned an issue to Unassigned Puppet / PUP-4890 Add catalog_id to catalog Change By: Branan Riley Assignee: Branan Riley Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1653) Implement the outcome of PDB-1312 (TBD)
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1653 Implement the outcome of PDB-1312 (TBD) Change By: Steve Barlow Story Points: 5 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1737) Change storage_utils to dispatch on driver class
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1737 Change storage_utils to dispatch on driver class Change By: Steve Barlow Sprint: PuppetDB 2015-08- 12 26 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1726) PR (1514): Testing out cljfmt on 2.3.x - senior
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1726 PR (1514): Testing out cljfmt on 2.3.x - senior Change By: Steve Barlow Sprint: PuppetDB 2015-07-15, PuppetDB 2015-08- 12 26 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1732) Detail approach and set priorities for flipping acceptance tests to clojure tests
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1732 Detail approach and set priorities for flipping acceptance tests to clojure tests Change By: Steve Barlow Sprint: PuppetDB 2015-08- 12 26 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4952) acceptance test curl fails on sles-10
Title: Message Title Kevin Imber created an issue Puppet / PUP-4952 acceptance test curl fails on sles-10 Issue Type: Bug Assignee: Unassigned Created: 2015/07/29 8:51 AM Environment: sles-10-* hosts Priority: Normal Reporter: Kevin Imber In finishing up the work for PUP-4757, I saw that tests/concurrency/ticket_2659_concurrent_catalog_requests.rb fails for just sles-10 platforms while trying to run a curl command: error:0D0C50A1:asn1 encoding routines:ASN1_item_verify:unknown message digest algorithm The output from the Jenkins job is below: Launched 7242
Jira (PDB-1827) PQL: Prototype - include subquery & extract capability
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-1827 PQL: Prototype - include subquery & extract capability Change By: Kenneth Barber Assignee: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4953) fails to create authorized_key file with puppet on sles-10-i386
Title: Message Title Kevin Imber created an issue Puppet / PUP-4953 fails to create authorized_key file with puppet on sles-10-i386 Issue Type: Bug Assignee: Unassigned Created: 2015/07/29 8:57 AM Environment: sles-10-i386 Priority: Normal Reporter: Kevin Imber In PUP-4757, we added sles & ubuntu support to the PE AIO pipeline to ready puppet-agent to be promoted to PE. Once sles-10 (it seems in particular to be the i386 platform) was added, the tests/resource/ssh_authorized_key/create.rb test began failing. The output from the Jenkins job for this test is below: Begin tests/resource/ssh_authorized_key/create.rb should create an entry for an SSH a
Jira (PUP-4935) $HOME directory of the Puppet user is writable
Title: Message Title Jeremy Barlow commented on PUP-4935 Re: $HOME directory of the Puppet user is writable Rob Braden Matthaus Owens What do you think about this? I think the same question would apply for other packages as well, e.g., puppetdb's /opt/puppetlabs/server/data/puppetdb directory also has a 755 mode by default after installation. From Puppet Server's perspective, I'm not immediately aware of any problems that would result from making the puppet user's $HOME directory not writable, but I don't have any research to back this. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4935) $HOME directory of the Puppet user is writable
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-4935 $HOME directory of the Puppet user is writable Change By: Jeremy Barlow Scrum Team: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4951) "puppet module build" too picky about SemVer
Title: Message Title Andreas Kotes updated an issue Puppet / PUP-4951 "puppet module build" too picky about SemVer Change By: Andreas Kotes Parsing the metadata.json uses SemVer from lib/semver.rb (why not use Semantic everywhere?) which is unaccepting of SemVer 2.0:"A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version.""Build metadata MAY be denoted by appending a plus sign and a series of dot separated identifiers immediately following the patch or pre-release version.".. while the RegEx used is /^v?(\d+)\.(\d+)\.(\d+)(-[0-9A-Za-z-]*|)$/ .. Version "v2.5-foobar" is also invalid, while "v2.5.0-foobar" is fine. Semantic 1.4.1 fares somewhat better. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4485) Add a 'hiera' data provider
Title: Message Title Henrik Lindberg commented on PUP-4485 Re: Add a 'hiera' data provider That makes it unclear what 'backend' and 'type' is - people will confuse those. If flattened like that I suggest that backend is the type of the backend e.g. 'json', 'yaml', and that the name or id is used for the 'label' (that is used for errors etc.). The reason for supporting multiple entries is for those that have files of two or more types at the same level in the hierarchy. It saves them entering the same set of paths more than once. Worst case, they use json,yaml, and encrypted data and have 5-10 paths. You really want to specify those paths just once to avoid mistakes in changing only one of them. In general I think people think about this as "search these paths for files of these types". Possibly support both backend (one, the flattened you proposed with small name change), or backends which is then array of object with backend, datadir, and id. OTOH - the structure I proposed first supports all cases In hiera I think extensions are not entered in the paths, only the name of the files. Not sure what happens if a path has say '.json' extensions and searched with a yaml provider - it probably searches for '.json.yaml' in that case. So, I think paths should be without extension and that each provider adds that when actually searching for the file. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1123) Facter explodes with invalid locales
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1123 Facter explodes with invalid locales Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4485) Add a 'hiera' data provider
Title: Message Title
Thomas Hallgren commented on PUP-4485
Re: Add a 'hiera' data provider
"That makes it unclear what 'backend' and 'type' is - people will confuse those"
OK, so how about this. Replace :hierarchy: with :backends: and backend: with name:, like this:
---
:version: 4
:backends:
- { name: 'yaml1'
type: yaml,
datadir: 'some path',
...
"You really want to specify those paths just once to avoid mistakes in changing only one of them" Why? How often will people use both yaml and json in the same directory and in files with the same name? Have you ever seen any real use-case of this? To me this looks like a sub-optimal adaption of a corner case that I'm not sure will ever happen.
Jira (PUP-4545) Too many restarts on interaface changes for Fedora, RHEL, CentOS
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-4545 Too many restarts on interaface changes for Fedora, RHEL, CentOS Change By: Kenn Hussey Sprint: RE 2015-07-29 , RE 2015-08-12 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4949) Puppet Agent - Add PE testing in Jenkins pipeline
Title: Message Title Justin Stoller commented on PUP-4949 Re: Puppet Agent - Add PE testing in Jenkins pipeline Sounds good. What is the timeframe on this? I will pull working on that into our next sprint. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4545) Too many restarts on interaface changes for Fedora, RHEL, CentOS
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-4545 Too many restarts on interaface changes for Fedora, RHEL, CentOS Change By: Kenn Hussey Sprint: RE 2015-07-29, RE 2015-08- 12 26 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-4196 agent command line options ignored running under systemd Change By: Kenn Hussey Sprint: RE 2015-08- 12 26 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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
Title: Message Title
Matthaus Owens commented on PUP-4196
Re: agent command line options ignored running under systemd
Removing the {} around the opts in the unit file resolves the problem for me. This was applied to master/puppet 4 in https://github.com/puppetlabs/puppet/commit/57f0b8220078f5bea3ba12ccc3c83baed0ddf991.
Steve Traylen Does changing the ExecStart to
ExecStart=/usr/bin/puppet agent $PUPPET_EXTRA_OPTS --no-daemonize
resolve the issue for you? Side note: the above commit added the {}, which may explain why reverting the commit fixes it.
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-1123) Facter explodes with invalid locales
Title: Message Title Shaigy Nixon assigned an issue to Shaigy Nixon Facter / FACT-1123 Facter explodes with invalid locales Change By: Shaigy Nixon Assignee: qa Shaigy Nixon Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4485) Add a 'hiera' data provider
Title: Message Title Henrik Lindberg commented on PUP-4485 Re: Add a 'hiera' data provider We are catering to people's data the way they have it organized now - I am sure every possible combination is in use. We want to stick as close as possible to what is already there and the conceptual model people have. Therefore: They specify a 'hierarchy' (hence that key) They specify it in terms of a set of paths Some of the files in that set of paths come from some source that requires say json to be used where the rest are in yaml (or vice versa) Some of the files in that set of paths are encrypted using a special backend. They lack the ability to specify a more complex order today (now they only have provider a: all paths, provider b: all paths...) I think what I proposed most naturally adds abilities to specify more advanced configurations. I don't understand what you find wrong with it. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 ht
Jira (PUP-4935) $HOME directory of the Puppet user is writable
Title: Message Title Jeff McCune updated an issue Puppet / PUP-4935 $HOME directory of the Puppet user is writable Change By: Jeff McCune Comment: A comment with security level 'Developers' was removed. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4935) $HOME directory of the Puppet user is writable
Title: Message Title Jeff McCune assigned an issue to Julien Pivotto Puppet / PUP-4935 $HOME directory of the Puppet user is writable Change By: Jeff McCune Assignee: Julien Pivotto Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4935) $HOME directory of the Puppet user is writable
Title: Message Title Jeff McCune commented on PUP-4935 Re: $HOME directory of the Puppet user is writable Julien Pivotto Could you provide some impact data about this issue and some reasoning about why you think the home directory permissions should be changed? I'm hesitant to do so because a lot of our components assume that the home directory of the service account is writable. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4485) Add a 'hiera' data provider
Title: Message Title Henrik Lindberg commented on PUP-4485 Re: Add a 'hiera' data provider I understand that it is a bit more implementation work as the implementation needs to expand the structure and look for default values in the level above - otherwise the users have to do that and then they have to make changes in more than one place. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1828) puppetdb 3.0.2 2015-08-03 Release
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1828 puppetdb 3.0.2 2015-08-03 Release Issue Type: Task Assignee: Wyatt Alt Created: 2015/07/29 10:44 AM Priority: Normal Reporter: Wyatt Alt puppetdb 3.0.2 2015-08-03 Release When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward. When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready.
Jira (PDB-1829) Is the code ready for release?
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1829 Is the code ready for release? Issue Type: Sub-task Assignee: Wyatt Alt Created: 2015/07/29 10:44 AM Priority: Normal Reporter: Wyatt Alt If there are any version dependencies expressed in the code base, make sure these are up to date. For Puppet, make sure the shas used to build the MSI are correct. For Puppet-Server, make sure all references to the puppet version are correct. All tests (spec, acceptance) should be passing on all platforms for both stable & master. If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests Move all items that should be moved from Ready for CI to Ready for Review Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PDB%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%223.0.2%22
Jira (PDB-1834) Prepare long form release notes and short form release story
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1834 Prepare long form release notes and short form release story Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2015/07/29 10:45 AM Priority: Normal Reporter: Wyatt Alt Collaborating with product for release story Dependencies: Reconcile git commits and JIRA tickets Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PDB-1832) Merge master into stable
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1832 Merge master into stable Issue Type: Sub-task Assignee: Wyatt Alt Created: 2015/07/29 10:45 AM Priority: Normal Reporter: Wyatt Alt For some releases, the code base will need to be merged down to stable. NOTE: This is usually only during a x.y.0 release, but even then it may have already been done. If it doesn't apply, close this ticket. Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: git fetch upstream git rebase upstream/master git checkout stable
Jira (PDB-1830) Reconcile git commits and JIRA tickets
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1830 Reconcile git commits and JIRA tickets Issue Type: Sub-task Assignee: Wyatt Alt Created: 2015/07/29 10:44 AM Priority: Normal Reporter: Wyatt Alt Use the ticketmatch script to ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. cd ~/work git clone https://github.com/puppetlabs/ticketmatch cd ~/work/puppet # or whatever the repo is you're releasing from ruby ../ticketmatch/ticketmatch.rb Enter Git From Rev: 4.1.0 Enter Git To Rev: |master| stable Enter JIRA project: |PUP| Enter JIRA fix version: PUP 4.2.0 The output may contain the following headers: COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF ...) Lists git commits that don't have a corresponding ticket, at least not for the specified fix version. If the commit has a ticket, but the ticket is not targeted correctly, then the ticket's fixVersion should be updated. This can frequently happen if a ticket is initially targeted for a future release (master), but is pulled into an earlier release (stable), but the ticket's fixVersion is not updated.
Jira (PDB-1833) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1833 Is the Jira tidy-up done for this release and prepared for the next one? Issue Type: Sub-task Assignee: Wyatt Alt Created: 2015/07/29 10:45 AM Priority: Normal Reporter: Wyatt Alt This happens on Jira - we need to clean up the current release and prepare for the next release. Mark the version that's going out as "Released" in the Project Admin -> Versions panel. Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future) Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the "Release story" ticket): 'project = XX AND affectedVersion = 'X.Y.Y', Save as "Introduced in X.Y.Y", click Details, add permission for Everyone 'project = XX AND fixVersion = 'X.Y.Z', Save as "Fixes for X.Y.Z", click Details, add permission for Everyone
Jira (PDB-1831) Update version number in source
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1831 Update version number in source Issue Type: Sub-task Assignee: Wyatt Alt Created: 2015/07/29 10:44 AM Priority: Normal Reporter: Wyatt Alt Bump VERSION in lib/PDB/version.rb or project.clj to correct version. Commit the updated version file. e.g) commit -m "(packaging) Update FACTERVERSION to 1.7.3". If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask). Once this is done, hand the SHA to be built to RelEng to be tagged. Dependencies: Is the code ready for release? Reconcile git commits and JIRA tickets
Jira (PDB-1841) Send out announcements
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1841 Send out announcements Issue Type: Sub-task Assignee: Eric Sorenson Created: 2015/07/29 10:45 AM Priority: Normal Reporter: Wyatt Alt Melissa Stone: update the release google spreadsheet. Update the MSI build targets in the Puppet repo in ext/build_defaults.yaml. This needs to be done for any projects that are to get into the MSI (facter and hiera as of 8/2014) Send the drafted release notes email. If final send to puppet-announce and specific distribution lists (e.g. puppet to puppet-users & puppet-dev). If this release has security implications, also send the release announcement to puppet-security-announce Make a PSA on IRC letting those kiddos know about the new release. Something along the lines of "PSA: facter 1.7.3 now available" Dependencies:
Jira (PDB-1836) Smoke test packages
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1836 Smoke test packages Issue Type: Sub-task Assignee: Wyatt Alt Created: 2015/07/29 10:45 AM Priority: Normal Reporter: Wyatt Alt Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be limited to other package formats than deb and rpm. For the Puppet gem, we don't yet have automated acceptance testing, so some quick manual smoke testing should always be performed. Platform packages express their dependencies differently than gems, so it's possible to encounter a situation where the build pipeline produced packages out of sync with the gems. Lighter testing of Z releases is acceptable. Add a link to the Packages repository that you receive from the "Tag and create packages" subtask Ping folks on your team for help with different platforms. When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment, preferably with a code snippet showing the commands executed and their output. When all platforms
Jira (PDB-1838) Push tag
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1838 Push tag Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/07/29 10:45 AM Priority: Normal Reporter: Wyatt Alt The development team is responsible for updating the stable/master branches as necessary. This will be done after the version bump in version.rb. Dependencies: Go / No Go meeting (except where it's required to push the tag to build packages - MSIs) Add Comment This message was sent by Atlassian JIRA (v6.
Jira (PDB-1835) Tag the release and create packages
Title: Message Title
Wyatt Alt created an issue
PuppetDB / PDB-1835
Tag the release and create packages
Issue Type:
Sub-task
Assignee:
Melissa Stone
Created:
2015/07/29 10:45 AM
Priority:
Normal
Reporter:
Wyatt Alt
Tag and create packages
Developer provides the SHA - Wyatt Alt - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb)
checkout the sha
Make sure you are about to tag the correct thing
Create the tag e.g.) git tag -s -u {GPG key}
-m "1.7.3" 1.7.3
You need to know the pass phrase for this to complete successfully. It's important that we make sure all releases are signed to verify authenticity.
DO NOT push the tag to the repo, keep it local only
`git describe` will show you the tag. Make sure you're building what you think you're building.
Ma
Jira (PDB-1839) Packages pushed
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1839 Packages pushed Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/07/29 10:45 AM Priority: Normal Reporter: Wyatt Alt Push packages run `rake pl:jenkins:uber_ship` You will need the keys to the castle (aka the passphrase) for this to work. Don't forget to make sure everything looks like it's in the correct folder, the pkgs dir has been cleared out, and that you are shipping for all expected platforms. Get a second set of RelEng eyes on the packages that are about to be shipped to make sure everything looks a-okay. If you're shipping a gem you need to make sure you have a rubygems account, are an owner of that project, and have a gem config file. If you're shipping puppet you need to sign the MSI file for Windows. This is a manual process and the ship task doesn't ship or build the msi so talk to Moses or Haus for more details. This file also needs to be manually signed. Dependencies:
Jira (PDB-1840) Docs pushed
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1840 Docs pushed Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2015/07/29 10:45 AM Priority: Normal Reporter: Wyatt Alt Push the documentation updates to docs.puppetlabs.com. Dependencies: Go / No Go meeting (Status - Ship it!) Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PDB-1837) Go/no-go meeting (before 4pm)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1837 Go/no-go meeting (before 4pm) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2015/07/29 10:45 AM Priority: Normal Reporter: Wyatt Alt This should happen Monday-Thursday, before 4pm. We should not be shipping anything after 4:00 PM or on a Friday both for our users, and because shipping takes time. Get a yes/no for the release from dev, docs, product, qa, releng. This meeting is informal, over chat, and usually happens right before packages are pushed. Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release. Dependencies: Smoke testing Add Comment
Jira (PDB-1843) Close all resolved tickets in Jira
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1843 Close all resolved tickets in Jira Issue Type: Sub-task Assignee: Wyatt Alt Created: 2015/07/29 10:45 AM Priority: Normal Reporter: Wyatt Alt Close any tickets that have been resolved for the release. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PDB%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%223.0.2%22%20AND%20status%20%3D%20Resolved There is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route: Select Bulk Change - All # issues Step 1 - choose all relevant issues (likely all of them) Step 2 - Select "Transition Issues" Step 3 - Select "Closed" Step 4 - Select "Fixed" in Change Resolution. View what is about to change and confirm it. Then commit the change. Dependencies:
Jira (PDB-1842) Update dujour to notify users to use 3.0.2
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1842 Update dujour to notify users to use 3.0.2 Issue Type: Sub-task Assignee: Wyatt Alt Created: 2015/07/29 10:45 AM Priority: Normal Reporter: Wyatt Alt Update dujour to notify users to use 3.0.2. Dependencies: Packages pushed Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4949) Puppet Agent - Add PE testing in Jenkins pipeline
Title: Message Title Michael Smith commented on PUP-4949 Re: Puppet Agent - Add PE testing in Jenkins pipeline I'm not really sure, maybe in the next month. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1828) puppetdb 3.0.2 2015-08-03 Release
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1828 puppetdb 3.0.2 2015-08-03 Release Change By: Wyatt Alt Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1828) puppetdb 3.0.2 2015-08-03 Release
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1828 puppetdb 3.0.2 2015-08-03 Release Change By: Wyatt Alt Sprint: PuppetDB 2015-08-12 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1123) Facter explodes with invalid locales
Title: Message Title Shaigy Nixon updated an issue Facter / FACT-1123 Facter explodes with invalid locales Change By: Shaigy Nixon QA Risk Severity: High QA Risk Probability: Low QA Risk Severity Reason: puppet coredumps, installation failure for puppetserver QA Risk Assessment: High QA Highest Test Level: Acceptance QA Risk Assessment Reason: Core dump is ugly, graceful exit is the way QA Status: Reviewed Add Comment
Jira (PDB-1512) Don't allow overlapping syncs from the same host
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1512 Don't allow overlapping syncs from the same host Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1123) Facter explodes with invalid locales
Title: Message Title Michael Smith commented on FACT-1123 Re: Facter explodes with invalid locales Who's going to write the acceptance test? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1123) Facter explodes with invalid locales
Title: Message Title Shaigy Nixon commented on FACT-1123 Re: Facter explodes with invalid locales I can write the acceptance test Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4954) filebucket fails when environment is specified
Title: Message Title Ben Ford created an issue Puppet / PUP-4954 filebucket fails when environment is specified Issue Type: Bug Affects Versions: PUP 4.2.1 Assignee: Unassigned Created: 2015/07/29 12:29 PM Priority: Major Reporter: Ben Ford If the agent's `puppet.conf` specifies an environment and the ENC also specifies the environment, then filebucketing fails with an inscrutable error. root@binford2k:~ # cat /etc/puppetlabs/puppet/puppet.conf # This file can be used to override the default puppet settings. # See the following links for more details on what settings are available:
Jira (PUP-4954) filebucket fails when environment is specified
Title: Message Title
Ben Ford updated an issue
Puppet / PUP-4954
filebucket fails when environment is specified
Change By:
Ben Ford
If the agent's `puppet.conf` specifies an environment and the ENC also specifies the environment, then filebucketing fails with an inscrutable error and the run is marked as failed in the Console .{code}root@binford2k:~ # cat /etc/puppetlabs/puppet/puppet.conf# This file can be used to override the default puppet settings.# See the following links for more details on what settings are available:# - https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html# - https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html# - https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html# - https://docs.puppetlabs.com/references/latest/configuration.html[main]server = master.puppetlabs.vmenvironment_timeout = 0environmentpath = /etc/puppetlabs/code/environments[agent]certname = binford2k.puppetlabs.vmenvironment = binford2kroot@binford2k:~ # puppet agent -tInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsInfo: Caching catalog for binford2k.puppetlabs.vmInfo: Applying configuration version '1438197631'Notice: Hello binford2k.puppetlabs.vmNotice: /Stage[main]/Main/Node[default]/Notify[Hello binford2k.puppetlabs.vm]/message: defined 'message' as 'Hello binford2k.puppetlabs.vm'Notice: /Stage[main]/Userprefs::Bash/File[/root/.bashrc.puppet]/content:--- /root/.bashrc.puppet 2015-07-29 19:20:26.719816423 ++++ /tmp/puppet-file20150729-52505-17roz3n 2015-07-29 19:20:34.453201837 +@@ -1,5 +1,3 @@-#boogers- # NOTE: This file is managed by Puppet; any changes you make will be erased. parse_git_branch ()Info: Computing checksum on file /root/.bashrc.puppetError: Could not back up /root/.bashrc.puppet: Could not find a directory environment named 'binford2k' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?Error: Could not back up /root/.bashrc.puppet: Could not find a directory environment named 'binford2k' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?Error: /Stage[main]/Userprefs::Bash/File[/root/.bashrc.puppet]/content: change from {md5}1df06bcfcafd1511cccea89849c37102 to {md5}c81901d08fb7e2c27fff6ca1e450e99e failed: Could not back up /root/.bashrc.puppet: Could not find a directory environment named 'binford2k' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?Info: Stage[main]: Unscheduling all events on Stage[main]Notice: Applied catalog in 1.35 seconds{code}The environment exists.
Add Comment
Jira (PUP-4954) filebucket fails when environment is specified
Title: Message Title
Ben Ford updated an issue
Puppet / PUP-4954
filebucket fails when environment is specified
Change By:
Ben Ford
If the agent's `puppet.conf` specifies an environment and the ENC also specifies the environment, then filebucketing fails with an inscrutable error and the run is marked as failed in the Console.{code}root@binford2k:~ # cat /etc/puppetlabs/puppet/puppet.conf# This file can be used to override the default puppet settings.# See the following links for more details on what settings are available:# - https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html# - https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html# - https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html# - https://docs.puppetlabs.com/references/latest/configuration.html[main]server = master.puppetlabs.vmenvironment_timeout = 0environmentpath = /etc/puppetlabs/code/environments[agent]certname = binford2k.puppetlabs.vmenvironment = binford2kroot@binford2k:~ # puppet agent -tInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsInfo: Caching catalog for binford2k.puppetlabs.vmInfo: Applying configuration version '1438197631'Notice: Hello binford2k.puppetlabs.vmNotice: /Stage[main]/Main/Node[default]/Notify[Hello binford2k.puppetlabs.vm]/message: defined 'message' as 'Hello binford2k.puppetlabs.vm'Notice: /Stage[main]/Userprefs::Bash/File[/root/.bashrc.puppet]/content:--- /root/.bashrc.puppet 2015-07-29 19:20:26.719816423 ++++ /tmp/puppet-file20150729-52505-17roz3n 2015-07-29 19:20:34.453201837 +@@ -1,5 +1,3 @@-#boogers- # NOTE: This file is managed by Puppet; any changes you make will be erased. parse_git_branch ()Info: Computing checksum on file /root/.bashrc.puppetError: Could not back up /root/.bashrc.puppet: Could not find a directory environment named 'binford2k' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?Error: Could not back up /root/.bashrc.puppet: Could not find a directory environment named 'binford2k' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?Error: /Stage[main]/Userprefs::Bash/File[/root/.bashrc.puppet]/content: change from {md5}1df06bcfcafd1511cccea89849c37102 to {md5}c81901d08fb7e2c27fff6ca1e450e99e failed: Could not back up /root/.bashrc.puppet: Could not find a directory environment named 'binford2k' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?Info: Stage[main]: Unscheduling all events on Stage[main]Notice: Applied catalog in 1.35 seconds{code}The environment exists and *the file does not get updated* .
Add Comment
Jira (PUP-4924) Puppet Windows - Upgrading from 3.7.5 causes Ruby.exe/Rubyw.exe to go missing
Title: Message Title Rob Reynolds assigned an issue to Unassigned Puppet / PUP-4924 Puppet Windows - Upgrading from 3.7.5 causes Ruby.exe/Rubyw.exe to go missing Change By: Rob Reynolds Assignee: Rob Reynolds Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4485) Add a 'hiera' data provider
Title: Message Title Thomas Hallgren commented on PUP-4485 Re: Add a 'hiera' data provider I think there's enough differences between the hiera.yaml proposed here and the original to make room for additional improvements. Hence my desire to simplify, not just the implementation work needed behind the scenes, but also the actual configuration. The one originally proposed here is, IMO, over complicated and introduces ambiguities in how the paths are described (with our without extension). Granted, the original hiera configuration specifies a 'hierarchy' key at top level, but it also specifies a 'backends' key. Why is the former better when what we actually specify is a list of named and typed backends? That doesn't make sense to me. I think the best case to settle this discussion is to look at actual use-cases and the work it would entail to convert them. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4954) filebucket fails when environment is specified
Title: Message Title Ben Ford commented on PUP-4954 Re: filebucket fails when environment is specified This means that anyone who specifies the environment in their puppet.conf to avoid the Warning: Local environment: "production" doesn't match server specified node environment "binford2k", switching agent to "binford2k". warning completely loses the ability to manage files. Mitigation strategies: don't specify environment disable filebucket Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4954) filebucket fails when environment is specified
Title: Message Title Klynton Jessup commented on PUP-4954 Re: filebucket fails when environment is specified It's also worth noting here that the puppet_agent module does not do anything with the 'environment' setting in puppet.conf on upgrade: https://github.com/puppetlabs/puppetlabs-puppet_agent/blob/master/manifests/prepare/puppet_config.pp Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-3450) The module tool should embed and use the root CAs it cares about
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3450 The module tool should embed and use the root CAs it cares about Change By: Steve Barlow Sprint: Windows 2015-08- 12 26 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4683) repair winrm/winrm-fs gem
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4683 repair winrm/winrm-fs gem Change By: Steve Barlow Sprint: Windows 2015-07-01, Windows 2015-07-15, Windows 2015-08- 12 26 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4954) filebucket fails when environment is specified
Title: Message Title
Ben Ford updated an issue
Puppet / PUP-4954
filebucket fails when environment is specified
Change By:
Ben Ford
If the agent's `puppet.conf` specifies an environment and the ENC also specifies the environment , then filebucketing fails with an inscrutable error and the run is marked as failed in the Console.{code}root@binford2k:~ # cat /etc/puppetlabs/puppet/puppet.conf# This file can be used to override the default puppet settings.# See the following links for more details on what settings are available:# - https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html# - https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html# - https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html# - https://docs.puppetlabs.com/references/latest/configuration.html[main]server = master.puppetlabs.vmenvironment_timeout = 0environmentpath = /etc/puppetlabs/code/environments[agent]certname = binford2k.puppetlabs.vmenvironment = binford2kroot@binford2k:~ # puppet agent -tInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsInfo: Caching catalog for binford2k.puppetlabs.vmInfo: Applying configuration version '1438197631'Notice: Hello binford2k.puppetlabs.vmNotice: /Stage[main]/Main/Node[default]/Notify[Hello binford2k.puppetlabs.vm]/message: defined 'message' as 'Hello binford2k.puppetlabs.vm'Notice: /Stage[main]/Userprefs::Bash/File[/root/.bashrc.puppet]/content:--- /root/.bashrc.puppet 2015-07-29 19:20:26.719816423 ++++ /tmp/puppet-file20150729-52505-17roz3n 2015-07-29 19:20:34.453201837 +@@ -1,5 +1,3 @@-#boogers- # NOTE: This file is managed by Puppet; any changes you make will be erased. parse_git_branch ()Info: Computing checksum on file /root/.bashrc.puppetError: Could not back up /root/.bashrc.puppet: Could not find a directory environment named 'binford2k' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?Error: Could not back up /root/.bashrc.puppet: Could not find a directory environment named 'binford2k' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?Error: /Stage[main]/Userprefs::Bash/File[/root/.bashrc.puppet]/content: change from {md5}1df06bcfcafd1511cccea89849c37102 to {md5}c81901d08fb7e2c27fff6ca1e450e99e failed: Could not back up /root/.bashrc.puppet: Could not find a directory environment named 'binford2k' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?Info: Stage[main]: Unscheduling all events on Stage[main]Notice: Applied catalog in 1.35 seconds{code}The environment exists and *the file does not get updated*.
Add Comment
Jira (PUP-4757) Update pre-suites to install puppet-agent on "pe" platforms
Title: Message Title
Kevin Imber assigned an issue to Justin Stoller
Justin Stoller, would you take a quick look at this pipeline, to verify that the jobs are in the correct state?
The only difference to the jobs themselves should be that this block should be added between the "Preparing the workspace" and "Resolving dependencies" sections:
export BEAKER_PE_DIR="http://neptune.puppetlabs.lan/2015.2/preview/"
export BEAKER_PUPPET_AGENT_VERSION=$SUITE_VERSION
echo ""
echo "BEAKER_PUPPET_AGENT_VERSION=${BEAKER_PUPPET_AGENT_VERSION}"
export BEAKER_PUPPET_AGENT_SHA=$SUITE_COMMIT
echo ""
echo "BEAKER_PUPPET_AGENT_SHA=${BEAKER_PUPPET_AGENT_SHA}"
I've filed all the tickets that are results of this, and all of the code changes are in, so once you've reviewed this, it should be able to be closed.
Thanks, Kevin
Jira (PUP-4917) puppet resource package does not display McAfee Agent
Title: Message Title Rob Reynolds commented on PUP-4917 Re: puppet resource package does not display McAfee Agent Thank you Paul W. We don't currently look at QuietDisplayName. So I will update this ticket and set it to accepted. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4917) puppet resource package does not display McAfee Agent
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-4917 puppet resource package does not display McAfee Agent Change By: Rob Reynolds Labels: windows Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4917) puppet resource package does not display McAfee Agent
Title: Message Title Rob Reynolds assigned an issue to Unassigned Puppet / PUP-4917 puppet resource package does not display McAfee Agent Change By: Rob Reynolds Assignee: Rob Reynolds Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4917) puppet resource package does not display installs that use QuietDisplayName
Title: Message Title Rob Reynolds commented on PUP-4917 Re: puppet resource package does not display installs that use QuietDisplayName I'm under the impression that this probably affects all versions of Puppet on Windows. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4917) puppet resource package does not display installs that use QuietDisplayName
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-4917 puppet resource package does not display installs that use QuietDisplayName Change By: Rob Reynolds Summary: puppet resource package does not display McAfee Agent installs that use QuietDisplayName Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4917) puppet resource package does not display installs that use QuietDisplayName
Title: Message Title Rob Reynolds commented on PUP-4917 Re: puppet resource package does not display installs that use QuietDisplayName You can see that here: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/windows/package.rb#L16-L26 which calls https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/windows/msi_package.rb#L18-L29 https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/windows/exe_package.rb#L8-L16 Note that we don't look at QuietDisplayName. This should generally be pretty easy to add. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4955) Puppet 3.x ci:test:git pre-suite has implicit dependency on EPEL
Title: Message Title Michael Smith created an issue Puppet / PUP-4955 Puppet 3.x ci:test:git pre-suite has implicit dependency on EPEL Issue Type: Bug Affects Versions: PUP 3.8.1 Assignee: Eric Sorenson Components: Test Infrastructure Created: 2015/07/29 1:53 PM Priority: Normal Reporter: Michael Smith The Puppet 3.x ci:test:git pre-suite has an implicit dependency on EPEL for rubygem-json. This causes an error trying to run 3.x's ci:test:git rake task on a Centos 5 or 6 machine (maybe others). Any solution to this should be done in Puppet pre-suite. We could either enable EPEL, setup the puppetlabs-dep repo before loading package dependencies, or find some way around needing rubygem-json. I vote for loading puppetlabs-dep if that doesn't interfere with testing.
Jira (PUP-4917) puppet resource package does not display installs that use QuietDisplayName
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-4917 puppet resource package does not display installs that use QuietDisplayName Change By: Rob Reynolds Component/s: Types and Providers Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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.
