Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server

2019-08-28 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1400  
 
 
  Add 'run_command' endpoint to bolt-server   
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Sprint: 
 Skeletor Kanban 20190619, Skeletor Kanban 20190703, Skeletor Kanban 20190717, Skeletor Kanban 20190731, Skeletor Kanban 20190814, Skeletor Kanban 20190828 , Skeletor Kanban 20190911  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312869.1560800327000.78392.1567039380235%40Atlassian.JIRA.


Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server

2019-08-28 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols commented on  BOLT-1400  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add 'run_command' endpoint to bolt-server   
 

  
 
 
 
 

 
 Scott McClellan - looks like this was automatically closed - what's the correct ticket status here?  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312869.1560800327000.78376.1567039140767%40Atlassian.JIRA.


Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server

2019-08-28 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1400  
 
 
  Add 'run_command' endpoint to bolt-server   
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Labels: 
 closed-github-move docs_reviewed  run_command  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312869.1560800327000.78372.1567039020399%40Atlassian.JIRA.


Jira (PDB-4373) PDB has issues upgrading to versions later than 6.1 on centos6

2019-08-28 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt commented on  PDB-4373  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PDB has issues upgrading to versions later than 6.1 on centos6   
 

  
 
 
 
 

 
 We are currently blocked on promotions to Lovejoy due to some changes we made to support building for FIPs. So I don't know if we yet have an exact build. I will follow up with the team tomorrow and see if we can get something in to unblock the pipeline for Lovejoy.  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309068.155804266.78283.1567035720350%40Atlassian.JIRA.


Jira (PDB-2634) PQL & Hashes: Provide hash projection capability for facts & resource params

2019-08-28 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-2634  
 
 
  PQL & Hashes: Provide hash projection capability for facts & resource params   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Issue Type: 
 Improvement New Feature  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.127261.1461089739000.77936.1567031642365%40Atlassian.JIRA.


Jira (PDB-4492) Subquery extractions of json fields throw NullPointerException

2019-08-28 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4492  
 
 
  Subquery extractions of json fields throw NullPointerException   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Summary: 
 Subquery extractions  of json fields  throw NullPointerException  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322682.1567031295000.77928.1567031520253%40Atlassian.JIRA.


Jira (PDB-4492) Subquery extractions throw NullPointerException

2019-08-28 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4492  
 
 
  Subquery extractions throw NullPointerException   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 

  
 
 
 
 

 
 The type coercion matrix in the query engine (specifically engine.clj) does not properly handle json fields.Attempting to run a query such as{code}curl -X POST http://localhost:8080/pdb/query/v4/facts -H 'Content-Type:application/json'   -d '{"query": ["and",  ["=", "name", "ipaddress"],  ["in", "value",["extract", "facts", ["select_inventory", ["=", "certname", "host-9"] }'{code}Throws this  giant  stack trace.{code}2019-08-28 15:14:46,790 WARN  [qtp753236382-45] [o.e.j.s.HttpChannel] /pdb/query/v4/factsjava.lang.NullPointerException: nullat puppetlabs.puppetdb.query_eng.engine$convert_type.invokeStatic(engine.clj:83)at puppetlabs.puppetdb.query_eng.engine$convert_type.invoke(engine.clj:81)at clojure.core$map$fn__5873.invoke(core.clj:2766)at clojure.lang.LazySeq.sval(LazySeq.java:42)at clojure.lang.LazySeq.seq(LazySeq.java:51)at clojure.lang.RT.seq(RT.java:535)at clojure.core$seq__5402.invokeStatic(core.clj:137)at clojure.core.protocols$seq_reduce.invokeStatic(protocols.clj:24)at clojure.core.protocols$fn__8146.invokeStatic(protocols.clj:75)at clojure.core.protocols$fn__8146.invoke(protocols.clj:75)at clojure.core.protocols$fn__8088$G__8083__8101.invoke(protocols.clj:13)at clojure.core$reduce.invokeStatic(core.clj:6828)at clojure.core$into.invokeStatic(core.clj:6895)at clojure.core$mapv.invokeStatic(core.clj:6903)at clojure.core$mapv.invoke(core.clj:6903)at puppetlabs.puppetdb.query_eng.engine$eval33462$fn__33464.invoke(engine.clj:1279)at puppetlabs.puppetdb.query_eng.engine$eval33408$fn__33409$G__33399__33414.invoke(engine.clj:1242)at clojure.core$map$fn__5866.invoke(core.clj:2755)at clojure.lang.LazySeq.sval(LazySeq.java:42)at clojure.lang.LazySeq.seq(LazySeq.java:51)at clojure.lang.RT.seq(RT.java:535)at clojure.core$seq__5402.invokeStatic(core.clj:137)at clojure.core$map$fn__5866.invoke(core.clj:2746)at clojure.lang.LazySeq.sval(LazySeq.java:42)at clojure.lang.LazySeq.seq(LazySeq.java:51)at clojure.lang.Cons.next(Cons.java:39)at clojure.lang.LazySeq.next(LazySeq.java:83)at clojure.lang.RT.next(RT.java:713)at clojure.core$next__5386.invokeStatic(core.clj:64)at clojure.string$join.invokeStatic(string.clj:180)at clojure.string$join.invoke(string.clj:180)at honeysql.format$format_predicate_STAR_.invokeStatic(format.clj:366)at honeysql.format$format_predicate_STAR_.invoke(format.clj:356)at clojure.core$map$fn__5866.invoke(core.clj:2755)at clojure.lang.LazySeq.sval(LazySeq.java:42)at clojure.lang.LazySeq.seq(LazySeq.java:51)at clojure.lang.LazySeq.first(LazySeq.java:73)at clojure.lang.RT.first(RT.java:692)at clojure.core$first__5384.invokeS

Jira (PDB-4492) Subquery extractions throw NullPointerException

2019-08-28 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4492  
 
 
  Subquery extractions throw NullPointerException   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 

  
 
 
 
 

 
 The type coercion matrix in the query engine (specifically engine.clj) does not properly handle json fields.Attempting to run a query such as{code}curl -X POST http://localhost:8080/pdb/query/v4/facts -H 'Content-Type:application/json'   -d '{"query": ["and",  ["=", "name", "ipaddress"],  ["in", "value",["extract", "facts", ["select_inventory", ["=", "certname", "host-9"] }'{code}Throws this giant stack trace.{code}2019-08-28 15:14:46,790 WARN  [qtp753236382-45] [o.e.j.s.HttpChannel] /pdb/query/v4/factsjava.lang.NullPointerException: nullat puppetlabs.puppetdb.query_eng.engine$convert_type.invokeStatic(engine.clj:83)at puppetlabs.puppetdb.query_eng.engine$convert_type.invoke(engine.clj:81)at clojure.core$map$fn__5873.invoke(core.clj:2766)at clojure.lang.LazySeq.sval(LazySeq.java:42)at clojure.lang.LazySeq.seq(LazySeq.java:51)at clojure.lang.RT.seq(RT.java:535)at clojure.core$seq__5402.invokeStatic(core.clj:137)at clojure.core.protocols$seq_reduce.invokeStatic(protocols.clj:24)at clojure.core.protocols$fn__8146.invokeStatic(protocols.clj:75)at clojure.core.protocols$fn__8146.invoke(protocols.clj:75)at clojure.core.protocols$fn__8088$G__8083__8101.invoke(protocols.clj:13)at clojure.core$reduce.invokeStatic(core.clj:6828)at clojure.core$into.invokeStatic(core.clj:6895)at clojure.core$mapv.invokeStatic(core.clj:6903)at clojure.core$mapv.invoke(core.clj:6903)at puppetlabs.puppetdb.query_eng.engine$eval33462$fn__33464.invoke(engine.clj:1279)at puppetlabs.puppetdb.query_eng.engine$eval33408$fn__33409$G__33399__33414.invoke(engine.clj:1242)at clojure.core$map$fn__5866.invoke(core.clj:2755)at clojure.lang.LazySeq.sval(LazySeq.java:42)at clojure.lang.LazySeq.seq(LazySeq.java:51)at clojure.lang.RT.seq(RT.java:535)at clojure.core$seq__5402.invokeStatic(core.clj:137)at clojure.core$map$fn__5866.invoke(core.clj:2746)at clojure.lang.LazySeq.sval(LazySeq.java:42)at clojure.lang.LazySeq.seq(LazySeq.java:51)at clojure.lang.Cons.next(Cons.java:39)at clojure.lang.LazySeq.next(LazySeq.java:83)at clojure.lang.RT.next(RT.java:713)at clojure.core$next__5386.invokeStatic(core.clj:64)at clojure.string$join.invokeStatic(string.clj:180)at clojure.string$join.invoke(string.clj:180)at honeysql.format$format_predicate_STAR_.invokeStatic(format.clj:366)at honeysql.format$format_predicate_STAR_.invoke(format.clj:356)at clojure.core$map$fn__5866.invoke(core.clj:2755)at clojure.lang.LazySeq.sval(LazySeq.java:42)at clojure.lang.LazySeq.seq(LazySeq.java:51)at clojure.lang.LazySeq.first(LazySeq.java:73)at clojure.lang.RT.first(RT.java:692)at clojure.core$first__5384.invokeSta

Jira (PDB-4492) Subquery extractions throw NullPointerException

2019-08-28 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4492  
 
 
  Subquery extractions throw NullPointerException   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Method Found: 
 Needs Assessment Manual Test  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322682.1567031295000.77923.1567031402552%40Atlassian.JIRA.


Jira (PDB-4492) Subquery extractions throw NullPointerException

2019-08-28 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4492  
 
 
  Subquery extractions throw NullPointerException   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Affects Version/s: 
 PDB 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322682.1567031295000.77926.1567031402869%40Atlassian.JIRA.


Jira (PDB-4492) Subquery extractions throw NullPointerException

2019-08-28 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4492  
 
 
  Subquery extractions throw NullPointerException   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 

  
 
 
 
 

 
 The type coercion matrix in the query engine (specifically engine.clj) does not properly handle json fields.Attempting to run a query such as{code}curl -X POST http://localhost:8080/pdb/query/v4/facts -H 'Content-Type:application/json'   -d '{"query": ["and",  ["=", "name", "ipaddress"],  ["in", "value",["extract",  [ "facts" ] , ["select_inventory", ["=", "certname", "host-9"] }'{code}Throws this giant stack trace.{code}2019-08-28 15:14:46,790 WARN  [qtp753236382-45] [o.e.j.s.HttpChannel] /pdb/query/v4/factsjava.lang.NullPointerException: nullat puppetlabs.puppetdb.query_eng.engine$convert_type.invokeStatic(engine.clj:83)at puppetlabs.puppetdb.query_eng.engine$convert_type.invoke(engine.clj:81)at clojure.core$map$fn__5873.invoke(core.clj:2766)at clojure.lang.LazySeq.sval(LazySeq.java:42)at clojure.lang.LazySeq.seq(LazySeq.java:51)at clojure.lang.RT.seq(RT.java:535)at clojure.core$seq__5402.invokeStatic(core.clj:137)at clojure.core.protocols$seq_reduce.invokeStatic(protocols.clj:24)at clojure.core.protocols$fn__8146.invokeStatic(protocols.clj:75)at clojure.core.protocols$fn__8146.invoke(protocols.clj:75)at clojure.core.protocols$fn__8088$G__8083__8101.invoke(protocols.clj:13)at clojure.core$reduce.invokeStatic(core.clj:6828)at clojure.core$into.invokeStatic(core.clj:6895)at clojure.core$mapv.invokeStatic(core.clj:6903)at clojure.core$mapv.invoke(core.clj:6903)at puppetlabs.puppetdb.query_eng.engine$eval33462$fn__33464.invoke(engine.clj:1279)at puppetlabs.puppetdb.query_eng.engine$eval33408$fn__33409$G__33399__33414.invoke(engine.clj:1242)at clojure.core$map$fn__5866.invoke(core.clj:2755)at clojure.lang.LazySeq.sval(LazySeq.java:42)at clojure.lang.LazySeq.seq(LazySeq.java:51)at clojure.lang.RT.seq(RT.java:535)at clojure.core$seq__5402.invokeStatic(core.clj:137)at clojure.core$map$fn__5866.invoke(core.clj:2746)at clojure.lang.LazySeq.sval(LazySeq.java:42)at clojure.lang.LazySeq.seq(LazySeq.java:51)at clojure.lang.Cons.next(Cons.java:39)at clojure.lang.LazySeq.next(LazySeq.java:83)at clojure.lang.RT.next(RT.java:713)at clojure.core$next__5386.invokeStatic(core.clj:64)at clojure.string$join.invokeStatic(string.clj:180)at clojure.string$join.invoke(string.clj:180)at honeysql.format$format_predicate_STAR_.invokeStatic(format.clj:366)at honeysql.format$format_predicate_STAR_.invoke(format.clj:356)at clojure.core$map$fn__5866.invoke(core.clj:2755)at clojure.lang.LazySeq.sval(LazySeq.java:42)at clojure.lang.LazySeq.seq(LazySeq.java:51)at clojure.lang.LazySeq.first(LazySeq.java:73)at clojure.lang.RT.first(RT.java:692)at clojure.core$first__5384.inv

Jira (PDB-4373) PDB has issues upgrading to versions later than 6.1 on centos6

2019-08-28 Thread Joshua Partlow (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joshua Partlow commented on  PDB-4373  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PDB has issues upgrading to versions later than 6.1 on centos6   
 

  
 
 
 
 

 
 What build of puppetdb should we expect this changes in in 2019.2.x?  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309068.155804266.77533.1567026660247%40Atlassian.JIRA.


Jira (PUP-9754) Log resident configuration upon daemon launch

2019-08-28 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-9754  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Log resident configuration upon daemon launch   
 

  
 
 
 
 

 
 Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/5144c75f8c1257fd1aa572d70714d7f4f1a97a7b  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312512.1560543853000.77048.1567021560751%40Atlassian.JIRA.


Jira (PUP-9956) Exec logs output of Sensitive unless and onlyif checks at debug

2019-08-28 Thread Kris Bosland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kris Bosland updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9956  
 
 
  Exec logs output of Sensitive unless and onlyif checks at debug   
 

  
 
 
 
 

 
Change By: 
 Kris Bosland  
 
 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.320444.1565385879000.76584.1567009260221%40Atlassian.JIRA.


Jira (BOLT-1429) Inconsistent behavior in Boltspec::Run.run_command on Windows

2019-08-28 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer commented on  BOLT-1429  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Inconsistent behavior in Boltspec::Run.run_command on Windows   
 

  
 
 
 
 

 
 It was specifically about saving the runspace between commands on winrm if we're going to on local. If we're not doing that I don't have any concerns.  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314131.1561529132000.76411.1567005480317%40Atlassian.JIRA.


Jira (PUP-9465) group resource type misunderstands/misuses libuser

2019-08-28 Thread Gabriel Nagy (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Nagy commented on  PUP-9465  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: group resource type misunderstands/misuses libuser   
 

  
 
 
 
 

 
 James Ralston it seems that the only valid use-case for having this provider is being able to benefit from the manages_members feature to manage the membership of an arbitrary group with a single group resource. I'm not sure this warrants a separate provider, this can be accomplished in the existing provider with a conditional feature like:  
 
 
 
 
 has_feature :manages_members if Puppet.features.libuser?
  
 
 
 
  and then handle the "members" property. Thoughts?  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.293306.1548368109000.76328.1566999840199%40Atlassian.JIRA.


Jira (FACT-1853) facter networking is very slow on OpenStack compute node

2019-08-28 Thread Gabriel Nagy (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Nagy commented on  FACT-1853  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: facter networking is very slow on OpenStack compute node   
 

  
 
 
 
 

 
 Hi Chris Card, Mateusz Gozdek, We believe this is linked to LTH-162 and how open file descriptors are handled on Linux (GitHub PR). This should be fixed now, and puppet-agent builds with the fix should be available on the nightlies page over the next few days: http://nightlies.puppet.com/    
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.251436.1526644654000.76172.1566984600597%40Atlassian.JIRA.


Jira (PUP-9465) group resource type misunderstands/misuses libuser

2019-08-28 Thread Gabriel Nagy (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Nagy commented on  PUP-9465  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: group resource type misunderstands/misuses libuser   
 

  
 
 
 
 

 
 James Ralston I checked the reasoning behind the libuser code in puppet, it was introduced here: https://github.com/puppetlabs/puppet/pull/1442 

Some applications require local accounts and the useradd/groupadd commands currently used by the provider will not create a local account if they already exist remotely. The libuser commands luseradd/lgroupadd will allow a local name to duplicate a remote name. So these commands are used to force the local account creation. 
 That's where the forcelocal/libuser misunderstanding comes from. We'll investigate this further.  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.293306.1548368109000.76102.1566981360233%40Atlassian.JIRA.


Jira (PUP-9465) group resource type misunderstands/misuses libuser

2019-08-28 Thread Gabriel Nagy (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Nagy assigned an issue to Gabriel Nagy  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9465  
 
 
  group resource type misunderstands/misuses libuser   
 

  
 
 
 
 

 
Change By: 
 Gabriel Nagy  
 
 
Assignee: 
 Gabriel Nagy  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.293306.1548368109000.76098.1566980880575%40Atlassian.JIRA.