Jira (FACT-1434) Recognize "wxallowed" as mount option
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1434 Re: Recognize "wxallowed" as mount option pull request Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1434) Recognize "wxallowed" as mount option
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1434 Recognize "wxallowed" as mount option Issue Type: Improvement Affects Versions: FACT 3.1.7 Assignee: Unassigned Created: 2016/06/02 2:50 AM Environment: OpenBSD 6.0 Facter 3.1.8 Priority: Normal Reporter: Jasper Lievisse Adriaanse OpenBSD has recently added a new mount flag "wxallowed". Facter doesn't currently list that: % facter mountpoints./usr/local.options [
Jira (FACT-1432) Fixup OpenBSD networking facts
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1432 Re: Fixup OpenBSD networking facts PR: https://github.com/puppetlabs/facter/pull/1344 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1433) Unbreak OpenBSD swap facts
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1433 Re: Unbreak OpenBSD swap facts PR: https://github.com/puppetlabs/facter/pull/1345 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1433) Unbreak OpenBSD swap facts
Title: Message Title
Jasper Lievisse Adriaanse updated an issue
Facter / FACT-1433
Unbreak OpenBSD swap facts
Change By:
Jasper Lievisse Adriaanse
Currently the OpenBSD swap facts wildly overstate the case:{ available => "16.00 EiB", available_bytes => -2736640, capacity => "0%", encrypted => true, total => "16.00 EiB", total_bytes => -2736640, used => "0 bytes", used_bytes => 0}I don't know why I thought the current code was any good, but it failed to account for the different units as used in the OpenBSD kernel and as used by facter. Now the output is sane again:{ available => "8.00 GiB", available_bytes => 8587197440, capacity => "0%", encrypted => true, total => "8.00 GiB", total_bytes => 8587197440, used => "0 bytes", used_bytes => 0}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1433) Unbreak OpenBSD swap facts
Title: Message Title
Jasper Lievisse Adriaanse created an issue
Facter / FACT-1433
Unbreak OpenBSD swap facts
Issue Type:
Bug
Affects Versions:
FACT 3.1.7
Assignee:
Unassigned
Created:
2016/05/31 6:59 AM
Environment:
OpenBSD 6.0
Priority:
Normal
Reporter:
Jasper Lievisse Adriaanse
Currently the OpenBSD swap facts wildly overstate the case: { available => "16.00 EiB", available_bytes => -2736640, capacity => "0%", encrypted => true, total => "16.00 EiB", total_bytes => -2736640, used => "0 bytes", used_bytes => 0 }
I don't know why I thought the current code was any good, but it failed to account for the different units as used in the OpenBSD kernel and as used by facter.
Add Comment
Jira (FACT-1432) Fixup OpenBSD networking facts
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1432 Fixup OpenBSD networking facts Issue Type: Improvement Affects Versions: FACT 3.1.7 Assignee: Unassigned Created: 2016/05/30 9:59 AM Environment: OpenBSD 6.0 Priority: Normal Reporter: Jasper Lievisse Adriaanse When FACT-1116 was merged, it seems some parts went missing. I hadn't noticed earlier because I didn't update the facter port in OpenBSD, however I did so earlier today. There was discussion at https://github.com/puppetlabs/facter/pull/1041#issuecomment-122338470 . That point still stands. However I'd still like to get the code for this new PR in and work from there.
Jira (FACT-1431) Enable curl on OpenBSD
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1431 Enable curl on OpenBSD Issue Type: Improvement Affects Versions: FACT 3.1.7 Assignee: Unassigned Created: 2016/05/30 9:40 AM Environment: OpenBSD 6.0 Priority: Normal Reporter: Jasper Lievisse Adriaanse Facter builds perfectly fine with curl enabled on OpenBSD, so there's no need to prevent building it. Add Comment
Jira (FACT-1177) Add swap facts to OpenBSD memory resolver
Title: Message Title
Jasper Lievisse Adriaanse created an issue
Facter / FACT-1177
Add swap facts to OpenBSD memory resolver
Issue Type:
Improvement
Affects Versions:
FACT 3.0.2
Assignee:
Unassigned
Created:
2015/08/27 11:15 AM
Fix Versions:
FACT 3.1.0
Priority:
Normal
Reporter:
Jasper Lievisse Adriaanse
Currently the memory resolver on OpenBSD lacks support for the swap-related facts. With that part implemented memory.swap now returns:
{
available = 1.73 GiB,
Jira (FACT-1177) Add swap facts to OpenBSD memory resolver
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1177 Re: Add swap facts to OpenBSD memory resolver Pull request Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4337) OpenBSD package provider does not correctly install packages
Title: Message Title Jasper Lievisse Adriaanse commented on PUP-4337 Re: OpenBSD package provider does not correctly install packages Hi, Finally gotten around to looking into this. To be clear, the title seems to suggest nothing can be installed with the OpenBSD package provider, which is not true. There are however issues when trying to install packages that don't actually exist: Info: Applying configuration version '1440161319' Debug: Prefetching openbsd resources for package Debug: Executing '/usr/sbin/pkg_info -a' Debug: Executing '/usr/sbin/pkg_info sasquatch' Debug: Executing '/usr/sbin/pkg_info -I sasquatch' Debug: Executing '/usr/sbin/pkg_add -r sasquatch' Notice: /Stage[main]/Main/Package[sasquatch]/ensure: created Wether or not sasquatch exists in real life is another matter, but puppet should indeed fail instead of reporting the package has been installed. Note however: obsidian:2001 pup-4337 % doas pkg_add -r sasquatch Can't find sasquatch obsidian:2002 pup-4337 % echo $? 0 obsidian:2003 pup-4337 % And that's a bug in pkg_add(8). It should set the return value to something non-zero. I'll submit a PR shortly which results in: Error: pkg_add returned: Can't find sasquatch Error: /Stage[main]/Main/Package[sasquatch]/ensure: change from absent to present failed: pkg_add returned: Can't find sasquatch Notice: Finished catalog run in 4.65 seconds Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-4337) OpenBSD package provider does not correctly install packages
Title: Message Title Jasper Lievisse Adriaanse assigned an issue to Jasper Lievisse Adriaanse Puppet / PUP-4337 OpenBSD package provider does not correctly install packages Change By: Jasper Lievisse Adriaanse Assignee: JasperLievisseAdriaanse Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-891) dynamic library support cannot determine first_load on AIX
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-891 Re: dynamic library support cannot determine first_load on AIX The merge of pr #75 works for OpenBSD too. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1080) CFacter fails to link (libboost_log vs libboost_log-mt)
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1080 Re: CFacter fails to link (libboost_log vs libboost_log-mt) Peter Huene it's actually still an issue, however I'm working around it by forcing leatherman to link with boost_log: http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/sysutils/facter/patches/patch-vendor_leatherman_logging_CMakeLists_txt?rev=1.1content-type=text/x-cvsweb-markup Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1143) Processor resolver for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1143 Re: Processor resolver for OpenBSD PR Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1144) Memory resolver for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1144 Memory resolver for OpenBSD Issue Type: Improvement Affects Versions: FACT 3.0.2 Assignee: Unassigned Created: 2015/07/23 1:09 AM Environment: OpenBSD 5.8 Priority: Normal Reporter: Jasper Lievisse Adriaanse Facter is currently lacking a memory resolver for OpenBSD. Add Comment
Jira (FACT-1144) Memory resolver for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1144 Re: Memory resolver for OpenBSD PR Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1143) Processor resolver for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1143 Processor resolver for OpenBSD Issue Type: Improvement Affects Versions: FACT 3.0.2 Assignee: Unassigned Created: 2015/07/23 12:31 AM Environment: OpenBSD 5.8 Priority: Normal Reporter: Jasper Lievisse Adriaanse Currently there is no processor resolver for OpenBSD. Add Comment
Jira (FACT-1145) Virtualization resolver for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1145 Virtualization resolver for OpenBSD Issue Type: Improvement Affects Versions: FACT 3.0.2 Assignee: Unassigned Created: 2015/07/23 1:16 AM Environment: OpenBSD 5.8 Priority: Normal Reporter: Jasper Lievisse Adriaanse Facter is currently lacking a virtualization resolver for OpenBSD. Add Comment
Jira (FACT-1145) Virtualization resolver for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1145 Re: Virtualization resolver for OpenBSD PR Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1132) dmi resolver for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1132 dmi resolver for OpenBSD Issue Type: Improvement Affects Versions: FACT 3.0.1 Assignee: Unassigned Created: 2015/07/16 2:47 PM Environment: OpenBSD 5.8 Priority: Normal Reporter: Jasper Lievisse Adriaanse OpenBSD currently lacks many resolvers, so let's add a small one which adds the needed infrastructure bits for other resolvers to use. The dmi resolver could be used for this. Add Comment
Jira (FACT-1129) Correctly setup Ruby load path to unbreak loading rbconfig
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1129 Correctly setup Ruby load path to unbreak loading rbconfig Issue Type: Bug Affects Versions: FACT 3.0.1 Assignee: Unassigned Created: 2015/07/16 9:26 AM Environment: OpenBSD 5.8, Ruby 2.1.6 Priority: Normal Reporter: Jasper Lievisse Adriaanse On OpenBSD we have multiple Ruby versions, where for Ruby 2.1 the loadpath is set to: [/usr/local/lib/ruby/site_ruby/2.1, /usr/local/lib/ruby/site_ruby/2.1/x86_64-openbsd,
Jira (FACT-1130) Install facter.rb into vendorlibdir instead of vendordir
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1130 Install facter.rb into vendorlibdir instead of vendordir Issue Type: Bug Affects Versions: FACT 3.0.1 Assignee: Unassigned Created: 2015/07/16 9:42 AM Environment: OpenBSD 5.8, Ruby 2.1.6 Priority: Normal Reporter: Jasper Lievisse Adriaanse OpenBSD allows for installing multiple Ruby versions at the same time. Due to this, some directories are versioned to prevent conflicts. facter.rb was being installed into vendordir, which is unversioned and would thus create a conflict. It should however be installed into vendorlibdir which is versioned. On CentOS 7: irb(main):001:0 puts RbConfig::CONFIG['vendordir']
Jira (FACT-1129) Correctly setup Ruby load path to unbreak loading rbconfig
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1129 Re: Correctly setup Ruby load path to unbreak loading rbconfig pull request Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1130) Install facter.rb into vendorlibdir instead of vendordir
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1130 Re: Install facter.rb into vendorlibdir instead of vendordir pull request Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1132) dmi resolver for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1132 Re: dmi resolver for OpenBSD pull request Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1118) Add 'noatime' option to mountpoint fact
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1118 Add 'noatime' option to mountpoint fact Issue Type: Improvement Affects Versions: FACT 3.0.1 Assignee: Unassigned Components: Community Created: 2015/07/13 1:46 AM Environment: OpenBSD 5.8 Priority: Normal Reporter: Jasper Lievisse Adriaanse The mountpoints fact could be improved to also list the 'noatime' field for 'options'. I didn't guard it with an ifdef as it seems all systems I check have it (Linux, AIX, FreeBSD, OpenBSD).
Jira (FACT-930) Bad library dependency when building for FreeBSD
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-930 Re: Bad library dependency when building for FreeBSD In order to resolve this ticket the handling I added for OpenBSD will need to be expanded for FreeBSD too. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1118) Add 'noatime' option to mountpoint fact
Title: Message Title Jasper Lievisse Adriaanse updated an issue Facter / FACT-1118 Add 'noatime' option to mountpoint fact Change By: Jasper Lievisse Adriaanse Themountpointsfactcouldbeimprovedtoalsolistthe'noatime'fieldfor'options'.Ididn'tguarditwithanifdefasitseemsallsystemsIcheckhaveit(Linux,AIX,FreeBSD,OpenBSD). When#1081isresolvedIwillsubmitthePR. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1118) Add 'noatime' option to mountpoint fact
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1118 Re: Add 'noatime' option to mountpoint fact pull request Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1116) Unbreak network facts resolver on BSD
Title: Message Title Jasper Lievisse Adriaanse updated an issue Facter / FACT-1116 Unbreak network facts resolver on BSD Change By: Jasper Lievisse Adriaanse Summary: Unabletobuild Unbreak networkfactsresolveronBSD Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1116) Unable to build network facts resolver on BSD
Title: Message Title
Jasper Lievisse Adriaanse commented on FACT-1116
Re: Unable to build network facts resolver on BSD
Here's the pull request.
With that PR (and a separate forthcoming patch to actually build these files on OpenBSD) I get the following which matches ifconfig(8):
networking = {
domain = local,
fqdn = obsidian.local,
hostname = obsidian,
interfaces = {
em0 = {
mac = 4a:57:0b:01:ff:87,
mtu = 1500
},
enc0 = {
Jira (FACT-1116) Unable to build network facts resolver on BSD
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1116 Unable to build network facts resolver on BSD Issue Type: Bug Affects Versions: FACT 3.0.1 Assignee: Unassigned Components: Community Created: 2015/07/11 5:16 AM Environment: OpenBSD 5.8 GCC 4.9.2 Priority: Normal Reporter: Jasper Lievisse Adriaanse I'm trying to build the `bsd/network_resolver.cc` on OpenBSD, however it's failing like this: FAILED: /usr/local/bin/ccache eg++ -DBOOST_ALL_DYN_LINK -DBOOST_LOG_WITHOUT_WCHAR_T -DLEATHERMAN_LOGGING_NAMESPACE=\puppetlabs.facter\ -DUSE_OPENSSL -DUSE_POSIX_FUNCTIONS -DUSE_YAMLCPP -O2 -pipe
Jira (FACT-1116) Unable to build network facts resolver on BSD
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1116 Re: Unable to build network facts resolver on BSD Actually, I've figured it out myself so I'll submit a PR shortly. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1081) Unable to build filesystem_resolver
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1081 Re: Unable to build filesystem_resolver Michael Smith could you please have a look at this? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1081) Unable to build filesystem_resolver
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1081 Re: Unable to build filesystem_resolver Yup, I'm using: Using built-in specs. COLLECT_GCC=/usr/local/bin/eg++ COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-unknown-openbsd5.8/4.9.2/lto-wrapper Target: x86_64-unknown-openbsd5.8 Configured with: /usr/obj/gcc-4.9.2/gcc-4.9.2/configure --enable-libgcj --without-jar --verbose --program-transform-name='s,^,e,' --disable-nls --with-system-zlib --disable-libmudflap --disable-libgomp --disable-tls --with-as=/usr/bin/as --with-ld=/usr/bin/ld --with-gnu-ld --with-gnu-as --enable-threads=posix --enable-wchar_t --with-gmp=/usr/local --enable-languages=c,c++,fortran,objc,java,ada --disable-libstdcxx-pch --enable-cpp --enable-shared --prefix=/usr/local --sysconfdir=/etc --mandir=/usr/local/man --infodir=/usr/local/info --localstatedir=/var --disable-silent-rules --disable-gtk-doc Thread model: posix gcc version 4.9.2 (GCC)
Jira (FACT-1081) Unable to build filesystem_resolver
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1081 Re: Unable to build filesystem_resolver That didn't do the trick, seems like it's still the same error: /usr/obj/ports/facter-3.0.1/facter-3.0.1/lib/src/facts/bsd/filesystem_resolver.cc: In static member function 'static std::vectorstd::basic_stringchar facter::facts::bsd::filesystem_resolver::to_options(const statfs)': /usr/obj/ports/facter-3.0.1/facter-3.0.1/lib/src/facts/bsd/filesystem_resolver.cc:54:9: error: converting to 'std::tupleunsigned int, std::basic_stringchar, std::char_traitschar, std::allocatorchar ' from initializer list would use explicit constructor 'constexpr std::tuple_T1, _T2::tuple(_U1, _U2) [with _U1 = int; _U2 = std::basic_stringchar; template-parameter-2-3 = void; _T1 = unsigned int; _T2 = std::basic_stringchar]' }; Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (FACT-1081) Unable to build filesystem_resolver
Title: Message Title
Jasper Lievisse Adriaanse commented on FACT-1081
Re: Unable to build filesystem_resolver
Michael Smith does the output below of OpenBSD change your comment to a '' ?
mountpoints = {
/ = {
available = 341.29 MiB,
available_bytes = 357865472,
capacity = 66.15%,
device = /dev/sd2a,
filesystem = ffs,
options = [
local,
root
],
Jira (FACT-1081) Unable to build filesystem_resolver
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1081 Re: Unable to build filesystem_resolver We have a winner! I've submitted a PR for the make_tuple() changes. When that approach looks good I will add the needed #ifdef magic needed for OpenBSD when this PR is merged. Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options,
Jira (FACT-891) dynamic library support cannot determine first_load on AIX
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-891 Re: dynamic library support cannot determine first_load on AIX This is actually an issue on OpenBSD too. For example this was fixed in OpenJDK like this: http://hg.openjdk.java.net/bsd-port/jdk8/jdk/rev/ce213452b047 So perhaps the check should be modified to be: #if defined(RTLD_NOLOAD) _handle = dlopen(name.c_str(), RTLD_LAZY | RTLD_NOLOAD); #else _handle = dlopen(name.c_str(), RTLD_LAZY); #endif Otherwise I'll submit a PR to add _OpenBSD_ to the #ifdef for the time being. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1080) CFacter fails to link (libboost_log vs libboost_log-mt)
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1080 CFacter fails to link (libboost_log vs libboost_log-mt) Issue Type: Bug Affects Versions: FACT 3.0.1 Assignee: Unassigned Created: 2015/06/30 2:58 AM Environment: OpenBSD 5.8, Boost 1.58, GCC 4.9.2 Labels: leatherman facter Priority: Normal Reporter: Jasper Lievisse Adriaanse I'm currently in the process of porting CFacter to OpenBSD however there appears to be a linking issue. For some reason I end up with undefined references to: /usr/obj/ports/facter-3.0.1/build-amd64/lib/libfacter.so.0.0: undefined reference to `boost::log::v2_st::aux::default_attribute_names::message()' /usr/obj/ports/facter-3.0.1/build-amd64/lib/libfacter.so.0.0: undefined reference to `void boost::log::v2_st::aux::parse_date_time_formatchar(char const*, char const*, boost::log::v2_st::aux::date_time_format_parser_callbackchar)' [...] While I have -lboost_log-mt in the
Jira (FACT-1081) Unable to build filesystem_resolver
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1081 Unable to build filesystem_resolver Issue Type: Bug Affects Versions: FACT 3.0.1 Assignee: Unassigned Created: 2015/06/30 7:05 AM Environment: OpenBSD 5.8, GCC 4.9, Boost 1.58 Priority: Normal Reporter: Jasper Lievisse Adriaanse Compiling lib/src/facts/bsd/filesystem_resolver.cc (with a local modification to skip undefined flags) results in the following error: [1/18] /usr/local/bin/ccache eg++ -DBOOST_ALL_DYN_LINK -DBOOST_LOG_WITHOUT_WCHAR_T -DLEATHERMAN_LOGGING_NAMESPACE=\puppetlabs.facter\ -DUSE_OPENSSL -DUSE_POSIX_FUNCTIONS -DUSE_YAMLCPP -O2 -pipe -Wno-maybe-uninitialized -std=c++11 -Wall -Werror -Wno-unused-parameter -Wno-unused-local-typedefs -Wno-unknown-pragmas -Wno-missing-field-initializers -Wextra -DNDEBUG -fPIC -I/usr/obj/ports/facter-3.0.1/facter-3.0.1/lib/inc -I/usr/obj/ports/facter-3.0.1/facter-3.0.1/vendor/rapidjson-0.11/include -I/usr/local/include -I/usr/obj/ports/facter-3.0.1/facter-3.0.1/vendor/leatherman/vendor/boost-nowide -I/usr/obj/ports/facter-3.0.1/facter-3.0.1/vendor/leatherman/locale/inc -I/usr/obj/ports/facter-3.0.1/facter-3.0.1/vendor/leatherman/logging/inc -MMD -MT lib/CMakeFiles/libfactersrc.dir/src/facts/bsd/filesystem_resolver.cc.o -MF
Jira (FACT-1081) Unable to build filesystem_resolver
Title: Message Title Jasper Lievisse Adriaanse assigned an issue to Peter Huene Facter / FACT-1081 Unable to build filesystem_resolver Change By: Jasper Lievisse Adriaanse Assignee: PeterHuene Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1080) CFacter fails to link (libboost_log vs libboost_log-mt)
Title: Message Title Jasper Lievisse Adriaanse assigned an issue to Peter Huene Facter / FACT-1080 CFacter fails to link (libboost_log vs libboost_log-mt) Change By: Jasper Lievisse Adriaanse Assignee: PeterHuene Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4602) 'bsd' service provider doesn't work with rcng
Title: Message Title Jasper Lievisse Adriaanse created an issue Puppet / PUP-4602 'bsd' service provider doesn't work with rcng Issue Type: Bug Affects Versions: PUP 4.0.0 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2015/05/13 3:48 AM Priority: Normal Reporter: Jasper Lievisse Adriaanse Enabling services with rcng (NetBSD's rc system) doesn't work with the 'bsd' service provider. It writes 'foo_enable=YES' but that returns an error with rcng. A new provider subclassing the 'bsd' provider should be added to fix this. Add Comment
Jira (PUP-4602) 'bsd' service provider doesn't work with rcng
Title: Message Title Jasper Lievisse Adriaanse commented on PUP-4602 Re: 'bsd' service provider doesn't work with rcng When PUP-4562 is merged I'll submit the pull request for this. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4562) 'bsd' service provider non-functional
Title: Message Title Jasper Lievisse Adriaanse created an issue Puppet / PUP-4562 'bsd' service provider non-functional Issue Type: Bug Affects Versions: PUP 4.0.0 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2015/05/12 3:58 AM Priority: Normal Reporter: Jasper Lievisse Adriaanse The generic 'bsd' service provider was still using @model instead of @resource, therefore it was not working at all. There are currently no spec tests (or users?) for this provider which is probably why it went unnoticed for so long. Could that be backported to the 3.8 stable branches too? Add Comment
Jira (PUP-4562) 'bsd' service provider non-functional
Title: Message Title Jasper Lievisse Adriaanse commented on PUP-4562 Re: 'bsd' service provider non-functional I've amended the PR with a spec test so future changes can be more easily verified. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4562) 'bsd' service provider non-functional
Title: Message Title Jasper Lievisse Adriaanse commented on PUP-4562 Re: 'bsd' service provider non-functional PR: https://github.com/puppetlabs/puppet/pull/3918 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4546) pkgin output incorrectly parsed
Title: Message Title Jasper Lievisse Adriaanse commented on PUP-4546 Re: pkgin output incorrectly parsed PR: https://github.com/puppetlabs/puppet/pull/3905 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4546) pkgin output incorrectly parsed
Title: Message Title
Jasper Lievisse Adriaanse created an issue
Puppet / PUP-4546
pkgin output incorrectly parsed
Issue Type:
Bug
Affects Versions:
PUP 4.0.0
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
2015/05/08 1:59 AM
Environment:
cargos, pkgsrc 2015q1,
Priority:
Normal
Reporter:
Jasper Lievisse Adriaanse
The pkgin tool adjusts it's output when run from an interactive or non-interactive terminal by replacing spaces with semicolons. The provider was not adjusted for this and thus exhibited odd behaviour such as 'puppet resource package virt-what' resulting in:
package { 'virt-what': ensure = '1.15;Detect', }
The PR associated with the ticket switches the 'search' and 'list' commands to explicitly use '-p' (for parsable format) eventhough it's implied for non-interactive, and adjusts the regex accordingly.
Jira (PUP-4337) OpenBSD package provider does not correctly install packages
Title: Message Title Jasper Lievisse Adriaanse commented on PUP-4337 Re: OpenBSD package provider does not correctly install packages Hi, I will have a look at this the coming week. There are some other modifications to the package provider (from Sebastia@OpenBSD) that I will submit too which greatly improve the flavor handling. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3784) Puppet raises error when trying to apply user resources under FreeBSD
Title: Message Title Jasper Lievisse Adriaanse commented on PUP-3784 Re: Puppet raises error when trying to apply user resources under FreeBSD Hi, I actually do a ton of Puppet on OpenBSD and have never worked with the pw user provider. Having said that, does `puppet resource user joe` return anything for you? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3736) OpenBSD service provider should restart a service when flags are changed
Title: Message Title
Jasper Lievisse Adriaanse created an issue
Puppet / PUP-3736
OpenBSD service provider should restart a service when flags are changed
Issue Type:
Improvement
Affects Versions:
PUP 3.7.3
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
2014/12/04 12:17 AM
Environment:
OpenBSD -current
Priority:
Normal
Reporter:
Jasper Lievisse Adriaanse
Currently a service is not restarted when the flags for it are changed, which does not adhere to the rule of least surprise.
So for example if 'apmd_flags=-C' are set and the daemon runs with '-C', the following manifest will only update `/etc/rc.conf.local`:
``` service { 'apmd': ensure = running, enable = true, flags = '-A', ```
But the service that's currently running won't be affected and keeps running with '-C' instead of '-A'.
The proposed change is to force a restart of the service when the flags are
Jira (PUP-3736) OpenBSD service provider should restart a service when flags are changed
Title: Message Title Jasper Lievisse Adriaanse commented on PUP-3736 Re: OpenBSD service provider should restart a service when flags are changed PR: https://github.com/puppetlabs/puppet/pull/3376 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3723) Add support for setting a user's login class
Title: Message Title Jasper Lievisse Adriaanse created an issue Puppet / PUP-3723 Add support for setting a user's login class Issue Type: New Feature Affects Versions: PUP 3.7.3 Assignee: Kylo Ginsberg Components: Client Created: 2014/12/02 11:56 AM Environment: OpenBSD 5.6 and ruby-shadow 2.4.1 Priority: Normal Reporter: Jasper Lievisse Adriaanse Some systems (like OpenBSD) allow setting the user's login class. Support for this has been added to ruby-shadow 2.4.0, and Puppet can make use of this. I'm currently waiting for the merge of a PR on which this is dependant (https://github.com/puppetlabs/puppet/pull/3267), once that is merged I'll submit a new PR to implement a 'loginclass' feature for the 'user' type.
Jira (PUP-3604) Puppet fails to install correct package when 'ensure = $version' is set
Title: Message Title
Jasper Lievisse Adriaanse created an issue
Puppet / PUP-3604
Puppet fails to install correct package when 'ensure = $version' is set
Issue Type:
Bug
Affects Versions:
PUP 3.7.2
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
2014/11/02 12:04 PM
Environment:
OpenBSD
Priority:
Normal
Reporter:
Jasper Lievisse Adriaanse
On OpenBSD some packages have multiple versions available, such as Python 2.7 and 3.3, or openldap-server 2.3 and 2.4.
With a resource such as:
``` package { 'openldap-server': ensure = '2.4' }
```
Puppet would end up installing the first valid version it saw on a mirror (2.3, and not 2.4), which is generally the correct approach, unless a user specifically sets the version to install with `ensure`.
Jira (PUP-3604) Puppet fails to install correct package when 'ensure = $version' is set
Title: Message Title Jasper Lievisse Adriaanse commented on PUP-3604 Re: Puppet fails to install correct package when 'ensure = $version' is set PR: https://github.com/puppetlabs/puppet/pull/3266 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3605) Puppet doesn't remove users from groups
Title: Message Title Jasper Lievisse Adriaanse created an issue Puppet / PUP-3605 Puppet doesn't remove users from groups Issue Type: Bug Affects Versions: PUP 3.7.2 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2014/11/02 12:09 PM Environment: OpenBSD Priority: Normal Reporter: Jasper Lievisse Adriaanse The -G flag of the OpenBSD usermod command doesn't behave like most elsewhere. Instead of setting the groups, it appends the specified groups to the existing list of groups for a user. The analogue flag for Linux' -G flag is -S on OpenBSD.
Jira (PUP-3605) Puppet doesn't remove users from groups
Title: Message Title Jasper Lievisse Adriaanse commented on PUP-3605 Re: Puppet doesn't remove users from groups PR: https://github.com/puppetlabs/puppet/pull/3267 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3243) There's no way the 'bsd' service provider will work on OpenBSD
Title: Message Title Jasper Lievisse Adriaanse created an issue Puppet / PUP-3243 There's no way the 'bsd' service provider will work on OpenBSD Issue Type: Bug Assignee: Kylo Ginsberg Components: Types and Providers Created: 15/Sep/14 1:12 AM Priority: Normal Reporter: Jasper Lievisse Adriaanse OpenBSD has it's own service provider and the 'bsd' service provider will certainly not work on OpenBSD. Therefore remove 'OpenBSD' from the 'confine' list. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-685) Implement processors['speed'] for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-685 Implement processors['speed'] for OpenBSD Issue Type: Improvement Assignee: Eric Sorenson Created: 26/Aug/14 4:36 AM Priority: Normal Reporter: Jasper Lievisse Adriaanse The structured `processors` fact lacks the `speed` field on OpenBSD, this PR implements that: https://github.com/puppetlabs/facter/pull/771 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received
Jira (PUP-3144) Rewrite OpenBSD service provider with rcctl(8)
Title: Message Title Jasper Lievisse Adriaanse created an issue Puppet / PUP-3144 Rewrite OpenBSD service provider with rcctl(8) Issue Type: Improvement Assignee: Unassigned Created: 26/Aug/14 4:40 AM Priority: Normal Reporter: Jasper Lievisse Adriaanse OpenBSD has added the rcctl(8) tool to the base system, which is intended to provide a common tool for service and daemon management on OpenBSD. This PR implements the rewrite of the provider and tests: https://github.com/puppetlabs/puppet/pull/3017 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3066) Services are started before flags are set
Title: Message Title
Jasper Lievisse Adriaanse created an issue
Puppet / PUP-3066
Services are started before flags are set
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Kylo Ginsberg
Components:
Client
Created:
15/Aug/14 6:09 AM
Environment:
OpenBSD
Priority:
Normal
Reporter:
Jasper Lievisse Adriaanse
The OpenBSD service provider is marked `flaggable` which means that `flags` may be passed which are written into `/etc/rc.conf.local`. These flags control the behaviour of the service when they're started.
However it seems there's an issue in the ordering, the flags are written out to disk (flushed) after the service is started. This means that the service is started without the flags that have been set:
$ ps ax | grep apmd 26569 p6 R+ 0:00.00 grep apmd $ grep apmd /etc/rc.conf.local $ sudo puppet apply -e 'service {apmd: ensure = running, enable = true, flags = -C}
' Notice: Compiled catalog for obsidian.office.jasper.la in environment production in 0.81 seconds Notice: /Stage[main]/Main/Service[apmd]/ensure:
Jira (PUP-3066) Services are started before flags are set
Title: Message Title Jasper Lievisse Adriaanse commented on an issue Re: Services are started before flags are set PR: https://github.com/puppetlabs/puppet/pull/2978 Add Comment Puppet / PUP-3066 Services are started before flags are set The OpenBSD service provider is marked `flaggable` which means that `flags` may be passed which are written into `/etc/rc.conf.local`. These flags control the behaviour of the service when they're started. However it seems there's an issue in the ordering, the flags are written out to disk (flushed) _after_ the service is started. This means that the s... 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-621) Add OpenBSD support for 'partitions' fact
Title: Message Title Jasper Lievisse Adriaanse commented on an issue Re: Add OpenBSD support for 'partitions' fact Would it help functional testing if beaker were available on OpenBSD? Add Comment Facter / FACT-621 Add OpenBSD support for 'partitions' fact Currently the partitions fact only supports Linux, this PR adds support for OpenBSD too. 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-621) Add OpenBSD support for 'partitions' fact
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-621 Add OpenBSD support for 'partitions' fact Issue Type: Improvement Assignee: Eric Sorenson Created: 09/Jul/14 8:25 AM Priority: Normal Reporter: Jasper Lievisse Adriaanse Currently the partitions fact only supports Linux, this PR adds support for OpenBSD too. 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
Jira (FACT-621) Add OpenBSD support for 'partitions' fact
Title: Message Title Jasper Lievisse Adriaanse commented on an issue Re: Add OpenBSD support for 'partitions' fact PR is at: https://github.com/puppetlabs/facter/pull/722 Add Comment Facter / FACT-621 Add OpenBSD support for 'partitions' fact Currently the partitions fact only supports Linux, this PR adds support for OpenBSD too. 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-1638) Puppet 3.4.2 broken in OpenBSD
Title: Message Title
Jasper Lievisse Adriaanse commented on an issue
Re: Puppet 3.4.2 broken in OpenBSD
If you get Puppet 3.4.2 you're using OpenBSD 5.5 (release), right? If you upgrade to -current you'll have Puppet 3.6.2.
Anyways, CVSweb is indeed sub-optimal, or heck, cvs in general even...however if you checkout the `OPENBSD_5_5` tag, you'll have the sources that built the 3.4.2 package for OpenBSD 5.5. If you're tracking -current then you can omit checking out a specific tag and just look at the REVISION in the Makefile if that matches the 'pN' part of the package name.
Add Comment
Puppet / PUP-1638
Puppet 3.4.2 broken in OpenBSD
When running puppet agent -t --debug --trace I get the following error: {quote} Debug: Failed to load library 'selinux' for feature 'selinux' Debug: Using settings: adding file resource 'confdir': 'File[/etc/puppet]{:path=/etc/puppet, :ensure=:directory, :loglevel=:debug, :links=:follow, :backup=false}' Debug: Failed to load library 'shadow' f...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google
Jira (FACT-595) Unbreak {is_,}virtual fact for OpenBSD when running on KVM
Title: Message Title
Jasper Lievisse Adriaanse commented on an issue
Re: Unbreak {is_,}virtual fact for OpenBSD when running on KVM
https://github.com/puppetlabs/facter/pull/701
Add Comment
Facter / FACT-595
Unbreak {is_,}virtual fact for OpenBSD when running on KVM
It turned out the parse_virtualization method didn't account for KVM therefore at least OpenBSD wouldn't correctly set the virtual facts when running on KVM.
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-595) Unbreak {is_,}virtual fact for OpenBSD when running on KVM
Title: Message Title
Jasper Lievisse Adriaanse created an issue
Facter / FACT-595
Unbreak {is_,}virtual fact for OpenBSD when running on KVM
Issue Type:
Bug
Assignee:
Eric Sorenson
Created:
21/Jun/14 12:26 AM
Priority:
Normal
Reporter:
Jasper Lievisse Adriaanse
It turned out the parse_virtualization method didn't account for KVM therefore at least OpenBSD wouldn't correctly set the virtual facts when running on KVM.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-592) Add swapfree/swapsize facts for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-592 Add swapfree/swapsize facts for OpenBSD Issue Type: Improvement Affects Versions: 2.0.2 Assignee: Jasper Lievisse Adriaanse Created: 19/Jun/14 6:19 AM Priority: Normal Reporter: Jasper Lievisse Adriaanse OpenBSD lacks support for the swapsize and swapfree facts. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-592) Add swapfree/swapsize facts for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse commented on an issue Re: Add swapfree/swapsize facts for OpenBSD Actually, it seems they were already present but totally broken. https://github.com/puppetlabs/facter/pull/698 Add Comment Facter / FACT-592 Add swapfree/swapsize facts for OpenBSD OpenBSD lacks support for the swapsize and swapfree facts. 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-1638) Puppet 3.4.2 broken in OpenBSD
Title: Message Title
Jasper Lievisse Adriaanse commented on an issue
Re: Puppet 3.4.2 broken in OpenBSD
Hi,
It's actually fairly trivial to examine the patches: http://www.openbsd.org/cgi-bin/cvsweb/ports/sysutils/ruby-puppet/3/ And since I'm the maintainer of Puppet in OpenBSD, yes, there are plenty of patches in the package that are in various staging of being merged upstream.
In general, if there is a native package available for something on OpenBSD, use that instead of installing it via npm/pypi/gems or whatever source as changes are, the package has had fixes to make it work better on OpenBSD. Case in point, Puppet
Add Comment
Puppet / PUP-1638
Puppet 3.4.2 broken in OpenBSD
When running puppet agent -t --debug --trace I get the following error: {quote} Debug: Failed to load library 'selinux' for feature 'selinux' Debug: Using settings: adding file resource 'confdir': 'File[/etc/puppet]{:path=/etc/puppet, :ensure=:directory, :loglevel=:debug, :links=:follow, :backup=false}' Debug: Failed to load library 'shadow' f...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2578) Adjustments for new OpenBSD service provider
Title: Message Title
Jasper Lievisse Adriaanse created an issue
Puppet / PUP-2578
Adjustments for new OpenBSD service provider
Issue Type:
Improvement
Assignee:
Adrien Thebo
Components:
Types and Providers
Created:
15/May/14 12:08 AM
Priority:
Normal
Reporter:
Jasper Lievisse Adriaanse
After some more testing of @xaque208 new service provider I ran into an issue where a service from packages like:
service {'puppetboard': enable = true }
would end up with the following in /etc/rc.conf.local:
puppetboard_flags= This breaks the script, as it has sets it's local daemon_flags which are then overridden by the flags from rc.conf.local (to ), so if there are no :flags set, then the _flags= should not be written out.
Also, order is important for pkg_scripts as things like avahi-daemon need dbus_daemon to be started. Therefore pkg_scripts must not be sorted but just append to and let people define the order (if there needs to be one) by using dependency resources.
Thirdly, after some discussion it was deemed better (and faster) to turn #in_base? really into in base instead of not in base by looking at /etc/rc.conf which contains all the base daemons.
PR: https://github.com/puppetlabs/puppet/pull/2557
Jira (FACT-376) Backport OpenBSD changes to Facter 2
Title: Message Title Jasper Lievisse Adriaanse commented on an issue Re: Backport OpenBSD changes to Facter 2 Thank you very much! Add Comment Facter / FACT-376 Backport OpenBSD changes to Facter 2 Not a bug per se, but I was wondering about some code I've written last year for Facter that never got included into a release because they were features, not bugfixes. However, looking at the rc1 of facter 2.0.1 I noticed the code was most still not there: https://github.com/puppetlabs/facter/commits?author=jasperla https://github.com/puppetlabs/fa... 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-2454) User ID's below 1000, not 500, are generally considered system users on OpenBSD
Title: Message Title Jasper Lievisse Adriaanse created an issue Puppet / PUP-2454 User ID's below 1000, not 500, are generally considered system users on OpenBSD Issue Type: Improvement Assignee: Unassigned Created: 04/May/14 2:42 AM Priority: Normal Reporter: Jasper Lievisse Adriaanse Users can still modify this with 'uid_start' in adduser.conf, but in that case they'd need to provide an actual value instead of 'true'. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2454) User ID's below 1000, not 500, are generally considered system users on OpenBSD
Title: Message Title Jasper Lievisse Adriaanse commented on an issue Re: User ID's below 1000, not 500, are generally considered system users on OpenBSD PR: https://github.com/puppetlabs/puppet/pull/2547 Add Comment Puppet / PUP-2454 User ID's below 1000, not 500, are generally considered system users on OpenBSD Users can still modify this with 'uid_start' in adduser.conf, but in that case they'd need to provide an actual value instead of 'true'. 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-1069) Implement feature :upgradeable for OpenBSD package provider
Title: Message Title Jasper Lievisse Adriaanse commented on an issue Re: Implement feature :upgradeable for OpenBSD package provider New PR: https://github.com/puppetlabs/puppet/pull/2558 Add Comment Puppet / PUP-1069 Implement feature :upgradeable for OpenBSD package provider It's currently not possible to use ensure = latest on OpenBSD. The code itself works correct in my testing, however I'm having some issues with getting spec tests to pass and I'd appreciate some help with that as it appears to return the version for the bash fixture, and not the new (or old) version of tcsh. 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 Jasper Lievisse Adriaanse created an issue Facter / FACT-476 Make the 'processor' fact for OpenBSD consistent with other systems Issue Type: Improvement Affects Versions: 2.0.1 Assignee: Eric Sorenson Created: 02/May/14 11:54 AM Priority: Normal Reporter: Jasper Lievisse Adriaanse 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 Add Comment This message was sent by
Jira (PUP-2311) OpenBSD uninstall broken when multiple uninstall_options given
Title: Message Title Jasper Lievisse Adriaanse created an issue Puppet / PUP-2311 OpenBSD uninstall broken when multiple uninstall_options given Issue Type: Bug Affects Versions: 3.5.1 Assignee: Adrien Thebo Components: Types and Providers Created: 21/Apr/14 3:43 PM Environment: OpenBSD -current, amd64. Priority: Normal Reporter: Jasper Lievisse Adriaanse As I found out while working on :upgradeable today, the way we pass arguments to pkg_add/pkg_delete is slightly off. Currently we pass it a single string, which confuses pkg_* as it sees -r -z (without quotes) as a single argument, the same applies to the #uninstall method in case multiple uninstall_options were passed.
Jira (PUP-2311) OpenBSD uninstall broken when multiple uninstall_options given
Title: Message Title Jasper Lievisse Adriaanse commented on an issue Re: OpenBSD uninstall broken when multiple uninstall_options given PR: https://github.com/puppetlabs/puppet/pull/2563 Add Comment Puppet / PUP-2311 OpenBSD uninstall broken when multiple uninstall_options given As I found out while working on :upgradeable today, the way we pass arguments to pkg_add/pkg_delete is slightly off. Currently we pass it a single string, which confuses pkg_* as it sees -r -z (without quotes) as a single argument, the same applies to the #uninstall method in case multiple uninstall_options were passed. 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-376) Status of merged code in facter-2 vs. master
Title: Message Title Jasper Lievisse Adriaanse commented on an issue Re: Status of merged code in facter-2 vs. master Hi, I just noticed that 2.0.1 was released, however most of my contributions to Facter in the past year were not released as part of it: https://github.com/puppetlabs/facter/commit/fc8b1446c31ba595421bb8b039504835bf48172e https://github.com/puppetlabs/facter/commit/766c84a84a4a7008858c45eaf221402a81e1bfa2 https://github.com/puppetlabs/facter/commit/d58f8c512935f9c05fe8645d2d22bc05ddfb1c7c https://github.com/puppetlabs/facter/commit/42e2814800615c16ad3c0cf124f7aba1e99df9f1 Will these be merged at some point still? Add Comment Facter / FACT-376 Status of merged code in facter-2 vs. master Not a bug per se, but I was wondering about some code I've written last year for Facter that never got included into a release because they were features, not bugfixes. However, looking at the rc1 of facter 2.0.1 I noticed the code was most still not there: https://github.com/puppetlabs/facter/commits?author=jasperla https://github.com/puppetlabs/fa... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-564) Add OpenBSD to puppetdb.env
Title: Message Title Jasper Lievisse Adriaanse created an issue PuppetDB / PDB-564 Add OpenBSD to puppetdb.env Issue Type: Improvement Affects Versions: 1.6.3 Assignee: Unassigned Created: 31/Mar/14 2:52 AM Environment: OpenBSD 5.5-current Priority: Normal Reporter: Jasper Lievisse Adriaanse Adding OpenBSD specific variables allows the OpenBSD package maintained downstream in the OpenBSD ports tree to be greatly simplified. While here, I've adjusted the values for install_dir and libexec_dir to match the locations for third-party software on OpenBSD and I've fixed up the init script with the install_dir. Add Comment
Jira (PDB-564) Add OpenBSD to puppetdb.env
Title: Message Title
Jasper Lievisse Adriaanse commented on an issue
Re: Add OpenBSD to puppetdb.env
Pull request: https://github.com/puppetlabs/puppetdb/pull/905
Add Comment
PuppetDB / PDB-564
Add OpenBSD to puppetdb.env
Adding OpenBSD specific variables allows the OpenBSD package maintained downstream in the OpenBSD ports tree to be greatly simplified. While here, I've adjusted the values for {{install_dir}} and {{libexec_dir}} to match the locations for third-party software on OpenBSD and I've fixed up the init script with the {{install_dir}}.
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-376) Status of merged code in facter-2 vs. master
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-376 Status of merged code in facter-2 vs. master Issue Type: Task Affects Versions: 2.0.1 Assignee: Adrien Thebo Created: 06/Mar/14 11:31 AM Priority: Normal Reporter: Jasper Lievisse Adriaanse Not a bug per se, but I was wondering about some code I've written last year for Facter that never got included into a release because they were features, not bugfixes. However, looking at the rc1 of facter 2.0.1 I noticed the code was most still not there: https://github.com/puppetlabs/facter/commits?author=jasperla https://github.com/puppetlabs/facter/commits/facter-2?author=jasperla So what's the status of that? Will they be merged into facter-2 or ..? Add Comment
Jira (PUP-1218) Improve ssh-ed25519 integration
Title: Message Title
Jasper Lievisse Adriaanse commented on an issue
Re: Improve ssh-ed25519 integration
Thanks Kylo Ginsberg, I'll keep that in mind.
Add Comment
Puppet / PUP-1218
Improve ssh-ed25519 integration
For 3.4 support was added to store ssh-ed25519 keys through {{ssh_authorized_keys}}; this patch adds support for those keys to the {{sshkey}} type as well as to the {{ssh_authorized_keys}} provider}}'s parsed provider.
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/groups/opt_out.
Jira (PUP-1218) Improve ssh-ed25519 integration
Title: Message Title
Jasper Lievisse Adriaanse commented on an issue
Re: Improve ssh-ed25519 integration
This has been merged into master already, so is there any further review needed for it to appear in 3.5.0?
Add Comment
Puppet / PUP-1218
Improve ssh-ed25519 integration
For 3.4 support was added to store ssh-ed25519 keys through {{ssh_authorized_keys}}; this patch adds support for those keys to the {{sshkey}} type as well as to the {{ssh_authorized_keys}} provider}}'s parsed provider.
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/groups/opt_out.
Jira (PUP-1218) Improve ssh-ed25519 integration
Title: Message Title
Jasper Lievisse Adriaanse commented on an issue
Re: Improve ssh-ed25519 integration
This was merged as 702b8c4c934f7699d53be81319ae0eaf203067c4
Add Comment
Puppet / PUP-1218
Improve ssh-ed25519 integration
For 3.4 support was added to store ssh-ed25519 keys through {{ssh_authorized_keys}}; this patch adds support for those keys to the {{sshkey}} type as well as to the {{ssh_authorized_keys}} provider}}'s parsed provider.
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/groups/opt_out.
Jira (PUP-1218) Improve ssh-ed25519 integration
Title: Message Title Jasper Lievisse Adriaanse updated an issue Puppet / PUP-1218 Improve ssh-ed25519 integration Change By: Jasper Lievisse Adriaanse Fix Version/s: 3.5.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/groups/opt_out.
Jira (PUP-1218) Improve ssh-ed25519 integration
Title: Message Title Jasper Lievisse Adriaanse created an issue Puppet / PUP-1218 Improve ssh-ed25519 integration Issue Type: Improvement Affects Versions: 3.4.0 Assignee: Unassigned Components: Types and Providers Created: 21/Dec/13 1:44 PM Priority: Normal Reporter: Jasper Lievisse Adriaanse For 3.4 support was added to store ssh-ed25519 keys through ssh_authorized_keys; this patch adds support for those keys to the sshkey type as well as to the ssh_authorized_keys provider}}'s parsed provider. Add Comment
Jira (PUP-1204) Puppet Master (3.2.2/CentOs) - Puppet Agent (3.2.2/W2008)
Title: Message Title Jasper Lievisse Adriaanse commented on an issue Re: Puppet Master (3.2.2/CentOs) - Puppet Agent (3.2.2/W2008) With Puppet 3.4 on the master (OpenBSD) and the agent (Win7 / x86_64) I did not run into this issue anymore. Could someone confirm this? Add Comment Puppet / PUP-1204 Puppet Master (3.2.2/CentOs) - Puppet Agent (3.2.2/W2008) Hello, I am experiencing this issue. Could not retrieve domain: undefined method `gsub' for nil:NilClass Could not retrieve domain: undefined method `gsub' for nil:NilClass Could not retrieve domain: undefined method `gsub' for nil:NilClass Error: Failed to apply catalog: SSL_connect SYSCALL returned=5 errno=0 state=SSL v2/v3 read server hello A... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For
