Jira (PUP-7124) Options should be passed to hiera 3 backend when declared in Hiera v5 config
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7124 Options should be passed to hiera 3 backend when declared in Hiera v5 config Change By: Thomas Hallgren Release Notes: Not Needed 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-7116) Make gettext-setup optional
Title: Message Title Ethan Brown commented on PUP-7116 Re: Make gettext-setup optional Merged to master in https://github.com/puppetlabs/puppet/commit/620b2695f671f24a69cc1eb845bda1440f05f20e 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-7124) Options should be passed to hiera 3 backend when declared in Hiera v5 config
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-7124 Options should be passed to hiera 3 backend when declared in Hiera v5 config Issue Type: Bug Assignee: Thomas Hallgren Created: 2017/01/20 2:04 PM Fix Versions: PUP 4.9.0 Priority: Normal Reporter: Thomas Hallgren Hiera 5 must ensure that a newly added hiera3_backend entry in the Hiera 5 configuration takes declared options into account and propagates them to the backend. Add Comment
Jira (PUP-7099) Hiera lookup_key functions crash when using a location
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7099 Hiera lookup_key functions crash when using a location Change By: Eric Thompson QA Risk Assessment Reason: covered by unit tests 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-7099) Hiera lookup_key functions crash when using a location
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7099 Hiera lookup_key functions crash when using a location Change By: Eric Thompson QA Risk Assessment: Needs Assessment No Action 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-7112) puppet master startup errors
Title: Message Title Henrik Lindberg commented on PUP-7112 Re: puppet master startup errors weihw Hope Michael's tip about required user accounts helps you. Besides that, there is not much we can go on here. Suggest you try to get onto Slack #puppet channel, and ask for interactive help there. Trying to solve your problem via this ticket will be a very slow way of getting help. I am therefore closing this ticket. If you have additional information that we can reproduce feel free to come back and reopen this ticket. 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-7116) Make gettext-setup optional
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7116 Make gettext-setup optional Change By: Kenn Hussey Flagged: Impediment 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-7116) Make gettext-setup optional
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7116 Make gettext-setup optional Change By: Kenn Hussey Flagged: Impediment 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-7116) Make gettext-setup optional
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7116 Make gettext-setup optional Change By: Kenn Hussey Flagged: Impediment 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-7123) Update P/A beaker constraint in project acceptance Gemfiles to get beaker 3.9.0
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7123 Update P/A beaker constraint in project acceptance Gemfiles to get beaker 3.9.0 Change By: Moses Mendoza Example:https://github.com/puppetlabs/hiera/blob/master/acceptance/Gemfile#L13Change to "~> 3.1" to allow updates to range within the 3.x seriesEnsure this is set in all acceptance-tested components of puppet-agent Once this work is done, before adding Ubuntu 16.10 back into the P/A CI matrices, run an ad-hoc acceptance run of puppet-agent with these changes against 16.10 to make sure it works 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-7123) Update project acceptance Gemfiles to use new beaker version
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7123 Update project acceptance Gemfiles to use new beaker version Change By: Moses Mendoza Example:https://github.com/puppetlabs/hiera/blob/master/acceptance/Gemfile#L13Change to "~> 3.1" to allow updates to range within the 3.x series Ensure this is set in all acceptance-tested components of 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-7123) Update P/A beaker constraint in project acceptance Gemfiles to get beaker 3.9.0
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7123 Update P/A beaker constraint in project acceptance Gemfiles to get beaker 3.9.0 Change By: Moses Mendoza Summary: Update P/A beaker constraint in project acceptance Gemfiles to use new get beaker version 3.9.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-7123) Update P/A project acceptance Gemfiles to use new beaker version
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7123 Update P/A project acceptance Gemfiles to use new beaker version Change By: Moses Mendoza Summary: Update P/A project acceptance Gemfiles to use new beaker version 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-7123) Update project acceptance Gemfiles to use new beaker version
Title: Message Title Moses Mendoza created an issue Puppet / PUP-7123 Update project acceptance Gemfiles to use new beaker version Issue Type: Task Assignee: Unassigned Created: 2017/01/20 11:28 AM Priority: Normal Reporter: Moses Mendoza Example: https://github.com/puppetlabs/hiera/blob/master/acceptance/Gemfile#L13 Change to "~> 3.1" to allow updates to range within the 3.x series Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7123) Update project acceptance Gemfiles to use new beaker version
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7123 Update project acceptance Gemfiles to use new beaker version Change By: Moses Mendoza Sprint: AP 2017-01-25 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-7122) Add a rake task to update the POT file only on string changes
Title: Message Title Maggie Dreyer commented on PUP-7122 Re: Add a rake task to update the POT file only on string changes gettext-setup PR: https://github.com/puppetlabs/gettext-setup-gem/pull/19 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-7122) Add a rake task to update the POT file only on string changes
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-7122 Add a rake task to update the POT file only on string changes Change By: Maggie Dreyer Assignee: Maggie Dreyer 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-7122) Add a rake task to update the POT file only on string changes
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-7122 Add a rake task to update the POT file only on string changes Issue Type: Task Assignee: Unassigned Created: 2017/01/20 10:56 AM Priority: Normal Reporter: Maggie Dreyer We need a rake task that will cache the existing POT file of a project, generate a new one, and check for changes in actual string content, only replacing the file if relevant changes are found. This allows us to only update the POT file if necessary and avoid churn due to changing modification dates. This task needs to be added to the gettext-setup gem, then given a wrapper task in Puppet. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-7100) Add a Hiera 5 eyaml lookup_key function
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7100 Add a Hiera 5 eyaml lookup_key function Change By: Eric Thompson QA Risk Assessment: Needs Assessment Automate 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-7100) Add a Hiera 5 eyaml lookup_key function
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7100 Add a Hiera 5 eyaml lookup_key function Change By: Eric Thompson QA Risk Assessment Reason: dependence on 3rd party gem, we just need to ensure it works 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-7069) puppet module generate fails on windows
Title: Message Title Josh Cooper commented on PUP-7069 Re: puppet module generate fails on windows I believe this is specific to the current working directory being a vagrant mounted filesystem. There are also a handful of related bugs when dealing with non-NTFS filesystems: PUP-1450 , PUP-6012, PUP-3533, PUP-2788, PUP-7077, PUP-4959 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-6763) Make CI job to update POT files
Title: Message Title Maggie Dreyer commented on PUP-6763 Re: Make CI job to update POT files The gettext:update_pot rake task only considers actual string differences, not changes to timestamp or SHA, in order to help reduce churn. In order to avoid kicking off a new run of the pipeline when this job makes a commit, we are either going to ignore commits made by the Jenkins user (as done in puppet-agent) or ignore changes to the POT file specifically. The job exposes several options to help debug and customize it: localization_enabled will cause the job to be skipped, for example if only certain pipelines have i18n support; localization_pot_file allows the user to specify the destination for the POT file within the repo; and localization_push_changes allows the user run the job without actually committing anything to the repo (the POT file will still be diffed and the result printed to the log), for debugging purposes. This job is going to be added to the very end of the Puppet component pipeline, after the promotion to puppet-agent. This was necessary because changing the component SHA part way through the pipeline was going to cause a lot of issues. As a a result, the SHA with the new POT file, if one was committed, will not get promoted into our downstream project until the NEXT time the pipeline runs. 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-6763) Make CI job to update POT files
Title: Message Title
Maggie Dreyer updated an issue
Puppet / PUP-6763
Make CI job to update POT files
Change By:
Maggie Dreyer
In order to get translation of Puppet underway, we need CI job added to the Puppet component pipeline which does the following:* generates a POT file* includes the original current SHA in the updated POT file* commits updated POT file to the repo if there were changes (the resulting SHA is the one that will get promoted into puppet-agent) * notifies the Transifex server that an update has occurred The POT file can be generated via a rake command provided by the gettext gem: {{bundle exec rake gettext: pot update_pot }} . Note that in Puppet this rake task is accessed via a delegate task of the same name, to avoid a build-time dependency on the gettext-setup gem. The PO files produced by Transifex from this POT file will be copied from that directory to the correct location on the system when Puppet is installed.
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-7112) puppet master startup errors
Title: Message Title Michael Smith commented on PUP-7112 Re: puppet master startup errors That's a surprising number of errors for the same thing. Running Puppet as master requires a user named puppet, in a group named puppet. See https://docs.puppet.com/puppet/3.8/from_source.html#create-the-puppet-user-and-group-puppet-master-servers-only (linked from https://github.com/puppetlabs/puppet#installation). 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-1559) CoreOS is recognized as Debian in last stable CoreOS version
Title: Message Title Michael Smith updated an issue Facter / FACT-1559 CoreOS is recognized as Debian in last stable CoreOS version Change By: Michael Smith Fix Version/s: FACT 3.6.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 (FACT-1559) CoreOS is recognized as Debian in last stable CoreOS version
Title: Message Title Michael Smith updated an issue Facter / FACT-1559 CoreOS is recognized as Debian in last stable CoreOS version Change By: Michael Smith Labels: maintenance 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-1559) CoreOS is recognized as Debian in last stable CoreOS version
Title: Message Title Michael Smith updated an issue Facter / FACT-1559 CoreOS is recognized as Debian in last stable CoreOS version Change By: Michael Smith Release Notes Summary: Facter will now report the correct OS name for recent releases of CoreOS. Release Notes: Bug Fix 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-7113) Implement forcelocal in AIX providers
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7113 Implement forcelocal in AIX providers Change By: Moses Mendoza Acceptance Criteria: Can create a user on AIX with the :forcelocal option and AIX will only query/use local user database 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-7113) Implement forcelocal in AIX providers
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7113 Implement forcelocal in AIX providers Change By: Moses Mendoza Labels: aix aix-parity 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-7113) Implement forcelocal in AIX providers
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7113 Implement forcelocal in AIX providers Change By: Moses Mendoza Sprint: AP Grooming 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-7113) Implement forcelocal in AIX providers
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7113 Implement forcelocal in AIX providers Change By: Moses Mendoza Labels: aix 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-7113) Implement forcelocal in AIX providers
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7113 Implement forcelocal in AIX providers Change By: Moses Mendoza Team: Agent & Platform 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-7120) systemd service provider treats "active (exited)" status as "running"
Title: Message Title Moses Mendoza commented on PUP-7120 Re: systemd service provider treats "active (exited)" status as "running" Thanks for filing Chris Butler. This is an interesting problem. My understanding is that when a service is in "active (exited)" state, it implies that systemd isn't aware of any daemon associated with the service, so effectively systemd is saying "I ran the commands you suggested, and they exited 0, so we're good to go". If that's accurate, it's sort of like saying "Effectively I consider this service to be running, it just doesn't have a daemon". It feels like a state that isn't covered by Puppet's stopped, running, etc. 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-7121) pxp-agent fails to start on Cisco switch
Title: Message Title Andrew Brader commented on PUP-7121 Re: pxp-agent fails to start on Cisco switch [root@sb2sf02lf01 var]# systemctl status pxp-agent -l pxp-agent.service - PCP Execution Protocol (PXP) Agent Loaded: loaded (/usr/lib/systemd/system/pxp-agent.service; enabled) Active: failed (Result: exit-code) since Fri 2017-01-20 16:26:20 UTC; 4min 39s ago Process: 944 ExecStart=/bin/nsenter --net=/var/run/netns/management -- /opt/puppetlabs/puppet/bin/pxp-agent $PXP_AGENT_OPTIONS --foreground (code=exited, status=3) Main PID: 944 (code=exited, status=3) Jan 20 16:26:20 sb2sf02lf01 nsenter[944]: Executing: /bin/nsenter --net=/var/run/netns/management -- /opt/puppetlabs/puppet/bin/pxp-agent --foreground Jan 20 16:26:20 sb2sf02lf01 nsenter[944]: Failed to configure logging: cannot write to '/var/log/puppetlabs/pxp-agent/pxp-agent.log'; its parent directory does not exist
Jira (HI-548) Acceptance: Switch to newer Solaris 11 LDOM
Title: Message Title Stan Duffy created an issue Hiera / HI-548 Acceptance: Switch to newer Solaris 11 LDOM Issue Type: Task Assignee: Stan Duffy Created: 2017/01/20 8:43 AM Environment: Puppet Agent CI Priority: Normal Reporter: Stan Duffy Current LDOM has some performance issue. Switching to newer LDOM Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7121) pxp-agent fails to start on Cisco switch
Title: Message Title Andrew Brader created an issue Puppet / PUP-7121 pxp-agent fails to start on Cisco switch Issue Type: Bug Assignee: Unassigned Created: 2017/01/20 8:41 AM Environment: puppet -V returned '4.7.0' This is the guestshell environment running on the Cisco switch. The guestshell environment image we are using is Centos 7 x86_64. This is not to be confused with the Cisco bash shell. Priority: Normal Reporter: Andrew Brader While we are working at RBC, we noticed in pxp-agent service cannot start because /var/log/puppetlabs/pxp-agent directory does not exist. When we create said directory and restart the service, all is well. What we learned is that the /var/log is a symlink to /var/volatile/log which is volatile memory masked in the OS by the switch. /var/volatile upon restart of the guestshell environment is cleared. Add Comment
Jira (FACT-1560) Acceptance: Switch to newer Solaris 11 LDOM
Title: Message Title Stan Duffy created an issue Facter / FACT-1560 Acceptance: Switch to newer Solaris 11 LDOM Issue Type: Task Assignee: Stan Duffy Created: 2017/01/20 8:39 AM Environment: Puppet Agent CI Priority: Normal Reporter: Stan Duffy The current LDOM has some performance issues that we haven't sorted out, so we have created a new LDOM that is 18% faster. Going to switch to the new LDOM. Add Comment This message was sent by
Jira (PUP-7114) Re-vendor semantic_pupppet gem
Title: Message Title Henrik Lindberg commented on PUP-7114 Re: Re-vendor semantic_pupppet gem Looked like this was merged - moved it to "ready for CI". 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-3170) Cap integer and float sizes
Title: Message Title Henrik Lindberg commented on PUP-3170 Re: Cap integer and float sizes Maybe it is enough to handle this in the transformation to 3.x compliant values for parameters. That would ensure resources do not end up with numbers that cannot be serialized. The values stored that way can also not be considered intermediate values that will undergo further arithmetic (before being serialized). 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-7079) Windows scheduled_task spec failures on puppet (master)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7079 Windows scheduled_task spec failures on puppet (master) Change By: Kenn Hussey Fix Version/s: PUP 4.8.z 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-7094) The parser dump output formatting is off
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7094 The parser dump output formatting is off Change By: Henrik Lindberg Fix Version/s: PUP 5.0.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-7094) The parser dump output formatting is off
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7094 The parser dump output formatting is off Change By: Henrik Lindberg Priority: Normal Minor 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-7094) The parser dump output formatting is off
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7094 The parser dump output formatting is off Change By: Henrik Lindberg Summary: Possible bug in Puppet The parser dump output formatting is off 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-7094) Possible bug in Puppet parser
Title: Message Title Rune Juhl Jacobsen commented on PUP-7094 Re: Possible bug in Puppet parser Hi Henrik, The code evaluates correctly so you're no doubt right; the problem must lie in the s-_expression_ representation of the internal structures. I'm a bit embarrassed that it didn't cross my mind... Anyway, thank you for your help. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3193) Fix beaker bug around duplicate keys
Title: Message Title Ken Barber updated an issue PuppetDB / PDB-3193 Fix beaker bug around duplicate keys Change By: Ken Barber Sprint: NG 2016-11-30, NG 2016-12-14, NG 2017-01-11 , NG 2017-01-25 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-3170) Cap integer and float sizes
Title: Message Title Henrik Lindberg commented on PUP-3170 Re: Cap integer and float sizes Yes it is actually. If we run on an MRI on a 32 bit platform, then I think Bignum must be supported. So, what I suggested was wrong. 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-7120) systemd service provider treats "active (exited)" status as "running"
Title: Message Title Chris Butler created an issue Puppet / PUP-7120 systemd service provider treats "active (exited)" status as "running" Issue Type: Bug Affects Versions: PUP 4.7.0 Assignee: Unassigned Created: 2017/01/20 3:54 AM Environment: Debian Jessie Priority: Normal Reporter: Chris Butler In systemd, a service can end up with the status "active (exited)", in cases where the service was started but exited with a zero exit code. Unfortunately, Puppet doesn't treat a service in this state as "stopped", which I think it should. I see this when installing pgbouncer on Debian Jessie. After the package has been installed but before it's been configured, the service ends up in a "active (exited)" state: # systemctl status pgbouncer
Jira (PUP-5954) Change deprecation from PUP-2695 (merge class) to error
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-5954 Change deprecation from PUP-2695 (merge class) to error Change By: Thomas Hallgren Assignee: 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-5954) Change deprecation from PUP-2695 (merge class) to error
Title: Message Title Thomas Hallgren commented on PUP-5954 Re: Change deprecation from PUP-2695 (merge class) to error Merged to 5.0 at d8d2c9b. 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.
