Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title Geoff Nichols updated an issue Facter / FACT-718 Allow for disabling certain facts within Facter Change By: Geoff Nichols Component/s: DOCS 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-348) Facter should provide a convenient way to cache values
Title: Message Title Geoff Nichols updated an issue Facter / FACT-348 Facter should provide a convenient way to cache values Change By: Geoff Nichols Component/s: DOCS 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-6552) Regression: Redhat / Debian / Ubuntu can't specify 'init' provider
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6552 Regression: Redhat / Debian / Ubuntu can't specify 'init' provider Change By: Geoff Nichols Sprint: Client 2016-09-07, AP Holding 2016-11-30 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-6716) Error when purging local users on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6716 Error when purging local users on Windows Change By: Geoff Nichols Sprint: AP Holding 2016-11-30 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-6364) On AIX, an already installed package is not updated when using "ensure => latest"
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6364 On AIX, an already installed package is not updated when using "ensure => latest" Change By: Geoff Nichols Sprint: AP Holding 2016-11-30 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-6708) Agent does not save local copy of last_run_report.yaml if submission to report server fails
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6708 Agent does not save local copy of last_run_report.yaml if submission to report server fails Change By: Geoff Nichols Sprint: AP Holding 2016-11-30 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-3631) NIM provider uses a regex that is too restrictive when parsing RPM release tags
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3631 NIM provider uses a regex that is too restrictive when parsing RPM release tags Change By: Geoff Nichols Sprint: AP Holding 2016-11-30 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-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6675 Puppet::Util::Execution.execute 'hostname' returns nothing as daemon Change By: Geoff Nichols Sprint: AP Holding 2016-11-30 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-5334) Puppet can't remove users from groups in OSX.
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5334 Puppet can't remove users from groups in OSX. Change By: Geoff Nichols Sprint: AP Holding 2016-11-30 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-1431) Pre/Post-run commands don't work under Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-1431 Pre/Post-run commands don't work under Windows Change By: Geoff Nichols Sprint: AP Holding 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-6534) Windows parallel specs fail
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6534 Windows parallel specs fail Change By: Geoff Nichols Sprint: Windows 2016-07-27, Windows 2016-08-10, AP Grooming Top 11-20 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-6760) Solaris pkg provider does not correctly handle expiring cert
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6760 Solaris pkg provider does not correctly handle expiring cert Change By: Geoff Nichols Sprint: AP Grooming Top 11-20 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-6777) regression: incompatible character encodings: UTF-8 and ASCII-8BIT
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6777 regression: incompatible character encodings: UTF-8 and ASCII-8BIT Change By: Geoff Nichols Sprint: AP Grooming Top 11-20 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-1446) Improve the windows user check in facter/acceptance/test/facts/windows.rb
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1446 Improve the windows user check in facter/acceptance/test/facts/windows.rb Change By: Geoff Nichols Sprint: AP Grooming Top 11-20 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-1508) End-to-end POC for string externalization in Facter
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1508 End-to-end POC for string externalization in Facter Change By: Geoff Nichols Sprint: AP Grooming Top 11-20 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-6816) Make gettext a hard requirement
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6816 Make gettext a hard requirement Change By: Geoff Nichols Labels: i18n 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-6801) agent_specified_environment fact doesn't populate with the environment setting in the [agent] section
Title: Message Title Erik Hansen commented on PUP-6801 Re: agent_specified_environment fact doesn't populate with the environment setting in the [agent] section Michael Smith I only noticed it using 'facter -p agent_specified_environment' and in /etc/puppetlabs/mcollective/facts.yaml. With environment set in the [main] section this works. If the environment is in the [agent] section, no dice. puppet.conf: server = pe-201620-master.example.com #environment = nothing [agent] certname = pe-201620-agent2 environment = nothing Run: /opt/puppetlabs/puppet/bin/refresh-mcollective-metadata [root@pe-201620-agent2 ~]# cat /etc/puppetlabs/mcollective/facts.yaml | grep agent_spec [root@pe-201620-agent2 ~]# [root@pe-201620-agent2 ~]# facter -p agent_specified_environment (no output) Edit puppet.conf: [main] server = pe-201620-master.example.com
Jira (FACT-1521) Kstat code is invalid on modern compilers
Title: Message Title
Shawn Ferry updated an issue
Facter / FACT-1521
Kstat code is invalid on modern compilers
Change By:
Shawn Ferry
This blocks shipping Facter 3.x on Solaris [~branan] says this is/has always been broken and needs to be refactored I can't get this example code cleanhttps://gist.github.com/shawnferry/3067ab3be19312ee4f8281c05aaec9d8 {{ template<>long k_stat_entry::value(const std::string& attrib) const{return lookup(KSTAT_DATA_LONG, attrib)->value.l;}template<>int32_t k_stat_entry::value(const std::string& attrib) const{return lookup(KSTAT_DATA_INT32, attrib)->value.i32;}template<>uint32_t k_stat_entry::value(const std::string& attrib) const{return lookup(KSTAT_DATA_UINT32, attrib)->value.ui32;}template<>int64_t k_stat_entry::value(const std::string& attrib) const{return lookup(KSTAT_DATA_INT64, attrib)->value.i64;}}} {{root@puppet4-x86:/build-x86/facter/release# make[ 2%] Built target facter-jruby[ 3%] Building CXX object lib/CMakeFiles/libfactersrc.dir/src/util/solaris/k_stat.cc.o/build-x86/facter/lib/src/util/solaris/k_stat.cc:143:13: error: redefinition of ‘T facter::util::solaris::k_stat_entry::value(const string&) const [with T = long int; std::__cxx11::string = std::__cxx11::basic_string]’ int64_t k_stat_entry::value(const std::string& attrib) const ^/build-x86/facter/lib/src/util/solaris/k_stat.cc:125:10: note: ‘T facter::util::solaris::k_stat_entry::value(const string&) const [with T = long int; std::__cxx11::string = std::__cxx11::basic_string]’ previously declared here long k_stat_entry::value(const std::string& attrib) const ^/build-x86/facter/lib/src/util/solaris/k_stat.cc:149:14: error: redefinition of ‘T facter::util::solaris::k_stat_entry::value(const string&) const [with T = long unsigned int; std::__cxx11::string = std::__cxx11::basic_string]’ uint64_t k_stat_entry::value(const std::string& attrib) const ^/build-x86/facter/lib/src/util/solaris/k_stat.cc:119:13: note: ‘T facter::util::solaris::k_stat_entry::value(const string&) const [with T = long unsigned int; std::__cxx11::string = std::__cxx11::basic_string]’ previously declared here ulong_t k_stat_entry::value(const std::string& attrib) const ^*** Error code 1The following command caused the error:cd /build-x86/facter/release/lib && /usr/bin/c++ -DBOOST_ALL_DYN_LINK -DBOOST_LOG_WITHOUT_WCHAR_T -DBOOST_SYSTEM_NO_DEPRECATED -DLEATHERMAN_LOGGING_NAMESPACE=\"puppetlabs.facter\" -DPROJECT_DIR=\"/build-x86/facter/release\" -DPROJECT_NAME=\"FACTER\" -DUSE_CPPHOCON -DUSE_JRUBY_SUPPORT -DUSE_OPENSSL -DUSE_YAMLCPP -Dlibfacter_EXPORTS -I/build-x86/facter/lib/inc -I/build-x86/facter/vendor/rapidjson-0.11/include -I/build-x86/facter/../vendor/nowide/include -I/usr/java/include -I/usr/java/include/solaris -I/build-x86/i386-gcc/include -I/build-x86/i386-gcc/include/leatherman/vendor -Wno-maybe-uninitialized -pthreads -Wno-deprecated-declarations -std=c++11 -Wall -Werror -Wno-unused-parameter -Wno-unused-local-typedefs -Wno-unknown-pragmas -Wno-missing-field-initializers -O3 -DNDEBUG -fPIC -o CMakeFiles/libfactersrc.dir/src/util/solaris/k_stat.cc.o -c /build-x86/facter/lib/src/util/solaris/k_stat.ccmake: Fatal error:
Jira (FACT-1521) Kstat code is invalid on modern compilers
Title: Message Title
Shawn Ferry updated an issue
Facter / FACT-1521
Kstat code is invalid on modern compilers
Change By:
Shawn Ferry
This blocks shipping Facter 3.x on Solaris [~branan] says this is/has always been broken and needs to be refactored {{ template<>long k_stat_entry::value(const std::string& attrib) const{return lookup(KSTAT_DATA_LONG, attrib)->value.l;}template<>int32_t k_stat_entry::value(const std::string& attrib) const{return lookup(KSTAT_DATA_INT32, attrib)->value.i32;}template<>uint32_t k_stat_entry::value(const std::string& attrib) const{return lookup(KSTAT_DATA_UINT32, attrib)->value.ui32;}template<>int64_t k_stat_entry::value(const std::string& attrib) const{return lookup(KSTAT_DATA_INT64, attrib)->value.i64;}}} {{ root@puppet4-x86:/build-x86/facter/release# make[ 2%] Built target facter-jruby[ 3%] Building CXX object lib/CMakeFiles/libfactersrc.dir/src/util/solaris/k_stat.cc.o/build-x86/facter/lib/src/util/solaris/k_stat.cc:143:13: error: redefinition of ‘T facter::util::solaris::k_stat_entry::value(const string&) const [with T = long int; std::__cxx11::string = std::__cxx11::basic_string]’ int64_t k_stat_entry::value(const std::string& attrib) const ^/build-x86/facter/lib/src/util/solaris/k_stat.cc:125:10: note: ‘T facter::util::solaris::k_stat_entry::value(const string&) const [with T = long int; std::__cxx11::string = std::__cxx11::basic_string]’ previously declared here long k_stat_entry::value(const std::string& attrib) const ^/build-x86/facter/lib/src/util/solaris/k_stat.cc:149:14: error: redefinition of ‘T facter::util::solaris::k_stat_entry::value(const string&) const [with T = long unsigned int; std::__cxx11::string = std::__cxx11::basic_string]’ uint64_t k_stat_entry::value(const std::string& attrib) const ^/build-x86/facter/lib/src/util/solaris/k_stat.cc:119:13: note: ‘T facter::util::solaris::k_stat_entry::value(const string&) const [with T = long unsigned int; std::__cxx11::string = std::__cxx11::basic_string]’ previously declared here ulong_t k_stat_entry::value(const std::string& attrib) const ^*** Error code 1The following command caused the error:cd /build-x86/facter/release/lib && /usr/bin/c++ -DBOOST_ALL_DYN_LINK -DBOOST_LOG_WITHOUT_WCHAR_T -DBOOST_SYSTEM_NO_DEPRECATED -DLEATHERMAN_LOGGING_NAMESPACE=\"puppetlabs.facter\" -DPROJECT_DIR=\"/build-x86/facter/release\" -DPROJECT_NAME=\"FACTER\" -DUSE_CPPHOCON -DUSE_JRUBY_SUPPORT -DUSE_OPENSSL -DUSE_YAMLCPP -Dlibfacter_EXPORTS -I/build-x86/facter/lib/inc -I/build-x86/facter/vendor/rapidjson-0.11/include -I/build-x86/facter/../vendor/nowide/include -I/usr/java/include -I/usr/java/include/solaris -I/build-x86/i386-gcc/include -I/build-x86/i386-gcc/include/leatherman/vendor -Wno-maybe-uninitialized -pthreads -Wno-deprecated-declarations -std=c++11 -Wall -Werror -Wno-unused-parameter -Wno-unused-local-typedefs -Wno-unknown-pragmas -Wno-missing-field-initializers -O3 -DNDEBUG -fPIC -o CMakeFiles/libfactersrc.dir/src/util/solaris/k_stat.cc.o -c /build-x86/facter/lib/src/util/solaris/k_stat.ccmake: Fatal error: Command failed for target `lib/CMakeFiles/libfactersrc.dir/src/util/solaris/k_stat.cc.o'Current
Jira (FACT-1522) CI failing because beaker-abs conflicts with beaker 3
Title: Message Title Moses Mendoza commented on FACT-1522 Re: CI failing because beaker-abs conflicts with beaker 3 Downgraded priority as reverting beaker-abs addition to facter has allowed CI to proceed. Leaving open to track compatibility of beaker-abs w/beaker 3. Will probably mean moving this ticket to a different project than Facter, but will leave for Josh Cooper or Rick Bradley to decide if that's the right thing. 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-1522) CI failing because beaker-abs conflicts with beaker 3
Title: Message Title Moses Mendoza updated an issue Facter / FACT-1522 CI failing because beaker-abs conflicts with beaker 3 Change By: Moses Mendoza Sprint: AP 2016-11-02 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-1522) CI failing because beaker-abs conflicts with beaker 3
Title: Message Title Moses Mendoza assigned an issue to Josh Cooper Facter / FACT-1522 CI failing because beaker-abs conflicts with beaker 3 Change By: Moses Mendoza Assignee: Josh Cooper 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-1522) CI failing because beaker-abs conflicts with beaker 3
Title: Message Title Moses Mendoza updated an issue Facter / FACT-1522 CI failing because beaker-abs conflicts with beaker 3 Change By: Moses Mendoza Priority: Blocker Normal 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-1522) CI failing because beaker-abs conflicts with beaker 3
Title: Message Title Moses Mendoza updated an issue Facter / FACT-1522 CI failing because beaker-abs conflicts with beaker 3 Change By: Moses Mendoza Story Points: 2 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-1522) CI failing because beaker-abs conflicts with beaker 3
Title: Message Title Moses Mendoza commented on FACT-1522 Re: CI failing because beaker-abs conflicts with beaker 3 Ping Josh Cooper Rick Bradley 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-1522) CI failing because beaker-abs conflicts with beaker 3
Title: Message Title Maggie Dreyer commented on FACT-1522 Re: CI failing because beaker-abs conflicts with beaker 3 Reverting the commit allowed the pipeline to proceed, we don't appear to be using this gem yet. 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-1522) CI failing because beaker-abs conflicts with beaker 3
Title: Message Title Moses Mendoza commented on FACT-1522 Re: CI failing because beaker-abs conflicts with beaker 3 Not sure if we can just revert adding beaker-abs, added https://github.com/puppetlabs/facter/commit/c76c78ce8714dea99799c08c05f88ec6e6f84925, as pipelines might? be currently using it 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-1522) CI failing because beaker-abs conflicts with beaker 3
Title: Message Title Moses Mendoza created an issue Facter / FACT-1522 CI failing because beaker-abs conflicts with beaker 3 Issue Type: CI Blocker Assignee: Unassigned Created: 2016/10/21 4:27 PM Priority: Blocker Reporter: Moses Mendoza Beaker 3.1.0 was added to facter and all puppet-agent components to support running tests against MacOS Sierra and Server 2016, but this is now conflicting with the beaker-abs gem: From CI failure on facter/master: 15:38:59 Bundler could not find compatible versions for gem "beaker": 15:38:59 In Gemfile: 15:38:59 beaker (~> 3.1.0) 15:38:59
Jira (FACT-1521) Kstat code is invalid on modern compilers
Title: Message Title
Shawn Ferry created an issue
Facter / FACT-1521
Kstat code is invalid on modern compilers
Issue Type:
Bug
Affects Versions:
FACT 3.4.1
Assignee:
Unassigned
Created:
2016/10/21 3:51 PM
Environment:
GCC 5.3 Solaris 12
/root/user-config.jam using gcc : : : "-fPIC -std=c99" "-std=c++11 -fPIC" ;
JAVA_HOME=/usr/java cmake .. -DCMAKE_INSTALL_PREFIX=/build-x86/i386-gcc
Priority:
Blocker
Reporter:
Shawn Ferry
This blocks shipping Facter 3.x on Solaris
Branan Riley says this is/has always been broken and needs to be refactored
{{ template<> long k_stat_entry::value(const std::string& attrib) const { return lookup(KSTAT_DATA_LONG, attrib)->value.l; }
template<> int32_t k_stat_entry::value(const std::string& attrib) const { return lookup(KSTAT_DATA_INT32, attrib)->value.i32; }
template<> uint32_t k_stat_entry::value(const std::string& attrib) const { return lookup(KSTAT_DATA_UINT32, attrib)->value.ui32; }
template<> int64_t k_stat_entry::value(const std::string& attrib) const { return lookup(KSTAT_DATA_INT64,
Jira (PUP-6798) Ensuring latest does not use upgrade command in DNF
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6798 Ensuring latest does not use upgrade command in DNF Change By: Moses Mendoza Fix Version/s: PUP 4.8.0 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-6798) Ensuring latest does not use upgrade command in DNF
Title: Message Title Moses Mendoza commented on PUP-6798 Re: Ensuring latest does not use upgrade command in DNF merged to master at https://github.com/puppetlabs/puppet/commit/2a1f9ebafe8cf350fa94613e39a7cbc41f4d17c6 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-6803) puppet run status should be "failed" if there are failed generated resources
Title: Message Title Moses Mendoza commented on PUP-6803 Re: puppet run status should be "failed" if there are failed generated resources this has cleared CI and been promoted into puppet agent 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-6803) puppet run status should be "failed" if there are failed generated resources
Title: Message Title Moses Mendoza commented on PUP-6803 Re: puppet run status should be "failed" if there are failed generated resources merged to master at https://github.com/puppetlabs/puppet/commit/927c5f151b4dbccd00ece773c5a557abf048d7ab 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-6806) Update beaker version to 3.1.0 to allow MacOS Sierra testing Support
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6806 Update beaker version to 3.1.0 to allow MacOS Sierra testing Support Change By: Moses Mendoza Fix Version/s: PUP 4.8.0 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-6755) acceptance: strftime function
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6755 acceptance: strftime function Change By: Moses Mendoza Fix Version/s: PUP 4.8.0 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-6742) Add YARD tags for puppet log functions (debug, info, notice, etc)
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6742 Add YARD tags for puppet log functions (debug, info, notice, etc) Change By: Moses Mendoza Fix Version/s: PUP 4.8.0 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-6749) race condition smf and manifest-import
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6749 race condition smf and manifest-import Change By: Moses Mendoza Fix Version/s: PUP 4.8.0 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-6766) calling_all_functions test fails on master
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6766 calling_all_functions test fails on master Change By: Moses Mendoza Fix Version/s: PUP 4.8.0 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-6592) acceptance: Sensitive data
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6592 acceptance: Sensitive data Change By: Moses Mendoza Fix Version/s: PUP 4.8.0 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-6799) PEZ 2016.5.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6799 PEZ 2016.5.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided Change By: Moses Mendoza Fix Version/s: PUP 4.8.0 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-6245) Acceptance: fix zpool create zone test
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6245 Acceptance: fix zpool create zone test Change By: Moses Mendoza Fix Version/s: PUP 4.y Fix Version/s: PUP 4.8.0 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-6807) referencing non-existant variable in custom function crashes puppetserver
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6807 referencing non-existant variable in custom function crashes puppetserver Change By: Moses Mendoza Fix Version/s: PUP 4.8.0 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-6791) acceptance: add then and other functions to calling_all_functions test
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6791 acceptance: add then and other functions to calling_all_functions test Change By: Moses Mendoza Fix Version/s: PUP 4.8.0 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-6790) acceptance: file resource with and without trailing slash
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6790 acceptance: file resource with and without trailing slash Change By: Moses Mendoza Fix Version/s: PUP 4.8.0 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-6779) acceptance: puppet generate
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6779 acceptance: puppet generate Change By: Moses Mendoza Fix Version/s: PUP 4.8.0 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-6827) Address puppet acceptance test failures on windows server 2016
Title: Message Title Moses Mendoza commented on PUP-6827 Re: Address puppet acceptance test failures on windows server 2016 this has landed in latest puppet agent / master 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 (HI-542) Hiera dies with "no default supplied" if there is default but found keys is null
Title: Message Title Thomas Hallgren commented on HI-542 Re: Hiera dies with "no default supplied" if there is default but found keys is null No, Hiera versions >= 2.0 can differentiate between a found `nil` and a missing entry when given a default. This is a bug i Puppet. The test in HieraPuppet#lookup, line 13 is incorrect. It should read: if default.nil? && answer.nil? 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 (HI-542) Hiera dies with "no default supplied" if there is default but found keys is null
Title: Message Title Mariusz Gronczewski commented on HI-542 Re: Hiera dies with "no default supplied" if there is default but found keys is null Sure, it is what I'd expect and it is what happens if key does not exist. But if it does and is null it produces that unhelpful message. I've hit that when I accidentally removed value of key and it was pretty confusing to debug thanks to the message 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 (HI-541) Hiera cannot find datadir
Title: Message Title Henrik Lindberg commented on HI-541 Re: Hiera cannot find datadir For this kind of question it is best to use the Slack or IRC channels to get help figuring out what is wrong. If you are a PE user please contact Puppet Support. 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 (HI-541) Hiera cannot find datadir
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-541
Hiera cannot find datadir
Change By:
Henrik Lindberg
I have a working puppet 2016.2.1 using code manager (r10k) and environments (dev, staging, prod). This is working great. I than started to utilize hiera. When setting the hiera.yaml (as shown below). I'm getting the error "Cannot find datafile /etc/puppetlabs/code/environments*//*hieradata/common.yaml, skipping" {code} #---:backends: - yaml:hierarchy: - "nodes/%{::trusted.certname}" - "%{environment}" - "puppet_role/%{puppet_role}"- common:yaml::datadir: "/etc/puppetlabs/code/environments/%{::environment}/hieradata"# {code} I notice the double backslash which is a problem. If I replace the environment variable with an actual environment name (e.g. :datadir: "/etc/puppetlabs/code/environments/*development*/hieradata") and run hiera --debug i get back results. Has anyone run into 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 (HI-542) Hiera dies with "no default supplied" if there is default but found keys is null
Title: Message Title Henrik Lindberg commented on HI-542 Re: Hiera dies with "no default supplied" if there is default but found keys is null IIRC, this is by design in Hiera - as backends return Ruby nil to indicate 'not found'. Ping Thomas Hallgren ? 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-6825) Transient problem starting rabbitmq-server service on Ubuntu 10.04
Title: Message Title Maggie Dreyer commented on PUP-6825 Re: Transient problem starting rabbitmq-server service on Ubuntu 10.04 This failed again today: https://jenkins.puppetlabs.com/job/platform_puppet-agent_intn-van-sys_suite-daily-puppet-master/239/SLAVE_LABEL=beaker,TEST_TARGET=ubuntu1004-64a/testReport/junit/(root)/tests_resource_service/ticket_14297_handle_upstart_rb/ 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-6825) Transient problem starting rabbitmq-server service on Ubuntu 10.04
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-6825 Transient problem starting rabbitmq-server service on Ubuntu 10.04 Change By: Maggie Dreyer Issue Type: Bug CI Blocker 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 (HI-542) Hiera dies with "no default supplied" if there is default but found keys is null
Title: Message Title
Mariusz Gronczewski updated an issue
Hiera / HI-542
Hiera dies with "no default supplied" if there is default but found keys is null
Change By:
Mariusz Gronczewski
With manifest of{ { code} $a = hiera('some_null',"default")notify {"things happened ${a}":;} {code } } and YAML of{code}---some_null:{code}or { { code} ---some_null: ~ {code } } Puppet dies with:{ { code} Error: Evaluation Error: Error while evaluating a Function Call, Could not find data item some_null in any Hiera data file and no default supplied at /tmp/1.pp:4:6 on node ghroth.non.3dart.com {code } } It should either pick default value (which would be a nice way to do it if you want to use "default" on one host but keep value non-default on whole group) or at least have more descriptive error message like "found key is null".As it is currenly it is very misleading and hard to debug
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 (HI-542) Hiera dies with "no default supplied" if there is default but found keys is null
Title: Message Title
Mariusz Gronczewski updated an issue
Hiera / HI-542
Hiera dies with "no default supplied" if there is default but found keys is null
Change By:
Mariusz Gronczewski
With manifest of{{$a = hiera('some_null',"default")notify {"things happened ${a}":;}}}and YAML of{ { code} ---some_null: {code } } or {{---some_null: ~}}Puppet dies with:{{Error: Evaluation Error: Error while evaluating a Function Call, Could not find data item some_null in any Hiera data file and no default supplied at /tmp/1.pp:4:6 on node ghroth.non.3dart.com}}It should either pick default value (which would be a nice way to do it if you want to use "default" on one host but keep value non-default on whole group) or at least have more descriptive error message like "found key is null".As it is currenly it is very misleading and hard to debug
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 (HI-542) Hiera dies with "no default supplied" if there is default but found keys is null
Title: Message Title
Mariusz Gronczewski updated an issue
Hiera / HI-542
Hiera dies with "no default supplied" if there is default but found keys is null
Change By:
Mariusz Gronczewski
With manifest of{ { quote} $a = hiera('some_null',"default")notify {"things happened ${a}":;} {quote } } and YAML of{{---some_null:}}or {{---some_null: ~}}Puppet dies with:{{Error: Evaluation Error: Error while evaluating a Function Call, Could not find data item some_null in any Hiera data file and no default supplied at /tmp/1.pp:4:6 on node ghroth.non.3dart.com}}It should either pick default value (which would be a nice way to do it if you want to use "default" on one host but keep value non-default on whole group) or at least have more descriptive error message like "found key is null".As it is currenly it is very misleading and hard to debug
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 (HI-542) Hiera dies with "no default supplied" if there is default but found keys is null
Title: Message Title
Mariusz Gronczewski updated an issue
Hiera / HI-542
Hiera dies with "no default supplied" if there is default but found keys is null
Change By:
Mariusz Gronczewski
With manifest of { quote} { $a = hiera('some_null',"default")notify {"things happened ${a}":;} {quote } } and YAML of{{---some_null:}}or {{---some_null: ~}}Puppet dies with:{{Error: Evaluation Error: Error while evaluating a Function Call, Could not find data item some_null in any Hiera data file and no default supplied at /tmp/1.pp:4:6 on node ghroth.non.3dart.com}}It should either pick default value (which would be a nice way to do it if you want to use "default" on one host but keep value non-default on whole group) or at least have more descriptive error message like "found key is null".As it is currenly it is very misleading and hard to debug
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 (HI-542) Hiera dies with "no default supplied" if there is default but found keys is null
Title: Message Title
Mariusz Gronczewski updated an issue
Hiera / HI-542
Hiera dies with "no default supplied" if there is default but found keys is null
Change By:
Mariusz Gronczewski
With manifest of{{$a = hiera('some_null',"default")notify {"things happened ${a}":;}}}and YAML of{{---some_null:}}or {{---some_null: ~}}Puppet dies with:{{Error: Evaluation Error: Error while evaluating a Function Call, Could not find data item some_null in any Hiera data file and no default supplied at /tmp/1.pp:4:6 on node ghroth.non.3dart.com}}It should either pick default value (which would be a nice way to do it if you want to use "default" on one host but keep value non-default on whole group) or at least have more descriptive error message like "found key is null".As it is currenly it is very misleading and hard to debug
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 (HI-542) Hiera dies with "no default supplied" if there is default but found keys is null
Title: Message Title Mariusz Gronczewski created an issue Hiera / HI-542 Hiera dies with "no default supplied" if there is default but found keys is null Issue Type: Bug Affects Versions: HI 3.2.0 Assignee: Unassigned Created: 2016/10/21 5:37 AM Priority: Normal Reporter: Mariusz Gronczewski Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title Samuli Seppänen commented on FACT-1394 Re: Warning printed when 'ip route show' output contains "linkdown" I can confirm this on Fedora 24 with latest updates (as of now) installed, and latest puppet-agent from Fedora 24 yum repositories: $ uname -a Linux host.domain.com 4.7.7-200.fc24.x86_64 #1 SMP Sat Oct 8 00:21:59 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ puppet --version 4.7.0 The warning message: Debug: Facter: executing command: /sbin/ip route show Debug: Facter: default via 192.168.15.254 dev wlp3s0 proto static metric 600 Debug: Facter: 192.168.15.0/24 dev wlp3s0 proto kernel scope link src 192.168.15.7 metric 600 Debug: Facter: 192.168.124.0/24 dev virbr0 proto kernel scope link src 192.168.124.1 linkdown
