Jira (PUP-4550) Audit acceptance tests for user type
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4550 Audit acceptance tests for user type Change By: Eric Thompson It might be worth a broader audit of what our acceptance tests for the user type are missing. We have a few such tests, but at least the case found in pup-4491 slipped through the cracks. Also audit spec/integration and triage to test-rail similar to what was done for File resource. 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-4550) Audit acceptance tests for user type
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4550 Audit acceptance tests for user type Change By: Eric Thompson Sprint: Client 2015-05-27 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-4550) Audit acceptance tests for user type
Title: Message Title Eric Thompson assigned an issue to QA Puppet / PUP-4550 Audit acceptance tests for user type Change By: Eric Thompson Assignee: Eric Thompson 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-4550) Audit acceptance tests for user type
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4550 Audit acceptance tests for user type Change By: Eric Thompson Component/s: 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-4550) Audit acceptance tests for user type
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4550 Audit acceptance tests for user type Change By: Eric Thompson Assignee: 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-4491) Adding user to group fails
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4491 Adding user to group fails Change By: Kylo Ginsberg Sprint: Client 2015-05-13 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-4491) Adding user to group fails
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4491 Adding user to group fails Change By: Kylo Ginsberg Story Points: 1 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-4550) Audit acceptance tests for user type
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4550 Audit acceptance tests for user type Issue Type: Task Assignee: Unassigned Created: 2015/05/08 4:56 PM Fix Versions: PUP 4.x Priority: Normal Reporter: Kylo Ginsberg It might be worth a broader audit of what our acceptance tests for the user type are missing. We have a few such tests, but at least the case found in pup-4491 slipped through the cracks. Add Comment
Jira (PUP-4491) Adding user to group fails
Title: Message Title
Kylo Ginsberg updated an issue
Puppet / PUP-4491
Adding user to group fails
Change By:
Kylo Ginsberg
When adding a user to two groups a group , the command usermod fails . : {code:title=user.pp}user {'root': groups => ['root', 'wheel'],}{code}{code:title=Console output}Error: Could not set groups on user[root]: Execution of '/usr/sbin/usermod -S root,wheel root' returned 2: /usr/sbin/usermod: invalid option -- 'S'{code}
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-4477) Create a base agent upgrade module for rpm-based distro
Title: Message Title Michael Smith commented on PUP-4477 Re: Create a base agent upgrade module for rpm-based distro Richard Clamp Is MCO's server.cfg location configurable? For Puppet 3.8 can I expect it to only be at /etc/mcollective/server.cfg (on RPM distros)? 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-4543) Document best practices for acceptance tests with puppet 4
Title: Message Title William Hopper commented on PUP-4543 Re: Document best practices for acceptance tests with puppet 4 The workflow I ended up using: 1) Build a puppet-agent package with Vanagon, setting puppet.json to point at your development branch 2) Spin up a few VMpooler VMs (one master and one agent) and install your puppet-agent package on them. 4) Install puppetserver from yum/apt.puppetlabs.net on your master VM 4) Add the new private bindir to root / puppet's path, or symlink the binaries into /bin 5) Create a new preserved-hosts.yaml node config in puppet/acceptance/config/nodes which points to your new VMs 6) Run beaker directly, pointing it at your preserved-hosts.yaml file, with the preserve-hosts option set to always. The exact invocation looks something like: bundle exec beaker --hosts ./config/nodes/hosts_preserved.yaml --no-provision --preserve-hosts always --tests ./tests/ The preserved-hosts.yaml file will look something like: --- HOSTS: cr7ku0fnq4bgtyg.delivery.puppetlabs.net: roles: - master platform: el-7-x86_64
Jira (PUP-4477) Create a base agent upgrade module for rpm-based distro
Title: Message Title Michael Smith updated an issue Puppet / PUP-4477 Create a base agent upgrade module for rpm-based distro Change By: Michael Smith Prerequisites for this module to be used:* Agent is at puppet 3.8 and running correctly with stringify_facts = false** Only the version number constraint is enforced by the module* Master-side is puppetserver 2.1+ (i.e. supports both 3.x and 4.x network APIs)The base requirements are roughly:* check puppet version** if version < 3.8, fail** if version >= 4, warn** else upgradeIf upgrading:* Capture ssldir and copy all certs into new ssldir* Copy the current puppet.conf * Remove (or comment out) any deprecated settings in puppet.conf** stringify_facts, parser, ... (https://docs.puppetlabs.com/references/3.stable/configuration.html) * Remove disable_warnings* Remove vardir, rundir, libdir and confdir overrides (and any settings that derive from those settings by default)* Install the new agent, based off of PC1 on yum.puppetlabs.comNote: Installing the new agent will usually remove the old one. That handoff needs special attention to get the new agent up-and-running.MCollective * Copy and edit the server.cfg similar to Puppet* If libdir is set, append new paths to it* Update or replace logdir with the new logdir value* Update plugin.yaml and append new fact cache path to ith3. QArisk: hightest level: acceptance and 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 gr
Jira (PDB-1512) Don't allow overlapping syncs from the same host
Title: Message Title Russell Mull created an issue PuppetDB / PDB-1512 Don't allow overlapping syncs from the same host Issue Type: Task Assignee: Unassigned Created: 2015/05/08 3:59 PM Priority: Normal Reporter: Russell Mull If a sync is requested by the user when one is already running it should do one of these: politely decline, with a friendly message queue it up for later execution Add Comment
Jira (PUP-4477) Create a base agent upgrade module for rpm-based distro
Title: Message Title Michael Smith updated an issue Puppet / PUP-4477 Create a base agent upgrade module for rpm-based distro Change By: Michael Smith Prerequisites for this module to be used:* Agent is at puppet 3.8 and running correctly with stringify_facts = false** Only the version number constraint is enforced by the module* Master-side is puppetserver 2.1+ (i.e. supports both 3.x and 4.x network APIs)The base requirements are roughly:* check puppet version** if version < 3.8, fail** if version >= 4, warn** else upgradeIf upgrading:* Capture ssldir and copy all certs into new ssldir* Copy the current puppet.conf * Remove (or comment out) any deprecated settings in puppet.conf* * stringify_facts, parser, ...* Remove disable_warnings* Remove vardir, rundir, libdir and confdir overrides (and any settings that derive from those settings by default)* Install the new agent, based off of PC1 on yum.puppetlabs.comNote: Installing the new agent will usually remove the old one. That handoff needs special attention to get the new agent up-and-running.MCollective * Copy and edit the server.cfg similar to Puppet* If libdir is set, append new paths to it* Update or replace logdir with the new logdir value* Update plugin.yaml and append new fact cache path to ith3. QArisk: hightest level: acceptance and 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+u
Jira (PUP-4477) Create a base agent upgrade module for rpm-based distro
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4477 Create a base agent upgrade module for rpm-based distro Change By: Kylo Ginsberg Prerequisites for this module to be used:* Agent is at puppet 3.8 and running correctly with future parser stringify_facts = false ** Only the version number constraint is enforced by the module* Master-side is puppetserver 2.1+ (i.e. supports both 3.x and 4.x network APIs)The base requirements are roughly:* check puppet version** if version < 3.8, fail** if version >= 4, warn** else upgradeIf upgrading:* Capture ssldir and copy all certs into new ssldir* Copy the current puppet.conf * Remove (or comment out) any deprecated settings in puppet.conf* Remove disable_warnings* Remove vardir, rundir, libdir and confdir overrides (and any settings that derive from those settings by default)* Install the new agent, based off of PC1 on yum.puppetlabs.comNote: Installing the new agent will usually remove the old one. That handoff needs special attention to get the new agent up-and-running.MCollective * Copy and edit the server.cfg similar to Puppet* If libdir is set, append new paths to it* Update or replace logdir with the new logdir value* Update plugin.yaml and append new fact cache path to ith3. QArisk: hightest level: acceptance and 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...@googl
Jira (PUP-1931) mount provider improvement when options property is not specified
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1931 mount provider improvement when options property is not specified Change By: Eric Thompson QA Risk Assessment Reason: work arounds, small annoyance 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-1931) mount provider improvement when options property is not specified
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1931 mount provider improvement when options property is not specified 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 (PUP-1931) mount provider improvement when options property is not specified
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1931 mount provider improvement when options property is not specified Change By: Eric Thompson QA Risk Assessment: Medium 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-4491) Adding user to group fails
Title: Message Title Kylo Ginsberg commented on PUP-4491 Re: Adding user to group fails I verified the above fixes the problem. 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-1931) mount provider improvement when options property is not specified
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1931 mount provider improvement when options property is not specified Change By: Eric Thompson QA Risk Severity: Low 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-4491) Adding user to group fails
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4491 Adding user to group fails Change By: Kylo Ginsberg Fix Version/s: PUP 4.1.0 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-1931) mount provider improvement when options property is not specified
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1931 mount provider improvement when options property is not specified Change By: Eric Thompson QA Risk Probability: Medium 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-4473) Extend file-based ENC spec tests to include Windows
Title: Message Title Michael Smith assigned an issue to QA Puppet / PUP-4473 Extend file-based ENC spec tests to include Windows 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-735) Status unchanged when "Could not apply complete catalog"
Title: Message Title Michael Smith assigned an issue to QA Puppet / PUP-735 Status unchanged when "Could not apply complete catalog" 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 (PDB-1465) PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker
Title: Message Title gepetto-bot commented on PDB-1465 Re: PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker ajroetker commented: Refactored but relies on @wkalt's patch to remove late project 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-1511) make http error formats consistent with other services
Title: Message Title Kenneth Barber commented on PDB-1511 Re: make http error formats consistent with other services There is also this: https://github.com/puppetlabs/puppet-nogui/blob/master/patterns/api_style_guide.md#errors which is an attempt to document & standardize errors from UX. /cc J.D. Welch FYI. 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-1931) mount provider improvement when options property is not specified
Title: Message Title
Eric Thompson commented on PUP-1931
Re: mount provider improvement when options property is not specified
validated on ubuntu14.04 at SHA: 36c485f
root@ytuw6bemvvkx5hz ~]# puppet apply -e 'mount { "/mnt/": ensure => "defined", fstype => "ext2", device => "/dev/sda2" } '
Notice: Compiled catalog for ytuw6bemvvkx5hz.delivery.puppetlabs.net in environment production in 0.43 seconds
Notice: Applied catalog in 0.03 seconds
[root@ytuw6bemvvkx5hz ~]# cat /etc/fstab
# HEADER: This file was autogenerated at 2015-05-08 12:01:23 -0700
# HEADER: by puppet. While it can still be managed manually, it
# HEADER: is definitely not recommended.
#
# /etc/fstab
Jira (PUP-4549) puppet acts like a module's subcommand doesn't exist if given a bad --environmentpath
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4549 puppet acts like a module's subcommand doesn't exist if given a bad --environmentpath Change By: Eric Thompson Scrum Team: Language Client Platform 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-4549) puppet acts like a module's subcommand doesn't exist if given a bad --environmentpath
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4549 puppet acts like a module's subcommand doesn't exist if given a bad --environmentpath Change By: Eric Thompson Summary: puppet acts like preview a module's subcommand doesn't exist if given a bad --environmentpath 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-4549) puppet acts like preview subcommand doesn't exist if given a bad --environmentpath
Title: Message Title Eric Thompson moved an issue Puppet / PUP-4549 puppet acts like preview subcommand doesn't exist if given a bad --environmentpath Change By: Eric Thompson Key: PRE PUP - 39 4549 Project: Puppet Catalog Preview 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-4541) Create acceptance test for handling of default case in case statement in Puppet DSL
Title: Message Title Kurt Wall commented on PUP-4541 Re: Create acceptance test for handling of default case in case statement in Puppet DSL I dropped the risk level of PUP-4520 to Medium, so I can omit an acceptance test. Closing WNF. 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-735) Status unchanged when "Could not apply complete catalog"
Title: Message Title Josh Cooper commented on PUP-735 Re: Status unchanged when "Could not apply complete catalog" Fixup merged to stable in f72d2e7339e 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-1511) make http error formats consistent with other services
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1511 make http error formats consistent with other services Issue Type: Improvement Assignee: Unassigned Created: 2015/05/08 11:37 AM Priority: Normal Reporter: Wyatt Alt We have a guide here: https://confluence.puppetlabs.com/display/ENG/Exceptions+and+Slingshot I'm not sure we're following the standard anywhere. We should sync up with the rbac and NC teams to see what the unified approach is. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4420) Executable external facts broken in 4.0.0: not executable on agent
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-4420 Executable external facts broken in 4.0.0: not executable on agent Change By: Josh Cooper Assignee: Josh Cooper 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-4473) Extend file-based ENC spec tests to include Windows
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-4473 Extend file-based ENC spec tests to include Windows Change By: Josh Cooper Assignee: Josh Cooper 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-4541) Create acceptance test for handling of default case in case statement in Puppet DSL
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4541 Create acceptance test for handling of default case in case statement in Puppet DSL Change By: Kurt Wall Story Points: 1 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-4547) Ruby and irb on Windows can't find 'puppet', 'facter', etc.
Title: Message Title Michael Smith updated an issue Puppet / PUP-4547 Ruby and irb on Windows can't find 'puppet', 'facter', etc. Change By: Michael Smith We don't install our Ruby libraries into Ruby's default library paths, so all our tools have batch files that set LIBRUBY RUBYLIB . We didn't do the same for Ruby binaries, so anyone trying to use Ruby from the MSI with Puppet will have problems. See PUP-735 for a case that came up in acceptance tests.We should install our libraries into the normal Ruby library paths, as we do on other platforms, so Ruby things just work. 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-4548) Extend tests/reports/finalized_on_cycle.rb to Windows
Title: Message Title Michael Smith created an issue Puppet / PUP-4548 Extend tests/reports/finalized_on_cycle.rb to Windows Issue Type: Improvement Assignee: Unassigned Created: 2015/05/08 11:18 AM Priority: Normal Reporter: Michael Smith 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 ht
Jira (PUP-4436) With a gem install of puppet, when run as root, 'puppet {agent|apply}' fail
Title: Message Title
Josh Cooper commented on PUP-4436
Re: With a gem install of puppet, when run as root, 'puppet {agent|apply}' fail
With the PR, puppet as a gem no longer tries to create file/directories in the per-user locations:
[root@bs2fk9iuildw7ut ~]# env HOME=/dev/null puppet apply -e "notice(1)" --debug
...
Debug: /File[/etc/puppetlabs/puppet]/ensure: created
Debug: /File[/etc/puppetlabs/code]/ensure: created
Debug: /File[/opt/puppetlabs/puppet/cache]/ensure: created
Debug: /File[/var/log/puppetlabs/puppet]/ensure: created
Debug: /File[/var/run/puppetlabs]/ensure: created
Add Comment
Jira (PUP-4547) Ruby and irb on Windows can't find 'puppet', 'facter', etc.
Title: Message Title Michael Smith created an issue Puppet / PUP-4547 Ruby and irb on Windows can't find 'puppet', 'facter', etc. Issue Type: Bug Assignee: Unassigned Components: Windows Created: 2015/05/08 11:14 AM Priority: Normal Reporter: Michael Smith We don't install our Ruby libraries into Ruby's default library paths, so all our tools have batch files that set LIBRUBY. We didn't do the same for Ruby binaries, so anyone trying to use Ruby from the MSI with Puppet will have problems. See PUP-735 for a case that came up in acceptance tests. We should install our libraries into the normal Ruby library paths, as we do on other platforms, so Ruby things just work. Add Comment
Jira (PUP-735) Status unchanged when "Could not apply complete catalog"
Title: Message Title Michael Smith commented on PUP-735 Re: Status unchanged when "Could not apply complete catalog" Calling require 'puppet' from plain Ruby doesn't seem to have the environment setup to find Puppet. I'm not sure if that's something we want to fix; I don't see why the script requires Puppet in the first place. 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-1253) systemd service provider should support masking
Title: Message Title Kurt Wall updated an issue Puppet / PUP-1253 systemd service provider should support masking Change By: 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-96) Deprecate 'facter --puppet'
Title: Message Title Joshua Partlow commented on FACT-96 Re: Deprecate 'facter --puppet' Josh Cooper Would this change land in shallow gravy (along with any improvements needed to puppet facts?) I'm just thinking about the pe_mcollective changes. 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-963) Remove pre-suite environment setup for AIO
Title: Message Title Kurt Wall updated an issue Facter / FACT-963 Remove pre-suite environment setup for AIO Change By: Kurt Wall QA Risk Assessment Reason: N/A for testing tickets 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-965) facter doesn't run under jruby
Title: Message Title Kurt Wall updated an issue Facter / FACT-965 facter doesn't run under jruby Change By: 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-965) facter doesn't run under jruby
Title: Message Title Kurt Wall updated an issue Facter / FACT-965 facter doesn't run under jruby Change By: Kurt Wall QA Risk Assessment: High 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-1253) systemd service provider should support masking
Title: Message Title Kurt Wall commented on PUP-1253 Re: systemd service provider should support masking Kylo Ginsberg Should we just pull this on through? It seems like if this was problematic we would have heard about it before now. Thoughts? 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-963) Remove pre-suite environment setup for AIO
Title: Message Title Kurt Wall updated an issue Facter / FACT-963 Remove pre-suite environment setup for AIO Change By: 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 (PUP-4471) Acceptance test ensuring puppet apply works when an ENC returns an environment
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4471 Acceptance test ensuring puppet apply works when an ENC returns an environment Change By: Kurt Wall QA Risk Assessment Reason: N/A for testing tickets 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-4471) Acceptance test ensuring puppet apply works when an ENC returns an environment
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4471 Acceptance test ensuring puppet apply works when an ENC returns an environment Change By: 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-979) Facter acceptance in AIO fails due to older version of Beaker
Title: Message Title Kurt Wall updated an issue Facter / FACT-979 Facter acceptance in AIO fails due to older version of Beaker Change By: Kurt Wall QA Risk Assessment Reason: N/A for testing tickets 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-979) Facter acceptance in AIO fails due to older version of Beaker
Title: Message Title Kurt Wall updated an issue Facter / FACT-979 Facter acceptance in AIO fails due to older version of Beaker Change By: 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 (PUP-4537) Transitory failure on rdoc specs in AppVeyor
Title: Message Title Ethan Brown commented on PUP-4537 Re: Transitory failure on rdoc specs in AppVeyor I'm not aware of any issues there. Windows does have a limit for a fully qualified path (MAX_PATH 260 chars) that we do occasionally run in to, but I don't see that being a problem given that path is 152 characters long. I don't have the chance to dig in at the moment, but note that there are 3 nearly identical tests there (and 2 of the 3 are failing), so the temp file part looks like it could be a red herring? https://github.com/puppetlabs/puppet/blob/master/spec/integration/util/rdoc/parser_spec.rb#L161-L172 If you take a look at the path in question - C:/Users/appveyor/AppData/Local/Temp/1/rspecrun20150506-1356-1tdbqqr/rdoc_parser_tmp20150506-1356-1bl19oe/doc/_/_/Users/appveyor/AppData/Local/Temp/1, you'll see that it looks a little peculiar given Users/appveyor/AppData/Local/Temp/1 repeats twice. It would be good to know why that's the case, because at first glance it looks pretty fishy. 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-735) Status unchanged when "Could not apply complete catalog"
Title: Message Title Josh Cooper commented on PUP-735 Re: Status unchanged when "Could not apply complete catalog" Branan Riley can you take a look? 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-4491) Adding user to group fails
Title: Message Title Kylo Ginsberg commented on PUP-4491 Re: Adding user to group fails I wonder if the new openbsd user provider is bleeding through to other platforms and should be confined to just openbsd instead of just the defaultfor openbsd: https://github.com/puppetlabs/puppet/blob/088cdba9976914ebe2857ba2bdf2bac50fda339f/lib/puppet/provider/user/openbsd.rb#L13 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-735) Status unchanged when "Could not apply complete catalog"
Title: Message Title Eric Thompson commented on PUP-735 Re: Status unchanged when "Could not apply complete catalog" Josh Cooper the acceptance test is failing on windows against stable branch. 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-4115) Investigate Debian 6 32 bit AIO acceptance failure
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4115 Investigate Debian 6 32 bit AIO acceptance failure Change By: Eric Thompson Priority: Normal Minor 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-4115) Investigate Debian 6 32 bit AIO acceptance failure
Title: Message Title Eric Thompson commented on PUP-4115 Re: Investigate Debian 6 32 bit AIO acceptance failure looks like PUP-4340 didn't fix this. failed again on All In One Agent (stable): Step 4 – Puppet Tests beaker,debian-6-i386 today. reopening at low priority. Failed Tests Cases: Test Case tests/resource/file/source_attribute.rb reported: # Should have updated files. Expected /File\[\/tmp\/source_attr_testctime\]\/content: content changed/ to match "\e[0;32mInfo: Retrieving pluginfacts\e[0m\n\e[0;32mInfo: Retrieving plugin\e[0m\n\e[0;32mInfo: Caching catalog for uo82a7oa94rt82j.delivery.puppetlabs.net\e[0m\n\e[0;32mInfo: Applying configuration version '1431091904'\e[0m\n\e[mNotice: Applied catalog in 0.39 seconds\e[0m\n". > Add Comment
Jira (PUP-4540) Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type
Title: Message Title Victor Danilchenko commented on PUP-4540 Re: Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type The 'jessie' service provider in the upstream ticket (https://gist.github.com/leepa/9818b46b29b161413824) works – however, so does the stock 'debian' provider. The problem is that the service management gets automatically delegated to the Upstart provider instead. In fact, simply removing service/upstart.rb provider, or replacing it with string-substituted copy of the service/debian.rb, makes the problem go away. Of course this is not the correct solution, but it solves our specific problem. I am not sure if it's the same problem as the one described in PUP-4503, but if it isn't, it seems to be related. However, I don't think it's the same problem, because PUP-4503 apparently offers the 'jessie' provider as a replacement for the 'debian' provider – but in my case, on Vivid, the 'debian' provider actually works; it's not the provider itself that's broken, but the detection for which provider to delegate service management to. 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-4541) Create acceptance test for handling of default case in case statement in Puppet DSL
Title: Message Title Henrik Lindberg commented on PUP-4541 Re: Create acceptance test for handling of default case in case statement in Puppet DSL Does this really require an acceptance test? This ticket was added to the sprint without story points - please update if an acceptance test is really needed 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-4210) Support "rename" in the augeas resource type
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-4210 Support "rename" in the augeas resource type 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 (PUP-4210) Support "rename" in the augeas resource type
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-4210 Support "rename" in the augeas resource type 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 (PUP-4030) puppet module install does not consider no_proxy env var
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-4030 puppet module install does not consider no_proxy env var 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 (PUP-4030) puppet module install does not consider no_proxy env var
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-4030 puppet module install does not consider no_proxy env var 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 (PUP-3027) ENC should be aware of the requested environment
Title: Message Title Michal Zubac commented on PUP-3027 Re: ENC should be aware of the requested environment I would also appreciate this feature, as I want to assign classes using ENC based on chosen environment. Without worrying where the environment decision came from. I am voting for the second argument choice. 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-4469) Consider adding requested environment to ENC request call
Title: Message Title Michal Zubac commented on PUP-4469 Re: Consider adding requested environment to ENC request call As I understand the issue, it is not so related to PUP 4459 thing. You can have classes or parameters based on environment which is chosen. The environment can be chosen by agent or by ENC, but it does not matter in this ticket. I am also interested in this functionality, but more about it is already discussed in [PUP 3027https://tickets.puppetlabs.com/browse/PUP-3027]. 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-4542) mandatory attributes on defined resource types are not required for virtual/exported resources
Title: Message Title Geoff Williams commented on PUP-4542 Re: mandatory attributes on defined resource types are not required for virtual/exported resources Henrik Lindberg I did wonder if this was the case. It would be great if this could be reviewed in order to give a more consistent experience to end users 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-4537) Transitory failure on rdoc specs in AppVeyor
Title: Message Title Henrik Lindberg commented on PUP-4537 Re: Transitory failure on rdoc specs in AppVeyor Ethan Brown Rob Reynolds Any ideas regarding possible causes of intermittent failures wrt. a missing tmp file on windows? 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-4537) Transitory failure on rdoc specs in AppVeyor
Title: Message Title Henrik Lindberg commented on PUP-4537 Re: Transitory failure on rdoc specs in AppVeyor It appears that the problems are caused by missing files: No such file or directory @ rb_sysopen - C:/Users/appveyor/AppData/Local/Temp/1/rspecrun20150506-1356-1tdbqqr/rdoc_parser_tmp20150506-1356-1bl19oe/doc/__/__/Users/appveyor/AppData/Local/Temp/1 [00:13:33] /rspecrun20150506-1356-1tdbqqr/rdoc_parser_tmp20150506-1356-1bl19oe/modules/a_module/manifests/a_type_pp.html (Errno::ENOENT) So, some kind of problem with tmp files on Windows? Or creating directories in a path? (Have not yet looked at details what the tests actually do). 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/opt
Jira (PUP-4542) mandatory attributes on defined resource types are not required for virtual/exported resources
Title: Message Title Henrik Lindberg commented on PUP-4542 Re: mandatory attributes on defined resource types are not required for virtual/exported resources This is because the intent is to do late binding of the parameter values; they are set when the resource is realized not when it is instantiated. The defaults and data bindings that are in effect when the resource is realized determines if the value is missing or not. I.e. this is not a bug - it is the "specified" (in quotes because there is no written specification) behavior. Whether this is the desired behavior or not is a different issue. As we are going to be working a new compiler and catalog format, features like this one (lazy binding of parameters) are up for review. If we do change this it will have to be on a major version boundary. 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-4542) mandatory attributes on defined resource types are not required for virtual/exported resources
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4542 mandatory attributes on defined resource types are not required for virtual/exported resources Change By: Henrik Lindberg Scrum Team: 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 (PUP-4531) create_resources() should deep merge the default parameters
Title: Message Title Henrik Lindberg commented on PUP-4531 Re: create_resources() should deep merge the default parameters Yes, this ticket is a request for a new feature. I am also saying that there needs to be functions that have simple straight forward behavior to build other functions on. Say that we were to change the create_resources to always do deep merge, then there is no way to stop that from happening. This means adding more parameters to control if merge should take place or not. Then people will need control over the merge (which adds several additional options). This is what I am referring to as "swiss army knife" - a function that includes the functionality for "everything you need". From puppet 4.1.0 you can write functions in the puppet language and it is thus very simple to create your own mymodule::create_resources function that performs merges and calls the create_resources function in puppet core. If you want to do this before then, you need to write that function in ruby. If you are using future parser or are using puppet 4.0.0 you can use the 4.x function API to create a name spaces function (so you can use the same name 'create_resources' and not worry about it clashing with something else). 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-4531) create_resources() should deep merge the default parameters
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4531 create_resources() should deep merge the default parameters Change By: Henrik Lindberg Issue Type: Bug New Feature 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-4531) create_resources() should deep merge the default parameters
Title: Message Title Davide Ferrari commented on PUP-4531 Re: create_resources() should deep merge the default parameters Well, there is indeed an undocumented deep_merge() in stdlib (I use it quite a lot, hoping that it won't just disappear one day), and in fact I'm using it to work around the current behaviour, but it makes code more complex in my opinion. Anyway it seems to me that you comment feels like "it's not a bug, it's a feature", right? 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-1471) Puppetdb 2.3.3 perfomance issue afer upgrading from 1.6
Title: Message Title Akos Hencz commented on PDB-1471 Re: Puppetdb 2.3.3 perfomance issue afer upgrading from 1.6 We will have to test and schedule the update. When that's done I can compare the metric values. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4546) pkgin output incorrectly parsed
Title: Message Title Jasper Lievisse Adriaanse commented on PUP-4546 Re: pkgin output incorrectly parsed PR: https://github.com/puppetlabs/puppet/pull/3905 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4546) pkgin output incorrectly parsed
Title: Message Title
Jasper Lievisse Adriaanse created an issue
Puppet / PUP-4546
pkgin output incorrectly parsed
Issue Type:
Bug
Affects Versions:
PUP 4.0.0
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
2015/05/08 1:59 AM
Environment:
cargos, pkgsrc 2015q1,
Priority:
Normal
Reporter:
Jasper Lievisse Adriaanse
The pkgin tool adjusts it's output when run from an interactive or non-interactive terminal by replacing spaces with semicolons. The provider was not adjusted for this and thus exhibited odd behaviour such as 'puppet resource package virt-what' resulting in:
package { 'virt-what': ensure => '1.15;Detect', }
The PR associated with the ticket switches the 'search' and 'list' commands to explicitly use '-p' (for parsable format) eventhough it's implied for non-interactive, and adjusts the regex accordingly.
Jira (PUP-4545) To many restarts on interaface changes for Fedora, RHEL, CentOS
Title: Message Title Christoph Maser created an issue Puppet / PUP-4545 To many restarts on interaface changes for Fedora, RHEL, CentOS Issue Type: Bug Affects Versions: PUP 3.7.5 Assignee: Unassigned Created: 2015/05/08 12:19 AM Labels: puppet-agent Priority: Normal Reporter: Christoph Maser In https://projects.puppetlabs.com/issues/2776 a workaround was introduced to restart puppet on Fedora, RHEL, CentOS which restarts puppet on each interface change. The script /etc/NetworkManager/dispatcher.d/98-puppet restarts puppet agents every time a interface goes up or down regardless of the type. Nowadays with VMs and containers you can get a lot of interface up downs for virtual interfaces. Because of the workaround from #2776 this creates a lot of un-necessary agent restarts. A workaround of the workaround might be to make a regex blacklist for interface names, e.G. [ 'veht.', 'vibr.', 'docker.*'] A cleaner solution would be to actually monitor /etc/resolv.conf in an agent run, since changes in resolv.conf by agent was the original problem, and not to use NetworkManager for restarts.
