Jira (PUP-6006) A Puppet::ParseErrorWithIssue observed during rspec tests is not clear of the cause.
Title: Message Title Henrik Lindberg commented on PUP-6006 Re: A Puppet::ParseErrorWithIssue observed during rspec tests is not clear of the cause. Not sure where it logs. There should be helpers to be able to make assertions about what is logged. All exceptions are also logged. When there are multiple errors we log each one, and raise the "giving up" error that you have seen. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5907) Define the PCore Serialization API and Features
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5907 Define the PCore Serialization API and Features Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5907) Define the PCore Serialization API and Features
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5907 Define the PCore Serialization API and Features Change By: Henrik Lindberg Comment: x Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5907) Define the PCore Serialization API and Features
Title: Message Title Henrik Lindberg commented on PUP-5907 Re: Define the PCore Serialization API and Features The specification of XPP is now available in a google doc (markdown text). The intention is to make a PR against the specification repo. Before we do so, I wanted a first round of review in google doc as it is easier to comment and suggest changes that way. If making suggestions please do so in markdown format. Document for (pre) merge-review here: https://docs.google.com/document/d/1T_GgYsyfRACuayM2BimGa0Ix-MxUjAUyzZ8x-UQid_w/edit Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5768) Fix problematic usage of ENV for Windows
Title: Message Title Glenn Sarti assigned an issue to Ethan Brown Puppet / PUP-5768 Fix problematic usage of ENV for Windows Change By: Glenn Sarti Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6007) Irrelevant message when a module upgrade fails for reasons of unsatisfied dependencies versions
Title: Message Title
Francois Lafont updated an issue
Puppet / PUP-6007
Irrelevant message when a module upgrade fails for reasons of unsatisfied dependencies versions
Change By:
Francois Lafont
I have several modules installed but only one depends on the module {{arioch-keepalived}} (it's just an example, this particulary particular module has not importance doesn't matter here):{code:sh}~# cd /etc/puppetlabs/code/environments/production/~# grep -R --color arioch-keepalived modules/modules/keepalived/metadata.json: "name": "arioch-keepalived",modules/keepalived_vip/metadata.json:{"name":"arioch-keepalived","version_requirement":"1.2.0"}{code}As you can see, just one module depends on the module {{arioch-keepalived}}: it's the module {{keepalived_vip}} and it requires the module {{arioch-keepalived}} version 1.2.0 *exactly*.Now, I try to upgrade the module {{arioch-keepalived}}:{code:sh}~# puppet module upgrade arioch-keepalived --ignore-changesNotice: Preparing to upgrade 'arioch-keepalived' ...Notice: Found 'arioch-keepalived' (v1.2.0) in /etc/puppetlabs/code/environments/production/modules ...Notice: Downloading from https://forgeapi.puppetlabs.com ...Error: Could not upgrade module 'arioch-keepalived' (v1.2.0 -> latest) There are 3 newer versionsNo combination of dependency upgrades would satisfy all dependenciesDependencies will not be automatically upgraded across major versionsUpgrading one or more of these modules may permit the upgrade to succeed:- puppetlabs-stdlib- puppetlabs-concatUse `puppet module upgrade --force` to upgrade only this module{code}It's normal that the upgrade fails because the module {{keepalived_vip}} requires the module {{arioch-keepalived}} version 1.2.0 *exactly* (good!) but the message is completely irrelevant because it talks about the modules {{puppetlabs-stdlib}} and {{puppetlabs-concat}} which don't depend on {{arioch-keepalived}} at all. The real reason which explains why the upgrade is not possible is not given.
Add Comment
Jira (PUP-6008) Update all Windows modules (win and xplat) to remove initial gem install bundler
Title: Message Title Glenn Sarti created an issue Puppet / PUP-6008 Update all Windows modules (win and xplat) to remove initial gem install bundler Issue Type: Improvement Assignee: Unassigned Created: 2016/03/03 4:37 PM Priority: Normal Reporter: Glenn Sarti As part of PUP-5768 is found that the default appveyor yaml configuration was running gem install bundler which took a LOOONG time to complete. It was found that this step was not necessary as bundler is already at the latest version. All of the existing modules (windows and cross platform) should have the appveyor updated to remove this command. It can be removed from both stable and master branches. Add Comment This message
Jira (PUP-6007) Irrelevant message when a module upgrade fails for reasons of unsatisfied dependencies versions
Title: Message Title
Francois Lafont updated an issue
Puppet / PUP-6007
Irrelevant message when a module upgrade fails for reasons of unsatisfied dependencies versions
Change By:
Francois Lafont
I have several modules installed but only one depends on the module {{arioch-keepalived}} (it's just an example, this particulary module has not importance here):{code:sh}~# cd /etc/puppetlabs/code/environments/production/~# grep -R --color arioch-keepalived modules/modules/keepalived/metadata.json: "name": "arioch-keepalived",modules/keepalived_vip/metadata.json:{"name":"arioch-keepalived","version_requirement":"1.2.0"}{code}As you can see, just one module depends on the module {{arioch-keepalived}}: it's the module {{keepalived_vip}} and it requires the module {{arioch-keepalived}} version 1.2.0 *exactly*.Now, I try to upgrade the module {{arioch-keepalived}}:{code:sh}~# puppet module upgrade arioch-keepalived --ignore-changesNotice: Preparing to upgrade 'arioch-keepalived' ...Notice: Found 'arioch-keepalived' (v1.2.0) in /etc/puppetlabs/code/environments/production/modules ...Notice: Downloading from https://forgeapi.puppetlabs.com ...Error: Could not upgrade module 'arioch-keepalived' (v1.2.0 -> latest) There are 3 newer versionsNo combination of dependency upgrades would satisfy all dependenciesDependencies will not be automatically upgraded across major versionsUpgrading one or more of these modules may permit the upgrade to succeed:- puppetlabs-stdlib- puppetlabs-concatUse `puppet module upgrade --force` to upgrade only this module{code}It's normal that the upgrade fails because the module {{keepalived_vip}} requires the module {{arioch-keepalived}} version 1.2.0 *exactly* (good!) but the message is completely irrelevant because it talks about the modules {{puppetlabs-stdlib}} and {{puppetlabs-concat}} which don't depend on {{arioch-keepalived}} at all. The real reason which explains why the upgrade is not possible is not given.
Add Comment
This message
Jira (PUP-6007) Irrelevant message when a module upgrade fails for reasons of unsatisfied dependencies versions
Title: Message Title
Francois Lafont updated an issue
Puppet / PUP-6007
Irrelevant message when a module upgrade fails for reasons of unsatisfied dependencies versions
Change By:
Francois Lafont
I have several modules installed but only one depends on the module {{arioch-keepalived}} (it's just an example, this particulary module has importance here):{code:sh}~# cd /etc/puppetlabs/code/environments/production/~# grep -R --color arioch-keepalived modules/modules/keepalived/metadata.json: "name": "arioch-keepalived",modules/keepalived_vip/metadata.json:{"name":"arioch-keepalived","version_requirement":"1.2.0"}{code}As you can see, just one module depends on the module {{arioch-keepalived}}: it's the module {{ flaf- keepalived_vip}} and it requires the module {{arioch-keepalived}} version 1.2.0 *exactly*.Now, I try to upgrade the module {{arioch-keepalived}}:{code:sh}~# puppet module upgrade arioch-keepalived --ignore-changesNotice: Preparing to upgrade 'arioch-keepalived' ...Notice: Found 'arioch-keepalived' (v1.2.0) in /etc/puppetlabs/code/environments/production/modules ...Notice: Downloading from https://forgeapi.puppetlabs.com ...Error: Could not upgrade module 'arioch-keepalived' (v1.2.0 -> latest) There are 3 newer versionsNo combination of dependency upgrades would satisfy all dependenciesDependencies will not be automatically upgraded across major versionsUpgrading one or more of these modules may permit the upgrade to succeed:- puppetlabs-stdlib- puppetlabs-concatUse `puppet module upgrade --force` to upgrade only this module{code}It's normal that the upgrade fails because the module {{ flaf- keepalived_vip}} requires the module {{arioch-keepalived}} version 1.2.0 *exactly* (good!) but the message is completely irrelevant because it talks about the modules {{puppetlabs-stdlib}} and {{puppetlabs-concat}} which don't depend on {{arioch-keepalived}} at all. The real reason which explains why the upgrade is not possible is not given.
Add Comment
This
Jira (PUP-6007) Irrelevant message when a module upgrade fails for reasons of unsatisfied dependencies versions
Title: Message Title Francois Lafont commented on PUP-6007 Re: Irrelevant message when a module upgrade fails for reasons of unsatisfied dependencies versions I add just one remark. If I change manually the version of the module arioch-keepalived (in its metadata.json) and put version 1.2.4 to just break the dependencies, then the warning message with puppet module list is completely clear: ~# puppet module list Warning: Module 'arioch-keepalived' (v1.2.4) fails to meet some dependencies: 'olecam-keepalived_vip' (v0.1.3) requires 'arioch-keepalived' (v1.2.0) /etc/puppetlabs/code/environments/production/modules ├── arioch-keepalived (v1.2.4) invalid ├── flaf-basic_ntp (v0.1.0) ├── flaf-basic_packages (v0.1.9) [...]
Jira (PUP-6006) A Puppet::ParseErrorWithIssue observed during rspec tests is not clear of the cause.
Title: Message Title Rob Nelson commented on PUP-6006 Re: A Puppet::ParseErrorWithIssue observed during rspec tests is not clear of the cause. How can I see the logged errors from rspec-puppet? The only error I see right now is what's above; is there a cool flag I can use to see that? If so it would help with more than this issue! Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6007) Irrelevant message when a module upgrade fails for reasons of unsatisfied dependencies versions
Title: Message Title Francois Lafont created an issue Puppet / PUP-6007 Irrelevant message when a module upgrade fails for reasons of unsatisfied dependencies versions Issue Type: Improvement Affects Versions: PUP 4.3.2 Assignee: Unassigned Components: AIO Created: 2016/03/03 4:13 PM Environment: Ubuntu Trusty package puppet-agent 1.3.5-1trusty package puppetserver 2.2.1-1puppetlabs1 Priority: Normal Reporter: Francois Lafont I have several modules installed but only one depends on the module arioch-keepalived (it's just an example, this particulary module has importance here): ~# cd /etc/puppetlabs/code/environments/production/
Jira (PUP-5867) Static catalog acceptance: Why cached catalog is applied, Story PUP-5706
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5867 Static catalog acceptance: Why cached catalog is applied, Story PUP-5706 Change By: Sean Griffin QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5832) 4.x Sensitive Type - Handle Sensitive data in manifests, logs, catalog, reports and resource types.
Title: Message Title Henrik Lindberg commented on PUP-5832 Re: 4.x Sensitive Type - Handle Sensitive data in manifests, logs, catalog, reports and resource types. Comments received suggests that the Sensitive type should be called Encrypted as that more clearly signals what it is. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5832) 4.x Sensitive Type - Handle Sensitive data in manifests, logs, catalog, reports and resource types.
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-5832 4.x Sensitive Type - Handle Sensitive data in manifests, logs, catalog, reports and resource types. Change By: Adam Bottchen CS Priority: Critical CS Severity: 4 CS Business Value: 5 CS Frequency: 4 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6006) A Puppet::ParseErrorWithIssue observed during rspec tests is not clear of the cause.
Title: Message Title Henrik Lindberg commented on PUP-6006 Re: A Puppet::ParseErrorWithIssue observed during rspec tests is not clear of the cause. Not sure that gives a better message though or if it then announces that it gave up after 1 error. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6006) A Puppet::ParseErrorWithIssue observed during rspec tests is not clear of the cause.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6006 A Puppet::ParseErrorWithIssue observed during rspec tests is not clear of the cause. The errors are logged, since there is more and it cannot raise more than one exception. The cap is at 10 errors found in validation (but it can be raised). You can also cap it at 1 which means it gives up immediately. You can control that from your rspec test with Puppet[:max_errors] = 1 Change By: Henrik Lindberg Story Points: 1 Sprint: Language Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-6006) A Puppet::ParseErrorWithIssue observed during rspec tests is not clear of the cause.
Title: Message Title
Rob Nelson created an issue
Puppet / PUP-6006
A Puppet::ParseErrorWithIssue observed during rspec tests is not clear of the cause.
Issue Type:
Bug
Affects Versions:
PUP 4.3.2
Assignee:
Unassigned
Created:
2016/03/03 3:45 PM
Priority:
Normal
Reporter:
Rob Nelson
During rspec tests while migrating from Puppet 3 to Puppet 4, I encountered an error that was non-obvious to me.
24) wiki Set common params should contain Firewall[105 searchd]
Failure/Error: it { is_expected.to contain_firewall('105 searchd') }
Puppet::ParseErrorWithIssue:
Jira (PUP-5872) Static catalog acceptance: Correlate all agent run reports to a catalog, Story PUP-5533
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-5872 Static catalog acceptance: Correlate all agent run reports to a catalog, Story PUP-5533 Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5867) Static catalog acceptance: Why cached catalog is applied, Story PUP-5706
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-5867 Static catalog acceptance: Why cached catalog is applied, Story PUP-5706 Change By: Michael Smith Status: Ready for CI Test Assignee: Sean Griffin qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1345) Solaris automount entries in mountpoint result in huge fact lists
Title: Message Title Adam Bottchen updated an issue Facter / FACT-1345 Solaris automount entries in mountpoint result in huge fact lists Change By: Adam Bottchen CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1244) xenu vs. xen0 difference not recognized by Puppet
Title: Message Title Adam Bottchen updated an issue Facter / FACT-1244 xenu vs. xen0 difference not recognized by Puppet Change By: Adam Bottchen Labels: cspapercuts puppethack Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5964) Improve how type mismatches are asserted and reported
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5964 Improve how type mismatches are asserted and reported Change By: Henrik Lindberg Release Notes Summary: The error message generated from the function asssert_type is now of the same high quality as the message produced for automatically type checked parameters. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6005) Specify the ordering used for directory based main manifest
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6005 Specify the ordering used for directory based main manifest Issue Type: Improvement Assignee: Unassigned Created: 2016/03/03 2:32 PM Priority: Normal Reporter: Henrik Lindberg The puppet specifications currently does not define the ordering of a main manifest setting when it refers to a directory. It is depth first alphanumerically sorted, but there is no mention of this feature in the language specification repository, and it does not define the order in terms of Locale. Since it is unspecified, there are no rules specified regarding file names. The Ruby implementation performs a glob, and then a sort, and that is what is used. Add Comment
Jira (NPUP-24) Environment manifest setting, when a directory, is not recursing on subdirectories
Title: Message Title Henrik Lindberg commented on NPUP-24 Re: Environment manifest setting, when a directory, is not recursing on subdirectories Merged to master at: ccce3a8 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6001) Incomplete process table due to COLUMNS variable
Title: Message Title Robert Scheer commented on PUP-6001 Re: Incomplete process table due to COLUMNS variable Thanks Kylo Ginsberg. About that method of environment sanitization: it looks like it is deleting blacklisted variables, currently HOME, USER and LOGNAME. As it is impossible to create a blacklist that is complete, shouldn't environment sanitation be deleting all variables except those on a whitelist? I'm guessing the only ones that might be relevant, are PATH, LANG and LC_*. When looking at xargs -0 -n1 < /proc/`cat /var/run/puppet/agent.pid`/environ | sort on some freshly booted systems, I don't see anything else that seems useful. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5964) Improve how type mismatches are asserted and reported
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5964 Improve how type mismatches are asserted and reported Change By: Henrik Lindberg Fix Version/s: PUP 4.4.1 Fix Version/s: PUP 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5964) Improve how type mismatches are asserted and reported
Title: Message Title Henrik Lindberg commented on PUP-5964 Re: Improve how type mismatches are asserted and reported merged to stable f1a03019d906e7cee8a97c0a57cf25121603c867 and on to master. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5960) Document static catalog responses for catalog and file_metadata
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5960 Document static catalog responses for catalog and file_metadata Change By: Josh Cooper Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5960) Document static catalog responses for catalog and file_metadata
Title: Message Title Josh Cooper commented on PUP-5960 Re: Document static catalog responses for catalog and file_metadata Since this is a non-code change, moving to ready for review. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5960) Document static catalog responses for catalog and file_metadata
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-5960
Document static catalog responses for catalog and file_metadata
Change By:
Josh Cooper
Update api/docs for catalog (and possibly file_metadata) to document the new responses that can occur with static catalogs. Main additions are the {{metadata}} and {{recursive_metadata}} properties of the catalog, and within those the file_metadata objects can now include {{source} } and {{content_uri}} properties.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-2492) update data service per ops deployment requirements
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-2492 update data service per ops deployment requirements Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6004) should_modify_gid acceptance tests should generate an unused unique id
Title: Message Title Josh Cooper created an issue Puppet / PUP-6004 should_modify_gid acceptance tests should generate an unused unique id Issue Type: Bug Assignee: Unassigned Created: 2016/03/03 1:19 PM Priority: Normal Reporter: Josh Cooper puppet acceptance failed because the should_modify_gid acceptance test tried to create a group with a random gid, but it picked gid 33, which is already in use: 12:12:43 Begin tests/resource/group/should_modify_gid.rb 12:12:43 12:12:43 should modify gid of existing group 12:12:43
Jira (PUP-6001) Incomplete process table due to COLUMNS variable
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6001 Incomplete process table due to COLUMNS variable Change By: Kylo Ginsberg Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6001) Incomplete process table due to COLUMNS variable
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6001 Incomplete process table due to COLUMNS variable Change By: Kylo Ginsberg Sprint: Client Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6001) Incomplete process table due to COLUMNS variable
Title: Message Title Kylo Ginsberg commented on PUP-6001 Re: Incomplete process table due to COLUMNS variable Good news, bad news: The good news is that puppet has a nice method that does environment sanitization, e.g. see https://github.com/puppetlabs/puppet/blob/280674ff8e2cb4ee62ad24fec67f40e2e9110fa3/lib/puppet/util/execution.rb#L289-L294. The bad news is that the execution of ps doesn't use the common method that implements that environment sanitization: https://github.com/puppetlabs/puppet/blob/280674ff8e2cb4ee62ad24fec67f40e2e9110fa3/lib/puppet/provider/service/base.rb#L36 So the fix for this should be straightforward. Thanks for the nice writeup Robert Scheer! Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5960) Document static catalog responses for catalog and file_metadata
Title: Message Title Michael Smith updated an issue Puppet / PUP-5960 Document static catalog responses for catalog and file_metadata Change By: Michael Smith Fix Version/s: PUP 4.4.1 Fix Version/s: PUP 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5994) Puppet module install fails when modules have long path names
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5994 Puppet module install fails when modules have long path names Change By: Josh Cooper Fix Version/s: PUP 4.3.3 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5994) Puppet module install fails when modules have long path names
Title: Message Title Josh Cooper commented on PUP-5994 Re: Puppet module install fails when modules have long path names Removed 4.3.3 fix version since we won't be doing that release. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5996) acceptance: language/exported_resources.rb test fails when agent on master is run
Title: Message Title William Hopper updated an issue Puppet / PUP-5996 acceptance: language/exported_resources.rb test fails when agent on master is run Change By: William Hopper Scope Change Category: Found Scope Change Reason: Discovered this test was failing in the Puppetserver pipeline - brought in to unblock Story Points: 1 Sprint: Client 2016-03-09 (Burn CF) Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this
Jira (PUP-5959) Add test that static catalog metadata defaults match File type
Title: Message Title Josh Cooper commented on PUP-5959 Re: Add test that static catalog metadata defaults match File type Since this is a new spec test, moving to ready for review. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5996) acceptance: language/exported_resources.rb test fails when agent on master is run
Title: Message Title William Hopper commented on PUP-5996 Re: acceptance: language/exported_resources.rb test fails when agent on master is run Ah shoot, sorry Jeremy Barlow, I didn't realize there was a ticket for this or I would have put it in the commit title. This has already passed in our pipeline, so once it goes through in the puppetserver world we can call it resolved. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5960) Document static catalog responses for catalog and file_metadata
Title: Message Title Michael Smith commented on PUP-5960 Re: Document static catalog responses for catalog and file_metadata Only going to update the docs for catalog (which will return some file_metadata). There's no way to query the file_metadata terminus that's unique for static catalogs. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5960) Document static catalog responses for catalog and file_metadata
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-5960 Document static catalog responses for catalog and file_metadata Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5341) Tag fields in reports accidentally changed to Puppet::Util::TagSet objects
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-5341 Tag fields in reports accidentally changed to Puppet::Util::TagSet objects Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5959) Add test that static catalog metadata defaults match File type
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-5959 Add test that static catalog metadata defaults match File type Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1358) Add GCC 5.3.0 testing to CI, update instructions
Title: Message Title Michael Smith created an issue Facter / FACT-1358 Add GCC 5.3.0 testing to CI, update instructions Issue Type: Task Assignee: Unassigned Created: 2016/03/03 10:54 AM Priority: Normal Reporter: Michael Smith Add GCC 5.3.0 testing to AppVeyor and Travis CI (while preserving GCC 4.8) to ensure we don't backslide while preparing to switch packaging to GCC 5. Also update the README to build with GCC 5 (particularly Windows instructions). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2354) PuppetDB 4.0.0 needs automated testing for upgrades from 2.3.8
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2354 PuppetDB 4.0.0 needs automated testing for upgrades from 2.3.8 Change By: Susan McNerney We currently upgrade from whatever the previous release was to current. We should add to that the ability to specific a specific long term stable release (currently 2.3.8) and ensure that we are able to upgrade from that to current. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6003) spec/integration/type/package_spec isn't run on all platforms
Title: Message Title Michael Smith created an issue Puppet / PUP-6003 spec/integration/type/package_spec isn't run on all platforms Issue Type: Bug Assignee: Unassigned Created: 2016/03/03 10:41 AM Priority: Normal Reporter: Michael Smith This spec is really an integration test, but because it's a spec it's not run on all platforms. Change it to an integration test. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2354) PuppetDB 4.0.0 needs automated testing for upgrades from 2.3.8
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2354 PuppetDB 4.0.0 needs automated testing for upgrades from 2.3.8 Change By: Susan McNerney Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2354) PuppetDB 4.0.0 needs automated testing for upgrades from 2.3.8
Title: Message Title Susan McNerney commented on PDB-2354 Re: PuppetDB 4.0.0 needs automated testing for upgrades from 2.3.8 Michael Stahnke do you have an ETA for this? PDB 4.0.0's release date really can't be set until we know when this will be resolved. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6001) Incomplete process table due to COLUMNS variable
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6001 Incomplete process table due to COLUMNS variable Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2492) update data service per ops deployment requirements
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2492 update data service per ops deployment requirements Change By: Wyatt Alt Sprint: PuppetDB 2016-03-09 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5528) As a puppet administrator, I can enable direct puppet on a per environment basis as an onramp to adoption.
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5528 As a puppet administrator, I can enable direct puppet on a per environment basis as an onramp to adoption. Change By: Erik Dasher QA Contact: Kurt Wall Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5528) As a puppet administrator, I can enable direct puppet on a per environment basis as an onramp to adoption.
Title: Message Title Erik Dasher assigned an issue to Sean Griffin Puppet / PUP-5528 As a puppet administrator, I can enable direct puppet on a per environment basis as an onramp to adoption. Change By: Erik Dasher Assignee: qa Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5528) As a puppet administrator, I can enable direct puppet on a per environment basis as an onramp to adoption.
Title: Message Title Erik Dasher commented on PUP-5528 Re: As a puppet administrator, I can enable direct puppet on a per environment basis as an onramp to adoption. After briefly discussing this story with Kevin Corcoran, Kurt Wall and Sean Griffin, I'm reassigning it to Sean Griffin. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5527) (Control Catalog Compilation) As a puppet admin, I can update manifests on my master without causing agents to get those updates.
Title: Message Title Erik Dasher commented on PUP-5527 Re: (Control Catalog Compilation) As a puppet admin, I can update manifests on my master without causing agents to get those updates. After briefly discussing this story with Kevin Corcoran, Kurt Wall and Sean Griffin, I'm reassigning to to Sean Griffin. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5527) (Control Catalog Compilation) As a puppet admin, I can update manifests on my master without causing agents to get those updates.
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5527 (Control Catalog Compilation) As a puppet admin, I can update manifests on my master without causing agents to get those updates. Change By: Erik Dasher QA Contact: Kurt Wall Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5527) (Control Catalog Compilation) As a puppet admin, I can update manifests on my master without causing agents to get those updates.
Title: Message Title Erik Dasher assigned an issue to Sean Griffin Puppet / PUP-5527 (Control Catalog Compilation) As a puppet admin, I can update manifests on my master without causing agents to get those updates. Change By: Erik Dasher Assignee: Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5530) (Catalog Metadata) As a puppet administrator, I do not want the compile master to compile a catalog unless I have specified that the compilation should occur.
Title: Message Title Erik Dasher assigned an issue to Sean Griffin Puppet / PUP-5530 (Catalog Metadata) As a puppet administrator, I do not want the compile master to compile a catalog unless I have specified that the compilation should occur. Change By: Erik Dasher Assignee: Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5530) (Catalog Metadata) As a puppet administrator, I do not want the compile master to compile a catalog unless I have specified that the compilation should occur.
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5530 (Catalog Metadata) As a puppet administrator, I do not want the compile master to compile a catalog unless I have specified that the compilation should occur. Change By: Erik Dasher QA Contact: Kurt Wall Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5530) (Catalog Metadata) As a puppet administrator, I do not want the compile master to compile a catalog unless I have specified that the compilation should occur.
Title: Message Title Erik Dasher commented on PUP-5530 Re: (Catalog Metadata) As a puppet administrator, I do not want the compile master to compile a catalog unless I have specified that the compilation should occur. This is not planned for Burnside. Have briefly discussing this story with Kevin Corcoran, Kurt Wall and Sean Griffin; reassigning to Sean Griffin for now. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2386) Add Ubuntu 15.10/wily to acceptance testing
Title: Message Title Kurt Wall assigned an issue to Unassigned PuppetDB / PDB-2386 Add Ubuntu 15.10/wily to acceptance testing Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5025) Package resource showing notice when ensure attribute contains Epoch tag
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5025 Package resource showing notice when ensure attribute contains Epoch tag Change By: Kylo Ginsberg Fix Version/s: PUP 4.4.1 Fix Version/s: PUP 4.4.2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5705) As a puppet admin, I want to enable static catalogs on a per-env basis so I can test the behavior without affecting production nodes
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5705 As a puppet admin, I want to enable static catalogs on a per-env basis so I can test the behavior without affecting production nodes Change By: Erik Dasher QA Contact: Kurt Wall Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5705) As a puppet admin, I want to enable static catalogs on a per-env basis so I can test the behavior without affecting production nodes
Title: Message Title Erik Dasher commented on PUP-5705 Re: As a puppet admin, I want to enable static catalogs on a per-env basis so I can test the behavior without affecting production nodes After briefly discussing this story with Kevin Corcoran, Kurt Wall and Sean Griffin, I'm closing it and assigning it to Sean Griffin. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5705) As a puppet admin, I want to enable static catalogs on a per-env basis so I can test the behavior without affecting production nodes
Title: Message Title Erik Dasher assigned an issue to Sean Griffin Puppet / PUP-5705 As a puppet admin, I want to enable static catalogs on a per-env basis so I can test the behavior without affecting production nodes Change By: Erik Dasher Resolution: Done Assignee: Sean Griffin Status: In Progress Resolved Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6002) Syntax error when using hash in parameter list without parenthesis
Title: Message Title Henrik Lindberg commented on PUP-6002 Re: Syntax error when using hash in parameter list without parenthesis It is either: notice(); a-hash notice(a-hash) 'notice'; a-hash (which the rewriter turns into notice(a-hash) an instance of the resource type 'notice' that is in error: it lacks a title, the 'notice' should have been written 'Notice' as defaults were intended 'there is no resource type 'notice' (but that cannot be validated at parse time) When implemented, it was deemed that using resource expressions was far more common than calling functions that can be called without parentheses and calling them with a literal hash. The ambiguity is therefore resolved to mean 'this is a resource without a title'. I think we are not going to do anything about this problem any time soon - it is a major effort and an unambiguous grammar will need language changes. (Easiest would be to turn off the ability to call functions with a single argument without parentheses around the args - which is the cause of many ambiguities in the language). I am placing this in the TechDebt epic and leaving it open. Add Comment
Jira (PUP-6002) Syntax error when using hash in parameter list without parenthesis
Title: Message Title Henrik Lindberg commented on PUP-6002 Re: Syntax error when using hash in parameter list without parenthesis There is no easy way around that problem as there are duelling ambiguities involved. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6000) Puppet slowing down after calling Puppet.initialize_settings multiple times
Title: Message Title Mateusz Gozdek commented on PUP-6000 Re: Puppet slowing down after calling Puppet.initialize_settings multiple times Thank you for your kind words. That was my first bug report to some bigger project, so I wanted it to be as good as possible. I created pull request. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6000) Puppet slowing down after calling Puppet.initialize_settings multiple times
Title: Message Title Kylo Ginsberg commented on PUP-6000 Re: Puppet slowing down after calling Puppet.initialize_settings multiple times Mateusz Gozdek excellent writeup! Thanks for debugging this so thoroughly. Your description is complete almost to the point of being a PR itself Please feel free to submit a PR if you're so inclined; if not, hopefully with this level of detail we'd be able to put up a PR internally before long. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6000) Puppet slowing down after calling Puppet.initialize_settings multiple times
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6000 Puppet slowing down after calling Puppet.initialize_settings multiple times Change By: Kylo Ginsberg Sprint: Client Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6000) Puppet slowing down after calling Puppet.initialize_settings multiple times
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6000 Puppet slowing down after calling Puppet.initialize_settings multiple times Change By: Kylo Ginsberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2436) document PDB troubleshooting for support
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2436 document PDB troubleshooting for support Change By: Kenneth Barber Fix Version/s: PDB 3.2.x Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6002) Syntax error when using hash in parameter list without parenthesis
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6002 Syntax error when using hash in parameter list without parenthesis Change By: Thomas Hallgren Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6002) Syntax error when using hash in parameter list without parenthesis
Title: Message Title
Thomas Hallgren created an issue
Puppet / PUP-6002
Syntax error when using hash in parameter list without parenthesis
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/03/03 7:23 AM
Priority:
Normal
Reporter:
Thomas Hallgren
The following _expression_ results in a syntax error:
notice { xxx(1) => 'x' }
but this can be parsed without errors:
notice ( { xxx(1) => 'x' } )
A qualified guess is that the parser interprets the first _expression_ as:
Jira (PUP-5995) Stray UTF-8 character in manifest corrupts parsed parameters
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5995 Stray UTF-8 character in manifest corrupts parsed parameters Change By: Henrik Lindberg Fix Version/s: PUP 4.4.1 Fix Version/s: PUP 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5995) Stray UTF-8 character in manifest corrupts parsed parameters
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-5995 Stray UTF-8 character in manifest corrupts parsed parameters Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6001) Incomplete process table due to COLUMNS variable
Title: Message Title Robert Scheer created an issue Puppet / PUP-6001 Incomplete process table due to COLUMNS variable Issue Type: Bug Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/03/03 6:25 AM Environment: Debian with sysvinit Priority: Normal Reporter: Robert Scheer The ps command from the procps-ng project which is used on Debian and Ubuntu honours the environment variable COLUMNS: when set to a number, output lines are cut of at that many positions. The difference can be seen with these two commands: $ COLUMNS= ps -ef > /tmp/env1 $ COLUMNS=80 ps -ef > /tmp/env2 So, if COLUMNS is set, then the process table is most likely incomplete. I see this happening on our Debian "wheezy" systems, where COLUMNS exists in the environment in which the Puppet agent is started. Puppet apparently doesn't clean up its environment before it executes subcommands, so COLUMNS leaks through to ps resulting in an incomplete process table. And that causes problems with services that have hasstatus=>false and Puppet has to try to match the process in the process table, in our case a few similar services with patterns like 'rbldnsd.*spamhaus'. The bug doesn't manifest on Ubuntu because COLUMNS is not set there. I don't know about other operating systems. The fix to this particular problem is
Jira (PUP-5995) Stray UTF-8 character in manifest corrupts parsed parameters
Title: Message Title Thomas Hallgren commented on PUP-5995 Re: Stray UTF-8 character in manifest corrupts parsed parameters Merged to stable at 8a85af4 and onward to master at b238fdf. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5995) Stray UTF-8 character in manifest corrupts parsed parameters
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5995 Stray UTF-8 character in manifest corrupts parsed parameters Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5983) Environment Data Provider has different interpolation behavior than Hiera
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5983 Environment Data Provider has different interpolation behavior than Hiera Change By: Henrik Lindberg Fix Version/s: PUP 4.4.1 Fix Version/s: PUP 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5983) Environment Data Provider has different interpolation behavior than Hiera
Title: Message Title Thomas Hallgren commented on PUP-5983 Re: Environment Data Provider has different interpolation behavior than Hiera Merged to stable at 9ad8f7e and to master at 8eacdfc. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5995) Stray UTF-8 character in manifest corrupts parsed parameters
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5995 Stray UTF-8 character in manifest corrupts parsed parameters Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5995) Stray UTF-8 character in manifest corrupts parsed parameters
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5995 Stray UTF-8 character in manifest corrupts parsed parameters Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6000) Puppet slowing down after calling Puppet.initialize_settings multiple times
Title: Message Title Mateusz Gozdek created an issue Puppet / PUP-6000 Puppet slowing down after calling Puppet.initialize_settings multiple times Issue Type: Bug Affects Versions: PUP 3.8.6 Assignee: Kylo Ginsberg Attachments: initialize_settings.diff Components: Client, Community, Performance Created: 2016/03/03 12:57 AM Environment: Linux, Ubuntu 14.04 Trusty Priority: Normal Reporter: Mateusz Gozdek I experienced some performance issues using foreman-proxy version 1.10.2-1 during class import. Stack trace brought me to initializer.rb in theforeman/smart-proxy. Smart-proxy is calling Puppet.initialize_settings for each puppet class.
Jira (FACT-1244) xenu vs. xen0 difference not recognized by Puppet
Title: Message Title Rene van der Linden updated an issue Facter / FACT-1244 xenu vs. xen0 difference not recognized by Puppet Change By: Rene van der Linden Priority: Major Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1244) xenu vs. xen0 difference not recognized by Puppet
Title: Message Title Rene van der Linden updated an issue Facter / FACT-1244 xenu vs. xen0 difference not recognized by Puppet Change By: Rene van der Linden Priority: Blocker Critical Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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.
