Jira (PUP-2277) SRV record should be cached after a handshake
Title: Message Title Josh Cooper commented on PUP-2277 Re: SRV record should be cached after a handshake Mike, I'm closing this as a dup of PUP-5587. Normally I would keep this ticket open and close the later one, but in this case PUP-5587 was exported from redmine, our prior ticketing system. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1422) Facter should detect PhotonOS
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1422 Facter should detect PhotonOS Change By: Maggie Dreyer Scope Change Category: Adopted Scope Change Reason: Extra bandwidth, onboarding Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1422) Facter should detect PhotonOS
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1422 Facter should detect PhotonOS Change By: Maggie Dreyer Sprint: Client 2016- 07 06 - 13 29 ( HA, 1.5.3 failover ) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1498) scheduled_task won't update command
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Puppet / PUP-1498 scheduled_task won't update command Change By: Glenn Sarti Assignee: Erick Banks Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1498) scheduled_task won't update command
Title: Message Title Ethan Brown commented on PUP-1498 Re: scheduled_task won't update command Test change merged to stable in https://github.com/puppetlabs/puppet/commit/257d5b2d6ed94def50e8d6e040302d1c87135947 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2842) PDB should grant read-only access to different [read-database] user
Title: Message Title Wyatt Alt commented on PDB-2842 Re: PDB should grant read-only access to different [read-database] user This seems like a postgres configuration issue. I'd expect to see this if your read user did not have read access to the read database, and can reproduce the problem under that scenario. If my read and write users both have access to the database, I have no trouble executing queries despite separate users. Andrey Galkin can the user you're specifying as the read user actually read from the database itself, for instance through psql instead of PuppetDB? PuppetDB does not do any postgres configuration or permission management on behalf of the user, as the application does not have the required privileges. I think some kind of check on startup to ensure the read user has table access seems like a good idea. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1498) scheduled_task won't update command
Title: Message Title Erick Banks commented on PUP-1498 Re: scheduled_task won't update command QA demo'ed to me by Glenn. I pulled the puppet.msi from http://nightlies.puppetlabs.com/puppet-agent/latest/repos/windows/ and ensured the changes from the pr above were included. I applied a manifest with command "notepad.exe"; then changed the command to "notepad2.exe" and reapplied the manifest and watched it change. Applied the same manifest again to verify idempotentcy. The tests in acceptance/tests/resource/scheduled_task/should_modify.rb sufficiently cover the changing of commands. Will not FR. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6443) Verify agent compatibility with sensitive catalog data and redacted reports
Title: Message Title Adrien Thebo created an issue Puppet / PUP-6443 Verify agent compatibility with sensitive catalog data and redacted reports Issue Type: Task Assignee: Unassigned Created: 2016/06/24 2:43 PM Priority: Normal Reporter: Adrien Thebo In order to pass sensitive and redacted data around while preserving that sensitive or redacted context, we're going to need to change the format of catalogs and reports. Nominally this will be an extension of the existing formats instead of modifying parts of the existing format, but we do need to run through potential compatibility issues. We'll need to test various versions of the Puppet agent and make sure that they can safely ingest newer catalogs, and we'll need to see how the modified report format will be handled by PuppetDB. Add Comment
Jira (PDB-2842) PDB should grant read-only access to different [read-database] user
Title: Message Title Andrey Galkin created an issue PuppetDB / PDB-2842 PDB should grant read-only access to different [read-database] user Issue Type: Bug Affects Versions: PDB 4.1.2 Assignee: Unassigned Created: 2016/06/24 2:37 PM Priority: Normal Reporter: Andrey Galkin SITUATION: 1. [read-database] has different PostgreSQL user than in [database] section 2. The read-only user is allowed to connect to DB, but fails to query objects created by read-write user 3. Example output: WARN [o.e.j.s.HttpChannel] /pdb/query/v4/facts?query=[%22extract%22,[%22certname%22,%22name%22,%22value%22],[%22and%22,[%22in%22,%22certname%22,[%22extract%22,%22certname%22,[%22select_resources%22,[%22and%22,[%22=%22,%22type%22,%22Class %22],[%22=%22,%22title%22,%22Cftotalcontrol%22],[%22=%22,%22exported%22,false],[%22or%22,[%22=%22,%22name%22,%22cf_totalcontrol_key%22],[%22=%22,%22name%22,%22cf_totalcontrol_scope_keys%22
Jira (PUP-6442) Redact the message field of transaction events
Title: Message Title Adrien Thebo created an issue Puppet / PUP-6442 Redact the message field of transaction events Issue Type: Improvement Assignee: Unassigned Created: 2016/06/24 2:30 PM Priority: Normal Reporter: Adrien Thebo Events generated during resource application accept among other values an arbitrary message. The message is logged to indicate when resource properties change, and they include the previous value and the newly set value. This is problematic if the property is sensitive; even if the event itself knows that it is sensitive there's no good way of redacting the previous and desired values in that message. We need to either change the interface of Puppet::Transaction::Event to be able to redact messages containing sensitive information, or change how those messages are set to ensure that callers provide the redaction themselves. For the former case we can change events to take a format string, the previous value, desired value, and associated property and have the event itself take care of the redaction. For the latter case, we might have to do something evil like override Puppet::Property#is_to_s and Puppet::Property#should_to_s to provide the redaction themselves; this will have to be done in a way that handles subclasses that already override those methods. Add Comment
Jira (PDB-2841) Twice as much maximum-pool-size connections
Title: Message Title Wyatt Alt commented on PDB-2841 Re: Twice as much maximum-pool-size connections Andrey Galkin Okay, got it. Thanks for raising this – I'm going to close it as wontfix but I just added a note to the configuration docs and it should be live in 15-20 minutes or so. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6441) Redact events with sensitive data
Title: Message Title
Adrien Thebo updated an issue
Puppet / PUP-6441
Redact events with sensitive data
Change By:
Adrien Thebo
When Puppet synchronizes a property it stores the historical, previous, and desired values in an instance of {{Puppet::Transaction::Event}}. The event is both sent to the Puppet master in the transaction report and is logged as part of the normal Puppet logging. When an event is created that contains sensitive data, these fields need to be redacted in some manner to prevent the plaintext values from being emitted in the aforementioned logging and reports. Event objects also contain a message field that may contain sensitive information, but as far as the event is concerned this is an opaque string and thus cannot be redacted by the event itself.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6441) Redact events with sensitive data
Title: Message Title Adrien Thebo created an issue Puppet / PUP-6441 Redact events with sensitive data Issue Type: Improvement Assignee: Unassigned Created: 2016/06/24 2:08 PM Priority: Normal Reporter: Adrien Thebo When Puppet synchronizes a property it stores the historical, previous, and desired values in an instance of Puppet::Transaction::Event. The event is both sent to the Puppet master in the transaction report and is logged as part of the normal Puppet logging. When an event is created that contains sensitive data, these fields need to be redacted in some manner to prevent the plaintext values from being emitted in the aforementioned logging and reports. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-3768) scheduled_task keeps reapplying
Title: Message Title Erick Banks commented on PUP-3768 Re: scheduled_task keeps reapplying QA demo'ed to me by Glenn. I pulled the puppet.msi from http://nightlies.puppetlabs.com/puppet-agent/latest/repos/windows/ and ensured the changes from the pr above were included. Then ran a puppet apply on a manifest with "arguments=>x" where "x" was a string of characters 300 long. Also I feel the acceptance tests are sufficient to prove the change now accepts long argument strings. Will not do FR. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5269) Puppet scheduled_task provider on windows fails if non-ASCII characters are in Task Name
Title: Message Title Erick Banks commented on PUP-5269 Re: Puppet scheduled_task provider on windows fails if non-ASCII characters are in Task Name QA demo'ed to me by Glenn. I pulled the puppet.msi from http://nightlies.puppetlabs.com/puppet-agent/latest/repos/windows/ and ensured the changes from the pr above were included. Then ran a puppet apply on a manifest with a multibyte utf-8 character as the name of the manifest "test竹". The manifest was applied once and on the second run proved to be idempotent. I feel the tests in spec/unit/provider/scheduled_task/win32_taskscheduler_spec.rb are sufficient to prove the change works. Will not FR. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2841) Twice as much maximum-pool-size connections
Title: Message Title Andrey Galkin commented on PDB-2841 Re: Twice as much maximum-pool-size connections It did cause a problem until I realized where the excessive connections were coming from. Now, I know how to workaround that. It would be good to update the documentation with clear note of such behavior at least. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6415) static_compiler: symlinks in recursed directories don't work
Title: Message Title Josh Cooper commented on PUP-6415 Re: static_compiler: symlinks in recursed directories don't work Hi Chris, thanks for taking the time to investigate. We can definitely apply the patch to 4.x (and I don't see why not 3.x, since the static compiler is the only option there). Interesting to hear about puppetserver. Are there anything getting in the way of switching over? Or is it just you've never had reason to before? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6437) directoryservice user provider crashes if no ShadowHashData is found
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6437 directoryservice user provider crashes if no ShadowHashData is found Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2841) Twice as much maximum-pool-size connections
Title: Message Title Wyatt Alt commented on PDB-2841 Re: Twice as much maximum-pool-size connections Andrey Galkin this is by design – PuppetDB uses two pools, one for reads and one for writes. Among other things, this means your command processing will not block on http requests to the service to complete, and also has benefits for generalization to multiple-db setups. Is this causing you a problem? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2841) Twice as much maximum-pool-size connections
Title: Message Title Andrey Galkin created an issue PuppetDB / PDB-2841 Twice as much maximum-pool-size connections Issue Type: Bug Affects Versions: PDB 4.1.2 Assignee: Unassigned Components: PuppetDB Created: 2016/06/24 1:36 PM Priority: Normal Reporter: Andrey Galkin STEP 1: 1. [database] maximum-pool-size is set to 10 2. [read-database] is not set See 20 connections are created. STEP 2: 1. [database] maximum-pool-size is set to 10 2. [read-database] is configured the same, but with different host and/or port See 10 connections created to [database] instance and 10 other connections for [read-database] instance CLUE: perhaps, if [read-database] is missing then [database] is simply copied what leads to duplicated amount of connections. PROPOSED SOLUTION: make sure a single pool is used, if [read-database] is missing.
Jira (PUP-6409) "integer too big to convert to `int' at" with lookupvar
Title: Message Title Chris Price commented on PUP-6409 Re: "integer too big to convert to `int' at" with lookupvar I left my local repro attempt running for about 3 days and wasn't able to repro. So, I guess, Jürgen Thomann, if you are willing to try that suggestion about the ruby patch and the admin endpoint for flushing, let me know how it goes. If we don't get any actionable info then I can look into putting together a custom .jar file for you that adds some instrumentation to the JRuby code, and maybe that'll help us figure it out? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6430) Support Fedora 24 in DNF
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6430 Support Fedora 24 in DNF Change By: Geoff Nichols Fix Version/s: PUP 4.5.3 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5982) Acceptance: add test case for 'parser validate'
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-5982 Acceptance: add test case for 'parser validate' Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6440) Tag transaction events with sensitive data
Title: Message Title Adrien Thebo created an issue Puppet / PUP-6440 Tag transaction events with sensitive data Issue Type: Improvement Assignee: Unassigned Created: 2016/06/24 11:37 AM Priority: Normal Reporter: Adrien Thebo When sensitive properties are synchronized, that sensitive context needs to be preserved when an event is generated for the property change. On this surface this will be adding another field to the Puppet::Transaction::Event class, but adding this field will ripple and affect things such as the report serialization format, PuppetDB, and potentially report processors. We'll need to add this field and understand how it'll impact the rest of the Puppet ecosystem. Add Comment This message was sent by
Jira (PUP-6424) Passenger failing on Ubuntu 12.04 (precise)
Title: Message Title John Duarte commented on PUP-6424 Re: Passenger failing on Ubuntu 12.04 (precise) The test suite also passes when using the 'git' method on the latest SHA 5e4da09. Steps used are the same as those listed in the comment above. Substitute the following command to kick off the run: bundle exec rake ci:test:git CONFIG=config/nodes/precise.yaml SHA=5e4da09f3320e3c0109dc3108cd5ff4bbabf9997 FORK=puppetlabs Results Test Suite: tests @ 2016-06-24 16:58:37 + - Host Configuration Summary - - Test Case Summary for suite 'tests' - Total Suite Time: 1516.92 seconds
Jira (PUP-6439) Pass per-instance property sensitivity from resource catalog to resource harness
Title: Message Title Adrien Thebo created an issue Puppet / PUP-6439 Pass per-instance property sensitivity from resource catalog to resource harness Issue Type: Improvement Assignee: Unassigned Created: 2016/06/24 10:53 AM Priority: Normal Reporter: Adrien Thebo Per PUP-6435, Puppet::Resource instances will have additional metadata indicating that some properties are sensitive. This information needs to be passed from resources/the resource catalog down to the resource harness during catalog application so that we can perform the necessary event redaction. Ultimately, when the resource harness is synchronizing individual properties it needs to determine if a change event should be redacted, so this information ultimately needs to land in Puppet::Property instances. Add Comment
Jira (PDB-2782) Producer should be a queryable entity
Title: Message Title Molly Waggett assigned an issue to Molly Waggett PuppetDB / PDB-2782 Producer should be a queryable entity Change By: Molly Waggett Resolution: Fixed Assignee: Molly Waggett Status: Ready for Merge Closed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6398) Executing parallel specs on Windows is not reliable
Title: Message Title Daniel Lu commented on PUP-6398 Re: Executing parallel specs on Windows is not reliable A few parallel:spec test runs: Windows 2012 R2 x64, 4 cores, ran 3 times, passed 3 times Windows 2012 R2 x64, 2 cores, ran 2 times, passed 2 times OS X 10.11.5 x64, 8 cores, ran 3 times, passed 3 times Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6438) Parallel spec on Windows improvements, assoc lib/provider refactors
Title: Message Title Daniel Lu updated an issue Puppet / PUP-6438 Parallel spec on Windows improvements, assoc lib/provider refactors Change By: Daniel Lu As per comments on https://github.com/puppetlabs/puppet/pull/5041* Refactor lib/provider files to expose $CHILD_STATUS.exitstatus to the spec tests in a way that allows stubbing / mocking as with execution_spec or pacman_spec* Decide between fixing mocking for launchd_spec OS X specific tests in Windows, rather than and guarding.* Take a closer look at settings_spec changes. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6398) Executing parallel specs on Windows is not reliable
Title: Message Title Daniel Lu updated an issue Puppet / PUP-6398 Executing parallel specs on Windows is not reliable Change By: Daniel Lu Acceptance Criteria: Spec tests should pass on Windows with 0 failures when run with multiple coresand using: bundle exec rake parallel:spec Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6438) Parallel spec on Windows improvements, assoc lib/provider refactors
Title: Message Title Daniel Lu updated an issue Puppet / PUP-6438 Parallel spec on Windows improvements, assoc lib/provider refactors Change By: Daniel Lu Summary: Parallel spec on Windows fix improvements, assoc lib/provider refactors Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6437) directoryservice user provider crashes if no ShadowHashData is found
Title: Message Title Clay Caviness commented on PUP-6437 Re: directoryservice user provider crashes if no ShadowHashData is found https://github.com/puppetlabs/puppet/pull/5056 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6438) Parallel spec on Windows fix improvements, assoc lib/provider refactors
Title: Message Title Daniel Lu created an issue Puppet / PUP-6438 Parallel spec on Windows fix improvements, assoc lib/provider refactors Issue Type: Improvement Assignee: Daniel Lu Created: 2016/06/24 10:04 AM Labels: Engineering-Initiative Priority: Normal Reporter: Daniel Lu As per comments on https://github.com/puppetlabs/puppet/pull/5041 Refactor lib/provider files to expose $CHILD_STATUS.exitstatus to the spec tests in a way that allows stubbing / mocking as with execution_spec or pacman_spec Decide between fixing mocking for launchd_spec OS X specific tests in Windows, rather than guarding. Take a closer look at settings_spec changes.
Jira (PUP-6437) directoryservice user provider crashes if no ShadowHashData is found
Title: Message Title Clay Caviness created an issue Puppet / PUP-6437 directoryservice user provider crashes if no ShadowHashData is found Issue Type: Bug Affects Versions: PUP 4.5.2 Assignee: Unassigned Created: 2016/06/24 9:57 AM Environment: macOS 10.11.5 Priority: Normal Reporter: Clay Caviness Possibly related to link PUP-6410, if the user/directoryservice provider's get_attribute_from_dscl method returns nil when trying to fetch ShadowHashData, the whole thing explodes. We've only seen this rarely, and only when the provider's trying to read an empty username (which is probably another bug that should be handled). Debug: Prefetching directoryservice resources for user
Jira (PDB-2840) consider using wire formats instead of query formats as reference report data
Title: Message Title Molly Waggett commented on PDB-2840 Re: consider using wire formats instead of query formats as reference report data yeah, I've been wanting to somehow unify the way we test reports, catalogs, and fact(set)s, since right now they're all doing different things. I will definitely keep this in mind / look more into it when I start exploring which avenue might make the most sense. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6424) Passenger failing on Ubuntu 12.04 (precise)
Title: Message Title John Duarte commented on PUP-6424 Re: Passenger failing on Ubuntu 12.04 (precise) I am able to get a passing run using the previously known good SHA. Reproduction steps. Checkout puppet at 2bdfb23 git clone https://github.com/puppetlabs/puppet cd puppet git checkout 2bdfb23 Prepare for acceptance run cd acceptance rm -rf .bundle Gemfile.lock log junit export BUNDLE_BIN=.bundle/bin export BUNDLE_PATH=.bundle bundle package --all bundle install --local
Jira (FACT-1395) Replace Facter 2.x WMI Operating System kernel query with Windows API
Title: Message Title Glenn Sarti commented on FACT-1395 Re: Replace Facter 2.x WMI Operating System kernel query with Windows API CI completed with green; https://jenkins.puppetlabs.com/view/legacy_Facter/view/2.x/job/legacy_facter_init-nightly_2.x/23/ Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1446) Improve the windows user check in facter/acceptance/test/facts/window.rb
Title: Message Title Glenn Sarti created an issue Facter / FACT-1446 Improve the windows user check in facter/acceptance/test/facts/window.rb Issue Type: Improvement Assignee: Unassigned Created: 2016/06/24 9:40 AM Priority: Normal Reporter: Glenn Sarti In FACT-1442 the regular _expression_ used to validate the user identity from facter on windows was modified to be more broad. This was to expedite the CI pipelines passing due to Windows 10 being added. However the regex may be too broad and there value is never actually verified. This ticket should; Review the regex and find one that's more specific to stop false positives (as per the comments in https://github.com/puppetlabs/facter/pull/1358#discussion_r68339551) Investigate whether it is possible to verify that the value returned from facter is actually true
Jira (PDB-2526) Update PDB CLI to show tk-status alerts
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2526 Update PDB CLI to show tk-status alerts Change By: Russell Mull Sprint: HA 2016-07-13 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1071) Install Options for PIP package provider (incl. patch)
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1071 Install Options for PIP package provider (incl. patch) Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6436) Puppet run doesn't fail when Systemd fails to start service
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6436 Puppet run doesn't fail when Systemd fails to start service Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1153) Incorrect ordering of group and user resource purging
Title: Message Title Stephen Gelman commented on PUP-1153 Re: Incorrect ordering of group and user resource purging Kylo Ginsberg: We just upgraded to puppet 4.5.2 and the issue is now worse. Before, the group removal errored but the user removal succeeded so the issue went away on subsequent puppet runs. Now, the group removal failing causes cascading dependency failures and the user removal gets skipped. This means the only way we are able to remove users on the box is doing so by hand. Is it possible for this to be prioritized more now that it is a huge breaking issue for us, and presumably anyone recursively managing users and groups in debian/ubuntu? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6370) systemd provider does not honor documented enabled states
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6370
systemd provider does not honor documented enabled states
Change By:
William Hopper
Release Notes Summary:
Previously, when checking whether a service was enabled, the systemd provider used hardcoded strings to compare to the output of {{systemctl}}. Now, we use the exit code from {{systemctl}}, which ensures that the provider's view of a service is in line with that of the system.
Release Notes:
Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6370) systemd provider does not honor documented enabled states
Title: Message Title William Hopper updated an issue Puppet / PUP-6370 systemd provider does not honor documented enabled states Change By: William Hopper Story Points: 0 Fix Version/s: PUP 4.6.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1442) facter/acceptance/test/facts/window.rb fails on windows 10 x86 and x64 platforms
Title: Message Title Glenn Sarti commented on FACT-1442 Re: facter/acceptance/test/facts/window.rb fails on windows 10 x86 and x64 platforms Pipeline has gone green. Closing this ticket Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6422) ensure_resource not longer working with undef parameters
Title: Message Title Henrik Lindberg commented on PUP-6422 Re: ensure_resource not longer working with undef parameters The change to "modules team" is because they deal with stdlib, and the definition of what the functions are supposed to do. Do this: ret = false if resource = findresource(reference.to_s) matches = params.collect do |key, value| resource[key] == value.eql?(:undef) ? nil : value # eql? avoids bugs caused by monkeypatching in puppet end ret = params.empty? || !matches.include?(false) end ret The best is to make a PR against stdlib and ping David Schmitt (which I just did)
Jira (NPUP-46) Postfix call for the "type" function results in a parse error.
Title: Message Title Henrik Lindberg assigned an issue to qa Native Puppet / NPUP-46 Postfix call for the "type" function results in a parse error. Change By: Henrik Lindberg Status: Ready for Merge Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (NPUP-46) Postfix call for the "type" function results in a parse error.
Title: Message Title Henrik Lindberg commented on NPUP-46 Re: Postfix call for the "type" function results in a parse error. Merged to master: 4a029fa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (NPUP-9) Implement deep matches in case/selector expressions
Title: Message Title Henrik Lindberg commented on NPUP-9 Re: Implement deep matches in case/selector expressions Merged to master at: e82b362 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (NPUP-9) Implement deep matches in case/selector expressions
Title: Message Title Henrik Lindberg assigned an issue to qa Native Puppet / NPUP-9 Implement deep matches in case/selector expressions Change By: Henrik Lindberg Status: Ready for Merge Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (NPUP-46) Postfix call for the "type" function results in a parse error.
Title: Message Title John Duarte updated an issue Native Puppet / NPUP-46 Postfix call for the "type" function results in a parse error. Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (NPUP-46) Postfix call for the "type" function results in a parse error.
Title: Message Title John Duarte updated an issue Native Puppet / NPUP-46 Postfix call for the "type" function results in a parse error. Change By: John Duarte QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6268) Display cert information when interacting with certs via `puppet cert` application
Title: Message Title Kevin Corcoran commented on PUP-6268 Re: Display cert information when interacting with certs via `puppet cert` application Erik Dasher, Kurt Wall - I know that there is a separate ticket - SERVER-1359 - for the QA effort on the epic which contains this ticket. However, I think it would be really good to have some manual testing done by QA as a part of this ticket, since it significantly the output of puppet cert ... commands. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6436) Puppet run doesn't fail when Systemd fails to start service
Title: Message Title Martin Caslavsky created an issue Puppet / PUP-6436 Puppet run doesn't fail when Systemd fails to start service Issue Type: Bug Assignee: Unassigned Created: 2016/06/24 4:35 AM Environment: EL7 Priority: Normal Reporter: Martin Caslavsky Lets have Systemd unit file for a simple service, but pass wrong argument to ExecStart command: --foo. /usr/lib/systemd/system/ncat.service [Unit] Description=Ncat
Jira (PDB-2674) Problem with puppetdb encoding
Title: Message Title Angel L. Mateo commented on PDB-2674 Re: Problem with puppetdb encoding I have found out that agents connected to my puppet 3.8 server are running ruby 1.8, while the ones connected to puppetserver have ruby 1.9. puppetdb also runs ruby 1.8. Could this problem be related with codification issues between ruby 1.8 and 1.9? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6422) ensure_resource not longer working with undef parameters
Title: Message Title Reinhard Vicinus commented on PUP-6422 Re: ensure_resource not longer working with undef parameters Sorry to bother but is any information still needed? Also does the change of the scrum team to modules mean, that stdlib module needs to be updated? If so the defined_with_params function works this way: ret = false if resource = findresource(reference.to_s) matches = params.collect do |key, value| resource[key] == value end ret = params.empty? || !matches.include?(false) end ret The problem is, that :undef is compared to nil. So I changed defined_with_params to work again as expected this way:
Jira (NPUP-46) Postfix call for the "type" function results in a parse error.
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-46 Postfix call for the "type" function results in a parse error. Change By: Peter Huene Scope Change Category: Adopted Scope Change Reason: Had spare bandwidth for a very simple fix. Sprint: Language Triage 2016-06-29 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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.
