Jira (FACT-896) Solaris: undefined reference to symbol 'inet_ntop@@SUNW_1.7' when building Facter
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Facter / FACT-896 Solaris: undefined reference to symbol 'inet_ntop@@SUNW_1.7' when building Facter Change By: Eric Thompson Assignee: QA Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4317) Smoke test packages
Title: Message Title
William Hopper commented on PUP-4317
Re: Smoke test packages
RedHat 7
Starting and stopping an agent
[root@u8v9bdrz4y5vy3s ~]# puppet resource service puppet
service { 'puppet':
ensure => 'stopped',
enable => 'false',
}
[root@u8v9bdrz4y5vy3s ~]# systemctl start puppet
[root@u8v9bdrz4y5vy3s ~]# systemctl status puppet
puppet.service - Puppet agent
Loaded: loaded (/usr/lib/systemd/system/puppet.service; disabled)
Jira (PUP-4389) Write acceptance test for puppet agent service
Title: Message Title Josh Cooper created an issue Puppet / PUP-4389 Write acceptance test for puppet agent service Issue Type: Task Assignee: Unassigned Created: 2015/04/09 2:28 PM Priority: Normal Reporter: Josh Cooper Write an acceptance test to verify the puppet agent service can be started and stopped on platforms that support it (rhel, debian, windows, ...). This should exercise the init scripts, e.g. /etc/init.d/puppet, or in the case of windows (service control manager integration) to verify it works. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (FACT-914) Facter complains if locale is any thing other than LANG=C in Solaris
Title: Message Title Michael Smith updated an issue Facter / FACT-914 Facter complains if locale is any thing other than LANG=C in Solaris Change By: Michael Smith Summary: CFacter Facter complains if locale is any thing other than LANG=C in Solaris 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-914) CFacter complains if locale is any thing other than LANG=C in Solaris
Title: Message Title Michael Smith commented on FACT-914 Re: CFacter complains if locale is any thing other than LANG=C in Solaris Also, this should be covered by running facter as part of unit tests, via make test or ctest. 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-895) Solaris: "'getloadavg' was not declared in this scope" when building Facter
Title: Message Title Michael Smith commented on FACT-895 Re: Solaris: "'getloadavg' was not declared in this scope" when building Facter FR Notes: cfacter-build is still the definitive source for building native facter on Solaris, and has been updated to build facter#master. 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-896) Solaris: undefined reference to symbol 'inet_ntop@@SUNW_1.7' when building Facter
Title: Message Title Michael Smith commented on FACT-896 Re: Solaris: undefined reference to symbol 'inet_ntop@@SUNW_1.7' when building Facter FR Notes: cfacter-build is still the definitive source for building native facter on Solaris, and has been updated to build facter#master. 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-922) Add timeout for call to prtdiag on Solaris
Title: Message Title Michael Smith commented on FACT-922 Re: Add timeout for call to prtdiag on Solaris FR Notes: cfacter-build is still the definitive source for building native facter on Solaris, and has been updated to build facter#master. 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-914) CFacter complains if locale is any thing other than LANG=C in Solaris
Title: Message Title Michael Smith commented on FACT-914 Re: CFacter complains if locale is any thing other than LANG=C in Solaris FR Notes: cfacter-build is still the definitive source for building native facter on Solaris, and has been updated to build facter#master. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4388) Remove /etc/default/puppet on Debian
Title: Message Title Michael Smith created an issue Puppet / PUP-4388 Remove /etc/default/puppet on Debian Issue Type: Improvement Assignee: Unassigned Created: 2015/04/09 2:22 PM Labels: AIO_TechDebt Priority: Normal Reporter: Michael Smith Debian doesn't follow the Puppet post-install instructions because you have to also manually modify /etc/default/puppet to allow the service to start. That's non-obvious unless you're experienced with running services on Debian. The default script was added because debhelper started services on package install, while we require some configuration before the service can start. With the puppet-agent AIO package, services no longer start on install; they have to be manually started (as instructed in post-install), which means we can remove /etc/default/puppet and the extra install step that adds. Add Comment
Jira (PUP-4317) Smoke test packages
Title: Message Title Michael Smith commented on PUP-4317 Re: Smoke test packages Ran Puppet-Agent 1.0.0 on Ubuntu 14.04 x86_64 (agent) against Centos 6 x86_64 (master). Init script worked once I learned about updating /etc/default/puppet. 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-900) Facter doesn't use correct external facts path for non-Administrator on Windows
Title: Message Title Eric Thompson updated an issue Facter / FACT-900 Facter doesn't use correct external facts path for non-Administrator on Windows Change By: Eric Thompson QA Contact: Eric Thompson 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-900) Facter doesn't use correct external facts path for non-Administrator on Windows
Title: Message Title Eric Thompson updated an issue Facter / FACT-900 Facter doesn't use correct external facts path for non-Administrator on Windows Change By: Eric Thompson QA Status: Reviewed 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-900) Facter doesn't use correct external facts path for non-Administrator on Windows
Title: Message Title Eric Thompson commented on FACT-900 Re: Facter doesn't use correct external facts path for non-Administrator on Windows validated on windows2012r2 at SHA: de4b25e29b37b18f09853eddd62689d972131668 PS C:\facter-2.4.3-1038-gde4b25e-x64> $env:HOME C:\Users\Guest PS C:\facter-2.4.3-1038-gde4b25e-x64> .\bin\facter.exe os --debug 2015-04-09 13:51:32.649955 INFO puppetlabs.facter - executed with command line: os --debug. 2015-04-09 13:51:32.649955 DEBUG puppetlabs.facter - no loaded libraries found matching pattern .*ruby(\d)?(\d)?(\d)?\.d ll 2015-04-09 13:51:32.649955 DEBUG puppetlabs.facter - ruby could not be found on the PATH. 2015-04-09 13:51:32.649955 WARN puppetlabs.facter - could not locate a ruby library: custom facts will not be resolved.
Jira (FACT-946) Schema validation fail on f21
Title: Message Title Kurt Wall updated an issue Facter / FACT-946 Schema validation fail on f21 Change By: Kurt Wall QA Contact: Kurt Wall QA Status: Reviewed 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-946) Schema validation fail on f21
Title: Message Title Kurt Wall assigned an issue to Unassigned Facter / FACT-946 Schema validation fail on f21 Change By: Kurt Wall Assignee: Kurt Wall 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-946) Schema validation fail on f21
Title: Message Title Kurt Wall commented on FACT-946 Re: Schema validation fail on f21 This is a test bug. No Test Rail triage required. Risk Assessment: Probability: Low Impact: Low Test level: Unit Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3653) Unable to create/force empty Windows groups
Title: Message Title Ryan Gard updated an issue Puppet / PUP-3653 Unable to create/force empty Windows groups Change By: Ryan Gard Priority: Normal Blocker 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-946) Schema validation fail on f21
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Facter / FACT-946 Schema validation fail on f21 Change By: Kurt Wall Assignee: QA Kurt Wall 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-865) Native facter lost the output from stderr in external (and custom?) facts
Title: Message Title Eric Thompson commented on FACT-865 Re: Native facter lost the output from stderr in external (and custom?) facts validated on windows2012r2-rubyx64 at SHA: de4b25e29b37b18f09853eddd62689d972131668 PS C:\Users\Administrator> C:\facter-2.4.3-1038-gde4b25e-x64\bin\facter.exe --external-dir .\external foo 2015-04-09 12:59:34.767148 WARN puppetlabs.facter - could not locate a ruby library: custom facts will not be resolved. 2015-04-09 12:59:34.798422 WARN puppetlabs.facter - external fact file "C:/Users\Administrator\external\foo.bat" had ou tput on stderr: error bar Add Comment
Jira (FACT-947) Use GetUserProfileDirectory on Windows for more robust home directory lookup
Title: Message Title Michael Smith commented on FACT-947 Re: Use GetUserProfileDirectory on Windows for more robust home directory lookup FR Notes: This shouldn't have any visible effect except it probably ignores the %HOME% environment variable if set. It would be covered if we had an acceptance test for FACT-900 on a Standard User account. 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-865) Native facter lost the output from stderr in external (and custom?) facts
Title: Message Title Eric Thompson commented on FACT-865 Re: Native facter lost the output from stderr in external (and custom?) facts validated on ubuntu14.04 at SHA: root@jr581erm1bto78w:~# facter --external-dir external/ foo 2015-04-09 12:40:11.641478 WARN puppetlabs.facter - external fact file "/root/external/foo.sh" had output on stderr: error bar root@jr581erm1bto78w:~# cat external/foo.sh #!/bin/sh echo 'foo=bar' >&2 echo "error" Add Comment
Jira (FACT-946) Schema validation fail on f21
Title: Message Title Michael Smith assigned an issue to QA Facter / FACT-946 Schema validation fail on f21 Change By: Michael Smith Status: Ready for CI Test Assignee: QA 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-926) Provide meaningful operating system fact values for Arista EOS
Title: Message Title Michael Smith assigned an issue to QA Facter / FACT-926 Provide meaningful operating system fact values for Arista EOS Change By: Michael Smith Status: Ready for CI Test Assignee: QA 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-914) CFacter complains if locale is any thing other than LANG=C in Solaris
Title: Message Title Michael Smith assigned an issue to QA Facter / FACT-914 CFacter complains if locale is any thing other than LANG=C in Solaris Change By: Michael Smith Status: Ready for CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4373) Windows ADSI User resource - groups property should use SIDs instead of names
Title: Message Title Rob Reynolds assigned an issue to Ethan Brown Josh Cooper / Ethan Brown - this is ready to be looked over. Puppet / PUP-4373 Windows ADSI User resource - groups property should use SIDs instead of names Change By: Rob Reynolds Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3804) User resource cannot add DOMAIN\User style accounts (through Active Directory) and should emit error message
Title: Message Title Kurt Wall commented on PUP-3804 Re: User resource cannot add DOMAIN\User style accounts (through Active Directory) and should emit error message I did the work before Ryan Gard asked me to. Is that awesome teamwork or what? 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-865) Native facter lost the output from stderr in external (and custom?) facts
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Facter / FACT-865 Native facter lost the output from stderr in external (and custom?) facts Change By: Eric Thompson Assignee: QA Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4278) unless with else when then part is empty produces nil result (future parser)
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4278 unless with else when then part is empty produces nil result (future parser) Added missing Component Change By: Kurt Wall Component/s: Language 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 (PDB-1036) Create design/estimates around Console reporting needs
Title: Message Title Eric Sorenson assigned an issue to Eric Sorenson PuppetDB / PDB-1036 Create design/estimates around Console reporting needs Change By: Eric Sorenson Assignee: Kenneth Barber Eric Sorenson 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 (PDB-1263) Round robin support for EC2 subnets
Title: Message Title
Rob Browning updated an issue
PuppetDB / PDB-1263
Round robin support for EC2 subnets
Change By:
Rob Browning
Using VPCs requires that we pin our instances to a specific subnet which also implies a specific availability zone. Under normal conditions this is fine, but when one availability zone is at capacity, it results in errors like the one below:{noformat}[AWS EC2 500 0.194905 0 retries] run_instances(:block_device_mappings=>[{:device_name=>"/dev/sda1",:ebs=>{:delete_on_termination=>true,:volume_size=>8}}],:client_token=>"35a3e6d2-119b-431b-94c1-7bcebe5af82f",:disable_api_termination=>false,:image_id=>"ami-bd420e8d",:instance_initiated_shutdown_behavior=>"terminate",:instance_type=>"c3.large",:key_name=>"Beaker-jenkins-sector",:max_count=>1,:min_count=>1,:monitoring=>{:enabled=>true},:security_group_ids=>["sg-9f6926fa"],:subnet_id=>"subnet-92dd65f7") AWS::EC2::Errors::InsufficientInstanceCapacity We currently do not have sufficient c3.large capacity in the Availability Zone you requested (us-west-2b). Our system will be working on provisioning additional capacity. You can currently get c3.large capacity by not specifying an Availability Zone in your request or choosing us-west-2a, us-west-2c.Failed: errored in CLI.provision#{noformat}If we were not specifying an availability zone, it would have just picked one of the other zones that were under capacity (and we would have not seen the error). Since we need to have the subnet pinned in order to use VPCs [~ken] has created a subnet in each of the regions. If we were able to specify a list of subnet ids and beaker was able to roll to the next subnet when one failed, it would give us the same ability as not specifying a vpc/subnet.This change involves change changing Beaker to support a list of subnets, the failover code and updating PuppetDB to take advantage of that new subnet list feature.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4323) Close all resolved tickets in Jira
Title: Message Title Kylo Ginsberg commented on PUP-4323 Re: Close all resolved tickets in Jira n/a for puppet-agent 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-926) Provide meaningful operating system fact values for Arista EOS
Title: Message Title William Hopper commented on FACT-926 Re: Provide meaningful operating system fact values for Arista EOS Notes for FR: I wrote up an outline of the steps needed to build for Arista EOS here: https://confluence.puppetlabs.com/display/PP/Native+Facter+Build+Process+for+Arista+EOS. It's a bit involved Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4299) Prepare long form release notes and short form release story
Title: Message Title Steve Barlow assigned an issue to Eric Sorenson Puppet / PUP-4299 Prepare long form release notes and short form release story Change By: Steve Barlow Assignee: Nicholas Fagerlund Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4317) Smoke test packages
Title: Message Title Josh Cooper commented on PUP-4317 Re: Smoke test packages We are only releasing packages (so no gem or tarballs to be checked), and all packages have been through CI (including MSIs) and have started and stopped the master. We don't have any acceptance tests for starting and stopping puppet agent, and should verify that. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4314) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Josh Cooper commented on PUP-4314 Re: Is the Jira tidy-up done for this release and prepared for the next one? n/a for puppet-agent Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4311) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Josh Cooper commented on PUP-4311 Re: Is there a commit for every JIRA ticket targeted at the release? n/a for puppet-agent Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4310) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Josh Cooper commented on PUP-4310 Re: Is there a JIRA ticket targeted at the release for every commit? This is n/a for puppet-agent Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4309) Is the code ready for release?
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-4309 Is the code ready for release? Change By: Josh Cooper Resolution: Fixed Assignee: Kylo Ginsberg Josh Cooper Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4309) Is the code ready for release?
Title: Message Title Josh Cooper commented on PUP-4309 Re: Is the code ready for release? puppet-agent version dependencies were checked in https://tickets.puppetlabs.com/browse/RE-4039?focusedCommentId=160436&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-160436. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4325) Gem provider fails to run on Ruby 2.1.5 / Puppet 4 on Windows
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4325 Gem provider fails to run on Ruby 2.1.5 / Puppet 4 on Windows Change By: Steve Barlow Scope Change Reason: AIO 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-946) Schema validation fail on f21
Title: Message Title Michael Smith updated an issue Facter / FACT-946 Schema validation fail on f21 Change By: Michael Smith Sprint: Client 2015-04-15 Scrum Team: Client Platform Story Points: 1 Scope Change Reason: Acceptance failure Scope Change Category: Found Fix Version/s: FACT 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4387) Cyan colored notices
Title: Message Title Kylo Ginsberg commented on PUP-4387 Re: Cyan colored notices You are correct. Seems to have been introduced in https://github.com/puppetlabs/puppet/commit/ab7a88d145a9703c7811435528a071cd6fdf8bb4. From the commit message it doesn't look like the intent was to drop cyan from notices. 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-900) Facter doesn't use correct external facts path for non-Administrator on Windows
Title: Message Title Michael Smith assigned an issue to QA Facter / FACT-900 Facter doesn't use correct external facts path for non-Administrator on Windows Change By: Michael Smith Status: Ready for Review Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4387) Cyan colored notices
Title: Message Title
Elof Ofel updated an issue
Puppet / PUP-4387
Cyan colored notices
Change By:
Elof Ofel
You seem to have made a typo in puppet 3.7.x.In puppet 2.7, running {{puppet agent -t --noop}} produced lots of notice-lines in cyan color.After I upgraded to 3.7.4, the cyan color is gone. However, when When looking at the raw text output from the same above command , you see strange incomplete ANSI codes.Info-lines are correctly formatted, but all Notice-lines are incorrect.Example:{noformat}Esc[0;32mInfo: Loading factsEsc[0mEsc[0;32mInfo: Caching catalog for foo.bar.comEsc[0mEsc[0;32mInfo: Applying configuration version '1428593162'Esc[0mEsc[mNotice: /Stage[main]/Foo::Home/File[/foo/x]/ensure: current_value absent, should be file (noop)Esc[0m^{noformat}Somehow the ANSI color code "0;36" has disappeared.It should say:{noformat}Esc[0;36mNotice: /Stage[main]/Foo::Home/File[/foo/x]/ensure: current_value absent, should be file (noop)Esc[0m{noformat}(the end of all lines, Notices included, are correctly terminated with Esc[0m)
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4387) Cyan colored notices
Title: Message Title
Elof Ofel updated an issue
Puppet / PUP-4387
Cyan colored notices
Change By:
Elof Ofel
You seem to have made a typo in (at least) puppet 3.7. 4 x .In puppet 2.7, running ' {{ puppet agent -t --noop ' }} produced lots of notice-lines in cyan color. Now that After I 've upgraded to 3.7.4, the cyan color is gone.However, when looking at the raw text output, you see strange ANSI codes.Info-lines are correctly formatted, but all Notice-lines are incorrect.Example:{noformat}Esc[0;32mInfo: Loading factsEsc[0mEsc[0;32mInfo: Caching catalog for foo.bar.comEsc[0mEsc[0;32mInfo: Applying configuration version '1428593162'Esc[0mEsc[mNotice: /Stage[main]/Foo::Home/File[/foo/x]/ensure: current_value absent, should be file (noop)Esc[0m^{noformat}Somehow the ANSI color code "0;36" has disappeared.It should say:{noformat}Esc[0;36mNotice: /Stage[main]/Foo::Home/File[/foo/x]/ensure: current_value absent, should be file (noop)Esc[0m{noformat}(the end of all lines, Notices included, are correctly terminated with Esc[0m)
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-947) Use GetUserProfileDirectory on Windows for more robust home directory lookup
Title: Message Title Michael Smith created an issue Facter / FACT-947 Use GetUserProfileDirectory on Windows for more robust home directory lookup Issue Type: Improvement Assignee: Unassigned Created: 2015/04/09 9:00 AM Fix Versions: FACT 3.0.0 Priority: Normal Reporter: Michael Smith Use GetUserProfileDirectory on Windows for more robust home directory lookup. Currently we test %HOME%, then %HOMEDRIVE%%HOMEPATH%, then %USERPROFILE%. That doesn't port well to Server Core or Nano Server. Add Comment
Jira (PUP-4387) Cyan colored notices
Title: Message Title
Elof Ofel updated an issue
Puppet / PUP-4387
Cyan colored notices
Change By:
Elof Ofel
You seem to have made a typo in (at least) puppet 3.7.4.In puppet 2.7, running 'puppet agent -t --noop' produced lots of notice-lines in cyan color.Now that I've upgraded to 3.7.4, the cyan color is gone.However, when looking at the raw text output, you see strange ANSI codes.Info-lines are correctly formatted, but all Notice-lines are incorrect.Example:{noformat}Esc[0;32mInfo: Loading factsEsc[0mEsc[0;32mInfo: Caching catalog for foo.bar.comEsc[0mEsc[0;32mInfo: Applying configuration version '1428593162' ^ Esc [ [ 0mEsc[mNotice: /Stage[main]/Foo::Home/File[/foo/x]/ensure: current_value absent, should be file (noop)Esc[0m ^ {noformat}Somehow the ANSI color code "0;36" has disappeared. It should say:{noformat}Esc[0;36mNotice: /Stage[main]/Foo::Home/File[/foo/x]/ensure: current_value absent, should be file (noop)Esc[0m{noformat}(the end of all lines, Notices included, are correctly terminated with Esc[0m)
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4387) Cyan colored notices
Title: Message Title
Elof Ofel updated an issue
Puppet / PUP-4387
Cyan colored notices
Change By:
Elof Ofel
You seem to have made a typo in (at least) puppet 3.7.4.In puppet 2.7, running 'puppet agent -t --noop' produced lots of notice-lines in cyan color.Now that I've upgraded to 3.7.4, the cyan color is gone.However, when looking at the raw text output, you see strange ANSI codes.Info-lines are correctly formatted, but all Notice-lines are incorrect.Example:{noformat}Esc[0;32mInfo: Loading factsEsc[0mEsc[0;32mInfo: Caching catalog for foo.bar.comEsc[0mEsc[0;32mInfo: Applying configuration version '1428593162'^[[0mEsc[mNotice: /Stage[main]/Foo::Home/File[/foo/ .foo x ]/ensure: current_value absent, should be file (noop)Esc[0m{noformat}Somehow the ANSI color code "0;36" has disappeared. It should say:{noformat}Esc[0;36mNotice: /Stage[main]/Foo::Home/File[/foo/ .foo x ]/ensure: current_value absent, should be file (noop)Esc[0m{noformat}(the end of all lines, Notices included, are correctly terminated with Esc[0m)
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4387) Cyan colored notices
Title: Message Title
Elof Ofel updated an issue
Puppet / PUP-4387
Cyan colored notices
Change By:
Elof Ofel
You seem to have made a typo in (at least) puppet 3.7.4.In puppet 2.7, running 'puppet agent -t --noop' produced lots of notice-lines in cyan color.Now that I've upgraded to 3.7.4, the cyan color is gone.However, when looking at the raw text output, you see strange ANSI codes.Info-lines are correctly formatted, but all Notice-lines are incorrect.Example:{noformat}Esc[0;32mInfo: Loading factsEsc[0mEsc[0;32mInfo: Caching catalog for foo.bar.comEsc[0mEsc[0;32mInfo: Applying configuration version '1428593162'^[[0mEsc[mNotice: /Stage[main]/ Foobarfiles Foo ::Home/File[/ home/ foo/. bashrc foo ]/ensure: current_value absent, should be file (noop)Esc[0m{noformat}Somehow the ANSI color code "0;36" has disappeared. It should say:{noformat}Esc[0;36mNotice: /Stage[main]/ Foobarfiles Foo ::Home/File[/ home/ foo/. bashrc foo ]/ensure: current_value absent, should be file (noop)Esc[0m{noformat}(the end of all lines, Notices included, are correctly terminated with Esc[0m)
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4387) Cyan colored notices
Title: Message Title
Elof Ofel updated an issue
Puppet / PUP-4387
Cyan colored notices
Change By:
Elof Ofel
You seem to have made a typo in (at least) puppet 3.7.4.In puppet 2.7, running 'puppet agent -t --noop' produced lots of notice-lines in cyan color.Now that I've upgraded to 3.7.4, the cyan color is gone.However, when looking at the raw text output, you see strange ANSI codes.Info-lines are correctly formatted, but all Notice-lines are incorrect.Example: {noformat} Esc[0;32mInfo: Loading factsEsc[0mEsc[0;32mInfo: Caching catalog for foo.bar.comEsc[0mEsc[0;32mInfo: Applying configuration version '1428593162'^[[0mEsc[mNotice: /Stage[main]/Foobarfiles::Home/File[/home/foo/.bashrc]/ensure: current_value absent, should be file (noop)Esc[0m {noformat} Somehow the ANSI color code "0;36" has disappeared. It should say: {noformat} Esc[0;36mNotice: /Stage[main]/Foobarfiles::Home/File[/home/foo/.bashrc]/ensure: current_value absent, should be file (noop)Esc[0m {noformat} (the end of all lines, Notices included, are correctly terminated with Esc[0m)
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4387) Cyan colored notices
Title: Message Title Elof Ofel updated an issue Puppet / PUP-4387 Cyan colored notices Change By: Elof Ofel You seem to have made a typo in (at least) puppet 3.7.4.In puppet 2.7, running 'puppet agent -t --noop' produced lots of notice-lines in cyan color.Now that I've upgraded to 3.7.4, the cyan color is gone.However, when looking at the raw text output, you see strange ANSI codes.Info-lines are correctly formatted, but all Notice-lines are incorrect.Example:Esc[0;32mInfo: Loading factsEsc[0mEsc[0;32mInfo: Caching catalog for foo.bar.comEsc[0mEsc[0;32mInfo: Applying configuration version '1428593162'^[[0mEsc[mNotice: /Stage[main]/Foobarfiles::Home/File[/home/foo/.bashrc]/ensure: current_value absent, should be file (noop)Esc[0mSomehow the ANSI color code "0;36" has disappeared. It should say:Esc[0;36mNotice : /Stage[main]/Foobarfiles::Home/File[/home/foo/ . . bashrc]/ensure: current_value absent, should be file (noop)Esc[0m (the end of all lines, Notices included, are correctly terminated with Esc[0m) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4387) Cyan colored notices
Title: Message Title Elof Ofel updated an issue Puppet / PUP-4387 Cyan colored notices Change By: Elof Ofel You seem to have made a typo in (at least) puppet 3.7.4.In puppet 2.7, running 'puppet agent -t --noop' produced lots of notice-lines in cyan color.Now that I've upgraded to 3.7.4, the cyan color is gone.However, when looking at the raw text output, you see strange ANSI codes.Info-lines are correctly formatted, but all Notice-lines are incorrect.Example:Esc[0;32mInfo: Loading factsEsc[0mEsc[0;32mInfo: Caching catalog for foo.bar.comEsc[0mEsc[0;32mInfo: Applying configuration version '1428593162'^[[0mEsc[mNotice: /Stage[main]/Foobarfiles::Home/File[/home/foo/.bashrc]/ensure: current_value absent, should be file (noop)Esc[0mIt should say:Esc[0;36mNotice : .. Somehow the ANSI color code "0;36" has disappeared. (the end of all lines, Notices included, are correctly terminated with Esc[0m) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4387) Cyan colored notices
Title: Message Title Elof Ofel updated an issue Puppet / PUP-4387 Cyan colored notices Change By: Elof Ofel You seem to have made a typo in (at least) puppet 3.7.4.In puppet 2.7, running 'puppet agent -t --noop' produced lots of notice-lines in cyan color.Now that I've upgraded to 3.7.4, the cyan color is gone.However, when looking at the raw text output, you see strange ANSI codes.Info-lines are correctly formatted, but all Notice-lines are incorrect.Example:Esc[0;32mInfo: Loading factsEsc[0mEsc[0;32mInfo: Caching catalog for foo.bar.comEsc[0mEsc[0;32mInfo: Applying configuration version '1428593162'^[[0mEsc[mNotice: /Stage[main]/Foobarfiles::Home/File[/home/foo/.bashrc]/ensure: current_value absent, should be file (noop)Esc[0m Somehow the ANSI color code "0;36" has disappeared. It should say:Esc[0;36mNotice.. Somehow the ANSI color code "0;36" has disappeared. (the end of all lines, Notices included, are correctly terminated with Esc[0m) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4387) Cyan colored notices
Title: Message Title Elof Ofel updated an issue Puppet / PUP-4387 Cyan colored notices Change By: Elof Ofel You seem to have made a typo in (at least) puppet 3.7.4.In puppet 2.7, running 'puppet agent -t --noop' produced lost lots of notice-lines in cyan color.Now that I've upgraded to 3.7.4, the cyan color is gone.However, when looking at the raw text output, you see strange ANSI codes.Info-lines are correctly formatted, but all Notice-lines are incorrect.Example:Esc[0;32mInfo: Loading factsEsc[0mEsc[0;32mInfo: Caching catalog for foo.bar.comEsc[0mEsc[0;32mInfo: Applying configuration version '1428593162'^[[0mEsc[mNotice: /Stage[main]/Foobarfiles::Home/File[/home/foo/.bashrc]/ensure: current_value absent, should be file (noop)Esc[0mIt should say:Esc[0;36mNotice:(the end of all lines, Notices included, are correctly terminated with Esc[0m) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4387) Cyan colored notices
Title: Message Title Elof Ofel created an issue Puppet / PUP-4387 Cyan colored notices Issue Type: Bug Affects Versions: PUP 3.7.4 Assignee: Kylo Ginsberg Components: Client Created: 2015/04/09 8:33 AM Environment: FreeBSD 10.0 Labels: ANSI color Priority: Trivial Reporter: Elof Ofel Original Estimate: 1 hour Remaining Estimate: 1 hour
Jira (PUP-3483) Systemd provider doesn't scan for changed units
Title: Message Title Kylo Ginsberg commented on PUP-3483 Re: Systemd provider doesn't scan for changed units Michael Stahnke thoughts on this? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3483) Systemd provider doesn't scan for changed units
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3483 Systemd provider doesn't scan for changed units Change By: Kylo Ginsberg Scrum Team: Release Engineering Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3483) Systemd provider doesn't scan for changed units
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-3483 Systemd provider doesn't scan for changed units Change By: Kylo Ginsberg Assignee: Kylo Ginsberg 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-946) Schema validation fail on f21
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-946 Schema validation fail on f21 Issue Type: Bug Assignee: Unassigned Created: 2015/04/09 7:27 AM Priority: Normal Reporter: Kylo Ginsberg https://jenkins.puppetlabs.com/job/Facter-Package-Acceptance-master/label=beaker,platform=fedora-21-i386/370/testReport/junit/(root)/tests/verify_facts_rb/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (FACT-380) Private ipaddress is used as ipaddress fact
Title: Message Title Sam Weston commented on FACT-380 Re: Private ipaddress is used as ipaddress fact Thanks for the updates! 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 (PDB-1419) PR (176): Enable the module to manage entries in $confdir/config.ini - buzzdeee
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1419 PR (176): Enable the module to manage entries in $confdir/config.ini - buzzdeee Issue Type: Task Assignee: Unassigned Created: 2015/04/09 12:49 AM Labels: github module Priority: Normal Reporter: gepetto-bot Enable the module to manage entries in $confdir/config.ini Author: Sebastian Reitenbach Company: Github ID: buzzdeee Pull Request 176 Discussion Pull Request 176 File Diff Pull Request Description with regard to the command-processing section. Added new class server/config_ini.pp to manage contents of the config.ini. Three new parameters added:
