Jira (PUP-6915) sensitive_data_type test fails on Fedora
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-6915 sensitive_data_type test fails on Fedora Issue Type: CI Blocker Assignee: Unassigned Created: 2016/11/10 10:42 PM Priority: Normal Reporter: Maggie Dreyer The language/senstivite_data_type test fails on Fedora with the following error: PuppetAcceptance::DSL::Helpers.with_puppet_running_on failed (check backtrace for location) because: Host 'yqbpdualgts2s36.delivery.puppetlabs.net' exited with 1 running: tail -n 100 /var/log/messages Last 10 lines of output were: tail: cannot open ‘/var/log/messages’ for reading: No such file or directory
Jira (PUP-6899) puppet lookup ignores --hiera_config option
Title: Message Title
R.I.Pienaar commented on PUP-6899
Re: puppet lookup ignores --hiera_config option
Jesse Reynolds it looks under the environmentpath, so pass to your puppet lookup invocation the correct --environmentpath
% cd ~/temp/preso
% ls environments/production/hiera.yaml
environments/production/hiera.yaml
% puppet lookup --environmentpath /home/rip/temp/preso/environments users::local
{}
this is why you dont need to set hiera.yaml location, it's fixed relative to the env path
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6899) puppet lookup ignores --hiera_config option
Title: Message Title Jesse Reynolds commented on PUP-6899 Re: puppet lookup ignores --hiera_config option Thanks Henrik Lindberg ... Yes fine with me to kidnap this ticket as proposed Aside: I think not being able to test v4 hiera environment configs in isolation is a bit of a limiting factor. But maybe I'm not understanding things correctly. Could I set up enough puppet configuration options to convince puppet that it is a per environment hiera config that is being consulted when you run 'puppet lookup --explain ... ' ? ... Imagine you've cloned a control-repo into a random directory on your laptop and you just want to validate that the hiera v4 environment config is working as expected. 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-6909) useradd.rb report error
Title: Message Title stonelai commented on PUP-6909 Re: useradd.rb report error Here is the module which caused this proble. http://pastebin.com/VgazbkYx 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-6909) useradd.rb report error
Title: Message Title
stonelai commented on PUP-6909
Re: useradd.rb report error
:unmunge => proc { |value| if value == -1 :absent else # Expiry is days after 1970-01-01 (Date.new(1970,1,1) + value).strftime('%Y-%m-%d') end }
if the value is null, this script will run failed. An error message will be occur in puppet.
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-6762) (SPIKE) How and when do we get PO files from Transifex?
Title: Message Title Moses Mendoza commented on PUP-6762 Re: (SPIKE) How and when do we get PO files from Transifex? thanks for the ping Larissa Lane - added 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-6762) (SPIKE) How and when do we get PO files from Transifex?
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6762 (SPIKE) How and when do we get PO files from Transifex? Change By: Moses Mendoza Transifex is third-party translation-as-a-service provider that provides translation services in the form of PO files. * Workflow includes committing PO files from Transifex to a Github repository.* Design a workflow for getting files from Transifex to us.h5. Questions:* Does the Transifex integration use a push or pull model to obtain code/strings to be translated?A: Transifex watches the Github repo for changes to a PO file using a webhook. When changes are made, it pulls the latest version of the PO file into Transifex.* Does the Transifex integration use a push or pull model to provide PO files?A: Transifex waits for a PO file in Transifex to reach 100% translated and reviewed. When the status of the PO file changes to 100% reviewed, Transifex pushes the latest version of the file to the source Github repo.* If push model, what are the security implications and design to mitigate?A: The configuration of the Transifex server is described in [OPS-9632|https://tickets.puppetlabs.com/browse/OPS-9632]. What specific security questions do you have? *Specific Security Questions* If the credentials stored by transifex are compromised what is our risk exposure?** what are the specific access rights bestowed by said credentials? (ie push to one github repo? all repos? admin?)** Are there options available to us to reduce that risk?** ex: create an account with access to a fork only and then automate creation of a PR?** ex: create an account with limited rights (is this possible?)* (risk to release cycle) How do we prevent introducing changes to puppet when it would be disruptive to a release cycle (ie 'frozen' dates)** maybe establish windows when push is allowed?** make sure all reviewers know to check with agent team and puppet maintainers before pushing? (possibly error prone?)** automated PR (rather than push) might make this a moot point Add Comment
Jira (PUP-6907) Don't provide $name (and perhaps others) in EPP scope
Title: Message Title Alex Jurkiewicz commented on PUP-6907 Re: Don't provide $name (and perhaps others) in EPP scope Yeah, special-casing a scope does sound bad the morning after this bug was filed! I don't have any smart ideas really, just one which is also a special-case but perhaps less so. Create a new scope which either no variables by default or perhaps only facter ones. Other variables (eg globals from ENC) would have to be explicitly loaded. But beyond that, perhaps this simply has to remain a tricky gotcha for new programmers 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-6762) (SPIKE) How and when do we get PO files from Transifex?
Title: Message Title Larissa Lane commented on PUP-6762 Re: (SPIKE) How and when do we get PO files from Transifex? Geoff Nichols Moses Mendoza Can you add a list of questions here that you have about security of the Transifex integration? I have set up an API user in github specifically for the integration, and also an API user in Transifex that is also used only for this purpose. The integration requires the Github API user's name and access token, and the Transifex API user's name and password. 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-6762) (SPIKE) How and when do we get PO files from Transifex?
Title: Message Title Larissa Lane updated an issue Puppet / PUP-6762 (SPIKE) How and when do we get PO files from Transifex? Change By: Larissa Lane Transifex is third-party translation-as-a-service provider that provides translation services in the form of PO files. * Workflow includes committing PO files from Transifex to a Github repository.* Design a workflow for getting files from Transifex to us.h5. Questions:* Does the Transifex integration use a push or pull model to obtain code/strings to be translated?A: Transifex watches the Github repo for changes to a PO file using a githook webhook . When changes are made, it pulls the latest version of the PO file into Transifex.* Does the Transifex integration use a push or pull model to provide PO files?A: Transifex waits for a PO file in Transifex to reach 100% translated and reviewed. When the status of the PO file changes to 100% reviewed, Transifex pushes the latest version of the file to the source Github repo.* If push model, what are the security implications and design to mitigate?A: The configuration of the Transifex server is described in [OPS-9632|https://tickets.puppetlabs.com/browse/OPS-9632]. What specific security questions do you have? 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.
Jira (PUP-6914) ruby expand_path in file type breaks leading-tilde file resources
Title: Message Title Christopher Wood commented on PUP-6914 Re: ruby expand_path in file type breaks leading-tilde file resources Original thread: https://groups.google.com/forum/#!topic/puppet-users/vG8Wbtiwgow 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 (PDOC-135) Strings doesn't recognize `return_type` in 4.x function dispatch
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-135 Strings doesn't recognize `return_type` in 4.x function dispatch Change By: William Hopper Fix Version/s: PDOC 1.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 (PDOC-135) Strings doesn't recognize `return_type` in 4.x function dispatch
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-135 Strings doesn't recognize `return_type` in 4.x function dispatch Change By: William Hopper Sprint: PDS 2016-11-16 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 (PDOC-135) Strings doesn't recognize `return_type` in 4.x function dispatch
Title: Message Title William Hopper assigned an issue to William Hopper Puppet Strings / PDOC-135 Strings doesn't recognize `return_type` in 4.x function dispatch Change By: William Hopper Assignee: William Hopper 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-6914) ruby expand_path in file type breaks leading-tilde file resources
Title: Message Title Christopher Wood created an issue Puppet / PUP-6914 ruby expand_path in file type breaks leading-tilde file resources Issue Type: Bug Affects Versions: PUP 4.8.0 Assignee: Unassigned Components: Types and Providers Created: 2016/11/10 2:44 PM Environment: $ uname -a Linux cwl 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux $ cat /etc/debian_version 8.6 $ puppet --version 4.8.0 $ /opt/puppetlabs/puppet/bin/ruby --version ruby 2.1.9p490 (2016-03-30 revision 54437) [x86_64-linux] Priority: Minor Reporter: Christopher Wood This to reproduce: $ cat x.pp
Jira (PUP-6895) Puppet package provider for Python's pip fails when Perl's pip is installed
Title: Message Title Thomas Kishel commented on PUP-6895 Re: Puppet package provider for Python's pip fails when Perl's pip is installed Ethan Brown Thanks Ethan. It's tricky: the puppet package provider has a responsibility to verify the command it uses, and the user has a responsibility to not have two different commands with the same name in the path. Some research favors Python: https://fedorahosted.org/fpc/ticket/280 My suggested solution only addresses the issue on Windows where Python pip has an .exe extension. Perl pip is installed as both an executable named pip and pip.bat. A better solution would be to loop through the found pip commands and test each to see if it is Python's pip. I'll research that and see if I can create a reasonable test before pursuing with core. It sounds like more inspection than I'd expect from the provider and may introduce its own fragility, but this is package provider code and both commands are provide packages, so we should not claim ignorance. E Salberg I agree and have renamed this ticket. My notes about pip_cmd and execpipe are general improvements, and wouldn't help with this issue. 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-6913) Spec tests fail when run on a windows host whose name exceeds 15 characters
Title: Message Title
Josh Cooper created an issue
Puppet / PUP-6913
Spec tests fail when run on a windows host whose name exceeds 15 characters
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/11/10 1:57 PM
Priority:
Normal
Reporter:
Josh Cooper
Our windows jenkins agents in CI.Next have hostnames (not fqdn) longer than 15 characters. As a result Socket.gethostname and Win32 GetComputerName return different results (the former is a truncated version of the latter), e.g. jenkins-slave-w vs jenkins-slave-win2012r2-...
Two tests in spec/integration/util/windows/principal_spec.rb fail because they are using Socket.gethostname when they instead need to use GetComputerName in subsequent calls to LookupAccountNameW.
07:11:29 1) Puppet::Util::Windows::SID::Principal.lookup_account_name should create an instance from a local account prefixed with hostname
07:11:29 Failure/Error: Puppet::Util::Windows::SID.sid_to_name(computer_sid.sid + '-500').split('\\').last :
07:11:29
Jira (PDOC-136) Strings doesn't recognize `>> Type` syntax for return type of puppet language functions
Title: Message Title
William Hopper created an issue
Puppet Strings / PDOC-136
Strings doesn't recognize `>> Type` syntax for return type of puppet language functions
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/11/10 1:53 PM
Priority:
Normal
Reporter:
William Hopper
function example(String $name) >> String {
"hello"
}
In this example, >> String says that this function returns a string. Currently, Strings ignores this which requires the user to document the return type with the @return tag.
Jira (PUP-6895) Puppet package provider for Python's pip fails when Perl's pip is installed
Title: Message Title Thomas Kishel updated an issue Puppet / PUP-6895 Puppet package provider for Python's pip fails when Perl's pip is installed Change By: Thomas Kishel Summary: pip Puppet package provider does not work with perl for Python's pip ( fails when Perl's pip .bat) is installed on windows 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 (PDOC-135) Strings doesn't recognize `return_type` in 4.x function dispatch
Title: Message Title
William Hopper updated an issue
Puppet Strings / PDOC-135
Strings doesn't recognize `return_type` in 4.x function dispatch
Change By:
William Hopper
Acceptance Criteria:
Given the following function, strings should correctly identify that the 'subtract_ints` overload returns type 'Numeric'.{code}# Subtracts two things.Puppet::Functions.create_function(:subtract) do # @param x The first integer. # @param y The second integer. # @return Returns x - y. # @example Subtracting two integers. # subtract(5, 1) => 4 dispatch :subtract_ints doparam 'Integer', :xparam 'Integer', :yreturn_type 'Numeric' end def subtract_ints(x, y)x - y endend{code}
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 (PDOC-135) Strings doesn't recognize `return_type` in 4.x function dispatch
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-135 Strings doesn't recognize `return_type` in 4.x function dispatch Issue Type: Bug Assignee: Unassigned Created: 2016/11/10 1:45 PM Priority: Normal Reporter: William Hopper Puppet 4.x API functions can include a return_type 'blah' in each of their dispatches. Strings should use this to document the return type for the overload rather than requiring the type to be documented in the @return tag. Example: # Subtracts two things. Puppet::Functions.create_function(:subtract) do # @param x The first integer. # @param y The second integer.
Jira (PUP-6834) lookup explain shows found data incorrectly
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-6834 lookup explain shows found data incorrectly Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-6834) lookup explain shows found data incorrectly
Title: Message Title Henrik Lindberg commented on PUP-6834 Re: lookup explain shows found data incorrectly merged to master at: dc5fac9 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-6899) puppet lookup ignores --hiera_config option
Title: Message Title Henrik Lindberg commented on PUP-6899 Re: puppet lookup ignores --hiera_config option Ok to kidnap this ticket to make classic hiera barf if it gets a v4 config? (It will be moved to the Hiera project). 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-3179) (maint) pin addressable gem to avoid ruby 2 dependency
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3179 (maint) pin addressable gem to avoid ruby 2 dependency Issue Type: Bug Assignee: Unassigned Created: 2016/11/10 12:55 PM Priority: Normal Reporter: gepetto-bot 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
Jira (PDOC-134) Follow up Strings blog post: delivering docs
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-134 Follow up Strings blog post: delivering docs Issue Type: Task Assignee: Unassigned Created: 2016/11/10 12:54 PM Priority: Normal Reporter: William Hopper Should cover: Delivering Documentation to Users Hosting documentation as github pages Running the Strings web server Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6883) Unlisted module dependency in metadata.json results in weird errors
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6883 Unlisted module dependency in metadata.json results in weird errors Change By: Henrik Lindberg Labels: metadata 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-6883) Unlisted module dependency in metadata.json results in weird errors
Title: Message Title Rune Juhl Jacobsen commented on PUP-6883 Re: Unlisted module dependency in metadata.json results in weird errors I've attached a log from the Puppet server. You were correct however; the old implementation had a bug in which Scope::lookupvar was called with an invalid argument. Thank you for the hint – I'll close the issue again. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3178) Create/Deploy EC2 "zombie killer"
Title: Message Title Daniel Parks commented on PDB-3178 Re: Create/Deploy EC2 "zombie killer" Ops is actually writing a general zombie killer in the near future, see OPS-11419. Sorry you weren't in the loop on that. 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-6883) Unlisted module dependency in metadata.json results in weird errors
Title: Message Title Rune Juhl Jacobsen updated an issue Puppet / PUP-6883 Unlisted module dependency in metadata.json results in weird errors Change By: Rune Juhl Jacobsen Attachment: puppet.log Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6912) acceptance: test maintenance for failures against server
Title: Message Title Eric Thompson created an issue Puppet / PUP-6912 acceptance: test maintenance for failures against server Issue Type: Task Assignee: Eric Thompson Created: 2016/11/10 11:24 AM Labels: maintenance Priority: Normal Reporter: Eric Thompson 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
Jira (PUP-6895) pip provider does not work with perl pip (pip.bat) installed on windows
Title: Message Title E Salberg commented on PUP-6895 Re: pip provider does not work with perl pip (pip.bat) installed on windows As someone who also reported this... The issue isn't that we need Python support on Windows (which we don't currently). It's that the pip provider overreaches on Windows and assumes that the pip associated with perl is the same as that associated with python. This completely breaks "puppet resource package" - it errors out because it tries to run "pip freeze", which obviously doesn't work. So I would actually say on windows, the description (for us) would be: "puppet resource package" does not work with perl pip (pip.bat) installed on windows I'm working with Puppet support on workarounds (although I'm assuming removing perl from the system path is out of the question), and I'll look at the pull request option - I can easily put in something for the prepend (and test it), but I'm not sure about those latest methods that are mentioned - would people over there be able to help with that? 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-6895) pip provider does not work with perl pip (pip.bat) installed on windows
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6895 pip provider does not work with perl pip (pip.bat) installed on windows Change By: Ethan Brown Labels: maintenance windows 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-6895) pip provider does not work with perl pip (pip.bat) installed on windows
Title: Message Title Ethan Brown commented on PUP-6895 Re: pip provider does not work with perl pip (pip.bat) installed on windows Thomas Kishel thanks for the report. We've moved this to a maintenance ticket, which means that the core Puppet Agent & Platform team is unlikely to work on this directly, given our other commitments. However, there is a maintenance team affiliated with core Puppet that might be able to work on this as time allows. Also, we're evaluating if we want to move Python package support out of core Puppet into an additional module as it is slightly out of place with operating system package management.. That said, if you feel strongly about landing a fix, I'd suggest you open up a pull request at https://github.com/puppetlabs/puppet/pulls - this will help to jump-start any work that the Puppet maintainers would undertake resolving this problem. On another note, there is a pretty well-maintained Python module at https://forge.puppet.com/stankevich/python that lacks Windows support. It might be a more worthwhile effort in the long-run to improve Windows support there is that's something you're interested in. Thanks again for the report! 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-6895) pip provider does not work with perl pip (pip.bat) installed on windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6895 pip provider does not work with perl pip (pip.bat) installed on windows Change By: Geoff Nichols Sprint: AP Triage 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-6904) Evaluate FileType and ParsedFile classes for UTF-8 compatibility
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6904 Evaluate FileType and ParsedFile classes for UTF-8 compatibility Change By: Geoff Nichols 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-6860) puppet on solaris 11 should support exists? for services
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6860 puppet on solaris 11 should support exists? for services Change By: Geoff Nichols 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-6860) puppet on solaris 11 should support exists? for services
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6860 puppet on solaris 11 should support exists? for services Change By: Geoff Nichols 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-6895) pip provider does not work with perl pip (pip.bat) installed on windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6895 pip provider does not work with perl pip (pip.bat) installed on windows Change By: Geoff Nichols 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 (PUP-6895) pip provider does not work with perl pip (pip.bat) installed on windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6895 pip provider does not work with perl pip (pip.bat) installed on windows Change By: Geoff Nichols 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-6911) variables_refreshed_each_compilation test can fail uptime comparisons
Title: Message Title Jeremy Barlow assigned an issue to Jeremy Barlow Puppet / PUP-6911 variables_refreshed_each_compilation test can fail uptime comparisons Change By: Jeremy Barlow Assignee: Jeremy Barlow 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-6911) variables_refreshed_each_compilation test can fail uptime comparisons
Title: Message Title Jeremy Barlow created an issue Puppet / PUP-6911 variables_refreshed_each_compilation test can fail uptime comparisons Issue Type: Bug Assignee: Jeremy Barlow Components: QA Created: 2016/11/10 9:35 AM Priority: Normal Reporter: Jeremy Barlow The variables_refreshed_each_compilation acceptance test can fail when the uptime seconds that the test is comparing happen are for strings where the earlier uptime is lexicographically later than the later uptime. For example, this test failed in the puppetserver pipeline here with the following console output: jubzk4qxrpdh8r2.delivery.puppetlabs.net (ubuntu1604-32-2) 03:09:15$ puppet agent -t --server ks6npbjxt60nblz.delivery.puppetlabs.net --environment variables_refreshed_each_compilation_nmjw1l2b
Jira (PUP-6910) I'd like to create a scheduled_task that runs at startup and repeats every 15 minutes after
Title: Message Title Nick Walker created an issue Puppet / PUP-6910 I'd like to create a scheduled_task that runs at startup and repeats every 15 minutes after Issue Type: Improvement Assignee: Unassigned Created: 2016/11/10 9:14 AM Priority: Normal Reporter: Nick Walker The Problem I want to run a task at startup and every 15 minutes after. This is not supported by the windows 2003 version of scheduled tasks that get created from puppet. The solution Update the scheduled task resource, potentially allowing the user to specify the version of the task to create. Add Comment This message was
Jira (FACT-1532) ipv6 facts in RHEL5 systems
Title: Message Title Michael Smith updated an issue Facter / FACT-1532 ipv6 facts in RHEL5 systems Change By: Michael Smith 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-6686) Timespan sometimes parses fractions incorrectly.
Title: Message Title claud commented on PUP-6686 Re: Timespan sometimes parses fractions incorrectly. http://gardemeublespascher.fr/ http://demenageurs-sur-paris.fr/ http://location-mont-meuble-paris.fr/ http://devistransportpiano.fr/ http://devis-transport-piano.fr/ http://demenageur-paris-devis.fr/ http://www.gardemeublespascher.com/ http://transportpianoparis.devistransportpiano.fr/ http://transport-piano-paris.devis-transport-piano.fr/ http://gardemeublesparis.fr/ http://location-montemeuble-paris.com/ http://monte-meuble-pas-cher.com/ http://expresschauffagisteparis.fr/ 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-6882) Incorrect handling of escape sequence precedence
Title: Message Title Henrik Lindberg commented on PUP-6882 Re: Incorrect handling of escape sequence precedence Thanks for the report - this is indeed wrong - it should be possible to escape the backslash before the u. 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-6882) Incorrect handling of escape sequence precedence
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6882 Incorrect handling of escape sequence precedence Change By: Henrik Lindberg Acceptance Criteria: It should be possible to escape a unicode character specification in a string using both short and long form. 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-6882) Incorrect handling of escape sequence precedence
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6882
Incorrect handling of escape sequence precedence
Change By:
Henrik Lindberg
Story Points:
1
Release Notes Summary:
It was not possible to escape a unicode character using{code}"\\u"{code}
Team:
Puppet Developer Support
Sprint:
PDS 2016-11-30
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
Jira (PUP-6538) deprecate hiera_xxx functions (in favour of lookup)
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-6538 deprecate hiera_xxx functions (in favour of lookup) 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-6882) Incorrect handling of escape sequence precedence
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6882 Incorrect handling of escape sequence precedence Change By: Henrik Lindberg Fix Version/s: PUP 4.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-6882) Incorrect handling of escape sequence precedence
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6882 Incorrect handling of escape sequence precedence Change By: Henrik Lindberg 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 (PUP-6899) puppet lookup ignores --hiera_config option
Title: Message Title Henrik Lindberg commented on PUP-6899 Re: puppet lookup ignores --hiera_config option The setting --hiera_config is for global "classic" hiera only. It has no effect what so ever on lookup's configuration of the environment data or any module's data; they are always in a fixed position within the env or within the module. To experiment simply use a branch of the env, or use a copy of the env with a different name. What is somewhat surprising here is that hiera (global/classic) does not report the v4 format as being wrong. Maybe it simply does not understand it and thinks it is empty or something. Other than that, I think it works exactly like it is supposed to work. Since it is likely that people will try what was tried here, we should probably add a check so that hiera (classic) barfs if it finds a version 4 config file. 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-3168) convergence test failiures 11/03/16
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3168 convergence test failiures 11/03/16 Change By: Ryan Senior Sprint: Hopper 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-3178) Create/Deploy EC2 "zombie killer"
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3178 Create/Deploy EC2 "zombie killer" Change By: Ryan Senior Sprint: Hopper 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-3175) Check on pdb upgrade shovel test failure (2016-11-07)
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3175 Check on pdb upgrade shovel test failure (2016-11-07) Change By: Ryan Senior Sprint: Hopper SE 2016-11-16 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-6856) data-in-modules: missing facts during building of the hierarchy fails the lookup completely and silently
Title: Message Title Henrik Lindberg commented on PUP-6856 Re: data-in-modules: missing facts during building of the hierarchy fails the lookup completely and silently merged to master at: b0209f5 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-6856) data-in-modules: missing facts during building of the hierarchy fails the lookup completely and silently
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-6856 data-in-modules: missing facts during building of the hierarchy fails the lookup completely and silently Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-6875) [Spike] Investigate usage of ReGex \w character class in Puppet
Title: Message Title Henrik Lindberg commented on PUP-6875 Re: [Spike] Investigate usage of ReGex \w character class in Puppet Please note that simply changing \w to :word: is not doable for elements of the puppet language since names are case independent and for many characters in the :word: class there is no way to do up/down case without also having a Locale. We cannot make the language be locale dependant. To work well we would need to make the language either be case dependant, or use Ruby's wonky "ascii is up/down-cased, but not others"-mode. 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-6907) Don't provide $name (and perhaps others) in EPP scope
Title: Message Title Henrik Lindberg commented on PUP-6907 Re: Don't provide $name (and perhaps others) in EPP scope The main problem here is that the "node scope" behaves as if "node" is a resource and as such it gets meta parameters. Unsure what would break if we change that (which is what I would really like to change). EPP must get the top scope, and when there is a node, that happens to be node scope (or it would not see the correct set of global variables). We want fewer special cases rather that adding new ones. 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-3175) Check on pdb upgrade shovel test failure (2016-11-07)
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3175 Check on pdb upgrade shovel test failure (2016-11-07) Change By: Ryan Senior Team: Systems Engineering 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-3175) Check on pdb upgrade shovel test failure (2016-11-07)
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3175 Check on pdb upgrade shovel test failure (2016-11-07) Change By: Ryan Senior Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3160) Help SE and Hafjell teams design/protype unmanaged resources
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-3160 Help SE and Hafjell teams design/protype unmanaged resources Change By: Ryan Senior Assignee: Ryan Senior 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-3178) Create/Deploy EC2 "zombie killer"
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-3178 Create/Deploy EC2 "zombie killer" Issue Type: Task Assignee: Unassigned Created: 2016/11/10 4:09 AM Labels: maintenance Priority: Normal Reporter: Ryan Senior Ops has disabled the EC2 "zombie killer" script. This has caused us to orphan EC2 instances and thus increase our EC2 bill. OPS-10831 has more discussion on this, but it's likely to be a long time before a new zombie killer script/process is decided and the Ops team doesn't want to re-enable the existing script. We need to write our own version of this to keep costs down. I think this will involve: Getting new credentials for the new zombie killer to run under Creating a script/program to query for all EC2 instances, tagged as PuppetDB that are older than N (maybe 3 hours?) and terminate them Deploy the script somewhere (slice?) to check this periodically
Jira (PUP-1460) Puppet hangs trying to replace a FIFO
Title: Message Title Stefan Pijnappels commented on PUP-1460 Re: Puppet hangs trying to replace a FIFO The puppet module build command also hangs indefinitely if a socket or FIFO is included in the /files directory of the module being built. This appears to be the result of the command trying to copy an infinitely large file into the package. A better solution would be for the command to either skip or error out if a socket or FIFO is encountered. 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-1532) ipv6 facts in RHEL5 systems
Title: Message Title Alexandre Barth created an issue Facter / FACT-1532 ipv6 facts in RHEL5 systems Issue Type: Bug Affects Versions: FACT 3.5.0 Assignee: Unassigned Created: 2016/11/10 2:40 AM Environment: CentOS 5/RedHat 5 Priority: Normal Reporter: Alexandre Barth I use CentOS/RedHat 5/6/7 systems whith ipv6 disabled. In 5 systems, facter generate ipv6 facts with ipv4 informations : ipaddress : 192.168.1.1 ipaddress6 : 192.168.1.1 ipaddress_eth0 : 192.168.1.1 ipaddress6_eth0 : 192.168.1.1 In 6/7 systems, these facts related to ipv6 are not present. Add Comment
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Angel L. Mateo commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources I have checked that replacing create_resources with a loop creating the resources fixes the problem. I have also tried with puppetserver 2.7.0 (with create_resources) and the problems seems to be fixed too. 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.
