Jira (PUP-9688) User resource sets password on every puppet agent run (Windows)
Title: Message Title
Philip Olsen commented on PUP-9688
Re: User resource sets password on every puppet agent run (Windows)
I have done some further testing and believe the issue is based on the login type passed into the LogonUserW within the windows user.rb code here: https://github.com/puppetlabs/puppet/blob/f19c5674ccd95ce28bd54ed21db5b9bf02bc547b/lib/puppet/util/windows/user.rb At lines 85-89, the value of fLOGON32_LOGON_NETWORK is 3 which is a LOGON32_LOGON_NETWORK type (see below). This fails if the user is not allowed network logon rights (by design). As a fix, could we update the code to attempt a LOGON32_LOGON_INTERACTIVE if the initial LOGON32_LOGON_NETWORK fails? It would essentially just need an additional if statement to be built in here but I don't have the ruby coding skills to implement it myself. Perhaps someone more skilled in ruby could implement?
FFI::MemoryPointer.new(:handle, 1) do |token_pointer| if LogonUserW(wide_string(name), wide_string('.'), password.nil? ? FFI::Pointer::NULL : wide_string(password), fLOGON32_LOGON_NETWORK, fLOGON32_PROVIDER_DEFAULT, token_pointer) == FFI::WIN32_FALSE raise Puppet::Util::Windows::Error.new(_("Failed to logon user %
Unknown macro: {name}
") %
Unknown macro: { name}
) end
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8774) puppet device does not use locking
Title: Message Title Adam Gardner commented on PUP-8774 Re: puppet device does not use locking I think this should be revisited. While it certainly does not make sense for puppet device to be locked across all targets, it makes a lot of sense to try and protect against a single proxy running puppet device against the same target multiple times simultaneously. Just like each device target has its own cache, it should have its own lock file: /opt/puppetlabs/puppet/cache/devices//state/device_catalog_run.lock, most likely. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-1243) When a command is not specified on CLI a helpful error message is not raised
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1243 When a command is not specified on CLI a helpful error message is not raised Change By: Cas Donoghue Assignee: Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-901) Improve Plan Logging with apply
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-901
Improve Plan Logging with apply
Change By:
Nick Lewis
Problem I want useful human readable output showing the events from each targets apply during a plan. This is especially useful when debugging an apply statement in a plan.Refactor logging and outputting * All actions (plan start/finish, step start/finish, node start/result) are handed to the outputter as an event stream. * {{--verbose}} becomes an option for the outputter not the logger. * "verbose" is now defined to mean node-level results are included in the output when using the human format. "verbose" has no meaning for the JSON format. * Plans default to non-verbose, everything else defaults to verbose. {{ \ --no-verbose}} is accepted as an addition to {{--verbose}} * "plan logging" becomes an outputter concept, rather than an executor concept * {{without_default_logging}} becomes state tracked on the outputter that causes it to simply ignore action events.Human outputter * Human outputter without verbose prints starting action and summary for action messages. * Human outputter prints full node-level result with {{--verbose}} * For {{bolt apply}} _without_ verbose, human outputter only prints a summary of the run * For {{bolt apply}} _with_ verbose, human outputter prints logs from each report showing at least changes. This is probably notice level messages and above, maybe excluding messages where the source is "Puppet". * All output from this outputter can go to stdout (currently messages go to stderr for plans)JSON outputter: * When in non-plan mode behaves as it does currently. * Logs entire JSON format of {{apply}} result on stderr for each node at {{--verbose}} * This outputter can show intermediate results on stderr in human format, but doesn't have to for this ticketLog output: * The default console log level is now "warn". No "human-oriented" output should come from the logger except for warnings and errors. * Log files still default to "info". * {{\-\-debug}} still sets debug level for console logger, {{\-\-verbose}} does not affect the logger at all * A "logger outputter" should consume the event stream and translate each event to appropriate log messages that are passed to the loggerPuppet log functions: * Eventually these should be handled by the outputter rather than the logger directly, but this is left to a later ticket.apply_prep/get_resources: * These probably need to have specific events the outputter can handle. That is out of scope for this ticket. For now just rely on {{without_default_logging}}
Jira (BOLT-1227) Document how Bolt will use local SSH config
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1227 Document how Bolt will use local SSH config Change By: Cas Donoghue Assignee: Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-1225) Link to packaged plans and tasks from running * pages
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1225 Link to packaged plans and tasks from running * pages Change By: Cas Donoghue Labels: docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4362) Fix upgrade_oldest
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-4362 Fix upgrade_oldest Change By: Zachary Kent Assignee: Zachary Kent Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4362) Fix upgrade_oldest
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-4362 Fix upgrade_oldest Issue Type: Bug Assignee: Unassigned Created: 2019/04/29 2:35 PM Priority: Normal Reporter: Zachary Kent :upgrade_oldest test weren't running as expected. Make sure that when upgrading from PDB 5.2.0 -> 6.X.X the correct repos are available. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8984) Add JSON output option to `puppet parser validate`
Title: Message Title Kris Bosland commented on PUP-8984 Re: Add JSON output option to `puppet parser validate` Merged into master at bae2d75. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9651) Delete low risk acceptance tests
Title: Message Title John Duarte commented on PUP-9651 Re: Delete low risk acceptance tests The merged PR removes all of the low risk tests. No follow-on PRs are needed. I have updated the state to "Ready for CI". Thanks Jacob Helwig! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4308) Check whether pdb is unkillable when db is unavailable at startup
Title: Message Title
Rob Browning updated an issue
PuppetDB / PDB-4308
Check whether pdb is unkillable when db is unavailable at startup
Change By:
Rob Browning
While working on other things, I noticed that a "lein test ..." run might have become unkillable (i.e. C-c didn't kill it, kill wouldn't kill it, and I resorted to kill -9) when I tried this in a test:{code:clojure}(with- temp test -db (svc-utils/call-with-single-quiet-pdb-instance (-> (svc-utils/create-temp-config) (assoc :database *db*) (assoc-in [:database :user ] "invalid-user") (assoc-in [:global :vardir] shared-vardir)) (fn [] ...))){code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (PDB-4068) Migrate to clojure.java-time or directly to built-in Java time
Title: Message Title Rob Browning commented on PDB-4068 Re: Migrate to clojure.java-time or directly to built-in Java time See the linked tickets for relevant progress. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4068) Migrate to clojure.java-time or directly to built-in Java time
Title: Message Title Rob Browning commented on PDB-4068 Re: Migrate to clojure.java-time or directly to built-in Java time My current inclination is to just move to use java.time directly as the implementation, after migrating all of the relevant time functions to puppetdb.time (i.e. so that's the only place we call external time libraries). It also looks like this might be substantially easier if https://www.threeten.org/threeten-extra/ is a reasonable dependency. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4308) Check whether pdb is unkillable when db is unavailable at startup
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-4308 Check whether pdb is unkillable when db is unavailable at startup Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9652) Delete acceptance tests with 'audit:delete' tag
Title: Message Title Jacob Helwig assigned an issue to John Duarte Puppet / PUP-9652 Delete acceptance tests with 'audit:delete' tag Change By: Jacob Helwig Assignee: John Duarte Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9651) Delete low risk acceptance tests
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-9651 Delete low risk acceptance tests Change By: Jacob Helwig Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9651) Delete low risk acceptance tests
Title: Message Title Jacob Helwig assigned an issue to John Duarte Puppet / PUP-9651 Delete low risk acceptance tests Change By: Jacob Helwig Assignee: John Duarte Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9652) Delete acceptance tests with 'audit:delete' tag
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-9652 Delete acceptance tests with 'audit:delete' tag Change By: Jacob Helwig Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9651) Delete low risk acceptance tests
Title: Message Title Jacob Helwig commented on PUP-9651 Re: Delete low risk acceptance tests Merged to master branch in 14878c4e11. John Duarte, OK to move to "Ready for CI" or were there going to be follow-on PRs for this ticket? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-1259) Acceptance tests for local transport in bolt
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-1259 Acceptance tests for local transport in bolt Change By: Lucy Wyman Assignee: Cas Donoghue Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9685) Allow providing required facts during Puppet initialization
Title: Message Title Rob Braden updated an issue Puppet / PUP-9685 Allow providing required facts during Puppet initialization Change By: Rob Braden Sprint: Coremunity Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9685) Allow providing required facts during Puppet initialization
Title: Message Title Rob Braden updated an issue Puppet / PUP-9685 Allow providing required facts during Puppet initialization Change By: Rob Braden Team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9686) Allow initializing Puppet w/o loading Facter
Title: Message Title Rob Braden updated an issue Puppet / PUP-9686 Allow initializing Puppet w/o loading Facter Change By: Rob Braden Team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9686) Allow initializing Puppet w/o loading Facter
Title: Message Title Rob Braden updated an issue Puppet / PUP-9686 Allow initializing Puppet w/o loading Facter Change By: Rob Braden Sprint: Coremunity Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9652) Delete acceptance tests with 'audit:delete' tag
Title: Message Title John Duarte commented on PUP-9652 Re: Delete acceptance tests with 'audit:delete' tag There is no more to be done for this ticket. I have moved it to the "Ready for CI" status. Thanks Jacob Helwig! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9652) Delete acceptance tests with 'audit:delete' tag
Title: Message Title Jacob Helwig commented on PUP-9652 Re: Delete acceptance tests with 'audit:delete' tag PR merged to master branch in c29c5ad5ea. John Duarte is there more to be done for this ticket, or is it OK to move this to "Ready for CI"? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4305) "null?" query of facts against the query/v4/nodes endpoint results in "Value does not match schema" errors
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4305 "null?" query of facts against the query/v4/nodes endpoint results in "Value does not match schema" errors Change By: Jarret Lavallee CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9389) Add new parameter to File for tempfile staging location
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-9389 Add new parameter to File for tempfile staging location Change By: Jacob Helwig Fix Version/s: PUP 6.5.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9389) Add new parameter to File for tempfile staging location
Title: Message Title Jacob Helwig commented on PUP-9389 Re: Add new parameter to File for tempfile staging location This has been merged to the master branch in 2834f16cef. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9389) Add new parameter to File for tempfile staging location
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-9389 Add new parameter to File for tempfile staging location Change By: Jacob Helwig Release Notes Summary: The temporary location used when creating the new content for a File resource can now be customized using the `staging_location` parameter. Release Notes: Enhancement Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9688) User resource sets password on every puppet agent run (Windows)
Title: Message Title Philip Olsen commented on PUP-9688 Re: User resource sets password on every puppet agent run (Windows) https://github.com/puppetlabs/puppet/blob/f19c5674ccd95ce28bd54ed21db5b9bf02bc547b/lib/puppet/util/windows/user.rb Could the issue lie in the error returned by lines 62-77 in the above? Perhaps just needs to cleanly handle the error code relevant when a user is denied logon rights from the network? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9688) User resource sets password on every puppet agent run (Windows)
Title: Message Title
Patrick Grant created an issue
Puppet / PUP-9688
User resource sets password on every puppet agent run (Windows)
Issue Type:
Bug
Affects Versions:
PUP 5.5.10
Assignee:
Unassigned
Created:
2019/04/29 3:25 AM
Priority:
Normal
Reporter:
Patrick Grant
*Puppet Version: 5.5.10 *Puppet Server Version: 5.3.7 OS Name/Version: WIndows Server 2016 When using the following simple code to set the Administrator password on Windows:
$adminpassword = 'slkdhfl@#$slkW223'
if $adminpassword {
user { 'Administrator':
ensure => present,
password => $adminpassword,
