Jira (PUP-9044) Update puppet portage package provider for new output generated by qatom
Title: Message Title Matthew Thode commented on PUP-9044 Re: Update puppet portage package provider for new output generated by qatom Is there a place I can track the forward ports? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PUP-9044) Update puppet portage package provider for new output generated by qatom
Title: Message Title Matthew Thode commented on PUP-9044 Re: Update puppet portage package provider for new output generated by qatom Ya, contributing doesn't really call out making your change to the oldest active branch (and that tooling will forward port for you). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PUP-9044) Update puppet portage package provider for new output generated by qatom
Title: Message Title Matthew Thode commented on PUP-9044 Re: Update puppet portage package provider for new output generated by qatom https://github.com/puppetlabs/puppet/pull/6976 is the PR to master (6.1). It should clean merge all the way back to 5.x Do you want PRs for all the branches back to 5.5? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PUP-9044) Update puppet portage package provider for new output generated by qatom
Title: Message Title Matthew Thode commented on PUP-9044 Re: Update puppet portage package provider for new output generated by qatom It looks like the code is in 4.x versions as well, do I need to backport it myself or wait for master to merge first? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PUP-9044) Update puppet portage package provider for new output generated by qatom
Title: Message Title Matthew Thode created an issue Puppet / PUP-9044 Update puppet portage package provider for new output generated by qatom Issue Type: Bug Assignee: Matthew Thode Components: Types and Providers Created: 2018/08/06 10:58 PM Priority: Normal Reporter: Matthew Thode Puppet Version: puppet-agent-5.5.4 Puppet Server Version: 5.3.4 OS Name/Version: Gentoo qatom output used to look like: qatom app-admin/puppet app-admin puppet (null) ...but now looks like... qatom app-admin/puppet app-admin puppet in app-portage/portage-utils-0.72 and above. Desired Behavior: the qatom output to be parsed correctly Actual Behavior: Error: Could not update: Execution of '/usr/bin/emerge -update app-admin/puppet' returned 1: !!! 'app-admin/puppet-' is not a valid package atom. Add Comment
Jira (FACT-1618) Facter 3.6.4 fails to build with leatherman 0.12.0
Title: Message Title Matthew Thode commented on FACT-1618 Re: Facter 3.6.4 fails to build with leatherman 0.12.0 Not sure why this 'needs info' or has been assigned to me, but as far as Gentoo goes, 0.12.1 has been packaged and stabilized, 0.12.0 has been removed. So it's fixed downstream and upstream released a fix in 0.12.0, so... fixed? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1618) Facter 3.6.4 fails to build with leatherman 0.12.0
Title: Message Title Matthew Thode commented on FACT-1618 Re: Facter 3.6.4 fails to build with leatherman 0.12.0 I can wait til 0.12.1 comes out. We (gentoo) generally have multiple versions of packages available, so ideally it should work with both. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1578) Facter incorrectly converts integers causing negative values to be stored in PDB
Title: Message Title Matthew Thode commented on FACT-1578 Re: Facter incorrectly converts integers causing negative values to be stored in PDB This is still failing (see https://tickets.puppetlabs.com/browse/FACT-1618 for more info). reverting 9dc37895c677f6e7e0ec3e748de5938d9273d814 AND 97bcbed321f3f3b972d3399ee3d2e2ed1765f09e at least lets me build again. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1618) Facter 3.6.4 fails to build with leatherman 0.12.0
Title: Message Title Matthew Thode commented on FACT-1618 Re: Facter 3.6.4 fails to build with leatherman 0.12.0 here's the downstream report https://bugs.gentoo.org/show_bug.cgi?id=616890 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1618) Facter 3.6.4 fails to build with leatherman 0.12.0
Title: Message Title
Matthew Thode updated an issue
Facter / FACT-1618
Facter 3.6.4 fails to build with leatherman 0.12.0
Change By:
Matthew Thode
I'm not sure if the version of ruby (2.1 here) is no longer supported in leatherman or some other issue, but here's the failure. What is odd is that facter-3.6.3 does build with leatherman 0.12.0.{{ [ 35%] Building CXX object lib/CMakeFiles/libfactersrc.dir/src/util/scoped_file.cc.ocd /var/tmp/portage/dev-ruby/facter-3.6.4/work/facter-3.6.4_build/lib && /usr/bin/x86_64-pc-linux-gnu-g++ -DBOOST_ALL_DYN_LINK -DBOOST_LOG_WITHOUT_WCHAR_T -DBOOST_SYSTEM_NO_DEPRECATED -DLEATHERMAN_I18N -DLEATHERMAN_LOGGING_NAMESPACE=\"puppetlabs.facter\" -DLEATHERMAN_USE_LOCALES -DPROJECT_DIR=\"/var/tmp/portage/dev-ruby/facter-3.6.4/work/facter-3.6.4_build\" -DPROJECT_NAME=\"FACTER\" -DUSE_BLKID -DUSE_CPPHOCON -DUSE_CURL -DUSE_OPENSSL -DUSE_YAMLCPP -Dlibfacter_EXPORTS -I/var/tmp/portage/dev-ruby/facter-3.6.4/work/all/facter-3.6.4/lib/inc -I/var/tmp/portage/dev-ruby/facter-3.6.4/work/all/facter-3.6.4/../vendor/nowide/include -I/usr/include/leatherman/vendor -DNDEBUG -march=native -O2 -pipe -Wno-maybe-uninitialized -std=c++11 -Wall -Wno-unused-parameter -Wno-unused-local-typedefs -Wno-unknown-pragmas -Wno-missing-field-initializers -Wextra -fPIC -o CMakeFiles/libfactersrc.dir/src/util/scoped_file.cc.o -c /var/tmp/portage/dev-ruby/facter-3.6.4/work/all/facter-3.6.4/lib/src/util/scoped_file.cc/var/tmp/portage/dev-ruby/facter-3.6.4/work/all/facter-3.6.4/lib/src/ruby/module.cc: In member function ‘leatherman::ruby::VALUE facter::ruby::module::to_ruby(const facter::facts::value*) const’:/var/tmp/portage/dev-ruby/facter-3.6.4/work/all/facter-3.6.4/lib/src/ruby/module.cc:400:25: error: ‘const struct leatherman::ruby::api’ has no member named ‘rb_ll2inum’ return ruby.rb_ll2inum(static_cast(ptr->value()));}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1618) Facter 3.6.4 fails to build with leatherman 0.12.0
Title: Message Title
Matthew Thode updated an issue
Facter / FACT-1618
Facter 3.6.4 fails to build with leatherman 0.12.0
Change By:
Matthew Thode
I'm not sure if the version of ruby (2.1 here) is no longer supported in leatherman or some other issue, but here's the failure. What is odd is that facter-3.6.3 does build with leatherman 0.12.0. {{ [ 35%] Building CXX object lib/CMakeFiles/libfactersrc.dir/src/util/scoped_file.cc.ocd /var/tmp/portage/dev-ruby/facter-3.6.4/work/facter-3.6.4_build/lib && /usr/bin/x86_64-pc-linux-gnu-g++ -DBOOST_ALL_DYN_LINK -DBOOST_LOG_WITHOUT_WCHAR_T -DBOOST_SYSTEM_NO_DEPRECATED -DLEATHERMAN_I18N -DLEATHERMAN_LOGGING_NAMESPACE=\"puppetlabs.facter\" -DLEATHERMAN_USE_LOCALES -DPROJECT_DIR=\"/var/tmp/portage/dev-ruby/facter-3.6.4/work/facter-3.6.4_build\" -DPROJECT_NAME=\"FACTER\" -DUSE_BLKID -DUSE_CPPHOCON -DUSE_CURL -DUSE_OPENSSL -DUSE_YAMLCPP -Dlibfacter_EXPORTS -I/var/tmp/portage/dev-ruby/facter-3.6.4/work/all/facter-3.6.4/lib/inc -I/var/tmp/portage/dev-ruby/facter-3.6.4/work/all/facter-3.6.4/../vendor/nowide/include -I/usr/include/leatherman/vendor -DNDEBUG -march=native -O2 -pipe -Wno-maybe-uninitialized -std=c++11 -Wall -Wno-unused-parameter -Wno-unused-local-typedefs -Wno-unknown-pragmas -Wno-missing-field-initializers -Wextra -fPIC -o CMakeFiles/libfactersrc.dir/src/util/scoped_file.cc.o -c /var/tmp/portage/dev-ruby/facter-3.6.4/work/all/facter-3.6.4/lib/src/util/scoped_file.cc/var/tmp/portage/dev-ruby/facter-3.6.4/work/all/facter-3.6.4/lib/src/ruby/module.cc: In member function ‘leatherman::ruby::VALUE facter::ruby::module::to_ruby(const facter::facts::value*) const’:/var/tmp/portage/dev-ruby/facter-3.6.4/work/all/facter-3.6.4/lib/src/ruby/module.cc:400:25: error: ‘const struct leatherman::ruby::api’ has no member named ‘rb_ll2inum’ return ruby.rb_ll2inum(static_cast(ptr->value())); }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1618) Facter 3.6.4 fails to build with leatherman 0.12.0
Title: Message Title
Matthew Thode created an issue
Facter / FACT-1618
Facter 3.6.4 fails to build with leatherman 0.12.0
Issue Type:
Bug
Affects Versions:
FACT 3.6.4
Assignee:
Unassigned
Created:
2017/04/28 10:58 AM
Fix Versions:
FACT 3.6.3
Priority:
Major
Reporter:
Matthew Thode
I'm not sure if the version of ruby (2.1 here) is no longer supported in leatherman or some other issue, but here's the failure. What is odd is that facter-3.6.3 does build with leatherman 0.12.0.
{{[ 35%] Building CXX object lib/CMakeFiles/libfactersrc.dir/src/util/scoped_file.cc.o cd /var/tmp/portage/dev-ruby/facter-3.6.4/work/facter-3.6.4_build/lib && /usr/bin/x86_64-pc-linux-gnu-g++ -DBOOST_ALL_DYN_LINK -DBOOST_LOG_WITHOUT_WCHAR_T -DBOOST_SYSTEM_NO_DEPRECATED -DLEATHERMAN_I18N -DLEATHERMAN_LOGGING_NAMESPACE=\"puppetlabs.facter\" -DLEATHERMAN_USE_LOCALES -DPROJECT_DIR=\"/var/tmp/portage/dev-ruby/facter-3.6.4/work/facter-3.6.4_build\" -DPROJECT_NAME=\"FACTER\" -DUSE_BLKID -DUSE_CPPHOCON -DUSE_CURL -DUSE_OPENSSL -DUSE_YAMLCPP -Dlibfacter_EXPORTS -I/var/tmp/portage/dev-ruby/facter-3.6.4/work/all/facter-3.6.4/lib/inc -I/var/tmp/portage/dev-ruby/facter-3.6.4/work/all/facter-3.6.4/../vendor/nowide/include -I/usr/include/leatherman/vendor -DNDEBUG -march=native -O2 -pipe -Wno-maybe-uninitialized -std=c++11 -Wall -Wno-unuse
Jira (PUP-6939) New users are confused by package's ensure=>$version
Title: Message Title Matthew Thode commented on PUP-6939 Re: New users are confused by package's ensure=>$version An example of this is https://gist.github.com/80860761d3f523b4e19fa2e99c96e613 (didn't see a way to upload) specifically for gentoo the qatom binary allows us to parse package names Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PUP-6939) New users are confused by package's ensure=>$version
Title: Message Title Matthew Thode commented on PUP-6939 Re: New users are confused by package's ensure=>$version You could actually overload the package name instead. 1. providers learn how to parse package names based on their package naming guidelines 2. warn about version strings in `ensure` 3. once this is available to "most" users, start deprecating version strings in ensure at runtime 4. once "most" deprecations are addressed, remove the original functionality in the next major puppet version Basically the same, but without a new property. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PUP-6939) New users are confused by package's ensure=>$version
Title: Message Title Matthew Thode commented on PUP-6939 Re: New users are confused by package's ensure=>$version This would also allow us to remove specific versions of versionable packages. see https://projects.puppetlabs.com/issues/2061 for the old discussion. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PUP-7095) Enable portage install and uninstall options
Title: Message Title Matthew Thode commented on PUP-7095 Re: Enable portage install and uninstall options The PR for this is in https://github.com/puppetlabs/puppet/pull/5498 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PUP-7095) Enable portage install and uninstall options
Title: Message Title Matthew Thode created an issue Puppet / PUP-7095 Enable portage install and uninstall options Issue Type: New Feature Affects Versions: PUP 4.8.1 Assignee: Unassigned Components: Types and Providers Created: 2017/01/12 9:55 AM Priority: Normal Reporter: Matthew Thode Portage (emerge) supports being run with command line options, lets allow there use. emerge --with-bdeps=y --update --deep etc Add Comment
Jira (FACT-1539) facter 3.5.0 (and 3.5.1) fail to build
Title: Message Title
Matthew Thode commented on FACT-1539
Re: facter 3.5.0 (and 3.5.1) fail to build
Thanks, this is the patch that fixes it for me
https://gist.github.com/6e945dfa6676848da82dac3c3d095e80
diff -Naur /var/tmp/portage/dev-ruby/facter-3.5.0/work/all/facter-3.5.0.old/lib/inc/facter/facts/collection.hpp /var/tmp/portage/dev-ruby/facter-3.5.0/work/all/facter-3.5.0/lib/inc/facter/facts/collection.hpp — /var/tmp/portage/dev-ruby/facter-3.5.0/work/all/facter-3.5.0.old/lib/inc/facter/facts/collection.hpp 2016-10-21 18:32:16.0 -0500 +++ /var/tmp/portage/dev-ruby/facter-3.5.0/work/all/facter-3.5.0/lib/inc/facter/facts/collection.hpp 2016-11-28 19:36:55.025454011 -0600 @@ -94,7 +94,7 @@
for the facts they resolve */ collection(std::set const& blocklist = std::set(),
std::unordered_map const& ttls = {}); + std::unordered_map const& ttls = std::unordered_map{});
/**
Destructor for fact collection. diff -Naur /var/tmp/portage/dev-ruby/facter-3.5.0/work/all/facter-3.5.0.old/lib/tests/collection_fixture.hpp /var/tmp/portage/dev-ruby/facter-3.5.0/work/all/facter-3.5.0/lib/tests/collection_fixture.hpp
/var/tmp/portage/dev-ruby/facter-3.5.0/work/all/facter-3.5.0.old/lib/tests/collection_fixture.hpp 2016-10-21 18:32:16.0 -0500 +++ /var/tmp/portage/dev-ruby/facter-3.5.0/work/all/facter-3.5.0/lib/tests/collection_fixture.hpp 2016-11-28 19:36:47.322311122 -0600 @@ -10,7 +10,7 @@ { public: collection_fixture(std::set const& blocklist = std::set(),
std::unordered_map const& ttls = {}); + std::unordered_map const& ttls = std::unordered_map{});
protected: virtual std::vector get_external_fact_directories() const override;
Jira (FACT-1539) facter 3.5.0 (and 3.5.1) fail to build
Title: Message Title Matthew Thode commented on FACT-1539 Re: facter 3.5.0 (and 3.5.1) fail to build I've hit this with GCC as well (seeing the build log) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1539) facter 3.5.0 (and 3.5.1) fail to build
Title: Message Title Matthew Thode created an issue Facter / FACT-1539 facter 3.5.0 (and 3.5.1) fail to build Issue Type: Bug Affects Versions: FACT 3.5.0, FACT 3.5.1 Assignee: Unassigned Created: 2016/11/26 6:49 PM Priority: Normal Reporter: Matthew Thode This is from 3.5.0 and git master GIT update --> repository: https://github.com/puppetlabs/facter.git at the commit: 01c09a2c5b0525e9a303a14f1a4e279df8c2d42c Gentoo bug: https://bugs.gentoo.org/show_bug.cgi?id=600942 Gist of build log (also in bug above): https://gist.github.com/prometheanfire/b6a172204e9b63f4ae51b39bcbddf43e Not sure what's causing the build failure, but it is repeatable by my users. Add Comment
Jira (FACT-1537) Facter 3.5.0 tarball is broken
Title: Message Title Matthew Thode commented on FACT-1537 Re: Facter 3.5.0 tarball is broken I wonder if this is what's causing my compile time problems (gentoo) https://gist.github.com/prometheanfire/b6a172204e9b63f4ae51b39bcbddf43e https://bugs.gentoo.org/show_bug.cgi?id=600942 let me know if you think I should still open a new bug for this Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PDB-2045) puppetdb immediately closes valid ssl connection
Title: Message Title
Matthew Thode commented on PDB-2045
Re: puppetdb immediately closes valid ssl connection
OK, update time, but first, I noticed that your ssl output did not include 'Netscape Cert Type', I do have that defined in mine, it is a seperate option from the tls web client/server options, so I enabled both.
Here's my working X509v3 section, thanks for the help.
{{ X509v3 extensions: X509v3 Basic Constraints: critical CA:FALSE X509v3 Subject Key Identifier: 1E:22:97:84:50:72:C1:65:68:E7:9C:26:3E:CC:E1:72:5F:38:67:7F X509v3 Authority Key Identifier: keyid:96:47:9F:EA:34:BC:79:DA:99:F9:25:1C:52:BE:A0:A4:84:C4:20:52 DirName:/C=US/ST=TX/L=San Antonio/O=mthode.org/CN=mthode.org/emailAddress=mth...@mthode.org serial:15
X509v3 Key Usage: critical Digital Signature, Non Repudiation, Key Encipherment, Data Encipherment X509v3 Extended Key Usage: critical TLS Web Server Authentication, TLS Web Client Authentication Netscape Cert Type: SSL Client, SSL Server Netscape Comment: xca certificate}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-2045) puppetdb immediately closes valid ssl connection
Title: Message Title Matthew Thode commented on PDB-2045 Re: puppetdb immediately closes valid ssl connection I am using tinyca to generate the certs, it gives the option when signing a cert of making it a server cert or client cert, I thought that server certs superceded client certs so used them for puppet and puppetdb, I'll switch them to client certs and report back. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2045) puppetdb immediately closes valid ssl connection
Title: Message Title Matthew Thode commented on PDB-2045 Re: puppetdb immediately closes valid ssl connection Here's 2092 lines of log from puppetdb, it throws a general ssl error. Seems to start fine but failed on a connection from puppetserver. Here's the puppetdb log https://gist.github.com/prometheanfire/42d7c79e49eae852b17c Here's the puppetserver log (just the connection to puppetdb) https://gist.github.com/prometheanfire/81132568f8c3820d8520 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2045) puppetdb immediately closes valid ssl connection
Title: Message Title Matthew Thode commented on PDB-2045 Re: puppetdb immediately closes valid ssl connection here's the openssl command echo 'GET /' | openssl s_client -connect puppet.mthode.org:8081 -4 -tls1_2 -no_ssl3 -no_ssl2 -no_tls1 -no_tls1_1 -CAfile ca.pem -cert public.pem -key private.pem I'm using puppetserver 2.1.1 and I saw the error first on a puppet run (400 error trying to connect to puppetdb) Warning: Error 400 on SERVER: Could not retrieve facts for puppet-client.mthode.org: Failed to find facts from PuppetDB at puppet:8140: Failed to execute '/pdb/query/v4/nodes/puppet-client.mthode.org/facts' on any of the following 'server_urls': https://puppetdb.mthode.org:8081 this is with `soft_write_failure = true` Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2045) puppetdb immediately closes valid ssl connection
Title: Message Title Matthew Thode commented on PDB-2045 Re: puppetdb immediately closes valid ssl connection also tested with the following setup with the same errors mthode.org CA -> puppet.mthode.org CA -> puppetdb.mthode.org CERT Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2045) puppetdb immediately closes valid ssl connection
Title: Message Title Matthew Thode commented on PDB-2045 Re: puppetdb immediately closes valid ssl connection Here's the CA setup mthode.org -> puppet.mthode.org cert V puppet.mthode.org CA -> puppet.mthode.org cert Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2045) puppetdb immediately closes valid ssl connection
Title: Message Title Matthew Thode commented on PDB-2045 Re: puppetdb immediately closes valid ssl connection ya, curl and s_client with a get for that path both fail the same. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2045) puppetdb immediately closes valid ssl connection
Title: Message Title Matthew Thode commented on PDB-2045 Re: puppetdb immediately closes valid ssl connection curl -L https://puppet.mthode.org:8081/v4/version --cacert ca.pem --cert public.pem --key private.pem -v -4 --tlsv1 same result Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2045) puppetdb immediately closes valid ssl connection
Title: Message Title Matthew Thode commented on PDB-2045 Re: puppetdb immediately closes valid ssl connection echo 'GET /' | openssl s_client -connect puppet.mthode.org:8081 -4 -tls1_2 -no_ssl3 -no_ssl2 -no_tls1 -no_tls1_1 -CAfile ca.pem -cert public.pem -key private.pem same results, same with curl curl -L https://puppet.mthode.org:8081/v4/version --cacert ca.pem --cert public.pem --key private.pem -v -4 --tlsv1.2 Trying 10.0.1.11... Connected to puppet.mthode.org (10.0.1.11) port 8081 (#0) Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH successfully set certificate verify locations: CAfile: ca.pem CApath: /etc/ssl/certs TLSv1.2 (OUT), TLS Unknown, Certificate Status (22): TLSv1.2 (OUT), TLS handshake, Client hello (1): TLSv1.2 (IN), TLS handshake, Server hello (2): TLSv1.2 (IN), TLS handshake, Certificate (11): TLSv1.2 (IN), TLS handshake, Request CERT (13): TLSv1.2 (IN), TLS handshake, Server finished (14): TLSv1.2 (OUT), TLS handshake, Certificate (11): TLSv1.2 (OUT), TLS handshake, Client key exchange (16): TLSv1.2 (OUT), TLS handshake, CERT verify (15): TLSv1.2 (OUT), TLS change cipher, Client hello (1): TLSv1.2 (OUT), TLS handshake, Finished (20): Unknown SSL protocol error in connec
Jira (PDB-2045) puppetdb immediately closes valid ssl connection
Title: Message Title Matthew Thode commented on PDB-2045 Re: puppetdb immediately closes valid ssl connection first time after startup the s_client error is different, as follows write:errno=104 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2045) puppetdb immediately closes valid ssl connection
Title: Message Title Matthew Thode created an issue PuppetDB / PDB-2045 puppetdb immediately closes valid ssl connection Issue Type: Bug Affects Versions: PDB 3.1.0 Assignee: Unassigned Created: 2015/10/12 8:12 AM Priority: Normal Reporter: Matthew Thode I have an intermediate setup as doc'd here https://docs.puppetlabs.com/puppet/latest/reference/config_ssl_external_ca.html#option-2-single-intermediate-ca the ca.pem has the intermediate ca followed by the root ca the public.pem is just the pubkey, no chain the private.pem is just the privkey Here's what I get when I use s_client to connect using the same ca/pub/priv that puppetdb is using https://gist.github.com/prometheanfire/612498a2658a631e6111 It returns 'OK', but also has an interesting line (number8). It returns the same if forcing s_client to -tls1_2 and if you don't echo anything into it. It simply immediately exits 140204798609104:error:140790E5:SSL routines:ssl23_write:ssl handshake failure:s23_lib.c:177: I'm at a loss as to why this is happening but it seems like a bug, so...
Jira (PDB-2044) ssl-set up should look for an intermediate cert when building the ca.pem file
Title: Message Title Matthew Thode updated an issue PuppetDB / PDB-2044 ssl-set up should look for an intermediate cert when building the ca.pem file Change By: Matthew Thode Issue Type: Sub-task Improvement Parent: PDB-646 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2044) ssl-set up should look for an intermediate cert when building the ca.pem file
Title: Message Title Matthew Thode updated an issue PuppetDB / PDB-2044 ssl-set up should look for an intermediate cert when building the ca.pem file Change By: Matthew Thode Issue Type: Improvement Sub-task Parent: PDB-646 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2044) ssl-set up should look for an intermediate cert when building the ca.pem file
Title: Message Title Matthew Thode created an issue PuppetDB / PDB-2044 ssl-set up should look for an intermediate cert when building the ca.pem file Issue Type: Improvement Affects Versions: PDB 3.1.0 Assignee: Unassigned Created: 2015/10/12 7:51 AM Priority: Normal Reporter: Matthew Thode `ssl_client_ca_auth` is requested to be defined in the agent config when setting up, it would be good to check for this value when building the ca.pem file for puppetdb. puppet agent --configprint ssl_client_ca_auth /etc/puppetlabs/puppet/ssl/certs/issuer.pem Add Comment
Jira (PUP-4916) fix hiera documentation in relation to deep_merge_options in hiera.yaml
Title: Message Title
Matthew Thode created an issue
Puppet / PUP-4916
fix hiera documentation in relation to deep_merge_options in hiera.yaml
Issue Type:
Bug
Assignee:
Kylo Ginsberg
Components:
Client
Created:
2015/07/22 4:08 PM
Labels:
hiera
Priority:
Normal
Reporter:
Matthew Thode
:deep_merge_options: needs a ruby hash, not a yaml hash https://docs.puppetlabs.com/hiera/3.0/configuring.html#deepmergeoptions
original, as per docs was: :deep_merge_options: :merge_hash_arrays => true
new, and now working with hiera_hash: :deep_merge_options: { merge_hash_arrays => true }
we could either doc this, or do an internal conversion of yaml to ruby datatypes I think.
Add
Jira (PUP-4902) routes.yaml should allow an alias for terminus, with the rename to termini
Title: Message Title Matthew Thode created an issue Puppet / PUP-4902 routes.yaml should allow an alias for terminus, with the rename to termini Issue Type: Bug Affects Versions: PUP 4.2.0 Assignee: Unassigned Components: Puppet Server Created: 2015/07/20 6:49 AM Labels: puppet Priority: Normal Reporter: Matthew Thode the default routes.yaml for connecting to puppetdb has the following, I believe that terminus should be allowed to be termini, as that package seems to have been renamed for puppetdb-3. — master: facts: terminus: puppetdb cache: yaml
Jira (FACT-1089) Release leatherman-0.1.0 or 0.2.0
Title: Message Title Matthew Thode created an issue Facter / FACT-1089 Release leatherman-0.1.0 or 0.2.0 Issue Type: Release Affects Versions: FACT 3.0.1 Assignee: Unassigned Created: 2015/07/04 9:21 PM Fix Versions: FACT 3.0.1 Labels: github package Priority: Normal Reporter: Matthew Thode From reading the cmake file for facter 3.0.1 it seems like leatherman is a dependency. In attempting to package leatherman (so I can package the new facter) I found no release to base my packaging on. I imagine other distros would like a release as well. Also, I'll make this a separate issue if needed, but it seems that leatherman is sourced as a submodule and only (see https://github.com/puppetlabs/facter/blob/3.0.1/CMakeLists.txt#L31 ). If I download the release from github then facter is not buildable because leatherman is not bundled (as it is with downloads.puppet.com). If leatherman is going to be used for more then just building fac
Jira (FACT-997) Packages pushed
Title: Message Title Matthew Thode commented on FACT-997 Re: Packages pushed Got alerted that a new tag was pushed without a gem being published, will watch for release here. 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-836) facter 2.4.2 2015-03-09 Release
Title: Message Title Matthew Thode commented on FACT-836 Re: facter 2.4.2 2015-03-09 Release gem not published to rubygems, https://rubygems.org/gems/facter 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 (FACT-343) failure to detect if running in a VM
Title: Message Title Matthew Thode commented on an issue Re: failure to detect if running in a VM it seems like having the value of 0x4NNN from one of the following commands seems to verify that it's in a VM cpuid -1 -r -k cpuid -1 -r 00:23 < iggy > okay, that 0x4000 is the hypervisor signature 00:23 < iggy > ebx=0x4b4d564b ecx=0x564b4d56 edx=0x004d equates to KVMKVMKVM 00:24 < iggy > and on Xen it's different (eax=0x4002 ebx=0x566e6558 ecx=0x65584d4d edx=0x4d4d566e) 00:24 < iggy > afaik, vmware has something similar 00:24 < iggy > (dunno about vbox, etc.) 00:25 < iggy > so I think just the presence of that flag means in a VM Add Comment Facter / FACT-343 failure to detect if running in a VM I was able to verify I was in a VM by running the following command (hackish, but works...). cpuid | grep -i guest\ status hypervisor guest status = false 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 recei
Jira (FACT-343) failure to detect if running in a VM
Title: Message Title Matthew Thode created an issue Facter / FACT-343 failure to detect if running in a VM Issue Type: Bug Affects Versions: 1.7.5 Assignee: Eric Sorenson Created: 18/Feb/14 9:56 PM Environment: Running within kvm with virtio-scsi and passing the cpu through as native Priority: Normal Reporter: Matthew Thode I was able to verify I was in a VM by running the following command (hackish, but works...). cpuid | grep -i guest\ status hypervisor guest status = false Add Comment
