Jira (PUP-2707) Puppet loads ZFS module on FreeBSD when ZFS is not enabled
Title: Message Title Remko Catersels commented on an issue Re: Puppet loads ZFS module on FreeBSD when ZFS is not enabled It does. Probably because of the zpool upgrade command. Any zfs/zpool command will automatically trigger the loading of the ZFS kernel module. Add Comment Puppet / PUP-2707 Puppet loads ZFS module on FreeBSD when ZFS is not enabled When puppet starts it triggers loading of the ZFS kernel module. This also happens when the machine does not have ZFS. root@w4:~ # kldstat Id Refs Address Size Name 1 1 0x8020 15b9558 kernel root@w4:~ # puppet agent -v --test Info: Retrieving plugin [cut for brevity] Notice: Finished catalog run in 17.58 seconds ... 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-1060) enablerepo and disablerepo for yum type
Title: Message Title
Sylvain Mougenot commented on an issue
Re: enablerepo and disablerepo for yum type
I confirm the previous comment : it is broken since 3.6.1.
Sample code
enablerepo.pp
yumrepo {'nginx':
name = 'nginx',
baseurl = 'http://nginx.org/packages/centos/6/$basearch/',
enabled = '0',
gpgcheck = '0',
descr= 'Nginx Repo'
}
package { 'nginx':
ensure = present,
install_options = ['--enablerepo=nginx'],
require = Yumrepo['nginx']
}
puppet apply -dv enablerepo.pp
Works on 3.6.0 :
Debug: Prefetching yum resources for package
Debug: Executing '/bin/rpm --version'
Debug: Executing '/bin/rpm -qa --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n''
Debug: Executing '/bin/rpm -q nginx --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'
Debug: Executing '/bin/rpm -q nginx --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n --whatprovides'
Debug: Package[nginx](provider=yum): Ensuring = present
Debug: Executing '/usr/bin/yum -d 0 -e 0 -y --enablerepo=Sogelink-CACHE install nginx'
Debug: Executing '/bin/rpm -q nginx --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'
Notice: /Stage[main]/Commun::Proxy_ign_inte/Package[nginx]/ensure: created
Fails on 3.6.1 or 3.6.2 :
Debug: Prefetching yum resources for package
Debug: Executing '/bin/rpm --version'
Debug: Executing '/bin/rpm -qa --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n''
Debug: Executing '/bin/rpm -q nginx --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'
Debug: Executing '/usr/bin/yum -d 0 -e 0 -y list nginx'
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list nginx' returned 1: Error: No matching Packages to list
Error: /Stage[main]/Commun::Proxy_ign_inte/Package[nginx]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y list nginx' returned 1: Error: No matching Packages to list
Jira (PUP-1060) enablerepo and disablerepo for yum type
Title: Message Title
Felix Frank commented on an issue
Re: enablerepo and disablerepo for yum type
Thanks for taking the time to look into this.
I believe that a regression should be tracked through a new Ticket that refers to this one instead of re-opening.
Add Comment
Puppet / PUP-1060
enablerepo and disablerepo for yum type
it would be nice to be able to enable a disabled repo for the installation on one package. for example installing facter from EPEL. something like; {noformat} package { facter: ensure = installed, enablerepo = [ epel, epel-testing ]; } {noformat}
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-2819) Managed files on
Title: Message Title Sebastian Lehn created an issue Puppet / PUP-2819 Managed files on Issue Type: Bug Affects Versions: 2.7.23 Assignee: Kylo Ginsberg Components: Types and Providers Created: 23/Jun/14 4:15 AM Priority: Normal Reporter: Sebastian Lehn Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2781) 'puppet module generate' create not compatible metadata.json with forge
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-2781 'puppet module generate' create not compatible metadata.json with forge Change By: Ethan Brown Assignee: EthanBrown 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 Ethan Brown assigned an issue to Ethan Brown Hiera / HI-273 Support Bundler workflow on x64 Change By: Ethan Brown Assignee: EthanBrown 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-2781) 'puppet module generate' create not compatible metadata.json with forge
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-2781
'puppet module generate' create not compatible metadata.json with forge
Verified generated metadata.json uses version_range
{
name: AzureDemo/moddepfr,
version: 0.1.0,
author: AzureDemo,
summary: Do it to do it,
license: Apache 2.0,
source: n/a,
project_page: n/a,
issues_url: n/a,
dependencies: [
{
name: puppetlabs-stdlib,
version_range: = 1.0.0
}
]
}
Tried publishing to forge anyhow, got the attached error.
Change By:
Ethan Brown
Attachment:
ScreenShot2014-06-23at4.50.06AM.png
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-2819) Managed files on FUSE without chmod/chown functionality
Title: Message Title Sebastian Lehn updated an issue Puppet / PUP-2819 Managed files on FUSE without chmod/chown functionality Change By: Sebastian Lehn Environment: -DebianWheezy7.5-Proxmox[pve-manager/3.2-4/e24a91c1(runningkernel:2.6.32-27-pve)] Affects Version/s: 3.6.2 Summary: Managedfileson FUSEwithoutchmod/chownfunctionality Sinceanupgradeofpuppetagentfrom(2.7.18-5)to(2.7.23-1)puppetisunabletomanagefilesonFUSE-Filesystempmxcfs.pmxcfsisafilesystemwithoutownerandpermissions.(https://pve.proxmox.com/wiki/Proxmox_Cluster_file_system_%28pmxcfs%29)Puppetstemporaryfilehandlinggotchangedinbetween,thatitcallstempfile.chownaswellastempfile.chmodoneveryrunthetargetfileshouldchange.Puppetskipstheresourcewithfailed:Functionnotimplementederror.(seeinfunctionPuppet.Util.replace_file())Theoriginversion2.7.18tempfilehandlingwasmoreacceptable,becauseitkeptthecurrentvaluesofmode,uidandgid_without_tryingtosetiteverytime.I'vealsotriedtosetcurrentownerandmodeinpuppet-whichwouldbeaacceptableworkaroundforme-butitdidnotworkbecausetempfilehandling.Maybeyoucouldofferanoptiontodefineadifferentpathfortempfileswhichwouldrelaxthesituationtoo.I'vetriedtochangethisbehaviorbywritinganotherfile-providerbuttempfile-handlingisdoneincoreutilclass.Formethatisarealmajorbugbecauseitchangesacorefunctionalityofpuppetwithinaminor-update! Add Comment
Jira (PUP-2781) 'puppet module generate' create not compatible metadata.json with forge
Title: Message Title
Ethan Brown commented on an issue
Re: 'puppet module generate' create not compatible metadata.json with forge
Upon using the newly published code, metadata.json is
{
name: AzureDemo/moddepfr,
version: 0.1.0,
author: AzureDemo,
summary: n/a,
license: Apache 2.0,
source: n/a,
project_page: null,
issues_url: null,
dependencies: [
{
version_requirement: = 1.0.0,
name: puppetlabs-stdlib
}
]
}
I was able to successfully publish this module to the forge – see attached screenshot
Add Comment
Puppet / PUP-2781
'puppet module generate' create not compatible metadata.json with forge
When one generate module by puppet it automaticlly adds version_range instead of version_requirement which is required to publish module {code} dependencies: [ { name: puppetlabs-stdlib, version_range: = 1.0.0 } ] {code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2781) 'puppet module generate' create not compatible metadata.json with forge
Title: Message Title Ethan Brown updated an issue Puppet / PUP-2781 'puppet module generate' create not compatible metadata.json with forge Change By: Ethan Brown Attachment: ScreenShot2014-06-23at5.20.27AM.png 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-335) Revisit how facter detects GCE instances
Title: Message Title Ethan Brown assigned an issue to Unassigned Facter / FACT-335 Revisit how facter detects GCE instances Change By: Ethan Brown Assignee: EthanBrown 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 Ethan Brown assigned an issue to Josh Cooper Just starting to verify specs, but we've got an issue right out of the gate with running specs thanks to spec_helper wanting to require 'win32console' Hiera / HI-273 Support Bundler workflow on x64 Change By: Ethan Brown Assignee: EthanBrown 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 (PUP-2813) Puppet parser is totally broken in this weird way
Title: Message Title
Henrik Lindberg commented on an issue
Re: Puppet parser is totally broken in this weird way
The problem is most likely in the concat function as it MUTATES the operand. See PUP-2090, and try the work around described there to see if that helps.
I am closing this as a duplicate of PUP-2090 (please reopen if the work around did not solve the issue).
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
Jira (HI-273) Support Bundler workflow on x64
Title: Message Title
Ethan Brown commented on an issue
Re: Support Bundler workflow on x64
PR has been sent against your branch: https://github.com/joshcooper/hiera/pull/1
I know that you mention here that Hiera needs FFI and Hiera doesn't need to know that.
However, I wonder if it makes sense to keep FFI in there for now, and to create a new ticket which uses an FFI based Win32 call to replace this chunk of Hiera code:
https://github.com/puppetlabs/hiera/blob/master/install.rb#L153
configdir = File.join(Dir::COMMON_APPDATA, PuppetLabs, hiera, etc)
https://github.com/puppetlabs/hiera/blob/7e8cb42897b8a848d43ef6249b589831775ff6c4/lib/hiera/util.rb#L42-L44
def common_appdata
Dir::COMMON_APPDATA
end
Or are we concerned that `win32-dir` is now always expected to be a part of Hiera and therefore might break 3rd parties relying on it?
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 ...
Jira (PUP-2341) puppet parser validate - no output when everything's ok
Title: Message Title Henrik Lindberg commented on an issue Re: puppet parser validate - no output when everything's ok Marcelo Carlos so, would you like a Syntax ok output to stdout ? 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) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send 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-2811) Provide method for class masquerading
Title: Message Title Henrik Lindberg commented on an issue Re: Provide method for class masquerading Posting my comment to this from puppet-dev... I see this as an essential feature to support maintainable modules. And by this, I mean a mechanism that decouples the wanted Element and its Container (where the Element is the thing we want/need/require, and the Container is the named thing it is in, typically a Module). This can be achieved by modules describing their provided and required capabilities. These are described as name spaced names and they are versioned. This creates an open ended system that can describe dependencies on either modules (like now) by using a name in the Module namespace, a gem in a gem namespace, a puppet class in a puppet name space, new types of dependencies can be added etc. As a very nice side effect the ability to describe provided capabilities makes it possible for a described entity to list the same capability multiple times with different versions, or version ranges, thus making it possible to describe components as backwards compatible, if not in full, for a smaller portion of the services it contains. The difficulty with this (any other similar solution) is the resolution of the dependencies as it requires something like a SAT solver. I worked on the implementation of such a system for Eclipse (Eclipse p2) which has been in use for a couple of years now as the software update/configuration mechanism for the Ecipse ecosystem. (If you are a Puppet Labs Geppetto user you have already used it, as it is what updates Geppetto with new releases). While such a system (as p2) is very flexible and powerful, the main problem is to explain why something is not installable (complete / updateable) - i.e. when there are parts missing, or when there are ambiguities. Even though p2 has such capabilities (thanks to the sat solver in use) it is often still a bit of a puzzle when facing non regular configurations (or tracking down the metadata that has bad consequences). If we do not attempt to solve the resolution, and simply validate the constraints, the problem is much much simpler, but you also do not get any help configuring a solution (except being slapped when the configuration is wrong/incomplete). It would be very interesting to conduct an experiment using p2 to describe configurations in the puppet domain. The p2 system can be used for other things than Java/OSGi/Eclipe and it is supported in the Nexus repository manager. Add Comment
Jira (PUP-2304) Implement requirements support for the PMT
Title: Message Title Henrik Lindberg commented on an issue Re: Implement requirements support for the PMT The simple approach of requiring a particular version of a named container of mixed services is a much to blunt instrument. The true dependency is most often a requirement on an implementation of a particular service/API of a particular version, and we simply to not have that granularity. There is nothing inherently wrong about being able to specify a hard requirement on one named container of a particular version as it may be that it is known that that is the only such provider of what is wanted. This is also the least flexible, and that requires constant changes of the consumer's meta data. I would like to see a system that is built on provided and required capabilities where it is possible to be much more fine grained and for a provider to provide a capability with multiple versions. (Or said differently, the provider of a capability can say something like I can be called both the 1.1 way, the 1.2 way, and the 2.0 way). This also looks like the same idea expressed in PUP-2811 where I also commented with a longer explanation about provided and required capabilities. Add Comment Puppet / PUP-2304 Implement requirements support for the PMT We should implement support for validated (at install time) requirements for modules, particularly for Puppet and Facter. As an example, if a release of module is published with a 'puppet' requirement and the current Puppet version does not fall in that range PMT should refuse to install that release. This behaviour can be bypassed with the --ignore-r...
Jira (HI-273) Support Bundler workflow on x64
Title: Message Title
Ethan Brown commented on an issue
Re: Support Bundler workflow on x64
Gemfile.lock for Ruby ruby 2.0.0p481 (2014-05-08) [x64-mingw32]
PATH
remote: .
specs:
hiera (1.3.4)
json_pure
GEM
remote: https://rubygems.org/
specs:
builder (3.2.2)
diff-lcs (1.1.3)
ffi (1.9.3-x64-mingw32)
json_pure (1.8.1)
metaclass (0.0.4)
mocha (0.10.5)
metaclass (~ 0.0.1)
rake (10.1.1)
rspec (2.11.0)
rspec-core (~ 2.11.0)
rspec-expectations (~ 2.11.0)
rspec-mocks (~ 2.11.0)
rspec-core (2.11.1)
rspec-expectations (2.11.3)
diff-lcs (~ 1.1.3)
rspec-mocks (2.11.3)
watchr (0.7)
win32-dir (0.4.8)
ffi (= 1.0.0)
win32console (1.3.2)
yarjuf (1.0.5)
builder
rspec (= 2.0)
PLATFORMS
x64-mingw32
DEPENDENCIES
ffi (= 1.9.3)
hiera!
json (~ 1.7)
mocha (~ 0.10.5)
rake (~ 10.1.0)
rspec (~ 2.11.0)
watchr
win32-dir (~ 0.4.8)
win32console (= 1.3.2)
yarjuf (~ 1.0)
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 ...
Jira (HI-273) Support Bundler workflow on x64
Title: Message Title
Ethan Brown commented on an issue
Re: Support Bundler workflow on x64
I believe the Gemfile.lock diff is as expected
--- from_file
+++ PATH
@@ -9,7 +9,7 @@
specs:
builder (3.2.2)
diff-lcs (1.1.3)
-ffi (1.9.3-x64-mingw32)
+ffi (1.9.3-x86-mingw32)
json_pure (1.8.1)
metaclass (0.0.4)
mocha (0.10.5)
@@ -26,13 +26,13 @@
watchr (0.7)
win32-dir (0.4.8)
ffi (= 1.0.0)
-win32console (1.3.2)
+win32console (1.3.2-x86-mingw32)
yarjuf (1.0.5)
builder
rspec (= 2.0)
PLATFORMS
- x64-mingw32
+ x86-mingw32
DEPENDENCIES
ffi (= 1.9.3)
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)
Jira (PUP-1299) Deprecate and eliminate magic parameter array handling
Title: Message Title
Henrik Lindberg commented on an issue
Re: Deprecate and eliminate magic parameter array handling
merged to master: f292423
Add Comment
Puppet / PUP-1299
Deprecate and eliminate magic parameter array handling
Puppet's parser will automatically de-arrayify single element arrays for parameters (and properties). See `lib/puppet/parser/resource.rb` {code} result[p] = if v.is_a?(Array) and v.length == 1 v[0] else v end {code} As a result when writing a custom type, the parameter...
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-2511) Add parser function digest: uses digest_algorithm to hash, not strictly md5
Title: Message Title Henrik Lindberg commented on an issue Re: Add parser function digest: uses digest_algorithm to hash, not strictly md5 For functional review, simply call the digest function with a string, and vary the digest_algorithm setting to see that different digests are produced. Add Comment Puppet / PUP-2511 Add parser function digest: uses digest_algorithm to hash, not strictly md5 Puppet has an md5 parser function, which returns the MD5 digest of its argument. On hosts configured for compliance with U.S. Federal Information Processing Standard (FIPS) 140-2, attempts to use the MD5 algorithm cause errors, because MD5 is no longer FIPS Approved. This patch adds a parser function called digest, which returns the digest of its arg... 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
Jira (HI-273) Support Bundler workflow on x64
Title: Message Title
Ethan Brown commented on an issue
Re: Support Bundler workflow on x64
Diff for Gemfile.lock against stable PR #196, which works as-is
--- from_file
+++ PATH
@@ -9,7 +9,7 @@
specs:
builder (3.2.2)
diff-lcs (1.1.3)
-ffi (1.9.3-x86-mingw32)
+ffi (1.9.3-x64-mingw32)
json_pure (1.8.1)
metaclass (0.0.4)
mocha (0.10.5)
@@ -31,7 +31,7 @@
rspec (= 2.0)
PLATFORMS
- x86-mingw32
+ x64-mingw32
DEPENDENCIES
hiera!
I will merge that PR since it's good to go...
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)
Jira (HI-273) Support Bundler workflow on x64
Title: Message Title
Ethan Brown commented on an issue
Re: Support Bundler workflow on x64
PR #196 merged to stable in https://github.com/puppetlabs/hiera/commit/b337b670fd4b5fd5af7f926315089dee3f62084f
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 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-2715) custom facts in module's facts.d directory should only be distributed to clients that use the module
Title: Message Title Henrik Lindberg commented on an issue Re: custom facts in module's facts.d directory should only be distributed to clients that use the module This ticket is marked with 3x, and the only remaining (planned release in the 3x series is 3.7). We should either include this or move it to an appropriate release. Add Comment Puppet / PUP-2715 custom facts in module's facts.d directory should only be distributed to clients that use the module Custom facts placed in environments/production/mymodule/facts.d are distributed to all nodes even if the node does not use module in its node definition. It seems to me that this behavior doesn't make sense, nor is it (in my opinion) what would be the intuitive behavior. I have a custom fact that assumes the presence of vpn addresses that returns an e... 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
Jira (HI-273) Support Bundler workflow on x64
Title: Message Title
Ethan Brown commented on an issue
Re: Support Bundler workflow on x64
Also, looks like we have to live with the DL is deprecated, please use Fiddle on the Ruby 2 / Windows combo. http://stackoverflow.com/questions/15590450/ruby-2-0-0p0-irb-error-dl-is-deprecated-please-use-fiddle
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 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 (PUP-2757) Apply parses everything twice
Title: Message Title
Henrik Lindberg commented on an issue
Re: Apply parses everything twice
Ready for merge as part of PR-2749 for PUP-2714
Add Comment
Puppet / PUP-2757
Apply parses everything twice
When the runtime creates {{Puppet::Resource}} instances, an attempt is made to lookup its type. This means that code will attempt to lookup the type in {{known_resource_types}}. If {{known_resource_type}} is nil, the runtime will issue a call to {{initial_import}} which is the starting point of parsing and evaluating code. The {{Puppet::Resource#envron...
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-2774) class can `require` itself without raising an error
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2774 class can `require` itself without raising an error Change By: Henrik Lindberg Fix Version/s: 4.x 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
Ethan Brown commented on an issue
Re: Support Bundler workflow on x64
I updated the PR to the PR... to only install win32console on x86
New diff for Gemfile.lock
--- from_file
+++ PATH
@@ -9,7 +9,7 @@
specs:
builder (3.2.2)
diff-lcs (1.1.3)
-ffi (1.9.3-x86-mingw32)
+ffi (1.9.3-x64-mingw32)
json_pure (1.8.1)
metaclass (0.0.4)
mocha (0.10.5)
@@ -26,13 +26,12 @@
watchr (0.7)
win32-dir (0.4.8)
ffi (= 1.0.0)
-win32console (1.3.2-x86-mingw32)
yarjuf (1.0.5)
builder
rspec (= 2.0)
PLATFORMS
- x86-mingw32
+ x64-mingw32
DEPENDENCIES
hiera!
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)
Jira (HI-273) Support Bundler workflow on x64
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Hiera / HI-273 Support Bundler workflow on x64 Change By: Ethan Brown Assignee: JoshCooper EthanBrown 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
Ethan Brown commented on an issue
Re: Support Bundler workflow on x64
Merged to master in https://github.com/puppetlabs/hiera/commit/67c507cd65dcce3bc33b5f75b3aad6f9eb9fd609
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 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 No FR is needed for this since we don't have any OpenBSD test platforms. 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 (PUP-2777) Support Bundler workflow on x64
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-2777 Support Bundler workflow on x64 Change By: Ethan Brown Assignee: JoshCooper EthanBrown 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-2807) 4x logging functions does not include container
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-2807 4x logging functions does not include container Change By: Henrik Lindberg Assignee: AndyParker 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-2807) 4x logging functions does not include container
Title: Message Title Henrik Lindberg commented on an issue Re: 4x logging functions does not include container 3x behavior added to the 4x functions by passing the calling scope. Add Comment Puppet / PUP-2807 4x logging functions does not include container The logging functions (notice, error, etc) were modified in future evaluator to use the new function API and the new loaders. In the new implementation, it was missed that the old (i.e. current) functions also output the name of the calling container (i.e. the resource owning the scope). First - do we want it to continue working the same way? (And if... 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-2578) Adjustments for new OpenBSD service provider
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2578 Adjustments for new OpenBSD service provider 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-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' Verified on └ HOME= bundle exec facter 1/dev/null /home/adrien/eng/projects/platform/facter/lib/facter/util/config.rb:49:in `expand_path': non-absolute home (ArgumentError) from /home/adrien/eng/projects/platform/facter/lib/facter/util/config.rb:49:in `setup_default_ext_facts_dirs' from /home/adrien/eng/projects/platform/facter/lib/facter/util/config.rb:60:in `module:Config' from /home/adrien/eng/projects/platform/facter/lib/facter/util/config.rb:5:in `top (required)' from /home/adrien/eng/projects/platform/facter/lib/facter/util/resolution.rb:2:in `require' from /home/adrien/eng/projects/platform/facter/lib/facter/util/resolution.rb:2:in `top (required)' from /home/adrien/eng/projects/platform/facter/lib/facter/util/fact.rb:2:in `require' from /home/adrien/eng/projects/platform/facter/lib/facter/util/fact.rb:2:in `top (required)' from /home/adrien/eng/projects/platform/facter/lib/facter.rb:35:in `require' from /home/adrien/eng/projects/platform/facter/lib/facter.rb:35:in `module:Facter' from /home/adrien/eng/projects/platform/facter/lib/facter.rb:30:in `top (required)' from /home/adrien/eng/projects/platform/facter/lib/facter/application.rb:2:in `require' from /home/adrien/eng/projects/platform/facter/lib/facter/application.rb:2:in `top (required)' from /home/adrien/eng/projects/platform/facter/bin/facter:18:in `require' from /home/adrien/eng/projects/platform/facter/bin/facter:18:in `top (required)' from /home/adrien/eng/projects/platform/facter/.bundle/ruby/1.9.1/bin/facter:23:in `load' from /home/adrien/eng/projects/platform/facter/.bundle/ruby/1.9.1/bin/facter:23:in `main' └ echo $? 1 └ git checkout facter-2 Previous HEAD position was 469995b... Merge pull request #700 from whopper/dhcp_confine_fix Switched to branch 'facter-2' Your branch is up-to-date with 'upstream/facter-2'. └ HOME= bundle exec facter 1/dev/null └ echo $? 0 Add Comment Facter / FACT-190 couldn't find HOME environment --expanding '~/.facter/facts.d'
Jira (PUP-2755) Move iterative functions to 4x function API
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Move iterative functions to 4x function API
Validated that all functions fail appropriately under current parser when called as standard functions:
# for func in 'each' 'map' 'reduce' 'slice' 'with';do puppet apply -e \$x = $func('foo', 'bar');done
Error: each() is only available when parser/evaluator future is in effect at line 1 on node wordpress-demo.puppetdebug.vlan
Error: each() is only available when parser/evaluator future is in effect at line 1 on node wordpress-demo.puppetdebug.vlan
Error: map() is only available when parser/evaluator future is in effect at line 1 on node wordpress-demo.puppetdebug.vlan
Error: map() is only available when parser/evaluator future is in effect at line 1 on node wordpress-demo.puppetdebug.vlan
Error: reduce() is only available when parser/evaluator future is in effect at line 1 on node wordpress-demo.puppetdebug.vlan
Error: reduce() is only available when parser/evaluator future is in effect at line 1 on node wordpress-demo.puppetdebug.vlan
Error: slice() is only available when parser/evaluator future is in effect at line 1 on node wordpress-demo.puppetdebug.vlan
Error: slice() is only available when parser/evaluator future is in effect at line 1 on node wordpress-demo.puppetdebug.vlan
Error: with() is only available when parser/evaluator future is in effect at line 1 on node wordpress-demo.puppetdebug.vlan
Error: with() is only available when parser/evaluator future is in effect at line 1 on node wordpress-demo.puppetdebug.vlan
# for func in 'filter' 'match';do puppet apply -e $func('foo', 'bar');done
Error: filter() is only available when parser/evaluator future is in effect at line 1 on node wordpress-demo.puppetdebug.vlan
Error: filter() is only available when parser/evaluator future is in effect at line 1 on node wordpress-demo.puppetdebug.vlan
Error: match() is only available when parser/evaluator future is in effect at line 1 on node wordpress-demo.puppetdebug.vlan
Error: match() is only available when parser/evaluator future is in effect at line 1 on node wordpress-demo.puppetdebug.vlan
Add Comment
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 Sprint: Week2014-6-18to2014-6-25 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 updated an issue Facter / FACT-471 Swap size reported as 0 for SmartOS zone Change By: Adrien Thebo 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-476) Make the 'processor' fact for OpenBSD consistent with other systems
Title: Message Title Adrien Thebo updated an issue Facter / FACT-476 Make the 'processor' fact for OpenBSD consistent with other systems Change By: Adrien Thebo Sprint: Week2014-6-18to2014-6-25 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 updated an issue Facter / FACT-471 Swap size reported as 0 for SmartOS zone Change By: Adrien Thebo Sprint: Week2014-6-18to2014-6-25 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 updated an issue Facter / FACT-471 Swap size reported as 0 for SmartOS zone 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-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 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-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 Skipping FR since we don't have any SmartOS boxes. 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 updated an issue Facter / FACT-476 Make the 'processor' fact for OpenBSD consistent with other systems Change By: Adrien Thebo 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-476) Make the 'processor' fact for OpenBSD consistent with other systems
Title: Message Title Josh Cooper updated an issue Facter / FACT-476 Make the 'processor' fact for OpenBSD consistent with other systems Change By: Josh Cooper Flagged: Impediment 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-190) couldn't find HOME environment --expanding '~/.facter/facts.d'
Title: Message Title Josh Cooper updated an issue Facter / FACT-190 couldn't find HOME environment --expanding '~/.facter/facts.d' Change By: Josh Cooper Flagged: Impediment 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 Josh Cooper updated an issue Facter / FACT-471 Swap size reported as 0 for SmartOS zone Change By: Josh Cooper Flagged: Impediment 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
hiera/stable ext/project_data.yaml is missing windows dependencies. It should depend on win32-dir for both x86 and x64, and win32console for x86 only.
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 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-2777) Support Bundler workflow on x64
Title: Message Title
Ethan Brown commented on an issue
Re: Support Bundler workflow on x64
Whoops, this is blocked on gem releases of Facter, Hiera ... and it would be preferable IMHO, to bump gems to FFI compatible versions before doing this.
Add Comment
Puppet / PUP-2777
Support Bundler workflow on x64
Puppet 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, puppet'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 (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 Assignee: EthanBrown 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 Andy Parker updated an issue Hiera / HI-273 Support Bundler workflow on x64 Change By: Andy Parker Sprint: Week2014-6-18to2014-6-25 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-417) Add acceptance cells which test with passenger instead of webrick.
Title: Message Title Andy Parker updated an issue Puppet / PUP-417 Add acceptance cells which test with passenger instead of webrick. Change By: Andy Parker Sprint: Week2014-3-05to2014-3-12,Week2014-3-12to2014-3-19,Week2014-6-11to2014-6-18 ,Week2014-6-25to2014-7-2 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 Andy Parker updated an issue Hiera / HI-273 Support Bundler workflow on x64 Change By: Andy Parker Sprint: Week2014-6- 25 18 to2014- 7 6 - 2 25 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 Andy Parker updated an issue Hiera / HI-273 Support Bundler workflow on x64 Change By: Andy Parker Sprint: Week2014-6-25to2014-7-2 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-417) Add acceptance cells which test with passenger instead of webrick.
Title: Message Title Andy Parker updated an issue Puppet / PUP-417 Add acceptance cells which test with passenger instead of webrick. Change By: Andy Parker Sprint: Week2014-3-05to2014-3-12,Week2014-3-12to2014-3-19,Week2014-6-11to2014-6-18 ,Week2014-6-18to2014-6-25 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-2703) tag should be a statement function in future parser
Title: Message Title Andy Parker updated an issue Puppet / PUP-2703 tag should be a statement function in future parser Change By: Andy Parker Sprint: Week2014-6- 25 18 to2014- 7 6 - 2 25 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-2663) Allow string to numeric conversion to start with + or -
Title: Message Title Andy Parker updated an issue Puppet / PUP-2663 Allow string to numeric conversion to start with + or - Change By: Andy Parker Sprint: Week2014-6- 25 18 to2014- 7 6 - 2 25 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-2750) expand profiler signature to support hierarchical profiling data
Title: Message Title Andy Parker updated an issue Puppet / PUP-2750 expand profiler signature to support hierarchical profiling data Change By: Andy Parker Sprint: Week2014-6- 25 18 to2014- 7 6 - 2 25 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-2511) Add parser function digest: uses digest_algorithm to hash, not strictly md5
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2511 Add parser function digest: uses digest_algorithm to hash, not strictly md5 Change By: Andy Parker Assignee: AndyParker 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-2663) Allow string to numeric conversion to start with + or -
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2663 Allow string to numeric conversion to start with + or - Change By: Andy Parker Assignee: AndyParker 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-2750) expand profiler signature to support hierarchical profiling data
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-2750 expand profiler signature to support hierarchical profiling data Change By: Andy Parker 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-2703) tag should be a statement function in future parser
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2703 tag should be a statement function in future parser Change By: Andy Parker Assignee: AndyParker 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-2711) The manifests directory should be recursively loaded when using directory environments
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2711 The manifests directory should be recursively loaded when using directory environments Change By: Henrik Lindberg Story Points: 3 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 (PUP-2711) The manifests directory should be recursively loaded when using directory environments
Title: Message Title
Henrik Lindberg commented on an issue
Re: The manifests directory should be recursively loaded when using directory environments
Turned out to be much simpler. Have to delay this to 4.0 though since it otherwise will create the risk of people getting files from subdirectories that they did not anticipate being included.
Add Comment
Puppet / PUP-2711
The manifests directory should be recursively loaded when using directory environments
We have a manifest directory with multiples subdirectories full of node definitions. We would prefer to stay with this layout rather than moving all the node definition files into the manifests directory. It would also make migration easier to directory environments as all one would need to do is remove the import function calls. {code} manifests ...
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
Jira (PUP-2711) The manifests directory should be recursively loaded when using directory environments
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2711 The manifests directory should be recursively loaded when using directory environments Change By: Henrik Lindberg Fix Version/s: 4.0.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-514) Add optional type to parameters
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-514 Add optional type to parameters 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-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 Manually verified on Sol 10 to make sure we didn't regress either. 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-574) Facter 2.1.0 2014-06-23 Release
Title: Message Title Adrien Thebo updated an issue Facter / FACT-574 Facter 2.1.0 2014-06-23 Release Change By: Adrien Thebo Assignee: ReleaseEngineering 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-2511) Add parser function digest: uses digest_algorithm to hash, not strictly md5
Title: Message Title Andy Parker commented on an issue Re: Add parser function digest: uses digest_algorithm to hash, not strictly md5 I'm going to pass this through functional review. The error reporting for future vs. current parser isn't great, but I don't think there is much that can be done. When this function gets ported over to the new api at some point in the future we can start putting into effect better error handling. Add Comment Puppet / PUP-2511 Add parser function digest: uses digest_algorithm to hash, not strictly md5 Puppet has an md5 parser function, which returns the MD5 digest of its argument. On hosts configured for compliance with U.S. Federal Information Processing Standard (FIPS) 140-2, attempts to use the MD5 algorithm cause errors, because MD5 is no longer FIPS Approved. This patch adds a parser function called digest, which returns the digest of its arg... 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 (FACT-575) Is the code ready for release?
Title: Message Title Adrien Thebo commented on an issue Re: Is the code ready for release? No new platforms added facter-2 branch will be merged into stable and cut from that. All issues targeted at 2.1 are in a Resolved state All specs and acceptance tests are passing. Add Comment Facter / FACT-575 Is the code ready for release? All tests (spec, acceptance) should be passing on all platforms for both stable master. * If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. * If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through sp... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2820) Array settings get misleading formatting for default values and error reporting
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-2820 Array settings get misleading formatting for default values and error reporting Issue Type: Bug Affects Versions: 3.6.2 Assignee: Unassigned Created: 23/Jun/14 10:28 AM Priority: Normal Reporter: Nicholas Fagerlund From the user's perspective, the new :array settings type is just a comma separated list, like we use in existing settings like dns_alt_names or tags. But the default values and error reporting for the disable_warnings setting aren't formatted with this in mind, and are presented in a confusing fashion: Error: Could not initialize global default settings: Cannot disable unrecognized warning types [stuff]. Valid values are [deprecations]. See also the config reference, which shows the default value as []. (http://docs.puppetlabs.com/references/latest/configuration.html#disablewarnings) If you try to follow these hints and give a value like [deprecations], you get: Error: Could not initialize global default settings: Cannot disable unrecognized warning types [[deprecations]]. Valid values are [deprecations]. Boo. The UI is a comma-separated list without
Jira (PUP-2821) disable_warnings section is inert in [master]
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-2821 disable_warnings section is inert in [master] Issue Type: Bug Affects Versions: 3.6.2 Assignee: Unassigned Created: 23/Jun/14 10:33 AM Priority: Normal Reporter: Nicholas Fagerlund The disable_warnings setting is completely ignored if it's set in the [master] section of puppet.conf. It seems to only be valid in the [main] section. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2703) tag should be a statement function in future parser
Title: Message Title
Andy Parker commented on an issue
Re: tag should be a statement function in future parser
Merged into master in bf5ad0
Add Comment
Puppet / PUP-2703
tag should be a statement function in future parser
The {{tag}} function should (just like include, require, contain, and the logging functions), be considered a statement function by the future parser. Now, it is required to use parentheses around its arguments.
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-2822) Description of disable_warnings setting is incomplete
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-2822 Description of disable_warnings setting is incomplete Issue Type: Bug Affects Versions: 3.6.2 Assignee: Nicholas Fagerlund Components: DOCS Created: 23/Jun/14 10:39 AM Priority: Normal Reporter: Nicholas Fagerlund The description currently reads: A list of warning types to disable. Currently the only warning type that can be disabled are deprecations, but more warning types may be added later. This needs a clearly labeled list of keywords; right now, the user has to guess. It could also use some context about why you would want to do this. Add Comment
Jira (FACT-575) Is the code ready for release?
Title: Message Title Josh Cooper commented on an issue Re: Is the code ready for release? We've added support for ruby 2.0 x64 on Windows. We do not have automated spec or acceptance tests for this yet (it is in progress). We need to manually verify the tests are passing. Also, due to QENG-790, jenkins facter spec jobs can return success even though the job failed. These jobs need to be manually verified (by looking at the jenkins console output). Add Comment Facter / FACT-575 Is the code ready for release? All tests (spec, acceptance) should be passing on all platforms for both stable master. * If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. * If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through sp... 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 (PUP-2703) tag should be a statement function in future parser
Title: Message Title
Andy Parker commented on an issue
Re: tag should be a statement function in future parser
Updated language specification with tag as an allowed function for statement style calls.
Add Comment
Puppet / PUP-2703
tag should be a statement function in future parser
The {{tag}} function should (just like include, require, contain, and the logging functions), be considered a statement function by the future parser. Now, it is required to use parentheses around its arguments.
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-575) Is the code ready for release?
Title: Message Title Adrien Thebo commented on an issue Re: Is the code ready for release? Latest facter windows specs (https://jenkins.puppetlabs.com/job/Facter-Specs-Windows-2.0/nodes=win2003r2/320/console and https://jenkins.puppetlabs.com/job/Facter-Specs-Windows-2.0/nodes=win2008r2/320/console) are passing. Add Comment Facter / FACT-575 Is the code ready for release? All tests (spec, acceptance) should be passing on all platforms for both stable master. * If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. * If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through sp... 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 (PUP-2389) Create ruby 2.0 branch for x64 in puppet-win32-ruby
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-2389 Create ruby 2.0 branch for x64 in puppet-win32-ruby 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 (PUP-839) FFI Puppet::Util::Windows::Security module
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-839 FFI Puppet::Util::Windows::Security module Change By: Rob Reynolds Assignee: RobReynolds 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-597) facter needs a package dependency on net-tools on rhel7 for ifconfig
Title: Message Title Tim Mooney created an issue Facter / FACT-597 facter needs a package dependency on net-tools on rhel7 for ifconfig Issue Type: Bug Affects Versions: 2.0.2, 1.7.6 Assignee: Eric Sorenson Created: 23/Jun/14 11:24 AM Priority: Normal Reporter: Tim Mooney With RHEL 7, a minimal install doesn't even include an ifconfig binary. It's still available as /sbin/ifconfig if you install the net-tools package, but it's no longer required and guaranteed to be there. I've tried both facter 1.7.6 and facter 2.0.2, both from the PuppetLabs repo, and because neither package records a dependency on net-tools for RHEL 7, neither version will correctly gather the interfaces fact, at least on a system where a minimal install was done. $ cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.0 (Maipo) $ type -a ifconfig -bash: type: ifconfig: not found $ facter --version 2.0.2 $ sudo facter | egrep 'interface' interfaces = $ sudo yum whatprovides /sbin/ifconfig net-tools-2.0-0.17.20131004git.el7.x86_64 : Basic networking tools Repo : rhel-x86_64-server-7 Matched from: Filename : /sbin/ifconfig $ sudo yum install net-tools $ sudo facter | egrep 'interfaces' interfaces = ens192,ens224,lo The easy, short-term fix is to update the package so that for RHEL 7, facter also requires that net-tools is installed. Note that I've linked this issue to FACT-184, since Red Hat has indicated that ifconfig is now deprecated and ip should be used instead. In addition, the release notes for RHEL 7 indicate that the output format
Jira (FACT-576) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Adrien Thebo commented on an issue Re: Is there a JIRA ticket targeted at the release for every commit? The commit for FACT-471 (46eac60) improperly referenced FACT-664 but was merged. Add Comment Facter / FACT-576 Is there a JIRA ticket targeted at the release for every commit? Ensure all tickets referenced in the commit log have a bug targeted at the release * git log old tag..new tag * look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release * Also, make sure the code itself is sane, that you understand why the change was made, etc. et... 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-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 For posterity, the commit for FACT-471 (46eac60) improperly referenced FACT-664 but was merged. 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-576) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Adrien Thebo commented on an issue Re: Is there a JIRA ticket targeted at the release for every commit? Functionality for FACT-465 was merged in 796919f64c2004ed10666abb90da174ba5d6 but those issues do not reference the issue. Add Comment Facter / FACT-576 Is there a JIRA ticket targeted at the release for every commit? Ensure all tickets referenced in the commit log have a bug targeted at the release * git log old tag..new tag * look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release * Also, make sure the code itself is sane, that you understand why the change was made, etc. et... 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-391) Validate FFI'ed native windows code against Ruby 2 x64
Title: Message Title
Josh Cooper commented on an issue
Re: Validate FFI'ed native windows code against Ruby 2 x64
Once PR 2787 is merged, we need to remove the gem from puppet-win32-ruby branch 2.0.0-x64 also
Add Comment
Puppet / PUP-391
Validate FFI'ed native windows code against Ruby 2 x64
Puppet makes some x86 assumptions in win32 native code. Once ruby 2.x x64 builds are available, we need to validate that our FFI'ed code continues to run on x64, and that we are not making bad assumptions, e.g. {code}0.chr * 4{code}
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 Josh Cooper commented on an issue Re: Create ruby 2.0 branch for x64 in puppet-win32-ruby Merged in bb8a39bc to 2.0.0-x64. Note the branch contains some gems that we plan on removing soon, and are covered by other tickets: sys-admin (PUP-391) windows-pr win32-api (PUP-2521) win32console (PUP-1281) Prior to merging, I ran facter and puppet using only this ruby and preinstalled gems. It looked good. Also compared facter output against a ruby 1.9.3 x86 run, and the diff was as expected, only uptime, memory, etc facts where different. 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
Jira (FACT-377) Does not detect LXC virtualization
Title: Message Title Adrien Thebo commented on an issue Re: Does not detect LXC virtualization Marking as a duplicate of FACT-189 . Add Comment Facter / FACT-377 Does not detect LXC virtualization Facter does not detect when run in an LXC virtual environment. It reports is_virtual = false and virtual = physical. 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-576) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Adrien Thebo commented on an issue Re: Is there a JIRA ticket targeted at the release for every commit? FACT-376 was merged in 627. Add Comment Facter / FACT-576 Is there a JIRA ticket targeted at the release for every commit? Ensure all tickets referenced in the commit log have a bug targeted at the release * git log old tag..new tag * look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release * Also, make sure the code itself is sane, that you understand why the change was made, etc. et... 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 (FACT-576) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Adrien Thebo commented on an issue Re: Is there a JIRA ticket targeted at the release for every commit? FACT-268 was merged in 297d804b1a. Add Comment Facter / FACT-576 Is there a JIRA ticket targeted at the release for every commit? Ensure all tickets referenced in the commit log have a bug targeted at the release * git log old tag..new tag * look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release * Also, make sure the code itself is sane, that you understand why the change was made, etc. et... 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 (FACT-576) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Adrien Thebo commented on an issue Re: Is there a JIRA ticket targeted at the release for every commit? FACT-190 was merged in 1a098cd. Add Comment Facter / FACT-576 Is there a JIRA ticket targeted at the release for every commit? Ensure all tickets referenced in the commit log have a bug targeted at the release * git log old tag..new tag * look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release * Also, make sure the code itself is sane, that you understand why the change was made, etc. et... 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 (FACT-576) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Adrien Thebo commented on an issue Re: Is there a JIRA ticket targeted at the release for every commit? All JIRA issues present and accounted for. Add Comment Facter / FACT-576 Is there a JIRA ticket targeted at the release for every commit? Ensure all tickets referenced in the commit log have a bug targeted at the release * git log old tag..new tag * look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release * Also, make sure the code itself is sane, that you understand why the change was made, etc. et... 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 Ethan Brown assigned an issue to Josh Cooper Hiera / HI-273 Support Bundler workflow on x64 Change By: Ethan Brown 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-377) Does not detect LXC virtualization
Title: Message Title Adrien Thebo updated an issue Facter / FACT-377 Does not detect LXC virtualization 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-484) virtual fact spews permission errors on Debian unstable
Title: Message Title Adrien Thebo updated an issue Facter / FACT-484 virtual fact spews permission errors on Debian unstable 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-484) virtual fact spews permission errors on Debian unstable
Title: Message Title
Adrien Thebo commented on an issue
Re: virtual fact spews permission errors on Debian unstable
Merged in 64b32dd5b0.
Add Comment
Facter / FACT-484
virtual fact spews permission errors on Debian unstable
The following happens only when running as an unprivileged user. When running _facter_ or _facter virtual_ (or puppet agent/apply fwiw), the following error is emitted (twice) {noformat} ffrank@geras:~/git/facter$ bundle exec facter virtual Could not retrieve fact='virtual', resolution='anonymous': Permission denied - /sys/firmware/dmi/entries/1...
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-337) _timestamp fact
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-337 _timestamp fact Change By: Wyatt Alt Sprint: 20140618to20140702 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-337) _timestamp fact
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-337 _timestamp fact Change By: Wyatt Alt 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 (HI-273) Support Bundler workflow on x64
Title: Message Title
Josh Cooper commented on an issue
Re: Support Bundler workflow on x64
Fix for gem packaging merged into stable in 2c3bced9
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 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-460) ci-bootstrap-from-artifacts.sh should fall-back to public Rubygems
Title: Message Title Adrien Thebo updated an issue Facter / FACT-460 ci-bootstrap-from-artifacts.sh should fall-back to public Rubygems 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-577) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Adrien Thebo commented on an issue Re: Is there a commit for every JIRA ticket targeted at the release? Commit a255384 incorrectly references FACT-247 when it should reference FACT-249 . Add Comment Facter / FACT-577 Is there a commit for every JIRA ticket targeted at the release? Ensure all tickets targeted at the release have a corresponding commit * git log old tag..new tag * This time, look through tickets targeted at this release in JIRA, and compare it to the commit log, looking for the corresponding numbers * [ticketmatch.rb script|https://gist.github.com/hlindberg/9520023] is a ruby script that helps with Is 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
