Jira (PUP-10020) Failed to transition the pxp-agent service to the SERVICE_RUNNING state
Title: Message Title cody fawcett commented on PUP-10020 Re: Failed to transition the pxp-agent service to the SERVICE_RUNNING state Thank you for the details 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.324730.1568481726000.100655.1568674260364%40Atlassian.JIRA.
Jira (PUP-9754) Log resident configuration upon daemon launch
Title: Message Title Josh Cooper commented on PUP-9754 Re: Log resident configuration upon daemon launch Jean Bond The puppet agent process will daemonize by default on POSIX systems, though it can be prevented a few different ways, such as setting Puppet[:daemonize]=false, specifying puppet agent ---onetime, or more commonly puppet agent --test. The new behavior in this ticket only occurs when the agent daemonizes and the log level is set to debug. Also Windows handles daemonizing differently, so this ticket doesn't apply to puppet on Windows. 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.100619.1568672940321%40Atlassian.JIRA.
Jira (PDB-4502) PuppetDB command size metrics are missing
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-4502 PuppetDB command size metrics are missing Change By: Zachary Kent Assignee: Rob Browning 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323996.156781861.100606.1568672760677%40Atlassian.JIRA.
Jira (PUP-5109) Puppet::Resource::Catalog::Compiler#set_server_facts always produces a warning on ipv6 only systems
Title: Message Title Jean Bond updated an issue Puppet / PUP-5109 Puppet::Resource::Catalog::Compiler#set_server_facts always produces a warning on ipv6 only systems Change By: Jean Bond Labels: IPv6 help_wanted resolved-issue-added 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.95553.144084808.100543.1568670360314%40Atlassian.JIRA.
Jira (PUP-10020) Failed to transition the pxp-agent service to the SERVICE_RUNNING state
Title: Message Title Josh Cooper commented on PUP-10020 Re: Failed to transition the pxp-agent service to the SERVICE_RUNNING state cody fawcett I believe you are running into PCP-863. There are situations where the pxp-agent.exe process is not killed when the service is restarted via nssm, which then interferes with future service operations. As as aside, the PCP project in JIRA is for the pxp-agent component of the puppet-agent package. I'm going to mark this is as a duplicate and close it. 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.324730.1568481726000.100483.1568669280340%40Atlassian.JIRA.
Jira (PDB-4504) add-resource-events-pk migration does not use batched inserts
Title: Message Title Nick Walker commented on PDB-4504 Re: add-resource-events-pk migration does not use batched inserts Rob Browning any possibility of getting this fixed before the next PE release? 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.324827.1568659575000.100334.1568666401872%40Atlassian.JIRA.
Jira (PDB-4504) add-resource-events-pk migration does not use batched inserts
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-4504 add-resource-events-pk migration does not use batched inserts Change By: Nick Walker Priority: Normal Major 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.324827.1568659575000.100315.1568666401613%40Atlassian.JIRA.
Jira (PDB-4504) add-resource-events-pk migration does not use batched inserts
Title: Message Title Nick Walker assigned an issue to Rob Browning PuppetDB / PDB-4504 add-resource-events-pk migration does not use batched inserts Change By: Nick Walker 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324827.1568659575000.100321.1568666401715%40Atlassian.JIRA.
Jira (PDB-4505) Log progress during resource events key migration
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4505 Log progress during resource events key migration Issue Type: Improvement Assignee: Rob Browning Created: 2019/09/16 1:15 PM Priority: Normal Reporter: 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 view this discussion on the web visit
Jira (PUP-8662) puppet plugin download doesn't re-use HTTP connections
Title: Message Title Jean Bond updated an issue Puppet / PUP-8662 puppet plugin download doesn't re-use HTTP connections Change By: Jean Bond Labels: resolved-issue-added 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.245716.1523666018000.100267.1568664840433%40Atlassian.JIRA.
Jira (PUP-9605) Type package (provider yum) fails when handling kernel packages
Title: Message Title Jean Bond updated an issue Puppet / PUP-9605 Type package (provider yum) fails when handling kernel packages Change By: Jean Bond Labels: needs_repro resolved-issue-added 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.303636.1554712703000.100262.1568664600223%40Atlassian.JIRA.
Jira (PUP-9754) Log resident configuration upon daemon launch
Title: Message Title Jean Bond commented on PUP-9754 Re: Log resident configuration upon daemon launch Josh Cooper or Ciprian Badescu, I'm looking for a bit of clarification on the release note. It says: (by default daemon mode can be enabled on POSIX systems and is disabled on Windows) Does the mean daemon mode is enabled by default on POSIX, or it is disabled by default on POSIX and the user can enable it? And for Windows, this says it is disabled by default. Can the user enable it? 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.100200.1568662320377%40Atlassian.JIRA.
Jira (PUP-9956) Exec logs output of Sensitive unless and onlyif checks at debug
Title: Message Title Jean Bond updated an issue Puppet / PUP-9956 Exec logs output of Sensitive unless and onlyif checks at debug Change By: Jean Bond Labels: resolved-issue-added 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.100176.1568661600256%40Atlassian.JIRA.
Jira (PDB-4504) add-resource-events-pk migration does not use batched inserts
Title: Message Title Charlie Sharpsteen updated an issue PuppetDB / PDB-4504 add-resource-events-pk migration does not use batched inserts Change By: Charlie Sharpsteen 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324827.1568659575000.100172.1568661540482%40Atlassian.JIRA.
Jira (PDB-4504) add-resource-events-pk migration does not use batched inserts
Title: Message Title
Charlie Sharpsteen updated an issue
PuppetDB / PDB-4504
add-resource-events-pk migration does not use batched inserts
Change By:
Charlie Sharpsteen
PuppetDB 6.3 added a primary key to the {{resource_events}} table in order tofacilitate functionality such as repacking and partitioning. In order to createa unique key, the hashing algorithm for resource events was changed. Thisresulted in a migration that re-writes the entire table in order to update thehash and remove duplicates. The re-write portion does not use batched insertswhen sending transformed data back to the database, which results in a separate{{INSERT}} statement being executed for each row in the {{resource_events}} table.h2. Reproduction Case - Install PuppetDB 5.2 - Populate Postgres with some test data and enable the pg_stat_statementsextension on the PuppetDB database: https://www.postgresql.org/docs/9.6/pgstatstatements.html - Upgrade to PuppetDB 6.3 and wait for migration 69 to finish - Compare the number of calls to {{INSERT INTO resource_events_transform}} tothe number of rows modified by that query and the number of rows in the{{resource_events}} table:{code:sql}SELECT sum(calls) AS calls, sum(rows) AS rows FROM pg_stat_statements WHERE query ILIKE 'insert into resource_events_transform%';SELECT count(*) FROM resource_events;{code}h3. Outcome{{pg_stat_statements}} shows that the {{INSERT}} is executed once per row inthe {{resource_events}} table:{noformat}pe-puppetdb=# SELECT sum(calls) AS calls, sum(rows) AS rows FROM pg_stat_statements WHERE query ILIKE 'insert into resource_events_transform%';-[ RECORD 1 ]--calls | 5698404rows | 5698404pe-puppetdb=# SELECT count(*) FROM resource_events;-[ RECORD 1 ]--count | 5779611{noformat}h3. Expected OutcomeThe insertion of transformed rows is batched such that the number of callsto {{INSERT}} is a few orders of magnitude smaller than the number of rowsin the {{resource_events}} table.
Add Comment
Jira (PDB-4504) add-resource-events-pk migration does not use batched inserts
Title: Message Title
Charlie Sharpsteen updated an issue
PuppetDB / PDB-4504
add-resource-events-pk migration does not use batched inserts
Change By:
Charlie Sharpsteen
PuppetDB 6.3 added a primary key to the {{resource_events}} table in order tofacilitate functionality such as repacking and partitioning. In order to createa unique key, the hashing algorithm for resource events was changed. Thisresulted in a migration that re-writes the entire table in order to update thehash and remove duplicates. The re-write portion does not use batched insertswhen sending transformed data back to the database, which results in a separate{{INSERT}} statement being executed for each row in the {{resource_events}} table.h2. Reproduction Case - Install PuppetDB 5.2 - Populate Postgres with some test data and [ enable the pg_stat_statementsextension | on thePuppetDB database: https://www.postgresql.org/docs/9.6/pgstatstatements.html ] on the PuppetDB database - Upgrade to PuppetDB 6.3 and wait for migration 69 to finish - Compare the number of calls to {{INSERT INTO resource_events_transform}} tothe number of rows modified by that query and the number of rows in the{{resource_events}} table:{code:sql}SELECT sum(calls) AS calls, sum(rows) AS rows FROM pg_stat_statements WHERE query ILIKE 'insert into resource_events_transform%';SELECT count(*) FROM resource_events;{code}h3. Outcome{{pg_stat_statements}} shows that the {{INSERT}} is executed once per row inthe {{resource_events}} table:{noformat}pe-puppetdb=# SELECT sum(calls) AS calls, sum(rows) AS rows FROM pg_stat_statements WHERE query ILIKE 'insert into resource_events_transform%';-[ RECORD 1 ]--calls | 5698404rows | 5698404pe-puppetdb=# SELECT count(*) FROM resource_events;-[ RECORD 1 ]--count | 5779611{noformat}h3. Expected OutcomeThe insertion of transformed rows is batched such that the number of callsto {{INSERT}} is a few orders of magnitude smaller than the number of rowsin the {{resource_events}} table.
Add Comment
Jira (PUP-8662) puppet plugin download doesn't re-use HTTP connections
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8662 puppet plugin download doesn't re-use HTTP connections Change By: Josh Cooper Fix Version/s: PUP 6.0.11 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.245716.1523666018000.100076.1568660341880%40Atlassian.JIRA.
Jira (PUP-9585) Do not output password for user type if it is marked Sensitive
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9585 Do not output password for user type if it is marked Sensitive Change By: Josh Cooper Fix Version/s: PUP 6.0.11 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.302109.1553793067000.100065.1568660341818%40Atlassian.JIRA.
Jira (PUP-4470) Puppet's http connection factory doesn't support authenticating proxies
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4470 Puppet's http connection factory doesn't support authenticating proxies Change By: Josh Cooper Fix Version/s: PUP 6.0.11 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.77763.1430247156000.100084.1568660341932%40Atlassian.JIRA.
Jira (PUP-5109) Puppet::Resource::Catalog::Compiler#set_server_facts always produces a warning on ipv6 only systems
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5109 Puppet::Resource::Catalog::Compiler#set_server_facts always produces a warning on ipv6 only systems Change By: Josh Cooper Fix Version/s: PUP 6.0.11 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.95553.144084808.100081.1568660341910%40Atlassian.JIRA.
Jira (PUP-9316) implement no_proxy in puppet.conf
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9316 implement no_proxy in puppet.conf Change By: Josh Cooper Fix Version/s: PUP 6.0.11 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.285347.1542320475000.100067.1568660341827%40Atlassian.JIRA.
Jira (PUP-2172) Don't use an http proxy when connecting to localhost
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2172 Don't use an http proxy when connecting to localhost Change By: Josh Cooper Fix Version/s: PUP 6.0.11 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.31144.1396893516000.100086.1568660341945%40Atlassian.JIRA.
Jira (PDB-4504) add-resource-events-pk migration does not use batched inserts
Title: Message Title Charlie Sharpsteen commented on PDB-4504 Re: add-resource-events-pk migration does not use batched inserts The loop resulting in this is here: https://github.com/puppetlabs/puppetdb/blob/6.3.4/src/puppetlabs/puppetdb/scf/migrate.clj#L1543-L1558 There are a couple items that lead to the INSERT being executed once per row: Reduce will iterate over each row in isolation, so there is only one row passed to jdbc/insert-multi!, instead of a batch of many rows. We’re passing a seq of hashes to jdbc/insert-multi! and the docs for that function indicate that will cause a separate database operation per hash of data. Item 1 might be addressed by using Clojure's partition function to chunk the list of rows into batches: http://clojuredocs.org/clojure.core/partition For item 2, the java.jdbc docs indicate that we should pas a seqence of lists of column values to jdbc/insert-multi!: https://github.com/clojure/java.jdbc/blob/java.jdbc-0.7.7/src/main/clojure/clojure/java/jdbc.clj#L1574-L1577 Also, it sounds like getting JDBC to do batched inserts with Postgres requires the :reWriteBatchedInserts option to be set on the database connection: https://github.com/clojure/java.jdbc/blob/java.jdbc-0.7.10/src/main/clojure/clojure/java/jdbc.clj#L1626-L1631 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9942) no_proxy environment variable does not work
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9942 no_proxy environment variable does not work Change By: Josh Cooper Fix Version/s: PUP 6.0.11 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.320046.1565215526000.100057.1568660280498%40Atlassian.JIRA.
Jira (PUP-9959) Add puppet plugin to help output
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9959 Add puppet plugin to help output Change By: Josh Cooper Fix Version/s: PUP 6.0.11 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.317346.1563668147000.100052.1568660280475%40Atlassian.JIRA.
Jira (PUP-9956) Exec logs output of Sensitive unless and onlyif checks at debug
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9956 Exec logs output of Sensitive unless and onlyif checks at debug Change By: Josh Cooper Fix Version/s: PUP 6.0.11 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.100056.1568660280494%40Atlassian.JIRA.
Jira (PUP-8685) Migrate gemspec info in project_data.yaml to the .gemspec file
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8685 Migrate gemspec info in project_data.yaml to the .gemspec file Change By: Josh Cooper Fix Version/s: PUP 4.10.z 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.248730.1525210589000.100011.1568659981832%40Atlassian.JIRA.
Jira (PUP-9216) Puppet agent version 4.10.12 is trying to access multiple VBE files which not even exists
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9216 Puppet agent version 4.10.12 is trying to access multiple VBE files which not even exists Change By: Josh Cooper Fix Version/s: PUP 4.10.z 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.279538.1539101232000.100020.1568659981906%40Atlassian.JIRA.
Jira (PUP-9515) Unable to deploy correct version of package
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9515 Unable to deploy correct version of package Change By: Josh Cooper Fix Version/s: PUP 4.10.z 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.298653.1551903888000.100023.1568659981925%40Atlassian.JIRA.
Jira (PUP-7648) Fix ci:test:git pre-suite on OSX 10.11
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7648 Fix ci:test:git pre-suite on OSX 10.11 Change By: Josh Cooper Fix Version/s: PUP 4.10.z 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.195321.1497140585000.17.1568659981811%40Atlassian.JIRA.
Jira (PDB-4504) add-resource-events-pk migration does not use batched inserts
Title: Message Title
Charlie Sharpsteen updated an issue
PuppetDB / PDB-4504
add-resource-events-pk migration does not use batched inserts
Change By:
Charlie Sharpsteen
PuppetDB 6.3 added a primary key to the ` {{ resource_events ` }} table in order tofacilitate functionality such as repacking and partitioning. In order to createa unique key, the hashing algorithm for resource events was changed. Thisresulted in a migration that re-writes the entire table in order to update thehash and remove duplicates. The re-write portion does not use batched insertswhen sending transformed data back to the database, which results in a seperate separate ` {{ INSERT ` }} statement being executed for each row in the ` {{ resource_events ` }} table.h2. Reproduction Case - Install PuppetDB 5.2 - Populate Postgres with some test data and [enable the pg_stat_statementsextension|https://www.postgresql.org/docs/9.6/pgstatstatements.html] on thePuppetDB database - Upgrade to PuppetDB 6.3 and wait for migration 69 to finish - Compare the number of calls to {{INSERT INTO resource_evetns_transform resource_events_transform }} tothe numer number of rows modified by that query and the number of rows in the{{resource_events}} table:{code:sql}SELECT sum(calls) AS calls, sum(rows) AS rows FROM pg_stat_statements WHERE query ILIKE 'insert into resource_events_transform%';SELECT count(*) FROM resource_events;{code}h3. Outcome{{pg_stat_statements}} shows that the {{INSERT}} is executed once per row inthe {{resource_events}} table:{noformat}pe-puppetdb=# SELECT sum(calls) AS calls, sum(rows) AS rows FROM pg_stat_statements WHERE query ILIKE 'insert into resource_events_transform%';-[ RECORD 1 ]--calls | 5698404rows | 5698404pe-puppetdb=# SELECT count(*) FROM resource_events;-[ RECORD 1 ]--count | 5779611{noformat}h3. Expected OutcomeThe insertion of transformed rows is batched such that the number of callsto {{INSERT}} is a few orders of magnitude smaller than the number of rowsin the {{resource_events}} table.
Add Comment
Jira (PUP-9824) Expand the apt provider to support virtual packages
Title: Message Title Josh Cooper commented on PUP-9824 Re: Expand the apt provider to support virtual packages Mihai Buzgau Alexandru Popa since this issue was released in 6.8.0, please leave this resolved and open a new ticket to add the virtual package support. 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.305263.135711000.4.1568659740587%40Atlassian.JIRA.
Jira (PDB-4504) add-resource-events-pk migration does not use batched inserts
Title: Message Title Charlie Sharpsteen created an issue PuppetDB / PDB-4504 add-resource-events-pk migration does not use batched inserts Issue Type: Bug Affects Versions: PDB 6.5.0, PDB 6.3.4 Assignee: Unassigned Created: 2019/09/16 11:46 AM Priority: Normal Reporter: Charlie Sharpsteen PuppetDB 6.3 added a primary key to the `resource_events` table in order to facilitate functionality such as repacking and partitioning. In order to create a unique key, the hashing algorithm for resource events was changed. This resulted in a migration that re-writes the entire table in order to update the hash and remove duplicates. The re-write portion does not use batched inserts when sending transformed data back to the database, which results in a seperate `INSERT` statement being executed for each row in the `resource_events` table. Reproduction Case Install PuppetDB 5.2 Populate Postgres with some test data and [enable the pg_stat_statements extension|https://www.postgresql.org/docs/9.6/pgstatstatements.html] on the PuppetDB database Upgrade to PuppetDB 6.3 and wait for migration 69 to finish Compare the number of calls to INSERT INTO resource_evetns_transform to the numer of rows modified by that query and the number of rows in the resource_events table:
Jira (PUP-9959) Add puppet plugin to help output
Title: Message Title Jean Bond updated an issue Puppet / PUP-9959 Add puppet plugin to help output Change By: Jean Bond Labels: resolved-issue-added 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.317346.1563668147000.99977.1568659501230%40Atlassian.JIRA.
Jira (PUP-9295) Notify resource exposes Sensitive data when message is a Sensitive data
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9295 Notify resource exposes Sensitive data when message is a Sensitive data Change By: Josh Cooper Fix Version/s: PUP 6.0.z Fix Version/s: PUP 6.4.z 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.283215.1540998541000.99973.1568659501200%40Atlassian.JIRA.
Jira (PUP-8744) Using a variable in a Type on a parameter results in an error unless the variable was already loaded
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8744 Using a variable in a Type on a parameter results in an error unless the variable was already loaded Change By: Josh Cooper Fix Version/s: PUP 6.0.z 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.251122.1526499439000.99982.1568659501302%40Atlassian.JIRA.
Jira (PUP-10020) Failed to transition the pxp-agent service to the SERVICE_RUNNING state
Title: Message Title cody fawcett commented on PUP-10020 Re: Failed to transition the pxp-agent service to the SERVICE_RUNNING state Josh Cooper, The output was provided on the client console when running "puppet agent -t" manually. What you are looking at, at least from what i see, is the failure of the service to to start, and therefore skipping. When this is encountered the pxp-agent service needs to be stopped, then the pxp-agent process needs to be stopped. Then the next call to the pxp-agent service will trigger a start that should be successful. Error: Failed to transition the pxp-agent service to the SERVICE_RUNNING state. Detail: Unexpected transition to the SER VICE_PAUSED state while waiting for the pending transition from SERVICE_CONTINUE_PENDING to SERVICE_RUNNING to finish. Error: /Stage[main]/Puppet_enterprise::Pxp_agent::Service/Service[pxp-agent]/ensure: change from 'paused' to 'running' f ailed: Failed to transition the pxp-agent service to the SERVICE_RUNNING state. Detail: Unexpected transition to the SER VICE_PAUSED state while waiting for the pending transition from SERVICE_CONTINUE_PENDING to SERVICE_RUNNING to finish. ( corrective) 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.324730.1568481726000.99809.1568657100249%40Atlassian.JIRA.
Jira (PUP-10020) Failed to transition the pxp-agent service to the SERVICE_RUNNING state
Title: Message Title Josh Cooper commented on PUP-10020 Re: Failed to transition the pxp-agent service to the SERVICE_RUNNING state cody fawcett I don't see the output "Unexpected transition to" in the pup.log attachment, just: [0;36mDebug: Service[pxp-agent](provider=windows): Service pxp-agent is SERVICE_PAUSED [0m [0;36mDebug: Service[pxp-agent](provider=windows): Service pxp-agent start type is SERVICE_AUTO_START [0m [0;36mDebug: Service[pxp-agent](provider=windows): Service pxp-agent is SERVICE_PAUSED [0m [0;36mDebug: Resuming the pxp-agent service [0m [0;36mDebug: Transitioning the pxp-agent service from SERVICE_PAUSED to SERVICE_RUNNING [0m [0;36mDebug: Waiting for the pending transition to the SERVICE_PAUSED state to finish. [0m [0;36mDebug: Waiting for the transition to finish [0m [0;36mDebug: The service transitioned to the SERVICE_CONTINUE_PENDING state. [0m [0;36mDebug: Waiting for the pending transition to the SERVICE_RUNNING state to finish. [0m [0;36mDebug: Class[Puppet_enterprise::Pxp_agent::Service]: Resource is being skipped, unscheduling all events [0m Also you can run with --no-color to eliminate the ANSI escape
Jira (PUP-10020) Failed to transition the pxp-agent service to the SERVICE_RUNNING state
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10020 Failed to transition the pxp-agent service to the SERVICE_RUNNING state Change By: Josh Cooper Team: Night's Watch 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.324730.1568481726000.99730.1568655300192%40Atlassian.JIRA.
Jira (PUP-10022) confusing behaviour when puppet agent -tv --noo is run
Title: Message Title Josh Cooper commented on PUP-10022 Re: confusing behaviour when puppet agent -tv --noo is run Historically Puppet's CLI supports partial matches, so "-noo" matches "--noop". However, there is a long standing bug that the partial match doesn't get applied, see PUP-2243. The argument "-no" is rejected because it is a partial match for all boolean CLI arguments, e.g. "no-splay", "-no-report", etc. I'm going to mark this as a duplicate of PUP-2243. This is actually a duplicate of 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.323385.1567558313000.99717.1568655120274%40Atlassian.JIRA.
Jira (PUP-10022) confusing behaviour when puppet agent -tv --noo is run
Title: Message Title Josh Cooper moved an issue Puppet / PUP-10022 confusing behaviour when puppet agent -tv --noo is run Change By: Josh Cooper Affects Version/s: puppet-agent 6.8.0 Affects Version/s: PUP 6.8.0 Key: PA PUP - 2881 10022 Project: Puppet Agent 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
Jira (PUP-10021) User resource always reports password changed when account disabled for Win 2012 R2
Title: Message Title Josh Cooper commented on PUP-10021 Re: User resource always reports password changed when account disabled for Win 2012 R2 Moved to PUP project 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.324443.1568255866000.99676.1568654400452%40Atlassian.JIRA.
Jira (PUP-10021) User resource always reports password changed when account disabled for Win 2012 R2
Title: Message Title Josh Cooper moved an issue Puppet / PUP-10021 User resource always reports password changed when account disabled for Win 2012 R2 Change By: Josh Cooper Component/s: Windows Component/s: Windows Key: PA PUP - 2901 10021 Project: Puppet Agent 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
Jira (PUP-10019) file resource checks source even if the file exists and replace is false
Title: Message Title Josh Cooper commented on PUP-10019 Re: file resource checks source even if the file exists and replace is false The file type docs say: Note that this only affects content; Puppet will still manage ownership and permissions. Which means puppet still needs to retrieve the owner/group/mode from the source. 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.324690.1568400128000.99659.1568654220307%40Atlassian.JIRA.
Jira (PUP-9109) File: source attribute broken for HTTP(s) URI's containing query parameters
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9109 File: source attribute broken for HTTP(s) URI's containing query parameters Change By: Josh Cooper Release Notes Summary: Puppet now preserves query parameters when retrieving file metadata and content for http/https file resources. Release Notes: Bug Fix 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.274566.1536231724000.99591.1568651700192%40Atlassian.JIRA.
Jira (PUP-9792) Merge of lookup_options not working
Title: Message Title
Matt Dainty commented on PUP-9792
Re: Merge of lookup_options not working
I've managed to get my example to work by changing manifests/site.pp to just the following:
$bar = 'bar'
notice(lookup('foo'))
Basically by ensuring the top scope variable is set before any lookup() is called, it gets the correct merge behaviour. This does suggest that lookup_options is getting cached for the lifetime of the compile. I'm trying to find where in the code this caching is done but I'm not having much luck so far.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you
Jira (FACT-2024) Replace name.end_with?('.*') with name.include?('.*')
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2024
Replace name.end_with?('.*') with name.include?('.*')
Change By:
Bogdan Irimie
Summary:
Replace name.end_with?('.*') with name. contains include? ('.*')
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.324773.1568644864000.99307.1568645340203%40Atlassian.JIRA.
Jira (FACT-2025) Investigate custom facts
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2025 Investigate custom facts Issue Type: New Feature Assignee: Unassigned Created: 2019/09/16 7:42 AM Priority: Normal Reporter: Bogdan Irimie Investigate how we can integrate custom facts into Facter NG. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-2024) Replace name.end_with?('.*') with name.contains('.*')
Title: Message Title
Bogdan Irimie assigned an issue to Bogdan Irimie
Facter / FACT-2024
Replace name.end_with?('.*') with name.contains('.*')
Change By:
Bogdan Irimie
Assignee:
Bogdan Irimie
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.324773.1568644864000.99297.1568644920703%40Atlassian.JIRA.
Jira (FACT-2024) Replace name.end_with?('.*') with name.contains('.*')
Title: Message Title
Bogdan Irimie created an issue
Facter / FACT-2024
Replace name.end_with?('.*') with name.contains('.*')
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2019/09/16 7:41 AM
Priority:
Normal
Reporter:
Bogdan Irimie
Regex facts can have the regex inside the name of a fact e.g. sshkey blockdevice__model
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1951) Create the git repo, configure travis
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1951 Create the git repo, configure travis Change By: Bogdan Irimie Epic Status: To Do Done 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.316815.1563365672000.99282.1568644620278%40Atlassian.JIRA.
Jira (FACT-1939) Investigate tools that gather facts in order to learn from their implementation
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1939 Investigate tools that gather facts in order to learn from their implementation Change By: Bogdan Irimie Epic Status: To Do Done 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.316643.156328400.99283.1568644620282%40Atlassian.JIRA.
Jira (PUP-9792) Merge of lookup_options not working
Title: Message Title Matt Dainty commented on PUP-9792 Re: Merge of lookup_options not working There's no such option, (on 5.5.16 at least): Error: Could not parse application options: invalid option: --evaluate I'm already using --compile as part of my tests, however I don't get the correct answer with the puppet lookup CLI, nor within a normal catalog compile. Your first comment suggested a lack of cache eviction, my example does suggest the lookup options aren't re-evaluated once the top scope variables are set. 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.313541.1561115342000.99263.1568643240423%40Atlassian.JIRA.
Jira (PUP-9962) stdlib : When ensure_resource() is used, it should correctly report duplicate resource declaration issues with more correct file and line numbers
Title: Message Title Gareth McGrillan updated an issue Puppet / PUP-9962 stdlib : When ensure_resource() is used, it should correctly report duplicate resource declaration issues with more correct file and line numbers Change By: Gareth McGrillan Zendesk Ticket IDs: 35700 Zendesk Ticket Count: 1 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.319159.1564655694000.99167.1568632920400%40Atlassian.JIRA.
Jira (PUP-9471) User management fails on MacOS 10.14 (Mojave)
Title: Message Title Mihai Buzgau assigned an issue to Unassigned Puppet / PUP-9471 User management fails on MacOS 10.14 (Mojave) Change By: Mihai Buzgau Assignee: Octavian Larion 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.294488.1549047148000.99141.1568629740375%40Atlassian.JIRA.
Jira (PUP-10017) Collapse dependency failures into Class level failures
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10017 Collapse dependency failures into Class level failures Change By: Mihai Buzgau Sprint: PR - Triage 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.324379.1568220393000.99132.1568629380973%40Atlassian.JIRA.
Jira (FACT-2018) Google Compute Engine metadata facts need endpoint change
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2018 Google Compute Engine metadata facts need endpoint change Change By: Mihai Buzgau Team: Night's Watch 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.324465.156829223.99107.1568628960215%40Atlassian.JIRA.
Jira (FACT-2018) Google Compute Engine metadata facts need endpoint change
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2018 Google Compute Engine metadata facts need endpoint change Change By: Mihai Buzgau Sprint: PR - Triage 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.324465.156829223.99104.1568628900212%40Atlassian.JIRA.
Jira (FACT-2016) Add the scope of found ipv6 addresses (global/linklocal/...) as a fact
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2016 Add the scope of found ipv6 addresses (global/linklocal/...) as a fact Change By: Mihai Buzgau Sprint: PR - Triage 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.324361.1568209514000.99097.1568628780433%40Atlassian.JIRA.
Jira (FACT-2016) Add the scope of found ipv6 addresses (global/linklocal/...) as a fact
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2016 Add the scope of found ipv6 addresses (global/linklocal/...) as a fact Change By: Mihai Buzgau Team: Night's Watch 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.324361.1568209514000.99095.1568628780425%40Atlassian.JIRA.
Jira (PUP-9999) Puppet::Type.type('yumrepo') wrongly reports enabled repo
Title: Message Title
Mihai Buzgau updated an issue
Puppet / PUP-
Puppet::Type.type('yumrepo') wrongly reports enabled repo
Change By:
Mihai Buzgau
Sprint:
PR - Triage
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.323658.1567695504000.99080.1568628660572%40Atlassian.JIRA.
Jira (FACT-2004) cloud fact does not detect Azure with NetworkManager
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2004 cloud fact does not detect Azure with NetworkManager Change By: Mihai Buzgau Sprint: PR - Triage 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.322752.1567082147000.99076.1568628600848%40Atlassian.JIRA.
Jira (PUP-9978) dnf package provider should support modularity streams
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9978 dnf package provider should support modularity streams Change By: Mihai Buzgau Sprint: PR - Triage 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.322208.1566835009000.99062.1568628480642%40Atlassian.JIRA.
Jira (PUP-9978) dnf package provider should support modularity streams
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9978 dnf package provider should support modularity streams Change By: Mihai Buzgau Team: Night's Watch 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.322208.1566835009000.99057.1568628480614%40Atlassian.JIRA.
Jira (PUP-9471) User management fails on MacOS 10.14 (Mojave)
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9471 User management fails on MacOS 10.14 (Mojave) Change By: Mihai Buzgau Sprint: PR - Triage, PR - 2019-03-06 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.294488.1549047148000.99019.1568628242098%40Atlassian.JIRA.
Jira (PUP-9824) Expand the apt provider to support virtual packages
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9824 Expand the apt provider to support virtual packages Change By: Mihai Buzgau Sprint: PR - 2019-06-12, PR - 2019-06-25, PR - 2019-07-10, PR - 2019-07-23 , NW - 2019-09-18 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.305263.135711000.99026.1568628242148%40Atlassian.JIRA.
Jira (PUP-9978) dnf package provider should support modularity streams
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9978 dnf package provider should support modularity streams Change By: Mihai Buzgau Team: Night's Watch 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.322208.1566835009000.98961.1568624760316%40Atlassian.JIRA.
Jira (FACT-2022) Os name fact for Solaris
Title: Message Title Alexandru Popa assigned an issue to Alexandru Popa Facter / FACT-2022 Os name fact for Solaris Change By: Alexandru Popa Assignee: Alexandru Popa 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.324752.1568622878000.98956.1568624580080%40Atlassian.JIRA.
Jira (PUP-9978) dnf package provider should support modularity streams
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9978 dnf package provider should support modularity streams Change By: Mihai Buzgau Team: Night's Watch 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.322208.1566835009000.98954.1568624220750%40Atlassian.JIRA.
Jira (PUP-9978) dnf package provider should support modularity streams
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9978 dnf package provider should support modularity streams Change By: Mihai Buzgau Team: Night's Watch 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.322208.1566835009000.98941.1568624040302%40Atlassian.JIRA.
Jira (FACT-2023) Implement facts for Solaris
Title: Message Title Alexandru Popa created an issue Facter / FACT-2023 Implement facts for Solaris Issue Type: Epic Assignee: Unassigned Created: 2019/09/16 1:35 AM Priority: Normal Reporter: Alexandru Popa 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
Jira (FACT-2022) Os name fact for Solaris
Title: Message Title Alexandru Popa created an issue Facter / FACT-2022 Os name fact for Solaris Issue Type: Task Assignee: Unassigned Created: 2019/09/16 1:34 AM Priority: Normal Reporter: Alexandru Popa 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
