Jira (PUP-3135) Square brackets in file names not handled properly
Title: Message Title Mario Oschwald created an issue Puppet / PUP-3135 Square brackets in file names not handled properly Issue Type: Bug Affects Versions: 3.6.2 Assignee: Kylo Ginsberg Components: Types and Providers Created: 25/Aug/14 7:07 AM Environment: Puppet 3.6.2 Priority: Normal Reporter: Mario Oschwald When trying to transfer a file (directly or as part of a recursive transfer) using the file resource that contains a square bracket '[' character. This issue arose when automating a cygwin installation where files like [.exe and [.1.gz are part of the regular installation. This issue seems related to PUP-2700 , unfortunately many special characters were tested there with the exception of square brackets. If I understand correctly though the fix supplied there is not available in 3.6.2 and may well work also for square brackets. Reproducing is trivial:
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Kylo Ginsberg commented on an issue Re: Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb I assigned this ticket to 3.7.0 just to get it on our radar. But AFAICT it's not something functional so we could certainly kick this can down the road. Add Comment Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Just recently there have been a few intermittent failures in resource/service/ticket_14297_handle_upstart.rb. (Btw note that this test is confined to Ubuntu.) Three examples: https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-4.0/label=acc-coord,platform=precise/212/consoleFull https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Issue Type: Bug Assignee: Unassigned Created: 25/Aug/14 7:53 AM Priority: Normal Reporter: Kylo Ginsberg Just recently there have been a few intermittent failures in resource/service/ticket_14297_handle_upstart.rb. (Btw note that this test is confined to Ubuntu.) Three examples: https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-4.0/label=acc-coord,platform=precise/212/consoleFull https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/job/Puppet-Package-Acceptance-master/787/label=acc-coord,platform=lucid/consoleText https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/job/Puppet-Package-Acceptance-master/786/label=acc-coord,platform=precise_and_lucid/consoleText In all 3 of these cases the test fails trying to manage the apache service on the master. Add Comment
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Kylo Ginsberg commented on an issue Re: Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Joshua Partlow one speculation here is that this has something to do with the recent add of passenger-based testing. I.e. is the start/stop of the apache service on the master a problem in the passenger scenario? I haven't looked into this at all, so just floating the idea. Add Comment Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Just recently there have been a few intermittent failures in resource/service/ticket_14297_handle_upstart.rb. (Btw note that this test is confined to Ubuntu.) Three examples: https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-4.0/label=acc-coord,platform=precise/212/consoleFull https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To
Jira (PUP-3129) Deprecate hidden _timestamp fact
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-3129 Deprecate hidden _timestamp fact Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3129) Deprecate hidden _timestamp fact
Title: Message Title Kurt Wall commented on an issue Re: Deprecate hidden _timestamp fact Henrik Lindberg Making sure I understand: $timestamp _is present in 3.7, but deprecated, so I should see a deprecation warning unless I have disable_warnings set. In addition, it is not in $facts, but only as a top-scope $::_timestamp. In 4.0, _timestamp will be removed completely. Add Comment Puppet / PUP-3129 Deprecate hidden _timestamp fact This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3117) Resource Expression Enhancements
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-3117 Resource _expression_ Enhancements Change By: Henrik Lindberg Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2914) Update packages to use RGen 0.7.0
Title: Message Title
Henrik Lindberg commented on an issue
Re: Update packages to use RGen 0.7.0
I expect it to pick the system installed version over the vendored (it is appended to the path). We have a version assertion in the code when Rgen is loaded that checks that it has certain features - if not, user is told to install 0.7.0.
That should probably be changed to uninstall or upgrade since Puppet now comes with Rgen.
Add Comment
Puppet / PUP-2914
Update packages to use RGen 0.7.0
PUP-2831 updated puppet to work with rgen 0.7.0. Before those fixes it made some mistakes that caused 0.7.0 to create issues, which might cause a problem for old packages of puppet that simply rely on {{= 0.6.5}}. We need to update the various packages that we make to depend on 0.7.0 and publish an RGen 0.7.0 package.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to
Jira (PUP-3129) Deprecate hidden _timestamp fact
Title: Message Title Kurt Wall updated an issue Puppet / PUP-3129 Deprecate hidden _timestamp fact Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3129) Deprecate hidden _timestamp fact
Title: Message Title Kurt Wall updated an issue Puppet / PUP-3129 Deprecate hidden _timestamp fact Change By: Kurt Wall QA Contact: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2040) Allow excluding content from Puppet module tool built packages
Title: Message Title Anderson Mills assigned an issue to Anderson Mills Puppet / PUP-2040 Allow excluding content from Puppet module tool built packages Change By: Anderson Mills Assignee: AndersonMills Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2040) Allow excluding content from Puppet module tool built packages
Title: Message Title
Kurt Wall commented on an issue
Re: Allow excluding content from Puppet module tool built packages
Anderson Mills It isn't entirely clear to me what was fixed here. The PR was closed w/out a merge. Should this be closed will-not-fix in favor of PE-3113?
Add Comment
Puppet / PUP-2040
Allow excluding content from Puppet module tool built packages
Puppet module tool only excludes some files from built tarball {{.\*, ~\*, pkg, ...}} The result is that module tarballs could have spec files, fixtures, and any temporary files created during build It should allow excluding content with {{puppet module build --exclude PATTERN1,PATTERN2,...}}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2040) Allow excluding content from Puppet module tool built packages
Title: Message Title
Kurt Wall commented on an issue
Re: Allow excluding content from Puppet module tool built packages
I found Brandon's PR. Ignore previous comment.
Add Comment
Puppet / PUP-2040
Allow excluding content from Puppet module tool built packages
Puppet module tool only excludes some files from built tarball {{.\*, ~\*, pkg, ...}} The result is that module tarballs could have spec files, fixtures, and any temporary files created during build It should allow excluding content with {{puppet module build --exclude PATTERN1,PATTERN2,...}}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2040) Allow excluding content from Puppet module tool built packages
Title: Message Title
Anderson Mills commented on an issue
Re: Allow excluding content from Puppet module tool built packages
Kurt Wall, also, just to be clear, this PR failed a functional review (because it doesn't ignore symlinks). I'm working on it now.
Add Comment
Puppet / PUP-2040
Allow excluding content from Puppet module tool built packages
Puppet module tool only excludes some files from built tarball {{.\*, ~\*, pkg, ...}} The result is that module tarballs could have spec files, fixtures, and any temporary files created during build It should allow excluding content with {{puppet module build --exclude PATTERN1,PATTERN2,...}}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3129) Deprecate hidden _timestamp fact
Title: Message Title Kylo Ginsberg commented on an issue Re: Deprecate hidden _timestamp fact @krw there's no deprecation warning, it will just be documented in release notes (by way of this ticket). Add Comment Puppet / PUP-3129 Deprecate hidden _timestamp fact This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3127) LDAP - introduce LDAP-Certificat Directory
Title: Message Title
Andreas Schuster commented on an issue
Re: LDAP - introduce LDAP-Certificat Directory
created pull request
Add Comment
Puppet / PUP-3127
LDAP - introduce LDAP-Certificat Directory
For *Solaris* based systems it is necessary to establisch the connection to the ldap server a little bit different then for e.g. Linux based systems. Therefore it is necessary to introduce this new config variable {{'ldapcrtdir'}} that allows the use of the server specific ldap certificates. On Solaris it points to {{/var/ldap}}. If {{ldapssl}} is se...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3069) Use a manifest setting in [master] as global manifests
Title: Message Title Joshua Partlow commented on an issue Re: Use a manifest setting in [master] as global manifests So, we would like to have a simple either or behavior: If environment-specific manifest, use that else use default_manifest. But it's actually more complicated because every directory environment already has it's own implicit $path_to_env/manifests directory. We can check to see if that directory exists, or if it has *.pp files in it, at the time of env initialization, but you will need to restart the puppet master or wait for an environment timeout to see a change if you have default_manifest set, and you want to specialize an existing environment by adding manifests to it's env specific default master dir. I guess that's no different than if you were to change the explicit environment.conf manifest setting. The logic that we are currently testing is: if environment.conf manifest setting is set, use that else if we see *.pp files in the implicit $path_to_env/manifests directory, use that else if default_manifest is set, use that else fallback to $path_to_env/manifests Add Comment Puppet / PUP-3069 Use a manifest setting in [master] as global manifests In some puppet installations, especially when an ENC is in use, there are not really any environment specific manifests. Instead the ENC controls all of the classes that are included for a node. However, there is still some global setup that needs to take place outside of the ENC. One example of this is globally setting up a filebucket for all file resour...
Jira (PUP-3129) Deprecate hidden _timestamp fact
Title: Message Title
Kurt Wall commented on an issue
Re: Deprecate hidden _timestamp fact
Thanks Kylo Ginsberg. Verified in master at SHA=fd95196c5592e154e98b32262872c58276fc79a1. _timestamp is present as a top-scope variable but not in the $facts hash:
$ be puppet apply --trusted_node_data --parser future -e 'notify { $::_timestamp: }'
Notice: Compiled catalog for breve.corp.puppetlabs.net in environment production in 0.37 seconds
Notice: 2014-08-25 10:10:23 -0700
Notice: /Stage[main]/Main/Notify[2014-08-25 10:10:23 -0700]/message: defined 'message' as '2014-08-25 10:10:23 -0700'
Notice: Finished catalog run in 0.02 seconds
$ be puppet apply --trusted_node_data --parser future -e 'notify { $facts[_timestamp]: }'
Error: Evaluation Error: Missing title. The title _expression_ resulted in undef at line 1:10 on node breve.corp.puppetlabs.net
Error: Evaluation Error: Missing title. The title _expression_ resulted in undef at line 1:10 on node breve.corp.puppetlabs.net
Add Comment
Puppet / PUP-3129
Deprecate hidden _timestamp fact
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To
Jira (PUP-2914) Update packages to use RGen 0.7.0
Title: Message Title
Moses Mendoza commented on an issue
Re: Update packages to use RGen 0.7.0
hmm, never mind, we probably don't want to remove system rgen if the user has it there for other purposes..
Add Comment
Puppet / PUP-2914
Update packages to use RGen 0.7.0
PUP-2831 updated puppet to work with rgen 0.7.0. Before those fixes it made some mistakes that caused 0.7.0 to create issues, which might cause a problem for old packages of puppet that simply rely on {{= 0.6.5}}. We need to update the various packages that we make to depend on 0.7.0 and publish an RGen 0.7.0 package.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2914) Update packages to use RGen 0.7.0
Title: Message Title
Moses Mendoza commented on an issue
Re: Update packages to use RGen 0.7.0
Matthaus Owens We may want to update the packaging to conflict/obsolete rgen? Can we have rgen-old automatically removed on install of puppet without advertising that we provide rgen?
Add Comment
Puppet / PUP-2914
Update packages to use RGen 0.7.0
PUP-2831 updated puppet to work with rgen 0.7.0. Before those fixes it made some mistakes that caused 0.7.0 to create issues, which might cause a problem for old packages of puppet that simply rely on {{= 0.6.5}}. We need to update the various packages that we make to depend on 0.7.0 and publish an RGen 0.7.0 package.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3069) Use a manifest setting in [master] as global manifests
Title: Message Title James Sweeny commented on an issue Re: Use a manifest setting in [master] as global manifests So, prior to directory environments, there are two ways site.pp can be specified: 1) $confdir/manifests/site.pp 2) $confdir/environments/$environment/site.pp In both cases, site.pp was a configurable name. PE users of (2) needed to replicate default resources into each environment, and though I don't know of any complaints, the way PE included filebucket was a common gotcha. Users of (1) are able to have a global site.pp that lacks environment-based promotion, but can be set by a group separate from the ones releasing control repositories. I argue that we need to preserve the old capabilities, and clearly document PE-specific gotchas to close this. I propose: 1) Bring back the manifest option in puppet.conf, with the same behavior it has pre-3.6. This would be applied as the default manifest in all environments, regardless of any configurations in respective environment.conf files. Throw warnings if an environment.conf tries to override, or if puppet.conf's manifest contains $environment. 2) Add a default_manifest option in puppet.conf which acts as a fallback if neither puppet.conf nor environment.conf specify manifest. Warn or error if puppet.conf specifies both. For both items proposed above, a precedence configurable in puppet.conf would be nice, but not mandatory. For item (1) proposed above, we should provide documented recommendations for companies that wish to allow the environment to specify a default manifest of its own. I would imagine this to involve creating a module in the environment that acts as a replacement site.pp with the owner of puppet.conf's site.pp including class with an internally agreed on name (e.g., include acme_base). This is just my opinion. The only thing I would fight strongly for is that users not lose any capabilities that existed prior to directory environments. Add Comment Puppet / PUP-3069 Use a manifest setting in [master] as global manifests
Jira (PUP-3032) Setting to cache `load_library` failures
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-3032 Setting to cache `load_library` failures Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2914) Update packages to use RGen 0.7.0
Title: Message Title
Michael Stahnke commented on an issue
Re: Update packages to use RGen 0.7.0
It does seem like puppet should prefer the vendored version of it's libs rather than system libs. I would assume we know what we're doing when we vendor stuff so it's more likely to be correct than some random package from a distribution (or us). Should that be a different bug? Henrik Lindberg
Add Comment
Puppet / PUP-2914
Update packages to use RGen 0.7.0
PUP-2831 updated puppet to work with rgen 0.7.0. Before those fixes it made some mistakes that caused 0.7.0 to create issues, which might cause a problem for old packages of puppet that simply rely on {{= 0.6.5}}. We need to update the various packages that we make to depend on 0.7.0 and publish an RGen 0.7.0 package.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-3069) Use a manifest setting in [master] as global manifests
Title: Message Title Nicholas Fagerlund commented on an issue Re: Use a manifest setting in [master] as global manifests Docs weighing in, sorry it took me a minute to get to this. Joshua Partlow, for the effect you're describing here, the name default_manifest works fine. (It sounds like we're still wrangling over the effect, though.) Option 1 in James' comment above sounds fiendishly difficult to document and comprehend. I can go into why if it isn't clear. Add Comment Puppet / PUP-3069 Use a manifest setting in [master] as global manifests In some puppet installations, especially when an ENC is in use, there are not really any environment specific manifests. Instead the ENC controls all of the classes that are included for a node. However, there is still some global setup that needs to take place outside of the ENC. One example of this is globally setting up a filebucket for all file resour... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1527) After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
Title: Message Title
Nicholas Fagerlund commented on an issue
Re: After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
Kurt Wall I'm not the one to ask! I was trying to find that out myself. But yes, that's what I understand from Adrien's response.
Add Comment
Puppet / PUP-1527
After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
gtAfter upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources, data taken from hiera. When hiera has the following data: check_apt_security : { check_command : check_nrpe_1arg!check_apt_security, contact_groups : sladmins, normal_check_interval : 10, ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more
Jira (PUP-3137) expiry parameter definition in user resource documentation needs update
Title: Message Title Carthik Sharma moved an issue Puppet / PUP-3137 expiry parameter definition in user resource documentation needs update Change By: Carthik Sharma Workflow: Education Platform Workflow Key: LEARNVM PUP - 53 3137 Project: LearningVM Puppet Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3137) expiry parameter definition in user resource documentation needs update
Title: Message Title Carthik Sharma commented on an issue Re: expiry parameter definition in user resource documentation needs update Here's a PR that addresses the concern: https://github.com/puppetlabs/puppet/pull/3013 Thanks! Add Comment Puppet / PUP-3137 expiry parameter definition in user resource documentation needs update When running through the Resource quest and reading expiry parameter portion from the output of 'puppet describe user' one sees: snipped - **expiry** The expiry date for this user. Must be provided in a zero-padded -MM-DD format --- e.g. 2010-02-19. If you want to make sure the user account does never expire, you can pass the... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (FACT-664) Is the code ready for release?
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-664 Is the code ready for release? Change By: Kylo Ginsberg Alltests(spec,acceptance)shouldbepassingonallplatformsforbothstablemaster. *Ifanewplatformhasbeenadded,makesurethatplatformhasacceptancetesting,newfeatureshavedecentcoverage,etc.etc. *Ifthereleaseisgoingtobecutfromasha,ratherthantheheadofabranch,makesurethatshaspecificallyhasgonethroughspec/acceptance/etc.tests *MoveallitemsthatshouldbemovedfromReadyforCItoReadyforReview Haveallticketsbeenresolved(passedFunctionalReview)?Ifnotpleaseaddanymissingticketstothecurrentsprint'sboard. NOTE:ThislinkmaynotworkproperlyforRCreleases.Editittoremovethe-rc#.https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20FACT%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%222.2.0%22 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3069) Use a manifest setting in [master] as global manifests
Title: Message Title Joshua Partlow commented on an issue Re: Use a manifest setting in [master] as global manifests Hi James Sweeny, thanks for taking the time to respond; I have some questions and clarifications below: So, prior to directory environments, there are two ways site.pp can be specified:1) $confdir/manifests/site.pp via the manifest setting 2) $confdir/environments/$environment/site.pp via the manifest setting with an interpolated $environment, aka dynamic environments and then there was a third way: 3) The manifest setting in an [envname] puppet.conf section if $environment == 'envname', which is what we've been calling legacy environments. Maybe this case never comes up for professional PE deployments? But I didn't want to leave it out in case it has other issues. In both cases, site.pp was a configurable name. PE users of (2) needed to replicate default resources into each environment, and though I don't know of any complaints, the way PE included filebucket was a common gotcha. James Sweeny can you clarify for me here; are you saying that PE users who began using dynamic environments had to account for PE expecting to have certain resources commonly loaded via $confdir/manifests/site.pp? And if so, what was/is the work around there? Users of (1) are able to have a global site.pp that lacks environment-based promotion, but can be set by a group separate from the ones releasing control repositories. I argue that we need to preserve the old capabilities, and clearly document PE-specific gotchas to close this. What I understand about this issue from you and Eric Sorenson is that this is an authorization issue. Some customers expect that they can have two different authorized roles; one which has authority over puppet.conf and which can declare a global manifest and enc, and another role or roles which can make per environment module changes? And the problem with directory environments for these customers, is that it allows the environment role to control the manifest? I propose:1) Bring back the manifest option in puppet.conf, with the same behavior it has pre-3.6. This would be applied as the default manifest in all environments, regardless of any configurations in respective environment.conf files. Throw warnings if an environment.conf tries to override, or if puppet.conf's manifest contains $environment. But what you're asking for here is both to bring back the old setting and give it new semantics as an uber manifest setting at the same time. Both for documenation confusion and just the implementation difficulty, I don't think we should do this. But is there a different setting we need to add...or, first, am I right that what you are looking for here is an 'overridding_manifest' which would take precedence over any environment specific one? 2) Add a default_manifest option in puppet.conf which acts as a fallback if neither puppet.conf nor environment.conf specify manifest. Warn or error if puppet.conf specifies both. To some extent, this already exists, but it is per environment. If environment.conf does not specify a manifest, it is $path_to_env/manifest. Is the problem here that if a customer has defaults they must be placed in each environment/manifest dir? Or that the
Jira (PUP-3069) Use a manifest setting in [master] as global manifests
Title: Message Title James Sweeny commented on an issue Re: Use a manifest setting in [master] as global manifests via the manifest setting with an interpolated $environment, aka dynamic environments and then there was a third way: 3) The manifest setting in an [envname] puppet.conf section if $environment == 'envname', which is what we've been calling legacy environments. Maybe this case never comes up for professional PE deployments? But I didn't want to leave it out in case it has other issues. Yes, agreed there is a third way. I didn't mention it because it is basically a subset of dynamic environments, and its functionality is mostly easily recreated in directory environments now. In both cases, site.pp was a configurable name. PE users of (2) needed to replicate default resources into each environment, and though I don't know of any complaints, the way PE included filebucket was a common gotcha. James Sweeny can you clarify for me here; are you saying that PE users who began using dynamic environments had to account for PE expecting to have certain resources commonly loaded via $confdir/manifests/site.pp? And if so, what was/is the work around there? Correct, specifically the default filebucket, and the filebucket configured as a File resource default in site.pp. The workaround for the original case, and in directory environments, is to instruct users that those items need to be included if they deviate from the default manifest. Users of (1) are able to have a global site.pp that lacks environment-based promotion, but can be set by a group separate from the ones releasing control repositories. I argue that we need to preserve the old capabilities, and clearly document PE-specific gotchas to close this. What I understand about this issue from you and Eric Sorenson is that this is an authorization issue. Some customers expect that they can have two different authorized roles; one which has authority over puppet.conf and which can declare a global manifest and enc, and another role or roles which can make per environment module changes? And the problem with directory environments for these customers, is that it allows the environment role to control the manifest? Yep. I propose: 1) Bring back the manifest option in puppet.conf, with the same behavior it has pre-3.6. This would be applied as the default manifest in all environments, regardless of any configurations in respective environment.conf files. Throw warnings if an environment.conf tries to override, or if puppet.conf's manifest contains $environment. But what you're asking for here is both to bring back the old setting and give it new semantics as an uber manifest setting at the same time. Both for documenation confusion and just the implementation difficulty, I don't think we should do this. But is there a different setting we need to add...or, first, am I right that what you are looking for here is an 'overridding_manifest' which would take precedence over any environment specific one?
Jira (FACT-669) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-669 Is the Jira tidy-up done for this release and prepared for the next one? Change By: Adrien Thebo Assignee: KyloGinsberg AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-617) Facter README.md should express semver/support
Title: Message Title Adrien Thebo updated an issue Facter / FACT-617 Facter README.md should express semver/support Change By: Adrien Thebo Fix Version/s: 2.2.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-637) Add lsbminordistrelease fact
Title: Message Title William Hopper commented on an issue Re: Add lsbminordistrelease fact This was merged at https://github.com/puppetlabs/facter/commit/407550b2d775e47497574c0c3bf18a82c2be61d1 Add Comment Facter / FACT-637 Add lsbminordistrelease fact This was originally added in https://github.com/puppetlabs/facter/pull/424 but was orphaned by the facter-2 branch work. Looks like a clean cherry-pick so let's pull it into facter 2.2 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-637) Add lsbminordistrelease fact
Title: Message Title William Hopper updated an issue Facter / FACT-637 Add lsbminordistrelease fact Change By: William Hopper Fix Version/s: 2.2.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-606) Remove sid/unstable from build_defaults
Title: Message Title Michael Smith updated an issue Facter / FACT-606 Remove sid/unstable from build_defaults Change By: Michael Smith Fix Version/s: 2.2.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-637) Add lsbminordistrelease fact
Title: Message Title William Hopper updated an issue Facter / FACT-637 Add lsbminordistrelease fact Change By: William Hopper Affects Version/s: 2.2.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2914) Update packages to use RGen 0.7.0
Title: Message Title
Henrik Lindberg commented on an issue
Re: Update packages to use RGen 0.7.0
I have not yet tried what happens and may have misspoken. It all depends on when the vendored libraries are added to the path. A ticket may be good anyway, since even if vendored have precedence, we may still want to have a discussion and record the decision.
Add Comment
Puppet / PUP-2914
Update packages to use RGen 0.7.0
PUP-2831 updated puppet to work with rgen 0.7.0. Before those fixes it made some mistakes that caused 0.7.0 to create issues, which might cause a problem for old packages of puppet that simply rely on {{= 0.6.5}}. We need to update the various packages that we make to depend on 0.7.0 and publish an RGen 0.7.0 package.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options,
Jira (PUP-3069) Use a manifest setting in [master] as global manifests
Title: Message Title Joshua Partlow commented on an issue Re: Use a manifest setting in [master] as global manifests Thanks for the quick answers, James Sweeny The problem is that customers would need to create default manifests in each environment, where it would not be strictly necessary from their perspective. The situation to imagine is a large customer where some groups can define their own environments, but are ignorant to many of the core we need to do this to make puppet work in our infrastructure requirements. In this situation (where, say, a group is creating an environment that only manages their subset of servers), any changes that should affect all puppet users at the company would need to be repeated by each environment user (who likely doesn't need to know or care). What's the current work around for this case? Is it just to set puppet.conf 'manifest' to something static '/our/absolute/manifests/site.pp' and the individual environments have an agreed upon classname convention for a class that always gets picked up from an environment (as I think you described in your first post?) Add Comment Puppet / PUP-3069 Use a manifest setting in [master] as global manifests In some puppet installations, especially when an ENC is in use, there are not really any environment specific manifests. Instead the ENC controls all of the classes that are included for a node. However, there is still some global setup that needs to take place outside of the ENC. One example of this is globally setting up a filebucket for all file resour...
Jira (PUP-3069) Use a manifest setting in [master] as global manifests
Title: Message Title James Sweeny commented on an issue Re: Use a manifest setting in [master] as global manifests What's the current work around for this case? Is it just to set puppet.conf 'manifest' to something static '/our/absolute/manifests/site.pp' and the individual environments have an agreed upon classname convention for a class that always gets picked up from an environment (as I think you described in your first post?) Yep, the current workaround (and I can think of customers who do this) is to not let environments have a site.pp at all, and basically do: modulepath=.../environments/$environment/modules manifest = $confdir/manifests/site.pp In my experience, sites doing this do not classify from site.pp, and use an ENC. If they weren't using an ENC though, I'd think the workaround would be include $::role in the global site.pp or something with hiera_include. Add Comment Puppet / PUP-3069 Use a manifest setting in [master] as global manifests In some puppet installations, especially when an ENC is in use, there are not really any environment specific manifests. Instead the ENC controls all of the classes that are included for a node. However, there is still some global setup that needs to take place outside of the ENC. One example of this is globally setting up a filebucket for all file
Jira (PUP-731) Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments
Title: Message Title Jon McKenzie commented on an issue Re: Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments As an interim step, would it at least be possible to notify (e.g. via debug messages) that distributed lib has been loaded more than once, or to specify the path of the lib that was loaded? We ran into a similar issue in our environment, and the error messages (which essentially boiled down to 'invalid parameter' messages) were extremely unhelpful in determining the ultimate root cause. Add Comment Puppet / PUP-731 Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments Quoted from a previous ticket, #4409 The key problem is that a master can’t reliably distinguish between two versions of the same native type that are used in different environments (or between an environment which uses a native type and an environment which doesn’t). This is due to the fact that native types are defined using ruby code, which the mast... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because
Jira (PUP-3138) improve spec functions produces and fails in language.rb
Title: Message Title
Henrik Lindberg created an issue
Puppet / PUP-3138
improve spec functions produces and fails in language.rb
Issue Type:
Improvement
Assignee:
Unassigned
Created:
25/Aug/14 1:06 PM
Fix Versions:
4.0.0
Priority:
Normal
Reporter:
Henrik Lindberg
The spec functions produces and fails makes it easy to write spec tests by giving it a hash of puppet source to expected results (a value or an error respectively for the two functions).
The wanted improvement is when the expectancy is not met. Since the function runs its own spec test, the error is reported as originating from language.rb and there is no trace of which test called it except for the source string being tested.
Earlier when the loop was performed in the file doing the source to expectancy mapping there was at least a reference to the file / line in the loop.
The current way the failure appears when reported makes it hard to figure out where the problem is.
The output may look like this:
1) Puppet resource expressions future parser parameters fails to evaluate notify { title: message = oops, * = { hash = value } } with message (?-mix:Invalid parameter hush)
Failure/Error: expect do
expected Puppet::Error with message matching /Invalid parameter hush/, got #Puppet::Error: Invalid parameter hash on Notify[title] at line 1 on node foonode with backtrace:
# ./lib/puppet/resource.rb:506:in `validate_parameter'
#
Jira (FACT-672) Smoke test packages
Title: Message Title Melissa Stone commented on an issue Re: Smoke test packages packages available at http://builds.puppetlabs.lan/facter/2.2.0/ Add Comment Facter / FACT-672 Smoke test packages 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). If this is a final release then the previous RC (which should be identical to what is currently being released) will have gone through th... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-672) Smoke test packages
Title: Message Title Kylo Ginsberg commented on an issue Re: Smoke test packages I'll take osx. Add Comment Facter / FACT-672 Smoke test packages 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). If this is a final release then the previous RC (which should be identical to what is currently being released) will have gone through th... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3069) Use a manifest setting in [master] as global manifests
Title: Message Title Joshua Partlow commented on an issue Re: Use a manifest setting in [master] as global manifests Ok, folks, so I think we need two settings, but I'm proposing that the second one be a switch for specifying whether or not per environment manifests are allowed. So in puppet.conf: allow_per_directory_manifests (defaults true) default_manifest (defaults to ) If allow_per_directory_manifest is set to false, then it is an initialization error if default_manifest is not set to something. (Whether or not that path exists/points to an actual directory or 'pp' file is a different question, and not an error, but we at least want to be able to have meaningful output when someone makes a v2.0/environments API call) The logic for how an environment manifest is set would be: if not allow_per_directory_manifests then default_manifest else if environment.conf manifest then use that else if we see *.pp files in the implicit $path_to_env/manifests directory, use that else if default_manifest is set, use that else fall back to $path_to_env/manifests Alternatively if not allow_per_directory_manifests then default_manifest else if environment.conf manifest then use that else if default_manifest is set use that else fall back to $path_to_env/manifests This later case is cleaner to implement, but I'm not sure if it easier to describe or less surprising from a user's perspective? @eric, @james, @beard, @nick what do you think? If I tried for English for the alternative case, it would be: If the allow_per_directory_manifests is set to false, then the default_manifest must be set, and that will be what is used in every environment. When allow_per_directory_manifests is true, and manifest is set in a directory environment's environment.conf, then it will be used in that specific environment. Otherwise, if the global puppet.conf default_manifest has been set, it will be used, and if nothing has been set in either puppet.conf or the directory environment's environment.conf, then the default per environment manifest directory will be used. Note that a global default_manifest setting prevents manifests in the default per environment manifest directory from being used. The fact that we will have a default_manifest in puppet.conf, and an implicit default manifest per directory environment makes it hard to talk about. I honestly don't know which is better. Without default_manifest set, you get the per directory environment manifest, whether from the implicit path or explicit environment.conf manifest setting. With default_manifest set, which takes precedence? puppet.conf's default_manifest or the existence of pp files in the implicit per directory manifest directory? Add Comment
Jira (PUP-3138) improve spec functions produces and fails in language.rb
Title: Message Title Henrik Lindberg commented on an issue Re: improve spec functions produces and fails in language.rb Also, if the expected _expression_ has a syntax error it may be hard to figure out where the error is coming from. Thus, the expectancy should be parsed and validated separately before evaluating it to ensure it is correct. Add Comment Puppet / PUP-3138 improve spec functions produces and fails in language.rb The spec functions produces and fails makes it easy to write spec tests by giving it a hash of puppet source to expected results (a value or an error respectively for the two functions). The wanted improvement is when the expectancy is not met. Since the function runs its own spec test, the error is reported as originating from language.rb and ther... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-3138) improve spec functions produces and fails in language.rb
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3138 improve spec functions produces and fails in language.rb Change By: Henrik Lindberg Component/s: TestInfrastructure Component/s: Server Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3140) Illegal number error should include the faulty number
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-3140 Illegal number error should include the faulty number Issue Type: Improvement Assignee: Andy Parker Components: DSL Created: 25/Aug/14 1:52 PM Fix Versions: 4.0.0 Priority: Normal Reporter: Henrik Lindberg When a faulty number is entered, say 42g the error message simply says Illegal number. It does give the line/offset, but it would be nice to also include the string that should have been a number. maybe also add, if a string value was intended, enclose the value in quotes. Add Comment
Jira (PUP-3131) Registry not reading back proper value for binary.
Title: Message Title Ethan Brown commented on an issue Re: Registry not reading back proper value for binary. It took a bit of discovery, but this set of build results highlights the issue under Windows 2012 x64 with an x64 Puppet build: http://jenkins-modules.delivery.puppetlabs.net/view/registry/view/old/job/puppetlabs-registry%20system%20FOSS%20x64/PLATFORM_CONFIG=windows-2012-64a,PUPPET_VERSION=3.6.2-1066-g5010aba-x64,SLAVE_LABEL=bundler/1/console Test Case ./acceptance/tests/resource/registry/should_manage_values.rb reported: #MiniTest::Assertion: Expected output to contain /Registry_value\[HKLM.Software.Vendor.PuppetLabsTest\w+\\SubKey1\\ValueBinary2\].data: data changed 'de ad be ef ca f1' to 'de ad be ef ca f2'/.. Expected /Registry_value\[HKLM.Software.Vendor.PuppetLabsTest\w+\\SubKey1\\ValueBinary2\].data: data changed 'de ad be ef ca f1' to 'de ad be ef ca f2'/ to match \e[0;32mInfo: Loading facts\e[0m\n\e[mNotice: Compiled catalog for oew5dl897os7n2g.delivery.puppetlabs.net in environment production in 0.33 seconds\e[0m\n\e[0;32mInfo: Applying configuration version '1408773546'\e[0m\n\e[mNotice: fact_phase: 2\e[0m\n\e[mNotice: /Stage[main]/Main/Notify[fact_phase]/message: defined 'message' as 'fact_phase: 2'\e[0m\n\e[mNotice: /Stage[main]/Main/Registry_value[32:HKLM\\Software\\Vendor\\PuppetLabsTest_Value_7XM4av8K\\SubKey1\\ValueArray4]/data: data changed 'Should be an array L1 phase=1,Should be an array L2 phase=1' to 'Should be an array L1 phase=2,Should be an array L2 phase=2'\e[0m\n\e[mNotice: /Stage[main]/Main/Registry_value[32:HKLM\\Software\\Vendor\\PuppetLabsTest_Value_7XM4av8K\\SubKey1\\ValueString2]/data: data changed 'Should be a string phase=1' to 'Should be a string phase=2'\e[0m\n\e[mNotice: /Stage[main]/Main/Registry_value[32:HKLM\\Software\\Vendor\\PuppetLabsTest_Value_7XM4av8K\\SubKey1\\ValueArray2]/data: data changed 'Should be an array L1 phase=1' to 'Should be an array L1 phase=2'\e[0m\n\e[mNotice: /Stage[main]/Main/Registry_value[32:HKLM\\Software\\Vendor\\PuppetLabsTest_Value_7XM4av8K\\SubKey1\\ValueBinary1]/data: data changed '01' to '02'\e[0m\n\e[mNotice: /Stage[main]/Main/Registry_value[32:HKLM\\Software\\Vendor\\PuppetLabsTest_Value_7XM4av8K\\SubKey1\\ValueArray1]/data: data changed 'Should be an array L1 phase=1' to 'Should be an array L1 phase=2'\e[0m\n\e[mNotice: /Stage[main]/Main/Registry_value[32:HKLM\\Software\\Vendor\\PuppetLabsTest_Value_7XM4av8K\\SubKey1\\ValueArray3]/data: data changed 'Should be an array L1 phase=1,Should be an array L2 phase=1' to 'Should be an array L1 phase=2,Should be an array L2 phase=2'\e[0m\n\e[mNotice: /Stage[main]/Main/Registry_value[32:HKLM\\Software\\Vendor\\PuppetLabsTest_Value_7XM4av8K\\SubKey1\\ValueBinary2]/data: data changed 'de be ef ca' to 'de ad be ef ca f2'\e[0m\n\e[mNotice: /Stage[main]/Main/Registry_value[32:HKLM\\Software\\Vendor\\PuppetLabsTest_Value_7XM4av8K\\SubKey1\\ValueArray5]/data: data changed 'Should be an array L1 phase=1,Should be an array L2 phase=1' to 'Should be an array L1 phase=2,Should be an array L2 phase=2'\e[0m\n\e[mNotice: /Stage[main]/Main/Registry_value[32:HKLM\\Software\\Vendor\\PuppetLabsTest_Value_7XM4av8K\\SubKey1\\ValueExpand2]/data: data changed '%SystemRoot% - Should be a REG_EXPAND_SZ phase=1' to '%SystemRoot% - Should be a REG_EXPAND_SZ phase=2'\e[0m\n\e[mNotice: /Stage[main]/Main/Registry_value[32:HKLM\\Software\\Vendor\\PuppetLabsTest_Value_7XM4av8K\\SubKey1\\ValueString4]/data: data changed 'Should be a string phase=1' to 'Should be a string phase=2'\e[0m\n\e[mNotice: /Stage[main]/Main/Registry_value[32:HKLM\\Software\\Vendor\\PuppetLabsTest_Value_7XM4av8K\\SubKey1\\ValueString3]/data: data changed 'Should be a string phase=1' to 'Should be a string
Jira (PUP-3131) Registry not reading back proper value for binary.
Title: Message Title
Ethan Brown commented on an issue
Re: Registry not reading back proper value for binary.
Relevant acceptance tests are at https://github.com/puppetlabs/puppetlabs-registry/blob/96868f1a762820d3ab51865efd986754820cb043/acceptance/tests/resource/registry/should_manage_values.rb#L184-L202
Add Comment
Puppet / PUP-3131
Registry not reading back proper value for binary.
Query truncates after 14 characters Notice: /Stage[main]/Main/Registry_value[HKLM\SOFTWARE\Puppet Labs\Puppet\SubKey1\ValueBinary2]/data: data changed 'de b e ef ca' to 'de ad be ef ca f2' also case sensitive. registry_value { 'HKLM\SOFTWARE\Puppet Labs\Puppet\SubKey1\ValueBinary2': type = binary, data ="" DE AD BE EF CA } Notice: /...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (FACT-669) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Adrien Thebo commented on an issue Re: Is the Jira tidy-up done for this release and prepared for the next one? Facter 2.3.0 version already exists: https://tickets.puppetlabs.com/browse/FACT/fixforversion/11855 Add Comment Facter / FACT-669 Is the Jira tidy-up done for this release and prepared for the next one? 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... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-669) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Adrien Thebo commented on an issue Re: Is the Jira tidy-up done for this release and prepared for the next one? Facter 2.2.1: https://tickets.puppetlabs.com/browse/FACT/fixforversion/11910 Add Comment Facter / FACT-669 Is the Jira tidy-up done for this release and prepared for the next one? 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... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-669) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Adrien Thebo commented on an issue Re: Is the Jira tidy-up done for this release and prepared for the next one? 2.2.0 version marked as released. Add Comment Facter / FACT-669 Is the Jira tidy-up done for this release and prepared for the next one? 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... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-669) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Adrien Thebo commented on an issue Re: Is the Jira tidy-up done for this release and prepared for the next one? Introduced in 2.2.0: https://tickets.puppetlabs.com/issues/?filter=12623 Add Comment Facter / FACT-669 Is the Jira tidy-up done for this release and prepared for the next one? 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... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-669) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Adrien Thebo commented on an issue Re: Is the Jira tidy-up done for this release and prepared for the next one? Fixed in 2.2.0: https://tickets.puppetlabs.com/issues/?filter=12624 Add Comment Facter / FACT-669 Is the Jira tidy-up done for this release and prepared for the next one? 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... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-631) operatingsystemmajrelease does not work on Solaris
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-631 operatingsystemmajrelease does not work on Solaris Change By: Kylo Ginsberg Affects Version/s: 2.2.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3141) PMT module list gives inaccurate warning message when module has bad semver
Title: Message Title Anderson Mills created an issue Puppet / PUP-3141 PMT module list gives inaccurate warning message when module has bad semver Issue Type: Bug Affects Versions: 3.7.0 Assignee: Unassigned Components: PMT Created: 25/Aug/14 2:11 PM Priority: Normal Reporter: Anderson Mills puppet module list gives an inaccurate error message about the version of a different depended-upon module when a module has a bad semver. $ puppet module list Warning: Missing dependency 'puppetlabs-stdlib': 'anderson-ugg' (v0.1) requires 'puppetlabs-stdlib' (= 1.0.0) /Users/anderson/.puppet/modules ├── anderson-ugg (v0.1) ├── ghoneycutt-hosts (v2.1.0) └── puppetlabs-stdlib (v4.3.2)
Jira (FACT-669) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Kylo Ginsberg commented on an issue Re: Is the Jira tidy-up done for this release and prepared for the next one? On the Introduced in 2.2.0 filter, I bulk-edited those tickets to remove the Affected Version field. Since 2.2.0 wasn't out yet, those haven't been introduced in 2.2.0. This might actually be something to add to the release ticket template. Add Comment Facter / FACT-669 Is the Jira tidy-up done for this release and prepared for the next one? 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... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (FACT-672) Smoke test packages
Title: Message Title Kylo Ginsberg commented on an issue Re: Smoke test packages I'll take trusty, precise, lucid. Add Comment Facter / FACT-672 Smoke test packages 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). If this is a final release then the previous RC (which should be identical to what is currently being released) will have gone through th... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-672) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Debian 6 looks good: root@debian-6-i386:/home/vagrant# facter -y --- kernelmajversion: 2.6 productname: VirtualBox ipaddress_eth0: 10.0.2.15 sshfp_rsa: |- SSHFP 1 1 a03ec0d9ca479337890f4323309c810b293cb9b8 SSHFP 1 2 664da055eb8ae3e2cabc0cb465a5e2115295c659489adcde95c825e8a49d4a2d kernelversion: 2.6.32 operatingsystemmajrelease: 6 lsbminordistrelease: 0 rubysitedir: /usr/local/lib/site_ruby/1.8 memorysize_mb: 375.61 blockdevice_sr0_vendor: VBOX bios_version: VirtualBox ps: ps -ef filesystems: ext2,ext3 lsbdistcodename: squeeze hardwareisa: unknown lsbdistrelease: 6.0.7 blockdevice_sda_size: 10632560640 uniqueid: 007f0101 blockdevice_sr0_size: 1073741312 kernel: Linux hostname: debian-6-i386 serialnumber: 0 osfamily: Debian kernelrelease: 2.6.32-5-686 network_eth0: 10.0.2.0 uptime_seconds: 72 facterversion: 2.2.0 sshfp_dsa: |- SSHFP 2 1 e2dec8bb4349c557cab7111cdeece9060ee65b1c SSHFP 2 2 1505077ddefd207792093b808c0d247a7d1710df50a46910f02955769efc06ab blockdevices: sda,sr0,sr1 boardserialnumber: 0 netmask_eth0: 255.255.255.0 swapsize_mb: 455.99 uuid: 3B9946D9-F532-4B93-AA8B-FFE4D227DF31 interfaces: eth0,lo macaddress_eth0: 08:00:27:3a:9d:d7 is_virtual: true manufacturer: innotek GmbH sshdsakey: B3NzaC1kc3MAAACBAMao58AjusuEma6TzpnF8h/lN7g0A3wWmAOyO8VuikEH4eCpE59AflF+z+c+jzhQa/oHl7fpf5XohTAkrY6W4Y/YQnOCkfrRKSa9NliRl+hYf+Y0lDTFr7Cdk8NE5aAWflNrVHxXrrSS+4x/D52BG5WnNG+psezosW6UuvciVMjLFQD3kZRXLhGZklygKctBIDY7Vb5TwQAAAIEAjMaroVHtoTu/3txJ/EeE6WJn4f37U/8j0harBF19KuJb8ult4sTlxg2FPGmdZBecPcMDbIxcuINzr2Jviyg9ZnzjbR44f106ZQgIFIjElO79XE3PsHJa0vfKpRuTmChnfcWgVH+T7tMLSRa9BO1kwy+Uj4bhqjpYpfpa/sWv+E8AAACBAKu4uMlXgwLDuqEfNZ5htQuIty6xkQRvPo1ziE06ppSj4Vy2NZy80OIFppwumkqKqxbS9j3SCxPj1M01Jsysx2HuJaWq0mTi/plMGxY3yN+YIbOpNGcOkOu1/JSlHMBjRwqEUy07Opo9SvhiBl5etWXw1V1Wg61VF0EOIp1xnV5b macaddress: 08:00:27:3a:9d:d7 uptime: 0:01 hours timezone: UTC mtu_lo: 16436 fqdn: debian-6-i386.dc1.puppetlabs.net boardmanufacturer: Oracle Corporation processors: models: - Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz physicalcount: 1 count: 1 path: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin hardwaremodel: i686 netmask_lo: 255.0.0.0 processorcount: 1 uptime_days: 0 virtual: virtualbox blockdevice_sr0_model: CD-ROM operatingsystemrelease: 6.0.7 system_uptime: seconds: 72 days: 0 hours: 0 uptime: 0:01 hours sshrsakey: B3NzaC1yc2EDAQABAAABAQCiKOi7C4mkdFzKbEugMDXZWE8aKwyJgakDarZdSrg7/Fmg7ihlprgv4pw3r1WNBmWFduvAEF1clQ/8aOcA2S9332FemzGVyvTSpoM2GtyLo5b2E07y2sPgLMEwtPZJSdOYjfBQZDTKYJlo003PVX5G2EKvkj30Ocqh1BI15QwJTJF6yhPw+9nlMJw1wlN9Z7oGKeeWPGW7c6d3GZceaAMlRFvyY30fb5Ip68m1f87lYA7tddEYPjY03NC9TbgDPJyzX2eLKH9mwzm6UCnIFGFkb7mwGsrEoILyvsjguJFSWHtubRCCOyGI5Aj5TSCf87Bw6sdomEq5QbTpGryWDac9 memorysize: 375.61 MB gid: root partitions: sda1: size: 497664 filesystem: ext2 uuid: c5e32508-1e4b-4a83-abc8-8f7bf3f9223f mount: /boot sda2: size: 2 sda5: size: 20262912 filesystem: LVM2_member rubyversion: 1.8.7 ipaddress: 10.0.2.15 mtu_eth0: 1500 memoryfree_mb: 341.07 os: name: Debian lsb: minordistrelease: 0 majdistrelease: 6 distdescription: Debian GNU/Linux 6.0.7 (squeeze) distid: Debian distrelease: 6.0.7 distcodename: squeeze family: Debian release: major: 6 full: 6.0.7 minor: 0 network_lo: 127.0.0.0 physicalprocessorcount: 1 bios_release_date: 12/01/2006 boardproductname: VirtualBox lsbdistid: Debian lsbdistdescription: Debian GNU/Linux 6.0.7 (squeeze) swapsize: 455.99 MB processor0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz blockdevice_sda_vendor: ATA blockdevice_sr1_model: CD-ROM swapfree_mb: 455.99 blockdevice_sda_model: VBOX HARDDISK architecture:
Jira (FACT-672) Smoke test packages
Title: Message Title William Hopper commented on an issue Re: Smoke test packages I'm working on Solaris as we speak - will jump on others once completed. Add Comment Facter / FACT-672 Smoke test packages 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). If this is a final release then the previous RC (which should be identical to what is currently being released) will have gone through th... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-672) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Debian 7: processors: models: - Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz count: 1 physicalcount: 1 kernel: Linux architecture: i386 hardwaremodel: i686 operatingsystem: Debian os: name: Debian family: Debian release: major: '7' minor: '0' full: '7.0' lsb: distcodename: wheezy distid: Debian distdescription: Debian GNU/Linux 7.0 (wheezy) distrelease: '7.0' majdistrelease: '7' minordistrelease: '0' processor0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz processorcount: '1' kernelrelease: 3.2.0-4-686-pae rubyversion: 1.9.3 hardwareisa: unknown ipaddress: 10.0.2.15 facterversion: 2.2.0 memorysize: 375.34 MB memoryfree: 343.61 MB swapsize: 456.00 MB swapfree: 456.00 MB swapsize_mb: '456.00' swapfree_mb: '456.00' memorysize_mb: '375.34' memoryfree_mb: '343.61' netmask: 255.255.255.0 uniqueid: 007f0101 gid: root lsbdistdescription: Debian GNU/Linux 7.0 (wheezy) selinux: 'false' lsbdistcodename: wheezy ps: ps -ef kernelversion: 3.2.0 lsbdistid: Debian kernelmajversion: '3.2' uptime_seconds: 55 lsbmajdistrelease: '7' operatingsystemrelease: '7.0' fqdn: debian-7-i386.vagrantup.com lsbdistrelease: '7.0' physicalprocessorcount: '1' uptime_hours: 0 interfaces: eth0,lo ipaddress_eth0: 10.0.2.15 macaddress_eth0: 08:00:27:7c:ea:12 netmask_eth0: 255.255.255.0 mtu_eth0: '1500' ipaddress_lo: 127.0.0.1 netmask_lo: 255.0.0.0 mtu_lo: '16436' osfamily: Debian lsbminordistrelease: '0' domain: vagrantup.com hostname: debian-7-i386 uptime: 0:00 hours path: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin system_uptime: seconds: 55 hours: 0 days: 0 uptime: 0:00 hours sshdsakey: B3NzaC1kc3MAAACBAI2OsI8BNQK2qMDbuVZjiPRlIjh5I5DZWcV2Z05bS8Q+ni5GD/ZDa1SANaQecrNVo6y3RIpL8Uo7Prhl8mR8+uWh+kvGRPu0lhTpWhptiiAeqti0ch9WmhD+tjVczrAV6m3Tt7xiYN3Nq0e4sVHmZi0GWqT6bxEWTC0ZAm5WoJQRFQCJrPr3aIOQDABg/wbQOfZ4eZlziwAAAIAOgpGUgAWBjeT/KfHHNvB8leBlcMemWccx9VaUE32+5olWe4apPbZXKqyEnNvR9dgoK7r5HlgbKqnP4u0PYV+PS47uEMy7IwVB+b2c3kWc3AiBryeWMxb4uQLvYvpxu4/mVkIWix0G8xgo6DnueMks6OF03Tw5zzKkO0QmPE6IHgAAAIAeIjtBDcckLCRlNrQ36VwpJvUYd+zVe/4FsMecU6FN6J8wQ61MCnNbwB2UGVqNcR0AWSMCeJwYosSTMkEWeBV+/cs4yWteAee/slGBudC+HJxMYBHvbfjNSwJs9m/Z1WS517Lf8tWaSwbfFahdrVTWxYpLfAZt2QzxFKGpLESEKw== sshfp_dsa: ! 'SSHFP 2 1 204b51330d83ec15c3ed522692ac10f70a7c072f SSHFP 2 2 0920fe3e886fa5703969635615e117ebdaed21624d3d402956161337b722ed33' sshrsakey: B3NzaC1yc2EDAQABAAABAQCpRpNCshDHQoTYCv0azEdzpPoVVNqb44WJKtqs8WY75p+bp7hdmWRhKLN1a/ySsb1iObBTMO/w5wkBRg6UNUhfdsdYs4dg/hhjQGLRT9aXSNCCkDkgdSKO6PtRo+5WiMxIjnw2J4g9FLKh/M5rR+J58Mqd7jYGCdqUwhYw6ymfNk+B64mdd/CS9H/WqSpNl9eSLPUjteKgcMdm+o8V9u0iIC55/7eC6HSbJ824hNSv0JHaN3TFohbGddKAkFhZSS1igh3iKHGtXEwzrRkUYRdvTdEGKJgJiWvQylL/dDyc7qI5//h1uY2sU454KaEHJmq4FI5DJNCLEXTJwsVx9nTf sshfp_rsa: ! 'SSHFP 1 1 6b2284770b39a525d6021b4a2b30e332762f115d SSHFP 1 2 26e33eabe0e8bcfdb538a99b9fba436fece8324f6a1e9f807c4d2a6bbd0e3da0' sshecdsakey: E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBJgtJl/IlHw74EqnSFT2xQRMZv2SHUogpIXN96GxxHfsx2x4TuZPHNrmmccp9u2MW3kpcWZzjLT552WPOiiQEW8= sshfp_ecdsa: ! 'SSHFP 3 1 2a365770ea6fd069c3c1f8b0b4b86c88b6b6b92a SSHFP 3 2 9a1dc83a76acef199fb765f24b194aecb8f6fc00e1ab7075d1562e119bed49b3' virtual: virtualbox is_virtual: 'true' uptime_days: 0 filesystems: ext2,ext3 boardmanufacturer: Oracle Corporation boardproductname: VirtualBox boardserialnumber: '0' bios_vendor: innotek GmbH bios_version: VirtualBox bios_release_date: 12/01/2006 manufacturer: innotek GmbH productname: VirtualBox serialnumber: '0' uuid: 36B62114-9C32-4681-BB2E-CE64D928F993 type: Other macaddress: 08:00:27:7c:ea:12 partitions: sda1: uuid: 3a907488-8406-4b75-b7fd-4910b63955d7 size: '497664' mount: /boot
Jira (FACT-672) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Working on Fedora 20. Add Comment Facter / FACT-672 Smoke test packages 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). If this is a final release then the previous RC (which should be identical to what is currently being released) will have gone through th... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-672) Smoke test packages
Title: Message Title William Hopper commented on an issue Re: Smoke test packages I'll grab Redhat 6 /7 and Centos 6 / 7 Add Comment Facter / FACT-672 Smoke test packages 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). If this is a final release then the previous RC (which should be identical to what is currently being released) will have gone through th... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3032) Setting to cache `load_library` failures
Title: Message Title
Josh Cooper commented on an issue
Re: Setting to cache `load_library` failures
I think there are a few things to verify here. Create a module that installs a gem using a package resource:
package { 'mygem':
ensure = installed,
provider = gem
}
defines a feature based on the gem:
Puppet.features.add(:myfeature, :libs = mygem)
and defines a type and provider that is confined based on the feature:
Puppet::Type.newtype(:something) do
newparam(:name, :namevar = true)
newproperty(:myprop)
end
Puppet::Type.type(:something).provide(:whatever) do
confine = myfeature
def myprop
end
def myprop=(value)
end
end
And defines a resource based on the type provider:
something { 'myname':
provider = whatever
}
This is similar to our ticket_6907_use_provider_in_same_run_it_becomes_suitable acceptance test, however, that uses an external command, not a feature. But it's a good point of reference for verifying this fix.
If always_cache_features is false, we should be able to install the gem, and use the provider within a single run.
If always_cache_features is true, the provider should not be suitable as determined at the start of the puppet run, and puppet should generate an error.
Change the feature definition to use a block, e.g.
Puppet.features.add(:myfeature) do
require mygem
end
For historical reasons, puppet has always cached the result when using a block... So puppet should generate an error that there is no suitable provider regardless of what always_cache_features is set to.
Ideally this should be part of a spec test, but I don't believe all of these cases are currently covered.
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Joshua Partlow commented on an issue Re: Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb It is, and this test should be changed to use a non-master agent rather than just picking the first agent, because it tries to ensure that apache2 is removed. I think the only reason we haven't seen this sooner (particularly in the pe runs), is because this test happens late in the alphabetical list of test files and we don't execute another test in the context of a running master after this point. That's not why the test itself is failing though. It has run successfully on a master node in other runs. Still looking into that. Add Comment Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Just recently there have been a few intermittent failures in resource/service/ticket_14297_handle_upstart.rb. (Btw note that this test is confined to Ubuntu.) Three examples: https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-4.0/label=acc-coord,platform=precise/212/consoleFull https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-839) PR (1064): Deprecate PG 9.1 instead, and remove nagging about 9.3 for PE users - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1064): Deprecate PG 9.1 instead, and remove nagging about 9.3 for PE users - kbarber Pull request Deprecate PG 9.1 instead, and remove nagging about 9.3 for PE users has been closed. Add Comment PuppetDB / PDB-839 PR (1064): Deprecate PG 9.1 instead, and remove nagging about 9.3 for PE users - kbarber h2. WIP: Deprecate PG 9.1 instead, and remove nagging about 9.3 for PE users * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1064 Discussion|https://github.com/puppetlabs/puppetdb/pull/1064] * [Pull Request 1064 File Diff|https://github.com/puppetlabs/puppetdb/pull/1064/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (FACT-672) Smoke test packages
Title: Message Title
William Hopper commented on an issue
Re: Smoke test packages
Redhat 7:
[root@f309ovo6qulftp5 ~]# facter --version 2.2.0
[root@f309ovo6qulftp5 ~]# facter architecture = x86_64 bios_release_date = 07/30/2013 bios_vendor = Phoenix Technologies LTD bios_version = 6.00 blockdevice_fd0_size = 4096 blockdevice_sda_model = Virtual disk blockdevice_sda_size = 8589934592 blockdevice_sda_vendor = VMware blockdevice_sr0_model = VMware IDE CDR10 blockdevice_sr0_size = 1073741312 blockdevice_sr0_vendor = NECVMWar blockdevices = fd0,sda,sr0 boardmanufacturer = Intel Corporation boardproductname = 440BX Desktop Reference Platform boardserialnumber = None dhcp_servers = {system=10.16.22.10, ens192=10.16.22.10}
domain = delivery.puppetlabs.net facterversion = 2.2.0 filesystems = xfs fqdn = f309ovo6qulftp5.delivery.puppetlabs.net gid = root hardwareisa = x86_64 hardwaremodel = x86_64 hostname = f309ovo6qulftp5 id = root interfaces = ens192,lo ipaddress = 10.18.45.253 ipaddress_ens192 = 10.18.45.253 ipaddress_lo = 127.0.0.1 is_virtual = true kernel = Linux kernelmajversion = 3.10 kernelrelease = 3.10.0-123.1.2.el7.x86_64 kernelversion = 3.10.0 lsbdistcodename = Maipo lsbdistdescription = Red Hat Enterprise Linux Server release 7.0 (Maipo) lsbdistid = RedHatEnterpriseServer lsbdistrelease = 7.0 lsbmajdistrelease = 7 lsbminordistrelease = 0 lsbrelease = :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch macaddress = 00:50:56:9b:24:f7 macaddress_ens192 = 00:50:56:9b:24:f7 manufacturer = VMware, Inc. memoryfree = 1.62 GB memoryfree_mb = 1655.26 memorysize = 1.80 GB memorysize_mb = 1841.28 mtu_ens192 = 1500 mtu_lo = 65536 netmask = 255.255.0.0 netmask_ens192 = 255.255.0.0 netmask_lo = 255.0.0.0 network_ens192 = 10.18.0.0 network_lo = 127.0.0.0 operatingsystem = RedHat operatingsystemmajrelease = 7 operatingsystemrelease = 7.0 os = {name=RedHat, family=RedHat, release= {major=7, minor=0, full=7.0}
, lsb={distcodename=Maipo, distid=RedHatEnterpriseServer, distdescription=Red Hat Enterprise Linux Server release 7.0 (Maipo), release=:core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch, distrelease=7.0, majdistrelease=7, minordistrelease=0}} osfamily = RedHat partitions = {sda1= {uuid=967e3fc9-3637-4c0a-b17e-d180cabcce9d, size=1024000, mount=/boot, filesystem=xfs}
, sda2={size=15751168, filesystem=LVM2_member}} path = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin physicalprocessorcount = 1 processor0 = Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz processor1 = Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz processorcount = 2 processors = {models=[Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz, Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz], count=2, physicalcount=1}
productname = VMware Virtual Platform ps = ps -ef rubysitedir = /usr/local/share/ruby/site_ruby/ rubyversion = 2.0.0 selinux = true selinux_config_mode = enforcing selinux_config_policy = unknown selinux_current_mode = enforcing selinux_enforced = true selinux_policyversion = 28 serialnumber = VMware-42 1b a5 5c 96 0b df b2-89 0c 50 d8 2c a3 85 86 sshecdsakey = E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBHkvfwClxVvdxDc4ADuzKSkYwQx6udBqctS9XAXB6yEdduWApC+FWskpjLQs61mKeWO2wpIscDIrC2LRhnXNqd8= sshfp_ecdsa = SSHFP 3 1 678029dbd06737d013e8cded0e1222e0950c6b01 SSHFP 3 2 3d2bb6e0047c1c7ef99dee74696e15a1c813d53b8a3d92079dd12d9d9be669bb sshfp_rsa = SSHFP 1 1 abc203895fdafaf7becd0af7480f26587b0ac44a SSHFP 1 2
Jira (PDB-842) PR (1066): fix factsets docs typo - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1066): fix factsets docs typo - wkalt Pull request fix factsets docs typo has been closed. Add Comment PuppetDB / PDB-842 PR (1066): fix factsets docs typo - wkalt h2. fix factsets docs typo * Author: Wyatt Alt * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1066 Discussion|https://github.com/puppetlabs/puppetdb/pull/1066] * [Pull Request 1066 File Diff|https://github.com/puppetlabs/puppetdb/pull/1066/files] h2. Pull Request Description (webhooks-id: a92b7d3338654dae6... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-672) Smoke test packages
Title: Message Title
William Hopper commented on an issue
Re: Smoke test packages
Redhat 6:
[root@l88z93mrkhj0gpa ~]# facter --version
2.2.0
[root@l88z93mrkhj0gpa ~]# facter
architecture = x86_64
bios_release_date = 07/30/2013
bios_vendor = Phoenix Technologies LTD
bios_version = 6.00
blockdevice_sda_model = Virtual disk
blockdevice_sda_size = 8589934592
blockdevice_sda_vendor = VMware
blockdevice_sr0_model = VMware IDE CDR10
blockdevice_sr0_size = 1073741312
blockdevice_sr0_vendor = NECVMWar
blockdevices = sda,sr0
boardmanufacturer = Intel Corporation
boardproductname = 440BX Desktop Reference Platform
boardserialnumber = None
domain = delivery.puppetlabs.net
facterversion = 2.2.0
filesystems = ext4,iso9660
fqdn = l88z93mrkhj0gpa.delivery.puppetlabs.net
gid = root
hardwareisa = x86_64
hardwaremodel = x86_64
hostname = l88z93mrkhj0gpa
id = root
interfaces = eth0,lo
ipaddress = 10.18.64.136
ipaddress_eth0 = 10.18.64.136
ipaddress_lo = 127.0.0.1
is_virtual = true
kernel = Linux
kernelmajversion = 2.6
kernelrelease = 2.6.32-431.11.2.el6.x86_64
kernelversion = 2.6.32
lsbdistcodename = Santiago
lsbdistdescription = Red Hat Enterprise Linux Server release 6.5 (Santiago)
lsbdistid = RedHatEnterpriseServer
lsbdistrelease = 6.5
lsbmajdistrelease = 6
lsbminordistrelease = 5
lsbrelease = :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
macaddress = 00:50:56:9B:90:73
macaddress_eth0 = 00:50:56:9B:90:73
manufacturer = VMware, Inc.
memoryfree = 1.68 GB
memoryfree_mb = 1720.52
memorysize = 1.83 GB
memorysize_mb = 1877.21
mtu_eth0 = 1500
mtu_lo = 16436
netmask = 255.255.0.0
netmask_eth0 = 255.255.0.0
netmask_lo = 255.0.0.0
network_eth0 = 10.18.0.0
network_lo = 127.0.0.0
operatingsystem = RedHat
operatingsystemmajrelease = 6
operatingsystemrelease = 6.5
os = {name=RedHat, release={minor=5, full=6.5, major=6}, family=RedHat, lsb={distid=RedHatEnterpriseServer, majdistrelease=6, distrelease=6.5, release=:base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch, distdescription=Red Hat Enterprise Linux Server release 6.5 (Santiago), distcodename=Santiago, minordistrelease=5}}
osfamily = RedHat
partitions = {sda1={filesystem=ext4, uuid=eb475619-f4b3-41af-91ca-b37fec3374d7, mount=/boot, size=1024000}, sda2={filesystem=LVM2_member, size=15751168}}
path = /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
physicalprocessorcount = 2
processor0 = Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz
processor1 = Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz
processorcount = 2
processors = {physicalcount=2, count=2, models=[Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz, Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz]}
productname = VMware Virtual Platform
ps = ps -ef
rubysitedir = /usr/lib/ruby/site_ruby/1.8
rubyversion = 1.8.7
selinux = true
selinux_config_mode = enforcing
selinux_config_policy = targeted
selinux_current_mode = enforcing
selinux_enforced = true
selinux_policyversion = 24
serialnumber = VMware-42 1b 84 a6 90 e3 0e 51-6d 79 e3 a4 fc 1f a9 70
sshdsakey =
Jira (PUP-2984) MSI downgrade from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec
Title: Message Title
Ethan Brown commented on an issue
Re: MSI downgrade from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec
Yes, I can confirm that even the existing code prior to this PR exhibits such behavior when changing architectures.
During an x86 - x86 upgrade path, the custom install directory is remembered correctly.
However, as soon as there is an architecture change, the property is no longer remembered. For instance, install Puppet 3.6.2 x86, then install Puppet 3.7 x64, and then install Puppet 3.6.2 x86 (or Puppet 3.7 x86). The original x86 directory is no longer remembered.
I would consider this a regression. I'm investigating if there's a straightforward mechanism to protect those keys across architecture installs. It would appear that the NeverOverwrite property of a Component can be set to allow this key to persist across uninstalls - http://wixtoolset.org/documentation/manual/v3/xsd/wix/component.html
Add Comment
Puppet / PUP-2984
MSI downgrade from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec
MSI downgrade from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec. It also doesn't remove the older path - this is what remains after install of x86 AFTER x64: {{C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files (x86)\Puppet Labs\Puppet\bin}} and it should be {{C:\Program Files (x...
Jira (FACT-672) Smoke test packages
Title: Message Title
William Hopper commented on an issue
Re: Smoke test packages
Centos 6:
[root@aoxs09p534vv1sh ~]# facter --version
2.2.0
[root@aoxs09p534vv1sh ~]# facter
architecture = x86_64
bios_release_date = 07/30/2013
bios_vendor = Phoenix Technologies LTD
bios_version = 6.00
blockdevice_sda_model = Virtual disk
blockdevice_sda_size = 8589934592
blockdevice_sda_vendor = VMware
blockdevice_sdb_model = Virtual disk
blockdevice_sdb_size = 8589934592
blockdevice_sdb_vendor = VMware
blockdevice_sr0_model = VMware IDE CDR10
blockdevice_sr0_size = 1073741312
blockdevice_sr0_vendor = NECVMWar
blockdevices = sda,sdb,sr0
boardmanufacturer = Intel Corporation
boardproductname = 440BX Desktop Reference Platform
boardserialnumber = None
domain = delivery.puppetlabs.net
facterversion = 2.2.0
filesystems = ext4,iso9660
fqdn = aoxs09p534vv1sh.delivery.puppetlabs.net
gid = root
hardwareisa = x86_64
hardwaremodel = x86_64
hostname = aoxs09p534vv1sh
id = root
interfaces = eth0,lo
ipaddress = 10.18.244.199
ipaddress_eth0 = 10.18.244.199
ipaddress_lo = 127.0.0.1
is_virtual = true
kernel = Linux
kernelmajversion = 2.6
kernelrelease = 2.6.32-431.11.2.el6.x86_64
kernelversion = 2.6.32
lsbdistcodename = Final
lsbdistdescription = CentOS release 6.5 (Final)
lsbdistid = CentOS
lsbdistrelease = 6.5
lsbmajdistrelease = 6
lsbminordistrelease = 5
lsbrelease = :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
macaddress = 00:50:56:9B:52:FC
macaddress_eth0 = 00:50:56:9B:52:FC
manufacturer = VMware, Inc.
memoryfree = 1.68 GB
memoryfree_mb = 1724.84
memorysize = 1.83 GB
memorysize_mb = 1877.21
mtu_eth0 = 1500
mtu_lo = 16436
netmask = 255.255.0.0
netmask_eth0 = 255.255.0.0
netmask_lo = 255.0.0.0
network_eth0 = 10.18.0.0
network_lo = 127.0.0.0
operatingsystem = CentOS
operatingsystemmajrelease = 6
operatingsystemrelease = 6.5
os = {release={minor=5, full=6.5, major=6}, family=RedHat, lsb={minordistrelease=5, release=:base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch, majdistrelease=6, distid=CentOS, distcodename=Final, distrelease=6.5, distdescription=CentOS release 6.5 (Final)}, name=CentOS}
osfamily = RedHat
partitions = {sdb1={size=16771797, filesystem=LVM2_member}, sda1={size=1024000, filesystem=ext4, uuid=c9b8c4a4-7c49-4cb0-b7ee-6dd795e27c87, mount=/boot}, sda2={size=15751168, filesystem=LVM2_member}}
path = /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
physicalprocessorcount = 2
processor0 = Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz
processor1 = Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz
processorcount = 2
processors = {models=[Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz, Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz], count=2, physicalcount=2}
productname = VMware Virtual Platform
ps = ps -ef
rubysitedir = /usr/lib/ruby/site_ruby/1.8
rubyversion = 1.8.7
selinux = true
selinux_config_mode = enforcing
selinux_config_policy = targeted
selinux_current_mode = enforcing
selinux_enforced = true
selinux_policyversion = 24
serialnumber = VMware-42 1b 73 ae f5 fc cf c7-cd b3 90 66 35 91 36 0f
sshdsakey =
Jira (FACT-672) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Fedora 20 looks good: --- kernel: Linux network_eth0: 10.0.2.0 network_lo: 127.0.0.0 ipaddress: 10.0.2.15 gid: root hardwaremodel: i686 hardwareisa: i686 timezone: EDT operatingsystemmajrelease: '20' netmask: 255.255.255.0 kernelrelease: 3.11.10-301.fc20.i686+PAE boardmanufacturer: Oracle Corporation boardproductname: VirtualBox boardserialnumber: '0' bios_vendor: innotek GmbH bios_version: VirtualBox bios_release_date: 12/01/2006 manufacturer: innotek GmbH productname: VirtualBox serialnumber: '0' uuid: 2EAEE2C0-2650-4F7F-8CE5-DD8AE4BCDF75 type: Other osfamily: RedHat fqdn: localhost.corp.puppetlabs.net uptime_days: 0 uptime_hours: 0 architecture: i386 hostname: localhost dhcp_servers: system: 10.0.2.2 eth0: 10.0.2.2 operatingsystem: Fedora uptime: 0:09 hours physicalprocessorcount: '1' path: /sbin:/bin:/usr/sbin:/usr/bin partitions: sda1: uuid: 0a1ed8a0-8a2e-41a2-849b-1c321b3243ec size: '1024000' mount: /boot filesystem: ext4 sda2: size: '19740672' filesystem: LVM2_member system_uptime: seconds: 583 hours: 0 days: 0 uptime: 0:09 hours uptime_seconds: 583 id: root ps: ps -ef virtual: virtualbox is_virtual: 'true' os: name: Fedora family: RedHat release: major: '20' full: '20' facterversion: 2.2.0 processors: models: - Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz count: 1 physicalcount: 1 selinux: 'true' selinux_enforced: 'true' selinux_policyversion: '28' selinux_current_mode: enforcing selinux_config_mode: enforcing selinux_config_policy: unknown rubysitedir: /usr/local/share/ruby/site_ruby/ memorysize: 496.50 MB memoryfree: 429.02 MB swapsize: 1.03 GB swapfree: 1.03 GB swapsize_mb: '1056.00' swapfree_mb: '1055.33' memorysize_mb: '496.50' memoryfree_mb: '429.02' processor0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz processorcount: '1' interfaces: eth0,lo ipaddress_eth0: 10.0.2.15 macaddress_eth0: 08:00:27:44:20:78 netmask_eth0: 255.255.255.0 mtu_eth0: '1500' ipaddress_lo: 127.0.0.1 netmask_lo: 255.0.0.0 mtu_lo: '65536' sshrsakey: B3NzaC1yc2EDAQABAAABAQDKqJFWNKQmmshrV2ZKbUoekdtlZjGTOBBsvcQUFxcVrTNBwOFBJXQWHyXcNYIwazr+wB649FViSj+fgCKxJJbGCcZQEUP3V7seQ6uXSefOsU294HONIOib4S+BjSbaZQ4Tixb6RQu8ux+Zyn/oJxDeEJnzkWJ5lbJAGlN2DIff4VF5cjeU1O0zOB0ZJ835Rnafzj3JyqGTiSLsqMYT27rff+xqY9Kd/uy61FH+9U0NAEFYmYmLs3yEef2rFB/J30ffWmaR+IYhmHJt8HuIsZJVyL6yXVCusSaan+541CSD3C7vw/i2U4b+eThctZfIrDsH1VwO5WEe2eDffGh3 sshfp_rsa: |- SSHFP 1 1 4f8a53b8a58061b0214a1f2d2df3b6c8254be91b SSHFP 1 2 6c753b2ce41423710ac8651706271c9b579ddb601659cca8e4b20cc47e647b34 sshecdsakey: E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBMkJcCXopEddEE7gljnkPwsrn65PEiMyzRLmNGB80oedzCctGK9JEJplHfhHySjjFzvPS4+ZpV7Tjqf6Q6NmLS4= sshfp_ecdsa: |- SSHFP 3 1 9a464815b13899a64bd03168fb553263d7de6f57 SSHFP 3 2 a6bb4a1261612f165496dd02ea6cf26a436af20ad4f965e3a29770772eea59e7 kernelmajversion: '3.11' operatingsystemrelease: '20' macaddress: 08:00:27:44:20:78 uniqueid: 007f0100 kernelversion: 3.11.10 blockdevice_sda_size: 10632560640 blockdevice_sda_vendor: ATA blockdevice_sda_model: VBOX HARDDISK blockdevice_sr0_size: 1073741312 blockdevice_sr0_vendor: VBOX blockdevice_sr0_model: CD-ROM blockdevice_sr1_size: 1073741312 blockdevice_sr1_vendor: VBOX blockdevice_sr1_model: CD-ROM blockdevices: sda,sr0,sr1 domain: corp.puppetlabs.net filesystems: ext2,ext3,ext4 rubyversion: 2.0.0
Jira (FACT-672) Smoke test packages
Title: Message Title
William Hopper commented on an issue
Re: Smoke test packages
Centos 7:
[root@pde0npf98ino0il ~]# facter --version
2.2.0
[root@pde0npf98ino0il ~]# facter
architecture = x86_64
bios_release_date = 07/30/2013
bios_vendor = Phoenix Technologies LTD
bios_version = 6.00
blockdevice_fd0_size = 4096
blockdevice_sda_model = Virtual disk
blockdevice_sda_size = 17179869184
blockdevice_sda_vendor = VMware
blockdevice_sr0_model = VMware IDE CDR10
blockdevice_sr0_size = 1073741312
blockdevice_sr0_vendor = NECVMWar
blockdevices = fd0,sda,sr0
boardmanufacturer = Intel Corporation
boardproductname = 440BX Desktop Reference Platform
boardserialnumber = None
dhcp_servers = {system=10.16.22.10, ens160=10.16.22.10}
domain = delivery.puppetlabs.net
facterversion = 2.2.0
filesystems = xfs
fqdn = pde0npf98ino0il.delivery.puppetlabs.net
gid = root
hardwareisa = x86_64
hardwaremodel = x86_64
hostname = pde0npf98ino0il
id = root
interfaces = ens160,lo
ipaddress = 10.18.11.65
ipaddress_ens160 = 10.18.11.65
ipaddress_lo = 127.0.0.1
is_virtual = true
kernel = Linux
kernelmajversion = 3.10
kernelrelease = 3.10.0-123.4.2.el7.x86_64
kernelversion = 3.10.0
macaddress = 00:50:56:9b:22:c4
macaddress_ens160 = 00:50:56:9b:22:c4
manufacturer = VMware, Inc.
memoryfree = 1.66 GB
memoryfree_mb = 1703.88
memorysize = 1.80 GB
memorysize_mb = 1841.39
mtu_ens160 = 1500
mtu_lo = 65536
netmask = 255.255.0.0
netmask_ens160 = 255.255.0.0
netmask_lo = 255.0.0.0
network_ens160 = 10.18.0.0
network_lo = 127.0.0.0
operatingsystem = CentOS
operatingsystemmajrelease = 7
operatingsystemrelease = 7.0.1406
os = {name=CentOS, family=RedHat, release={major=7, minor=0, full=7.0.1406}}
osfamily = RedHat
partitions = {sda1={uuid=4a9725cc-739a-45f5-8ea0-a83885eaeea0, size=1024000, mount=/boot, filesystem=xfs}, sda2={size=32528384, filesystem=LVM2_member}}
path = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin
physicalprocessorcount = 1
processor0 = Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz
processorcount = 1
processors = {models=[Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz], count=1, physicalcount=1}
productname = VMware Virtual Platform
ps = ps -ef
rubysitedir = /usr/local/share/ruby/site_ruby/
rubyversion = 2.0.0
selinux = true
selinux_config_mode = enforcing
selinux_config_policy = unknown
selinux_current_mode = enforcing
selinux_enforced = true
selinux_policyversion = 28
serialnumber = VMware-42 1b 03 80 2e 39 ea d5-c1 fe 76 1a c6 e6 48 8e
sshecdsakey = E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLqjIT44wYmXSU+vc5zsUUxf00XTllP22tjIwChv3sW7uNhtqLXc1bagOqpRLctiBi64bo/+CPvBJxUT3+5RWOc=
sshfp_ecdsa = SSHFP 3 1 d39b22b2e94886804feff4df669da23cdb358b58
SSHFP 3 2 94a8328bce249921a53ffd36cb1d4b7b5a723949abebd554d7d0507e8c83e04c
sshfp_rsa = SSHFP 1 1 e0f23ba5ff40fa9bc18c4fbb820c4f6afdef335d
SSHFP 1 2 9333a82d26cfb2e1e89368e8061eef1c48a87da677395cf02f0ff1b72d862008
sshrsakey = B3NzaC1yc2EDAQABAAABAQDBKcjgii7T6UEVEUZGYsI52NZmzbJABGJHqnR+xeAlCz0H939xVgQHK7/nCq3joxmVLwTKd7DTCqMn9x1Q7MJ9ERJWIUCgwPNdS4YDfq52nddk+FNtAfhiWsnAjS1MNGUDUcAxakOjvcWp/pPG6cGIq8gnnMdY3Nemlq3i3b5zruvv1z77Mq2rPthfibEP5kI3Hwt/rrcyIuUWiE5oGh0CBw4hLdB3BZMu0OzPcbKW/n8rM0krYB6t1aC5AJy/dIJrFVyjbvI6XFBfYm2eqMM0eZGaerpAt+d+/cmiFJF2PLAb5HxkeTpbm+gaiqfkI8UDsjc77wGvnvC3M3nz/6uL
swapfree = 1.60 GB
swapfree_mb = 1640.00
swapsize = 1.60 GB
swapsize_mb = 1640.00
system_uptime = {seconds=19754, hours=5, days=0, uptime=5:29 hours}
timezone = PDT
type = Other
uniqueid = 120a410b
uptime = 5:29 hours
uptime_days = 0
uptime_hours = 5
uptime_seconds = 19754
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Change By: Kylo Ginsberg Sprint: 2014-09-03 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-672) Smoke test packages
Title: Message Title
William Hopper commented on an issue
Re: Smoke test packages
Amazon 2014.03:
[root@lndm5fxhddqfbfr ~]# facter --version
2.2.0
[root@lndm5fxhddqfbfr ~]# facter
architecture = x86_64
bios_release_date = 07/30/2013
bios_vendor = Phoenix Technologies LTD
bios_version = 6.00
blockdevice_sda_model = Virtual disk
blockdevice_sda_size = 8697308160
blockdevice_sda_vendor = VMware
blockdevice_sr0_model = VMware IDE CDR10
blockdevice_sr0_size = 1073741312
blockdevice_sr0_vendor = NECVMWar
blockdevices = sda,sr0
boardmanufacturer = Intel Corporation
boardproductname = 440BX Desktop Reference Platform
boardserialnumber = None
domain = delivery.puppetlabs.net
facterversion = 2.2.0
filesystems = ext4,iso9660
fqdn = lndm5fxhddqfbfr.delivery.puppetlabs.net
gid = root
hardwareisa = x86_64
hardwaremodel = x86_64
hostname = lndm5fxhddqfbfr
id = root
interfaces = eth0,lo
ipaddress = 10.18.247.3
ipaddress_eth0 = 10.18.247.3
ipaddress_lo = 127.0.0.1
is_virtual = true
kernel = Linux
kernelmajversion = 2.6
kernelrelease = 2.6.32-431.11.2.el6.x86_64
kernelversion = 2.6.32
lsbdistcodename = n/a
lsbdistdescription = Amazon Linux AMI release 2014.03
lsbdistid = AmazonAMI
lsbdistrelease = 2014.03
lsbmajdistrelease = 2014
lsbminordistrelease = 03
lsbrelease = :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
macaddress = 00:50:56:9B:48:0F
macaddress_eth0 = 00:50:56:9B:48:0F
manufacturer = VMware, Inc.
memoryfree = 879.17 MB
memoryfree_mb = 879.17
memorysize = 996.38 MB
memorysize_mb = 996.38
mtu_eth0 = 1500
mtu_lo = 16436
netmask = 255.255.0.0
netmask_eth0 = 255.255.0.0
netmask_lo = 255.0.0.0
network_eth0 = 10.18.0.0
network_lo = 127.0.0.0
operatingsystem = Amazon
operatingsystemmajrelease = 2014
operatingsystemrelease = 2014.03
os = {name=Amazon, family=RedHat, release={major=2014, minor=03, full=2014.03}, lsb={distcodename=n/a, distid=AmazonAMI, distdescription=Amazon Linux AMI release 2014.03, release=:base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch, distrelease=2014.03, majdistrelease=2014, minordistrelease=03}}
osfamily = RedHat
partitions = {sda1={uuid=fef13390-440f-44d7-9a86-5d0fb16838c1, size=16980642, mount=/, filesystem=ext4}}
path = /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/opt/aws/bin:/root/bin
physicalprocessorcount = 1
processor0 = Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz
processorcount = 1
processors = {models=[Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz], count=1, physicalcount=1}
productname = VMware Virtual Platform
ps = ps -ef
rubysitedir = /usr/local/share/ruby/site_ruby/2.0
rubyversion = 2.0.0
selinux = false
serialnumber = VMware-42 1b d7 d8 c0 63 09 4c-c0 64 64 d1 be 1c 4f 78
sshdsakey = B3NzaC1kc3MAAACBALmrsTetkhZ7jkO/9gUMYwezNJKZhTMASksN9d4IzO9NfompFaE4TyZWDQpV3l+wToW+FiZf0RhG8cIQ6rst6x2UujuC37agNNf8/FdiyF4U9yl+y595LvXvkc7uFlQHV9iMK0m4TsQSRCerWIokGMv+YjeMpVDKkdEI3ycxQBzDFQDEuHZdBeDLG5V4nHSl4wwEowCIfQAAAIEAkZOo6D0H/VbNSrn/gPFOf9DeUIFNEA+sQMO/MGbS//zOd85u68HIqIgfA59b6gP0m9hbfk38KOK/izK/PvkWkZ2OazYUtlOUwLnQQPnOQUcAO1egwHkHadU5XXKjGE4L6lGbgWwtZHTU41wExpZaQYxyq6fySZwgXP1TGt/zv74AAACBAK05mWQptRJEerOoVO2luMYGBwilWO09+YoB6bLS94VFicWQxNs/MJnu7rCFW3jTWqZL+VKy//T4cJUg3k0XAjk7q5KgYdCyEUx7ZnK/hDGeYckFR3j3mJqR28nW3Y/fLoZLsqc7Hs40hQdlCPlDOucduRHmH6YadhQvzZQ/7ES0
sshecdsakey = E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBDA4B+Bjyff0X6HIwPY3sf1rbOWLXUFyu7RPI9qbIfMnKQ9l32ffvOBAcKGdxlp324bCRtYznplY1VUao772jCU=
sshfp_dsa = SSHFP 2 1
Jira (FACT-672) Smoke test packages
Title: Message Title
Adrien Thebo commented on an issue
Re: Smoke test packages
CentOS 5:
[root@localhost ~]# facter
architecture = i386
bios_release_date = 12/01/2006
bios_vendor = innotek GmbH
bios_version = VirtualBox
blockdevice_hda_size = 4294965248
blockdevice_hdc_size = 4294965248
blockdevice_sda_model = VBOX HARDDISK
blockdevice_sda_size = 10632560640
blockdevice_sda_vendor = ATA
blockdevices = hda,hdc,sda
boardmanufacturer = Oracle Corporation
boardproductname = VirtualBox
boardserialnumber = 0
domain = localdomain
facterversion = 2.2.0
filesystems = ext2,ext3,iso9660
fqdn = localhost.localdomain
gid = root
hardwareisa = i686
hardwaremodel = i686
hostname = localhost
id = root
interfaces = eth0,lo,sit0
ipaddress = 10.0.2.15
ipaddress_eth0 = 10.0.2.15
ipaddress_lo = 127.0.0.1
is_virtual = true
kernel = Linux
kernelmajversion = 2.6
kernelrelease = 2.6.18-348.el5
kernelversion = 2.6.18
macaddress = 08:00:27:14:DC:79
macaddress_eth0 = 08:00:27:14:DC:79
manufacturer = innotek GmbH
memoryfree = 295.23 MB
memoryfree_mb = 295.23
memorysize = 375.80 MB
memorysize_mb = 375.80
mtu_eth0 = 1500
mtu_lo = 16436
mtu_sit0 = 1480
netmask = 255.255.255.0
netmask_eth0 = 255.255.255.0
netmask_lo = 255.0.0.0
network_eth0 = 10.0.2.0
network_lo = 127.0.0.0
operatingsystem = CentOS
operatingsystemmajrelease = 5
operatingsystemrelease = 5.9
os = {release={full=5.9, minor=9, major=5}, family=RedHat, name=CentOS}
osfamily = RedHat
partitions = {sda2={size=20547135}, sda1={mount=/boot, filesystem=ext3, uuid=3dde0328-bc0f-4377-ad37-a7427ef8bc04, size=208782}}
path = /usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/vagrant/bin
physicalprocessorcount = 1
processor0 = Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz
processorcount = 1
processors = {physicalcount=1, count=1, models=[Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz]}
productname = VirtualBox
ps = ps -ef
rubysitedir = /usr/lib/ruby/site_ruby/1.8
rubyversion = 1.8.7
selinux = true
selinux_config_mode = enforcing
selinux_config_policy = targeted
selinux_current_mode = enforcing
selinux_enforced = true
selinux_policyversion = 21
serialnumber = 0
sshdsakey = B3NzaC1kc3MAAACBAKKhiPVK4t/rviwOHlRJglVybmwqmX710PsNh0/GjSj1Xl7i9WXBAUSyH01gTF70cmYDVlBsYK97n+yH4tBysavWJCweSYsCmoWAoIAnAxy0PkxfnvbdC8r1r7TIjqzYDctBFJlxDQJJbxP3pzPbiwoFQMuWYPg4ecWJCbAK1N2xFQChUyFqqu5EmmExX96rJSygMyDAtQAAAIEAliPF89Nmc10RGr8JMSPfiudEYJqkNRyWtEFXuS/7N9F8AWT4pWBQ0O/Tv5c6xPPFXoLaa/yl9Ht5v2ojmjhFyZzkgZt8BTKkd8PMUIDrTZteHGNC+p+XlWJsdVx1qmWAziqPx2ZqEQI7J5tmEc/qtpESO4GXPYbNlsCFpa/yy8gAAACAUCFlM7PurckeAee02QvJdxpDt/Za6AsHjn5IPwHLcujbFs0gD/fzjahTeVemv5upXqqVzqScbDkCTUyHlsjlYjWQZo9J+Vm0r81D6SxpGoseX3LoZmzllkWFVa2Oa/V9XqhxNcIbc3k065nXGwII5AxGQu5RZcmcqmwEL4oo5f4=
sshfp_dsa = SSHFP 2 1 d1efc678ce197de277448223eece233ddab1af2c
SSHFP 2 2 3f0a524896a8321895ca0e2d720081b407f42215d1784132502c9cdd8067fc22
sshfp_rsa = SSHFP 1 1 64ad22ccadfe518d06e9ed5ddcc99b958b153c8d
SSHFP 1 2 7de57c080e5ff6e0686283e5894fd9c11b85eea68d3ce0c359d64121d2a072ad
sshrsakey = B3NzaC1yc2EBIwAAAQEAnIJGJqJJbLnH7Lo4vNsRzasgyHOTeEfQPn7hdCq8RLt/R239VQe/P/82F2o0VWC5JgxzqsJjSFU/jzeP/ZA8UTSM8VXtwy7dwxdwp5XcAQfOthX8BParoEgKYoZ5DPs7B7ytiO91Em5euTT2L8Xz1Sum6HPTft4BxqJ4FD1VIOKwwMb6+gLT2gsbrDKx+IYyu9iJtbrm145q+3iLGPMFXdf+sdYb5nCu1E61R7dKyk5P/wqkco8ttxar3sTDqhZhvEsjF/Q216DpNzzmF139e+l0VotCd0dyepJBPXp0m/2qpNilNx8blSQ1d8Wkh+7O4HlxoiElDBkj+WrFuHJiFw==
swapfree = 1.03 GB
swapfree_mb = 1055.99
swapsize = 1.03 GB
swapsize_mb = 1055.99
system_uptime = {days=0, hours=0, uptime=0:05 hours, seconds=301}
timezone = PDT
type = Other
uniqueid = 007f0100
uptime = 0:05 hours
uptime_days = 0
uptime_hours = 0
uptime_seconds = 301
uuid = 16499068-E2E8-413D-9FB8-6057DEA016F0
virtual = virtualbox
Jira (PUP-3069) Use a manifest setting in [master] as global manifests
Title: Message Title Henrik Lindberg commented on an issue Re: Use a manifest setting in [master] as global manifests Here is my attempt at making this simpler: The search for the manifest to use for a directory based environment takes place in the following order, the first found entry wins: the directory environment's environment.conf manifest setting the default_manifest (which defaults to the $path_to_env/manifests - i.e. per environment) then nothing (warning / error?) (I am probably missing something that requires the way more complex descriptions how how it should work ???). The next issue is forbidding environments to set manifest. I imagine that this is not as simple as 'always allowing' or 'always denying' this with a global setting; 'always allowing' leaves it open, and 'always forbidding' makes it impossible to allow some (controlled) environments to behave differently (testing) even under central control !. As eric0 pointed out, this is an authorization issue and can be controlled with write protection in the file system, and /or with review of commits when pulling things in from git. To make puppet control this, I think the setting needs to be more elaborate. I can imagine different schemes were environments are either restricted or not by explicit listing names, or by a pattern. (I don't remember if we support a path to searches for an environment in multiple places, or if all environments have to be under a common root. If we have multiple locations, then the allow/restrict could be for the root of a group of environments. e.g. it could be something like: restrict_environment_manifest: true restrict_environment_manifest_exceptions: test_123, feature_y i.e. if restrict is true, then no environment except those in the green list exceptions are allowed to have their own manifest. If restrict is false, the exceptions list is ignored if present, and all environment may have a manifest setting. In any such scheme (puppet restricts), if a particular environment is not allowed to have its own setting then: it is an error if it has manifest set probably a warning (could be an error, or that files are just not used) if there are .pp files in $path_to_env/manifests (this to avoid the mystery of why they are not being used).
Jira (FACT-672) Smoke test packages
Title: Message Title Kylo Ginsberg commented on an issue Re: Smoke test packages Gem : https://gist.github.com/kylog/acbe9147af492abf36db Add Comment Facter / FACT-672 Smoke test packages 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). If this is a final release then the previous RC (which should be identical to what is currently being released) will have gone through th... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-672) Smoke test packages
Title: Message Title
Adrien Thebo commented on an issue
Re: Smoke test packages
Solaris 10:
architecture = i86pc
bios_release_date = 12/01/2006
bios_vendor = innotek GmbH
bios_version = 1.2
domain = corp.puppetlabs.net
facterversion = 2.2.0
fqdn = solaris-10u11-i386-vbox4210-nocm.corp.puppetlabs.net
gid =
hardwareisa = i386
hardwaremodel = i86pc
hostname = solaris-10u11-i386-vbox4210-nocm
id = root
interfaces = lo0,e1000g0
ipaddress = 10.0.2.15
ipaddress_e1000g0 = 10.0.2.15
ipaddress_lo0 = 127.0.0.1
is_virtual = true
kernel = SunOS
kernelmajversion = Generic_147148-26
kernelrelease = 5.10
kernelversion = Generic_147148-26
macaddress = 08:00:27:b8:fd:d1
macaddress_e1000g0 = 08:00:27:b8:fd:d1
manufacturer = innotek GmbH
memoryfree = 540.69 MB
memoryfree_mb = 540.69
memorysize = 768.00 MB
memorysize_mb = 768.00
mtu_e1000g0 = 1500
mtu_lo0 = 8232
netmask = 255.255.255.0
netmask_e1000g0 = 255.255.255.0
netmask_lo0 = 255.0.0.0
network_e1000g0 = 10.0.2.0
network_lo0 = 127.0.0.0
operatingsystem = Solaris
operatingsystemmajrelease = 10_u11
operatingsystemrelease = 10_u11
os = {name=Solaris, family=Solaris, release={major=10_u11, full=10_u11}}
osfamily = Solaris
path = /opt/csw/bin:/usr/sbin:/usr/bin:/usr/ucb
physicalprocessorcount = 1
processor0 = Intel(r) Core(tm) i7-3520M CPU @ 2.90GHz
processorcount = 1
processors = {models=[Intel(r) Core(tm) i7-3520M CPU @ 2.90GHz], physicalcount=1, count=1}
productname = VirtualBox
ps = ps -ef
rubysitedir = /opt/csw/lib/ruby/site_ruby/1.8
rubyversion = 1.8.7
serialnumber = 0
sshdsakey = B3NzaC1kc3MAAACBAPKE7MH3vAlt8pLc4SaLX17wZsYHQsDhjtL34mGNEj5pkMhDgsAW+FYP6ZxelVeqrCRtg2OhIJafbzOzaPtAhAiChLbPKGPj/TD6tp8SswhDICZVv0Qypa8+LwpLPfrRzFcOWNchzc60UsO32gm7jKz6AnJFR4X9+zVjf08GP1zHFQDRSsTO2HeXm6Uk2vR8QjYtDlD+VQAAAIBtEMq+kGJhu7K6IuPE9Za032cypwXceuQa5kC5Pjq0a1JYRFQu5o1EOF8iBK+GCSaQiw/3dKwwGzAqwVBzP7fkkBlCltg4hmMFIN/apRWimEYZ5cnzkTsSA/ei46farQusCCQyvLjHwHGytY5W6+M6V0uu/zC8CWyouiTeI3ALzQAAAIEAkwW5Zb9GPL3ChezElANl6JPp9SVdQuK4OMfz+KiDkTniKViboOYVk3fw7BSquCawrx4P4zMvl0/BYzjgY3MXovE7WPIWiYBymjSwMFqKwNC796zGFJTIZAA+57UCIRvfi3w3TC3lijYOZz3xoR9cCE5culcA1O6dHwe+E7bPLmg=
sshfp_dsa = SSHFP 2 1 25a3c71a6026fe985e68e59563082b9aa9345067
SSHFP 2 2 92f67d668778ae15f10cfa1a162b73e2de8aaf7fe762875fd92ba113e994acaf
sshfp_rsa = SSHFP 1 1 b09a53331e31234bd8f142605376caafaed4adee
SSHFP 1 2 97733b4cfa5a467da3ae03a34eec05b46420d4dec9d141f0cd2cf6a117a768d1
sshrsakey = B3NzaC1yc2EBIwAAAIEAnIFUhzpTYkJFYp1V1aRL0Il34QkXwQwio42dSon2v6HuJW0lSkEBu13Mbl3O4vqIwz1fe9JZ3JQpIXHt7ehRxpdd6Sl8PpgCLJ5nmKX6LWFXZ8ZRQPsxhObXnYDgYByXdArRDGb/sdxTGuF8wIDAQpE+PGZb28EW7aee05o7o9U=
swapfree = 1.00 GB
swapfree_mb = 1027.59
swapsize = 1.00 GB
swapsize_mb = 1027.59
system_uptime = {seconds=4020, days=0, hours=1, uptime=1:07 hours}
timezone = BST
type = 0x1 (other)
uniqueid = 187a449e
uptime = 1:07 hours
uptime_days = 0
uptime_hours = 1
uptime_seconds = 4020
uuid = 5ca01b88-de80-47a7-8191-876aec5a7411
virtual = virtualbox
zfs_version = 5
zonename = global
zones = 0
zpool_version = 32
Add Comment
Jira (FACT-679) Close all resolved tickets in Jira
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-679 Close all resolved tickets in Jira Change By: Adrien Thebo Assignee: KyloGinsberg AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-683) facter id broken on solaris10 as root
Title: Message Title Eric Thompson created an issue Facter / FACT-683 facter id broken on solaris10 as root Issue Type: Bug Assignee: Eric Sorenson Created: 25/Aug/14 4:08 PM Environment: solaris10 as in puppet acceptance setup Priority: Normal Reporter: Eric Thompson installed from source at SHA 5994c22 -bash-3.2# which facter /opt/csw/bin/facter -bash-3.2# facter /usr/bin/id: illegal option -- n Usage: id [-ap] [user] architecture = i86pc Add Comment
Jira (PUP-3069) Use a manifest setting in [master] as global manifests
Title: Message Title Joshua Partlow commented on an issue Re: Use a manifest setting in [master] as global manifests Henrik and I chatted for a bit, and he's suggesting that default_manifest's default value should be './manifest' as a way of collapsing it with the implicit concept of a per directory environment's default manifest. We think this is simpler to describe, so as he stated above, leaving out questions of forbidding per environment manifests, you have: the directory environment's environment.conf manifest setting or the default_manifest settting, which itself defaults to './manifest' which will be taken as a relative path to $path_to_env/manifests If default_manifest is set to something absolute, then we take that. The open question would be whether we allow other relative pathing such as './foo/bar/mymanifests'. It seems less confusing to me if we do that. Then default_manifest is just the path to your manifests, if absolute, it applies to all environments unless environment.conf overrides. If relative, then it is the default relative path to be checked in all environments if environment.conf does not specify manifest. As for restricting environment manifest, we agreed that additional work on greenlisting either certain trees of the environmentpath or certain environment name patterns could be a future ticket. I think the suggestion of handling authorization via file system permissions or review of commits handles the issue of how to actually make a puppet installation more secure, but not the simpler case of 'there is common puppet manifest setup needed for things to work in our installation and we don't want per environment module writers to have to worry about it' case that James Sweeny is describing? Add Comment Puppet / PUP-3069 Use a manifest setting in [master] as
Jira (PUP-1527) After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-1527 After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-678) Send out announcements
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-678 Send out announcements Change By: Adrien Thebo Assignee: EricSorenson AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1527) After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
Title: Message Title
Eric Thompson commented on an issue
Re: After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
tried reproducing this at b7ce5e6 with:
class mynagios {
nagios_service { check_ping:
use = generic-service,
notification_period = 24
}
}
include 'mynagios'
tips on how to reproduce/validate?
Add Comment
Puppet / PUP-1527
After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
gtAfter upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources, data taken from hiera. When hiera has the following data: check_apt_security : { check_command : check_nrpe_1arg!check_apt_security, contact_groups : sladmins, normal_check_interval : 10, ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-2817 Solaris Zone properties ip, dataset and inherit are not set upon zone creation Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation
Title: Message Title Eric Thompson updated an issue Puppet / PUP-2817 Solaris Zone properties ip, dataset and inherit are not set upon zone creation Change By: Eric Thompson QA Contact: ErikDasher EricThompson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title
Joshua Partlow commented on an issue
Re: Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
So Kylo Ginsberg one thing Britt and I are seeing in these failures is that `puppet resources service apache2 ensure=running` is successfully starting the service and reporting it as stopped. Is this a known limitation of the service provider or perhaps of how puppet resource interacts with the service provider?
n7utjhd3jxps5ta (master) 00:20:49$ env PATH=/usr/bin:/opt/puppet-git-repos/hiera/bin:${PATH} RUBYLIB=/opt/puppet-git-repos/hiera/lib:/opt/puppet-git-repos/hiera-puppet/lib:${RUBYLIB} puppet resource service apache2 ensure=running
Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations
(at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1109:in `issue_deprecation_warning')
Notice: /Service[apache2]/ensure: ensure changed 'stopped' to 'running'
service { 'apache2':
ensure = 'stopped',
}
n7utjhd3jxps5ta (master) executed in 1.05 seconds
* Check that status for started apache2
n7utjhd3jxps5ta (master) 00:20:50$ service apache2 status
Apache2 is running (pid 9973).
n7utjhd3jxps5ta (master) executed in 0.02 seconds
This was from a successful run: https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/job/Puppet-Package-Acceptance-master/label=acc-coord,platform=precise/789/consoleFull
And looks to be just a timing issue. Here with debug output on another test machine:
root@bds77xru5f0clnm:~# puppet resource service apache2 ensure=stopped
Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations
(at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1109:in `issue_deprecation_warning')
Notice: /Service[apache2]/ensure: ensure changed 'running' to 'stopped'
service { 'apache2':
ensure = 'stopped',
}
root@bds77xru5f0clnm:~# service apache2 status
Apache2 is NOT running.
root@bds77xru5f0clnm:~# puppet resource service apache2 ensure=running --debug; echo $?
Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations
(at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1109:in `issue_deprecation_warning')
Debug: Runtime environment: run_mode=user, ruby_version=1.8.7, puppet_version=3.6.2
Debug: Puppet::Type::Service::ProviderRunit: file /usr/bin/sv does not exist
Debug: Puppet::Type::Service::ProviderDaemontools: file /usr/bin/svstat does not exist
Debug: Puppet::Type::Service::ProviderRedhat: file /sbin/service does not exist
Debug: Puppet::Type::Service::ProviderLaunchd: file /bin/launchctl does not exist
Debug: Puppet::Type::Service::ProviderOpenrc: file /bin/rc-status does not exist
Debug: Puppet::Type::Service::ProviderSystemd: file systemctl does not exist
Debug: Puppet::Type::Service::ProviderGentoo: file /sbin/rc-update does not exist
Debug: Loaded state in 0.00 seconds
Debug: Service[apache2](provider=upstart): Could not find apache2.conf in /etc/init
Debug: Service[apache2](provider=upstart): Could not find apache2.conf in /etc/init.d
Debug: Service[apache2](provider=upstart): Could not find apache2 in /etc/init
Debug: Executing '/etc/init.d/apache2 status'
Debug: Executing '/etc/init.d/apache2 start'
Notice: /Service[apache2]/ensure: ensure changed 'stopped' to 'running'
Info: /Service[apache2]: Unscheduling refresh on Service[apache2]
Debug: Finishing transaction
Jira (PDB-842) PR (1066): fix factsets docs typo - wkalt
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-842 PR (1066): fix factsets docs typo - wkalt Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-842) PR (1066): fix factsets docs typo - wkalt
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-842 PR (1066): fix factsets docs typo - wkalt Change By: Kenneth Barber Sprint: 20140813to20140827 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3069) Use a manifest setting in [master] as global manifests
Title: Message Title
Joshua Partlow commented on an issue
Re: Use a manifest setting in [master] as global manifests
So do we have consensus around the following changes?
two new settings
default_manifest : describes where to find a directory environment's manifest(s); may be either absolute or relative. If relative, it is relative to a given directory environment root.
defaults to './manifests'
Raises an error if '$environment' is part of it's value (otherwise we're just recreating half of dynamic environments)
Probably raises an error if explicitly set to nothing ('default_manifest=' in puppet.conf...)
restrict_environment_manifest : describes whether or not to allow a directory environment to set it's own manifest. If true, then environment.conf manifest settings are ignored.
defaults to false
An error will be logged when an environment is loaded that has manifest set in it's environment.conf
We can't currently stop processing of requests in that 'potentially invalid' environment without stopping the puppet master process...how important is this issue?
Possibly warn if we see .pp files in ./manifests and restrict_environment_manifest is true
I'd like to know as early as possible in the morning if we all think the above is workable, usable and describable so we can try and get it implemented and tested tomorrow. Otherwise I don't see any hope of getting this in by our Wednesday release.
Thanks everyone! Josh
Jira (PUP-3142) exec type should allow passing of arguments as an array rather than a string
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-3142
exec type should allow passing of arguments as an array rather than a string
Issue Type:
New Feature
Assignee:
Unassigned
Created:
25/Aug/14 7:38 PM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
The exec type takes commands and arguments as a string, (@echo foo@) which will then get passed to /bin/sh (@sh -c echo foo@) by Kernel#system.
This can make things pretty awkward if the command you're trying to execute contains shell metacharacters or quotes of its own, and under appropriately pathological conditions could even be a security problem... (username 'rm -rf /' or something? shrug)
It'd be grand if the exec type would support passing things around as arrays. eg: pre exec {example: command = /bin/echo, arguments = [*, yay, *], }
/pre (Passing an array to Kernel#system bypasses the shell completely: http://www.ruby-doc.org/core/classes/Kernel.html#M005982)
-sq
Add Comment
Jira (PUP-2349) Deprecate non-string modes on file type
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Puppet / PUP-2349 Deprecate non-string modes on file type Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2349) Deprecate non-string modes on file type
Title: Message Title Kylo Ginsberg commented on an issue Re: Deprecate non-string modes on file type Reopening. An unintended side effect of this change was that it shows up during pluginsync, so on every agent run. I'll put up a PR to fix that. Add Comment Puppet / PUP-2349 Deprecate non-string modes on file type The future parser treats literal numbers as actual numbers instead of strings as the old parser did. This makes file resources that use unquoted mode values behave strangely (see PUP-2156). In order to provide a good experience and still have numbers be numbers in the language, the mode parameter of file resources needs to issue a deprecation warning f... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2349) Deprecate non-string modes on file type
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2349 Deprecate non-string modes on file type Change By: Kylo Ginsberg Sprint: 2014-08-06,2014-08-20 ,2014-09-03 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3050) Fix cfacter integration to match recent cfacter changes
Title: Message Title Kylo Ginsberg commented on an issue Re: Fix cfacter integration to match recent cfacter changes CFACT-44 is back in the FR column. Add Comment Puppet / PUP-3050 Fix cfacter integration to match recent cfacter changes cfacter has changed its gem so that most of the implementation now lies in the C++ source. This means we can entirely remove lib/facts.rb and change the cfacter option implementation to simply call a single method in the gem. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-684) EC2 facts unavailable
Title: Message Title Vinod Chandru commented on an issue Re: EC2 facts unavailable Unable to reproduce with a fresh instance. Add Comment Facter / FACT-684 EC2 facts unavailable Looks like [FACT-185|https://tickets.puppetlabs.com/browse/FACT-185] may have regressed in 2.2.0. I'm unable to retrieve ec2_* facts for an EC2 instance in VPC. Works fine in 2.1.0. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
