Jira (HI-273) Support Bundler workflow on x64
Title: Message Title Josh Cooper updated an issue Hiera / HI-273 Support Bundler workflow on x64 Change By: Josh Cooper Fix Version/s: 1.4.0 Fix Version/s: 1.3.5 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 (HI-273) Support Bundler workflow on x64
Title: Message Title
Josh Cooper commented on an issue
Re: Support Bundler workflow on x64
I had to create a PR against stable, because its Gemfile was wrong, e.g. windows-api, and it referenced gems that we need to eliminate. The only gem it actually needs to depend on is win32-dir, which itself has a dependency on ffi, though hiera doesn't need to know that. I also filed a separate PR against master, because it includes the ext/project_data.yaml file, used when generating hiera as a gem.
Add Comment
Hiera / HI-273
Support Bundler workflow on x64
Hiera expresses Windows gem dependencies (in master branch only, but not yet released) but it only applies to ruby x86. When running on x64, the gem dependencies do not apply, so you can't use bundler to install gems, and run specs. Currently, hiera's Gemfile uses the bundler `mingw` platform identifier, effectively: {noformat} platform :mingw do ...
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
Jira (PDB-717) PR (129): Auto enable strict_variables for unit tests when puppet 3.5 - mcanevet
Title: Message Title gepetto-bot commented on an issue Re: PR (129): Auto enable strict_variables for unit tests when puppet 3.5 - mcanevet mcanevet commented: @kbarber thanks, FYI : https://github.com/puppetlabs/puppetlabs-postgresql/pull/432 https://github.com/puppetlabs/puppetlabs-apache/pull/773 Add Comment PuppetDB / PDB-717 PR (129): Auto enable strict_variables for unit tests when puppet 3.5 - mcanevet h2. Auto enable strict_variables for unit tests when puppet 3.5 * Author: Mickal Canvet mickael.cane...@camptocamp.com * Company: camptocamp * Github ID: [mcanevet|https://github.com/mcanevet] * [Pull Request 129 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/129] * [Pull Request 129 File Diff|https://github.com/puppetlabs/p... 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
Jira (PUP-2813) Puppet parser is totally broken in this weird way
Title: Message Title
James Shubin created an issue
Puppet / PUP-2813
Puppet parser is totally broken in this weird way
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Unassigned
Created:
20/Jun/14 12:04 AM
Environment:
GNU/Linux
Priority:
Critical
Reporter:
James Shubin
run this code:
exec { '/bin/echo aaa': alias = 'aaa', }
exec { '/bin/echo bbb': alias = 'bbb', }
$r1 = [ Exec['aaa'], Exec['bbb'], ]
$x = [Exec['xxx']] $r2 = concat($r1, $x)
exec { '/bin/echo ccc': alias = 'ccc', # note that $r2 is commented out... require = $r1, #require = $r2, }
exec { '/bin/echo xxx': alias = 'xxx', # if we are using $r2 this should be a dependency loop... BUT require = Exec['ccc'], }
LOL it is anyways...
Jira (PUP-2813) Puppet parser is totally broken in this weird way
Title: Message Title
James Shubin commented on an issue
Re: Puppet parser is totally broken in this weird way
It's late, so maybe I'm just doing something silly, otherwise the parser is doing some really strange things. This should give you enough to reproduce, and tracking down this bug will hopefully find some serious scary bug or programming error in puppet. Thanks and goodluck!
Add Comment
Puppet / PUP-2813
Puppet parser is totally broken in this weird way
# run this code: exec { '/bin/echo aaa': alias = 'aaa', } exec { '/bin/echo bbb': alias = 'bbb', } $r1 = [ Exec['aaa'], Exec['bbb'], ] $x = [Exec['xxx']] $r2 = concat($r1, $x) exec { '/bin/echo ccc': alias = 'ccc', # note that $r2 is commented out... require = $r1, #require = $r2, } exec { '/bin/echo xxx': ali...
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-2341) puppet parser validate - no output when everything's ok
Title: Message Title Marcelo Carlos commented on an issue Re: puppet parser validate - no output when everything's ok Another reason for this is to allow error messages to be directed to stdout. This is necessary for code linters as the message is used to pinpoint the error. If I run: puppet parser validate test.pp 2 aa.tx it works fine, but puppet parser validate test.pp aa.tx doesn't. To implement linters, in most cases we need to use the stdout, hence the need the option to have the message sent to stdout. A --verbose flag for that purpose would be perfect. As a comparison, php in the command line supports such a feature. Regards Add Comment Puppet / PUP-2341 puppet parser validate - no output when everything's ok Running `puppet parser validate init.pp` returns nothing on the command line when there are no errors. Please consider adding a message like OK or No Parse Error that indicates to the user that the file(s) passed parser validation. This comes up for discussion at almost every fundamentals class I teach, where someone asks So I see no output, is t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1237) File-Serving Configuration parser does not implement allow_ip statements in fileserver.conf
Title: Message Title Alexander Birkner commented on an issue Re: File-Serving Configuration parser does not implement allow_ip statements in fileserver.conf Are there any updates? Add Comment Puppet / PUP-1237 File-Serving Configuration parser does not implement allow_ip statements in fileserver.conf In the current 3.0.0 release, the file serving configuration parser incorrectly handles allow_ip statements in fileserver.conf. Both an allow and allow_ip statement will result in Puppet::FileServing::Configuration::Parser.allow being called, which again calls Puppet::Network::AuthStore.allow. This will raise an AuthStoreError in case of an allow_ip ... 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-465) LinuxMint support is missing in facter stable/facter-2
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Facter / FACT-465 LinuxMint support is missing in facter stable/facter-2 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 (FACT-465) LinuxMint support is missing in facter stable/facter-2
Title: Message Title Kurt Wall commented on an issue Re: LinuxMint support is missing in facter stable/facter-2 Peter Huene Is Linux Mint 17 Quiana appropriate for FR? If so, does it matter if it uses Cinnamon, MATE, or one of the OEM versions of same? Add Comment Facter / FACT-465 LinuxMint support is missing in facter stable/facter-2 Detection of the LinuxMint distro is present in master, but missing in stable (2.0.1) and facter-2 (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.
Jira (PUP-1100) create_resources auto importing a manifest with a syntax error produce a bad error message
Title: Message Title Andy Parker updated an issue Puppet / PUP-1100 create_resources auto importing a manifest with a syntax error produce a bad error message Change By: Andy Parker Component/s: DSL Component/s: Community 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-465) LinuxMint support is missing in facter stable/facter-2
Title: Message Title Peter Huene commented on an issue Re: LinuxMint support is missing in facter stable/facter-2 Kurt Wall As far as I know, Qiana should be fine. Additionally, the choice of DE shouldn't make a difference to distro detection. My understanding is that the OEM install does a normal install but leaves some things not configured because it's assuming the user will complete the install once they buy the computer; that also should not make a difference when detecting the distro. Add Comment Facter / FACT-465 LinuxMint support is missing in facter stable/facter-2 Detection of the LinuxMint distro is present in master, but missing in stable (2.0.1) and facter-2 (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.
Jira (FACT-465) LinuxMint support is missing in facter stable/facter-2
Title: Message Title Kurt Wall commented on an issue Re: LinuxMint support is missing in facter stable/facter-2 Peter Huene Excellent! Thanks. Add Comment Facter / FACT-465 LinuxMint support is missing in facter stable/facter-2 Detection of the LinuxMint distro is present in master, but missing in stable (2.0.1) and facter-2 (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.
Jira (PDB-714) Exported resource relationship woes
Title: Message Title
Zach Leslie commented on an issue
Re: Exported resource relationship woes
This appears to be related to a module conflict. I triple checked the modules in each of the modulepaths and removed any conflicting modules which then allowed the catalog to get submitted to PuppetDB. I don't know why the catalog was compiling in the first place and failing on submission to PuppetDB, but in any case, the catalog is now retrievable by the node in question.
Apologies for the false alarm. Thanks for taking the time to look at this with me Kenneth Barber.
Add Comment
PuppetDB / PDB-714
Exported resource relationship woes
Consider the following. {code} @@concat::fragment { bacula-client-${::fqdn}: target = '/etc/bacula/conf.d/client.conf', content = template('bacula/client.conf.erb'), tag = bacula-${bacula::params::bacula_director}, } {code} The above resource exports a fragment from a node to be backed up. For those familiar with the fragmen...
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
Jira (PUP-2389) Create ruby 2.0 branch for x64 in puppet-win32-ruby
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2389 Create ruby 2.0 branch for x64 in puppet-win32-ruby Change By: Rob Reynolds Weneedtovendorx64versionsofruby2.0,andinstalltheappropriatesetsofgemsintobothbranches.Ruby2.1isnotyetreleasedonWindows.Theworkhereincludes:#create2.0.0-x64branch#vendorruby2.0.0-p545(x64)fromrubyinstaller.orgORneweriftheyreleaseapatchedversion#upgrade/installgemsforx64versions #upgrade/removegemsin1.9.3branchaswell(actuallynotsurewe'dneedtoremovethem) 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-2389) Create ruby 2.0 branch for x64 in puppet-win32-ruby
Title: Message Title Rob Reynolds commented on an issue Re: Create ruby 2.0 branch for x64 in puppet-win32-ruby Removed the notes for the upgrade/remove gems for 1.9.3 branch. That is another ticket I believe. Add Comment Puppet / PUP-2389 Create ruby 2.0 branch for x64 in puppet-win32-ruby We need to vendor x64 versions of ruby 2.0, and install the appropriate sets of gems into both branches. Ruby 2.1 is not yet released on Windows. The work here includes: # create 2.0.0-x64 branch # vendor ruby 2.0.0-p545 (x64) from rubyinstaller.org OR newer if they release a patched version # upgrade/install gems for x64 versions 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-190) Reports: ability to query by hash
Title: Message Title Jason Antman commented on an issue Re: Reports: ability to query by hash It is already possible to query for reports by hash using the v3 or higher API: http://docs.puppetlabs.com/puppetdb/2.0/api/query/v3/reports.html it's the same URL/param structure as the rest of the PuppetDB API queries. Add Comment PuppetDB / PDB-190 Reports: ability to query by hash Knowing the reports hash it should be possible to query for /reports/hash and get a single report back. The current solution would be to get all reports for a node, iterate over them and search for the hash. 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-465) LinuxMint support is missing in facter stable/facter-2
Title: Message Title Kurt Wall assigned an issue to Unassigned Facter / FACT-465 LinuxMint support is missing in facter stable/facter-2 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-2814) Remove naginator from FOSS acceptance jobs
Title: Message Title Josh Cooper created an issue Puppet / PUP-2814 Remove naginator from FOSS acceptance jobs Issue Type: Task Assignee: Unassigned Created: 20/Jun/14 10:24 AM Priority: Normal Reporter: Josh Cooper The naginator plugin has been more harmful for acceptance test than good. Examples include: https://jenkins.puppetlabs.com/view/Hiera/job/Hiera-Acceptance-Windows-master/ https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-master/ If naginator reruns an test when it shouldn't, it pulls a number of VMs from the pool. Acceptance jobs are also matrix jobs, so it has a combinatorial effect. Andy found In the history of PPAm there are 3 reruns that ended up resulting in a green and 11 that resulted in red in those 3 cases we probably ended up not reporting the problem that it covered up but 79% of the time it increased the load and time (79% = 11/14) Please audit all of the FOSS acceptance jobs (hiera, facter, puppet) and make sure naginator is disabled. Add Comment
Jira (PDB-190) Reports: ability to query by hash
Title: Message Title Kenneth Barber commented on an issue Re: Reports: ability to query by hash Jason Antman I think this ticket in particular is about adding the convenience route for querying by hash: [ken@kb ~]# curl 'http://localhost:8080/v3/reports/d8e2ec22077e97566d17aac2209edd6a42007c48' Missing required query parameter 'query'% Add Comment PuppetDB / PDB-190 Reports: ability to query by hash Knowing the reports hash it should be possible to query for /reports/hash and get a single report back. The current solution would be to get all reports for a node, iterate over them and search for the hash. 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 (PDB-190) Reports: ability to query by hash
Title: Message Title Kenneth Barber commented on an issue Re: Reports: ability to query by hash Jason Antman hmm. Re-reading Daniele Sluijters requirements in the old redmine ticket I think though we've achieved the spirit of the original request. Add Comment PuppetDB / PDB-190 Reports: ability to query by hash Knowing the reports hash it should be possible to query for /reports/hash and get a single report back. The current solution would be to get all reports for a node, iterate over them and search for the hash. 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-190) Reports: ability to query by hash
Title: Message Title Jason Antman commented on an issue Re: Reports: ability to query by hash Ahhh, ok. Add Comment PuppetDB / PDB-190 Reports: ability to query by hash Knowing the reports hash it should be possible to query for /reports/hash and get a single report back. The current solution would be to get all reports for a node, iterate over them and search for the hash. 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-567) Support Bundler workflow on x64
Title: Message Title
Josh Cooper commented on an issue
Re: Support Bundler workflow on x64
To verify, install ruby 2.0 x64 from http://www.rubyinstaller.org, and msysgit from http://msysgit.github.io/. Make sure both are in your PATH.
C:\ git clone git://github.com/puppetlabs/facter
C:\ cd facter
C:\facter git checkout facter-2
C:\facter bundle install --path .bundle
C:\facter bundle exec facter
C:\facter bundle install rake spec
Add Comment
Facter / FACT-567
Support Bundler workflow on x64
Facter expresses Windows gem dependencies, but it only applies to ruby x86. When running on x64, the gem dependencies do not apply, so you can't use bundler to install gems, and run specs. Currently, facter's Gemfile uses the bundler `mingw` platform identifier, effectively: {noformat} platform :mingw do gem 'ffi' ... end {noformat} {{Bu...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this
Jira (PDB-190) Reports: ability to query by hash
Title: Message Title Kenneth Barber commented on an issue Re: Reports: ability to query by hash Yeah the original rough requirement has more or less been fulfilled, but part of me doesn't mind having a convenience method like this. I think if people agree feel free to chime in. Add Comment PuppetDB / PDB-190 Reports: ability to query by hash Knowing the reports hash it should be possible to query for /reports/hash and get a single report back. The current solution would be to get all reports for a node, iterate over them and search for the hash. 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-570) Remove windows-pr as a Windows gem dependency
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Facter / FACT-570 Remove windows-pr as a Windows gem dependency Change By: Josh Cooper Assignee: JoshCooper 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-570) Remove windows-pr as a Windows gem dependency
Title: Message Title Josh Cooper commented on an issue Re: Remove windows-pr as a Windows gem dependency Failed review: C:\gems ruby --version ruby 2.0.0p481 (2014-05-08) [x64-mingw32] C:\gems gem install .\facter-2.0.2.149-x64-mingw32.gem Fetching: ffi-1.9.3-x64-mingw32.gem (100%) Successfully installed ffi-1.9.3-x64-mingw32 Fetching: win32-dir-0.4.8.gem (100%) Successfully installed win32-dir-0.4.8 Fetching: win32-api-1.5.1-universal-mingw32.gem (100%) Successfully installed win32-api-1.5.1-universal-mingw32 Fetching: windows-api-0.4.2.gem (100%) Successfully installed windows-api-0.4.2 Fetching: windows-pr-1.2.3.gem (100%) Successfully installed windows-pr-1.2.3 Fetching: win32-security-0.2.5.gem (100%) Successfully installed win32-security-0.2.5 Successfully installed facter-2.0.2.149-x64-mingw32 7 gems installed C:\gems gem dependency facter Gem facter-2.0.2.149-x64-mingw32 ffi (~ 1.9.3) win32-dir (~ 0.4.8) win32-security (~ 0.2.5) windows-pr (~ 1.2) Add Comment Facter / FACT-570 Remove windows-pr as a Windows gem dependency Facter uses the windows-pr gem, and its win32-api dependency, when determining if facter is running as root or not. We need to eliminate usages of this gem now that everything is ffi'ed. The code that needs to be replaced is already in puppet, and just needs to be copied over. This
Jira (FACT-570) Remove windows-pr as a Windows gem dependency
Title: Message Title Josh Cooper commented on an issue Re: Remove windows-pr as a Windows gem dependency Merged fix for project_data.yaml in commit 2d459bd. x64 C:\gems ruby --version ruby 2.0.0p481 (2014-05-08) [x64-mingw32] C:\gems gem install .\facter-2.0.2.150-x64-mingw32.gem Fetching: win32-dir-0.4.8.gem (100%) Successfully installed win32-dir-0.4.8 Fetching: win32-security-0.2.5.gem (100%) Successfully installed win32-security-0.2.5 Successfully installed facter-2.0.2.150-x64-mingw32 3 gems installed C:\gems gem dependency facter Gem facter-2.0.2.150-x64-mingw32 ffi (~ 1.9.3) win32-dir (~ 0.4.8) win32-security (~ 0.2.5) x86 C:\gems ruby --version ruby 1.9.3p545 (2014-02-24) [i386-mingw32] C:\gems gem install .\facter-2.0.2.150-x86-mingw32.gem Fetching: ffi-1.9.3-x86-mingw32.gem (100%) Fetching: win32-dir-0.4.8.gem (100%) Fetching: win32-security-0.2.5.gem (100%) Fetching: win32console-1.3.2-x86-mingw32.gem (100%) Successfully installed ffi-1.9.3-x86-mingw32 Successfully installed win32-dir-0.4.8 Successfully installed win32-security-0.2.5 Successfully installed win32console-1.3.2-x86-mingw32 Successfully installed facter-2.0.2.150-x86-mingw32 5 gems installed C:\gems gem dependency facter Gem facter-2.0.2.150-x86-mingw32 ffi (~ 1.9.3) win32-dir (~ 0.4.8) win32-security (~ 0.2.5) win32console (~ 1.3.2) Note x86 has an additional dependency on win32console, as expected. This can skip Functional Review. Add Comment Facter / FACT-570 Remove windows-pr as a Windows gem dependency
Jira (PDB-577) PuppetDB refuses to start broker if KahaDB lock file exists
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-577 PuppetDB refuses to start broker if KahaDB lock file exists Change By: Ryan Senior Assignee: WyattAlt 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-130) Provide human-friendly message if the infile specified to import/anonymzie doesn't exist
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-130 Provide human-friendly message if the infile specified to import/anonymzie doesn't exist Change By: Ryan Senior Assignee: WyattAlt 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-593) Facter assumes that route is in the path
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Facter / FACT-593 Facter assumes that route is in the path 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 (FACT-593) Facter assumes that route is in the path
Title: Message Title Kurt Wall updated an issue Facter / FACT-593 Facter assumes that route is in the path 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 (FACT-593) Facter assumes that route is in the path
Title: Message Title
Kurt Wall commented on an issue
Re: Facter assumes that route is in the path
Verified in facter-2 at SHA=2d459bdb9b398c72163df95a72d6d9de6f96f396. An strace of facter shows it does not use route -n.
Add Comment
Facter / FACT-593
Facter assumes that route is in the path
Acceptance tests are failing on rhel7 when trying to evaluate {{dhcp_servers}} fact: {noformat} q6mzikqnvnd9urf (agent) $ env RUBYLIB=/opt/puppet-git-repos/hiera/lib:/opt/puppet-git-repos/hiera-puppet/lib:${RUBYLIB} PATH=/usr/bin:/opt/puppet-git-repos/hiera/bin:${PATH} facter SCRIPT CALLED Could not retrieve fact='dhcp_servers', resolution='a...
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-353) some facts do not work with locales set
Title: Message Title Kurt Wall commented on an issue Re: some facts do not work with locales set Verified in master at SHA=XX. With the default locale, LANG=C, and LANG=de_DE, facter facts appear to work properly. $ be facter | grep mac macaddress = c8:e0:eb:14:69:b1 macaddress_bridge0 = ca:e0:eb:41:27:00 macaddress_en0 = c8:e0:eb:14:69:b1 macaddress_en2 = 10:dd:b1:d3:d3:55 macaddress_en3 = 32:00:19:d3:94:60 macaddress_en4 = 32:00:19:d3:94:61 macaddress_fw0 = 00:0a:27:02:00:52 macaddress_p2p0 = 0a:e0:eb:14:69:b1 macaddress_vmnet1 = 00:50:56:c0:00:01 macaddress_vmnet8 = 00:50:56:c0:00:08 macosx_buildversion = 13D65 macosx_productname = Mac OS X macosx_productversion = 10.9.3 macosx_productversion_major = 10.9 macosx_productversion_minor = 3 sp_machine_model = MacBookPro10,1 sp_machine_name = MacBook Pro $ LANG=C LC_ALL=C be facter | grep mac macaddress = c8:e0:eb:14:69:b1 macaddress_bridge0 = ca:e0:eb:41:27:00 macaddress_en0 = c8:e0:eb:14:69:b1 macaddress_en2 = 10:dd:b1:d3:d3:55 macaddress_en3 = 32:00:19:d3:94:60 macaddress_en4 = 32:00:19:d3:94:61 macaddress_fw0 = 00:0a:27:02:00:52 macaddress_p2p0 = 0a:e0:eb:14:69:b1 macaddress_vmnet1 = 00:50:56:c0:00:01 macaddress_vmnet8 = 00:50:56:c0:00:08 macosx_buildversion = 13D65 macosx_productname = Mac OS X macosx_productversion = 10.9.3 macosx_productversion_major = 10.9 macosx_productversion_minor = 3 sp_machine_model = MacBookPro10,1 sp_machine_name = MacBook Pro $ LANG=de_DE LC_ALL=de_DE be facter | grep mac macaddress = c8:e0:eb:14:69:b1 macaddress_bridge0 = ca:e0:eb:41:27:00 macaddress_en0 = c8:e0:eb:14:69:b1 macaddress_en2 = 10:dd:b1:d3:d3:55 macaddress_en3 = 32:00:19:d3:94:60 macaddress_en4 = 32:00:19:d3:94:61 macaddress_fw0 = 00:0a:27:02:00:52 macaddress_p2p0 = 0a:e0:eb:14:69:b1 macaddress_vmnet1 = 00:50:56:c0:00:01 macaddress_vmnet8 = 00:50:56:c0:00:08 macosx_buildversion = 13D65 macosx_productname = Mac OS X macosx_productversion = 10.9.3 macosx_productversion_major = 10.9 macosx_productversion_minor = 3 sp_machine_model = MacBookPro10,1 sp_machine_name = MacBook Pro Add Comment Facter / FACT-353 some facts do not work with locales set
Jira (FACT-353) some facts do not work with locales set
Title: Message Title Kurt Wall updated an issue Facter / FACT-353 some facts do not work with locales set 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 (FACT-353) some facts do not work with locales set
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Facter / FACT-353 some facts do not work with locales set 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 (PDB-190) Reports: ability to query by hash
Title: Message Title Daniele Sluijters commented on an issue Re: Reports: ability to query by hash Thinking back a bit I don't know why I really wanted it as a query option, just report/hash makes perfect sense to me. There might be other scenario's where being able to filter on the hash could be useful but the original need was just being able to fetch a report based on the hash. Add Comment PuppetDB / PDB-190 Reports: ability to query by hash Knowing the reports hash it should be possible to query for /reports/hash and get a single report back. The current solution would be to get all reports for a node, iterate over them and search for the hash. 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-335) Revisit how facter detects GCE instances
Title: Message Title Kurt Wall commented on an issue Re: Revisit how facter detects GCE instances Adrien Thebo I think it would be faster if you could just paste the before and after output of GCE facts. I need to setup GCE access, which will take a lot longer than just seeing the output in this particular case. Would you mind doing so? Add Comment Facter / FACT-335 Revisit how facter detects GCE instances With the launch of GCE v1 API, Google has revised the recommended way of determining if the virtual machine resides within GCE. Updated instructions state to use 'sudo dmidecode -s bios-vendor | grep Google' (same URL, new instructions at https://developers.google.com/compute/docs/instances#dmi). GCE v1 no longer requires google-only kernels and we ca... 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 (FACT-335) Revisit how facter detects GCE instances
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Facter / FACT-335 Revisit how facter detects GCE instances 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-1057) Remove 'collect' and 'select' iterative function stubs
Title: Message Title Kurt Wall updated an issue Puppet / PUP-1057 Remove 'collect' and 'select' iterative function stubs 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-1057) Remove 'collect' and 'select' iterative function stubs
Title: Message Title
Kurt Wall commented on an issue
Re: Remove 'collect' and 'select' iterative function stubs
Verified in master at SHA=dc1ad6858d0eac37b52d7e88bd76fe2b4a204ed8. Attempts to call the collect() or select() generate an error using both the current and future parser:
$ be puppet apply -e collect('') --parser future
Error: Evaluation Error: Unknown function: 'collect'. at line 1:1 on node breve.wifi.puppetlabs.net
Error: Evaluation Error: Unknown function: 'collect'. at line 1:1 on node breve.wifi.puppetlabs.net
$ be puppet apply -e collect('') --parser current
Error: Unknown function collect at line 1 on node breve.wifi.puppetlabs.net
Error: Unknown function collect at line 1 on node breve.wifi.puppetlabs.net
$ be puppet apply -e select('') --parser future
Error: Evaluation Error: Unknown function: 'select'. at line 1:1 on node breve.wifi.puppetlabs.net
Error: Evaluation Error: Unknown function: 'select'. at line 1:1 on node breve.wifi.puppetlabs.net
$ be puppet apply -e select('') --parser current
Error: Unknown function select at line 1 on node breve.wifi.puppetlabs.net
Error: Unknown function select at line 1 on node breve.wifi.puppetlabs.net
Add Comment
Puppet / PUP-1057
Remove 'collect' and 'select' iterative function stubs
The functions 'select' and 'collect' are currently stubs that raise an error (to help those using the future parser from 3.5 migrate their code). In 4.0.0 those stubs should be removed.
Jira (FACT-337) facter/master on solaris 11: Caught recursion on virtual
Title: Message Title Eric Sorenson updated an issue Facter / FACT-337 facter/master on solaris 11: Caught recursion on virtual Change By: Eric Sorenson Fix Version/s: 2.1 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-337) facter/master on solaris 11: Caught recursion on virtual
Title: Message Title
Eric Sorenson commented on an issue
Re: facter/master on solaris 11: Caught recursion on virtual
untargeting this from being a 2.1 release blocker, since it only happens intermittently on tests w/ facter master.
Add Comment
Facter / FACT-337
facter/master on solaris 11: Caught recursion on virtual
This appears to be the root cause behind two recent failures on Hiera-Acceptance. Note that, oddly enough, this may be the only *acceptance* job that includes matrix across puppet/{stable,master} and facter/{stable,master} https://jenkins.puppetlabs.com/job/Hiera-Acceptance-Solaris-master/facter=master,puppet=master,slave=acc-coord/106/consoleText h...
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-570) Remove windows-pr as a Windows gem dependency
Title: Message Title Josh Cooper commented on an issue Re: Remove windows-pr as a Windows gem dependency Commit 2d459bd passed CI, marking as resolved Add Comment Facter / FACT-570 Remove windows-pr as a Windows gem dependency Facter uses the windows-pr gem, and its win32-api dependency, when determining if facter is running as root or not. We need to eliminate usages of this gem now that everything is ffi'ed. The code that needs to be replaced is already in puppet, and just needs to be copied over. 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-2691) Real-world module skeletons still use the 'description' metadata property
Title: Message Title Pieter van de Bruggen updated an issue Puppet / PUP-2691 Real-world module skeletons still use the 'description' metadata property Change By: Pieter van de Bruggen Component/s: PMT 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-2079) puppet module generate can't copy template files without parsing/renaming them
Title: Message Title Pieter van de Bruggen updated an issue Puppet / PUP-2079 puppet module generate can't copy template files without parsing/renaming them Change By: Pieter van de Bruggen Story Points: 1 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-567) Support Bundler workflow on x64
Title: Message Title
Kurt Wall commented on an issue
Re: Support Bundler workflow on x64
Josh Cooper Is the last step supposed to be bundle exec rake spec?
Add Comment
Facter / FACT-567
Support Bundler workflow on x64
Facter expresses Windows gem dependencies, but it only applies to ruby x86. When running on x64, the gem dependencies do not apply, so you can't use bundler to install gems, and run specs. Currently, facter's Gemfile uses the bundler `mingw` platform identifier, effectively: {noformat} platform :mingw do gem 'ffi' ... end {noformat} {{Bu...
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-594) zpool_version fails using zfsonlinux
Title: Message Title
Michael Moll created an issue
Facter / FACT-594
zpool_version fails using zfsonlinux
Issue Type:
Bug
Affects Versions:
2.0.2
Assignee:
Eric Sorenson
Created:
20/Jun/14 1:53 PM
Priority:
Normal
Reporter:
Michael Moll
https://projects.puppetlabs.com/issues/20617 somehow this code didn't end up in facter 2.x:
$ git diff master..facter-2 ./lib/facter/zpool_version.rb diff --git a/lib/facter/zpool_version.rb b/lib/facter/zpool_version.rb index 7cd317e..d1b7ede 100644 — a/lib/facter/zpool_version.rb +++ b/lib/facter/zpool_version.rb @@ -4,7 +4,7 @@ Facter.add('zpool_version') do setcode do if Facter::Core::Execution.which('zpool') zpool_v = Facter::Core::Execution.exec('zpool upgrade -v')
zpool_version = zpool_v.scan(/^\s+(\d+)\s+/m).flatten.last unless zpool_v.empty? + zpool_version = zpool_v.match(/ZFS pool version (\d+)./).captures.first unless zpool_v.empty? end end end
please merge this into facter-2
Jira (PUP-2389) Create ruby 2.0 branch for x64 in puppet-win32-ruby
Title: Message Title Rob Reynolds commented on an issue Re: Create ruby 2.0 branch for x64 in puppet-win32-ruby And now I realize the naming of my branch may not be the best. Add Comment Puppet / PUP-2389 Create ruby 2.0 branch for x64 in puppet-win32-ruby We need to vendor x64 versions of ruby 2.0, and install the appropriate sets of gems into both branches. Ruby 2.1 is not yet released on Windows. The work here includes: # create 2.0.0-x64 branch # vendor ruby 2.0.0-p545 (x64) from rubyinstaller.org OR newer if they release a patched version # upgrade/install gems for x64 versions 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-190) couldn't find HOME environment --expanding '~/.facter/facts.d'
Title: Message Title Adrien Thebo commented on an issue Re: couldn't find HOME environment --expanding '~/.facter/facts.d' Merged into facter-2 in 1a098cd. Add Comment Facter / FACT-190 couldn't find HOME environment --expanding '~/.facter/facts.d' couldn't find HOME environment --expanding '~/.facter/facts.d' facter 1.7.4 fails when HOME is not set. This is an issue if running a script via EXEC that calls facter. Steps to reproduce: 1) login to linux server 2) run the following commands # unset HOME # facter Error: couldn't find HOME environment -- expanding '~/.facter/facts.d' 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-190) couldn't find HOME environment --expanding '~/.facter/facts.d'
Title: Message Title Adrien Thebo updated an issue Facter / FACT-190 couldn't find HOME environment --expanding '~/.facter/facts.d' Change By: Adrien Thebo Fix Version/s: 2.1 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-471) Swap size reported as 0 for SmartOS zone
Title: Message Title Adrien Thebo commented on an issue Re: Swap size reported as 0 for SmartOS zone Merged in ef50ea9. Add Comment Facter / FACT-471 Swap size reported as 0 for SmartOS zone The swap size\free facts report 0 even though a swap partition exists. This is due to the way the swap partition is mounted inside a SmartOS container. There is a pull request open for this issue with a fix: https://github.com/puppetlabs/facter/pull/664 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-476) Make the 'processor' fact for OpenBSD consistent with other systems
Title: Message Title Adrien Thebo commented on an issue Re: Make the 'processor' fact for OpenBSD consistent with other systems Merged into facter-2 in 20dc40d. Add Comment Facter / FACT-476 Make the 'processor' fact for OpenBSD consistent with other systems Turns out 'processor = sparc64' is too terse, we already get that information via other facts so make the 'processor' fact on OpenBSD behave like other systems and return a value like SUNW,UltraSPARC-T1 (rev 0.0) @ 1000 MHz 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-567) Support Bundler workflow on x64
Title: Message Title
Josh Cooper commented on an issue
Re: Support Bundler workflow on x64
Kurt Wall yep, you got it, thanks
Add Comment
Facter / FACT-567
Support Bundler workflow on x64
Facter expresses Windows gem dependencies, but it only applies to ruby x86. When running on x64, the gem dependencies do not apply, so you can't use bundler to install gems, and run specs. Currently, facter's Gemfile uses the bundler `mingw` platform identifier, effectively: {noformat} platform :mingw do gem 'ffi' ... end {noformat} {{Bu...
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-2365) Puppet module tool on windows cannot connect to the forge
Title: Message Title Nicholas Fagerlund commented on an issue Re: Puppet module tool on windows cannot connect to the forge Okay, thank you for clearing that up! I think I've got it now; changed the text to the following: This can occur when you run the `puppet module` subcommand on newly provisioned Windows nodes. The Puppet Forge uses an SSL certificate signed by the GeoTrust Global CA certificate. Newly provisioned Windows nodes may not have that CA in their root CA store yet. To resolve this and enable the `puppet module` subcommand on Windows nodes, do one of the following: Run Windows Update and fetch all available updates, then visit https://forge.puppetlabs.com in your web browser. The web browser will notice that the GeoTrust CA is whitelisted for automatic download, and will add it to the root CA store. Download the GeoTrust Global CA certificate from [GeoTrust's list of root certificates](https://www.geotrust.com/resources/root-certificates/) and manually install it by running `certutil -addstore Root GeoTrust_Global_CA.pem`. If that's all we needed, I think this ticket can be closed; reassigning to you for the decision just in case there's anything else left that I'm forgetting about. Add Comment Puppet / PUP-2365 Puppet module tool on windows cannot connect to the forge Due to heartbleed, operations
Jira (PUP-2365) Puppet module tool on windows cannot connect to the forge
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2365 Puppet module tool on windows cannot connect to the forge Change By: Nicholas Fagerlund Assignee: NicholasFagerlund JoshCooper 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.
