Jira (PDB-5339) Create docs with manual steps needed to run the entire IAS workflow
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5339 Create docs with manual steps needed to run the entire IAS workflow Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.420291.1634717312000.161146.1634888280041%40Atlassian.JIRA.
Jira (PDB-5314) Extract old catalog from PDB
Title: Message Title
Sebastian Miclea commented on PDB-5314
Re: Extract old catalog from PDB
Get facts for one node:
http://localhost:8080/pdb/query/v4/facts?query=["=", "certname", "host-1"]
Get facts for one node in environment
http://localhost:8080/pdb/query/v4/environments/production/facts?query=["=", "certname", "host-1"]
Get latest catalog for one node in environment:
http://localhost:8080/pdb/query/v4/catalogs?query=["and", ["=","certname","host-1"],["=", "environment", "production"]]_by=[{"field": "producer_timestamp", "order": "desc"}]=1
Add Comment
Jira (PDB-5314) Extract old catalog from PDB
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5314 Extract old catalog from PDB Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.419447.1634111756000.156957.1634541660034%40Atlassian.JIRA.
Jira (PDB-5213) Update PDB to pick up i18n changes from clj-parent
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5213 Update PDB to pick up i18n changes from clj-parent Change By: Sebastian Miclea Fix Version/s: PDB 6.19.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.408750.1627457775000.147094.1633440780026%40Atlassian.JIRA.
Jira (PDB-5216) Add optional query origin field
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5216 Add optional query origin field Change By: Sebastian Miclea Fix Version/s: PDB 6.19.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.408854.1627502694000.147092.1633440720157%40Atlassian.JIRA.
Jira (PDB-5135) PuppetDB should warn about resource titles that exceed Postgres index sizes
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5135 PuppetDB should warn about resource titles that exceed Postgres index sizes Change By: Sebastian Miclea Fix Version/s: PDB 6.19.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.399989.162152585.147093.1633440720200%40Atlassian.JIRA.
Jira (PDB-5235) Supress false positive nvd failure for CVE-2020-36448
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5235 Supress false positive nvd failure for CVE-2020-36448 Change By: Sebastian Miclea Fix Version/s: PDB 6.19.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.412918.1629491442000.147091.1633440720113%40Atlassian.JIRA.
Jira (PDB-5164) Fully document AST field syntax
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5164 Fully document AST field syntax Change By: Sebastian Miclea Fix Version/s: PDB 6.19.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.405083.1624981418000.147089.1633440660141%40Atlassian.JIRA.
Jira (PDB-5203) Script that runs the pdb locust load tests
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5203 Script that runs the pdb locust load tests Change By: Sebastian Miclea Fix Version/s: PDB 6.19.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.408406.162704879.147088.1633440660095%40Atlassian.JIRA.
Jira (PDB-5230) Add simple smoke tests for collected external queries
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5230 Add simple smoke tests for collected external queries Change By: Sebastian Miclea Fix Version/s: PDB 6.19.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.411384.1628624333000.147085.1633440600120%40Atlassian.JIRA.
Jira (PDB-5204) Perform diff on the locust results
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5204 Perform diff on the locust results Change By: Sebastian Miclea Fix Version/s: PDB 6.19.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.408407.1627050042000.147086.1633440600168%40Atlassian.JIRA.
Jira (PDB-5256) Puppet Query should have proper error message when it is failed
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5256 Puppet Query should have proper error message when it is failed Change By: Sebastian Miclea Fix Version/s: PDB 6.19.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.414480.1630996076000.147082.1633440540174%40Atlassian.JIRA.
Jira (PDB-4731) Misspelled query modifiers like groupy_by can result in all results being returned
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-4731 Misspelled query modifiers like groupy_by can result in all results being returned Change By: Sebastian Miclea Fix Version/s: PDB 6.19.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.358865.1589476358000.147081.1633440540128%40Atlassian.JIRA.
Jira (PDB-4985) Querying for trusted on the inventory endpoint doesn't hit the index
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-4985 Querying for trusted on the inventory endpoint doesn't hit the index Change By: Sebastian Miclea Fix Version/s: PDB 6.19.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.380554.1607543476000.147083.1633440540226%40Atlassian.JIRA.
Jira (PDB-5161) Specify and fully validate dotted projections
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5161 Specify and fully validate dotted projections Change By: Sebastian Miclea Fix Version/s: PDB 6.19.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.403713.1623862346000.147079.1633440420030%40Atlassian.JIRA.
Jira (PDB-5217) Restore AST query field parser
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5217 Restore AST query field parser Change By: Sebastian Miclea Fix Version/s: PDB 6.19.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.409105.1627518385000.147078.1633440360082%40Atlassian.JIRA.
Jira (PDB-5283) Document CD4PE environment creation
Title: Message Title Sebastian Miclea commented on PDB-5283 Re: Document CD4PE environment creation Docs added here: https://confluence.puppetlabs.com/display/ETR/Set+up+CD4PE+with+IA Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.416740.1632298148000.141966.1632900060027%40Atlassian.JIRA.
Jira (PDB-5262) Grouping by facts that contain "/" generates invalid SQL
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5262 Grouping by facts that contain "/" generates invalid SQL Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.415600.1631630062000.140663.1632812100188%40Atlassian.JIRA.
Jira (PDB-5283) Document CD4PE environment creation
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5283 Document CD4PE environment creation Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.416740.1632298148000.136366.1632306960050%40Atlassian.JIRA.
Jira (PDB-5262) Grouping by facts that contain "/" generates invalid SQL
Title: Message Title Sebastian Miclea created an issue PuppetDB / PDB-5262 Grouping by facts that contain "/" generates invalid SQL Issue Type: Bug Assignee: Unassigned Created: 2021/09/14 7:34 AM Priority: Normal Reporter: Sebastian Miclea Example query: ["extract",[["function", "count"], "facts.partitions.\/.size"], ["group_by", "facts.partitions.\/.size"]] Result: Unterminated identifier started at position 699 in SQL WITH inactive_nodes AS (SELECT certname FROM certnames WHERE (deactivated IS NOT NULL AND deactivated > '2021-08-31T14:29:44.254Z') OR (expired IS NOT NULL and expired > '2021-08-31T14:29:44.254Z')), not_active_nodes AS (SELECT certname FROM certnames WHERE (deactivated IS NOT NULL OR expired IS NOT NULL)) SELECT (fs.stable||fs.volatile)->'partitions'->'/'->'size' AS "facts.partitions./.size", count(*) count FROM factsets fs LEFT JOIN environments ON fs.environment_id = environments.id LEFT JOIN certnames ON fs.certname = certnames.certname WHERE NOT ((certnames.certname) in (SELECT certname FROM ( SELECT not_active_nodes.certname AS "certname" FROM not_active_nodes ) sub)) GROUP BY .size". Expected " char
Jira (PDB-5204) Perform diff on the locust results
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5204 Perform diff on the locust results Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.408407.1627050042000.117116.1629960900040%40Atlassian.JIRA.
Jira (PDB-5203) Script that runs the pdb locust load tests
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5203 Script that runs the pdb locust load tests Change By: Sebastian Miclea Summary: Script that runs the pdb benchmark locust load tests Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.408406.162704879.115603.1629834120342%40Atlassian.JIRA.
Jira (PDB-5203) Script that runs the pdb benchmark tests
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5203 Script that runs the pdb benchmark tests Change By: Sebastian Miclea The script does: - if a commit SHA is given as a parameter, than it checkouts to that and holds the SHA in a variable, needed to name the results folder. If no SHA is given, it pulls the latest changes from the 6.x branch and copies in a variable the latest commit SHA. - In the locust results folder, create a folder with -. - inside this folder create -another two named ingestion-ON and- ingestion-OFF - inside the two folders create folders -1000, 10.000,- 100.000 and -500.000- - start pdb - after pdb started, run locust in the needed results folders (the --csv parameter accepts folder paths) with all queries, with a warmup with one user, another one with -1 user, 10- -users- and 20 users. - -go to n1 server and start the benchmark with (30 min run interval, 30% data change) and the appropriate number of hosts, depending on the sandbox that's used.- - -go to the ingestion results folder and start locust again with the same settings.- - -kill the benchmark after locust is done.- - kill pdb. - inside the results folder delete the delete all files except the .html, _stats.csv and _failures.csv (not sure if we need those). Also the warmup files must be deleted. - Check the _failures.csv files, and if they are empty, delete them.-!!! For the 500.000 sandbox you need to change the main sandboxes path.- Add Comment This message was sent by Atlassian Jira
Jira (PDB-5227) Don't send reports to be stored by PDB if the index size for resource event is exceeded
Title: Message Title Sebastian Miclea commented on PDB-5227 Re: Don't send reports to be stored by PDB if the index size for resource event is exceeded I've set up a PR with the changes needed in the termini in order to stop sending reports if one of the resource events hits the upper limit for the `resource_events_resource_timestamp_z` index. An error will be printed with all the details related to the resource that is oversized and caused the error. Also, I noticed that currently the resource event is not saved if the error is thrown on insert, but the the resource is still saved in the database. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.411137.1628503417000.107985.1629111660033%40Atlassian.JIRA.
Jira (PDB-3715) PuppetDB doesn't complete shutdown after migration fails
Title: Message Title Sebastian Miclea assigned an issue to Unassigned PuppetDB / PDB-3715 PuppetDB doesn't complete shutdown after migration fails Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.216460.1508186567000.106868.1628841960047%40Atlassian.JIRA.
Jira (PDB-3715) PuppetDB doesn't complete shutdown after migration fails
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-3715 PuppetDB doesn't complete shutdown after migration fails Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.216460.1508186567000.106866.1628841900026%40Atlassian.JIRA.
Jira (PDB-5203) Script that runs the pdb benchmark tests
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5203 Script that runs the pdb benchmark tests Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.408406.162704879.106862.1628840160042%40Atlassian.JIRA.
Jira (PDB-5135) PuppetDB should warn about resource titles that exceed Postgres index sizes
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5135 PuppetDB should warn about resource titles that exceed Postgres index sizes Change By: Sebastian Miclea Release Notes: Not Needed Enhancement Release Notes Summary: On the resource_events_resource_*z partial has the multicolumn resource_events_resource_timestamp_xz index (timestamp, title and type) that is limited to 2712 bytes for postgres versions up to 11. Starting with postgres 12, the index size was reduced with 8 bytes. Having resource events that exceed this limit will cause PDB to fail to insert the row without to many info about what and where is the resource that caused the error. This pr adds extra logs with details to allow easier debugging. There are two messages printed, when the index is close to the limit (between 2500 and 2704) and when the limit is exceeded (over 2704). Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet
Jira (PDB-5135) PuppetDB should warn about resource titles that exceed Postgres index sizes
Title: Message Title Sebastian Miclea commented on PDB-5135 Re: PuppetDB should warn about resource titles that exceed Postgres index sizes Charlie Sharpsteen I've set up a PR fir the PupetDB termini that logs a message when the index limit is reached. With Rob Browning suggestion I've added a second log to warn that the size is near the limit. Currently I'm looking if it's possible to add the message from PDB, because for me, it's a bit confusing to have one error in pdb and one in puppetserver. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.399989.162152585.91198.1627393920185%40Atlassian.JIRA.
Jira (PDB-4985) Querying for trusted on the inventory endpoint doesn't hit the index
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-4985 Querying for trusted on the inventory endpoint doesn't hit the index Change By: Sebastian Miclea Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.380554.1607543476000.90908.1627371300040%40Atlassian.JIRA.
Jira (PDB-5135) PuppetDB should warn about resource titles that exceed Postgres index sizes
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5135 PuppetDB should warn about resource titles that exceed Postgres index sizes Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.399989.162152585.84960.1626780240030%40Atlassian.JIRA.
Jira (PDB-5159) Change filenames from PDB export to be compatible with stockpile
Title: Message Title
Sebastian Miclea updated an issue
PuppetDB / PDB-5159
Change filenames from PDB export to be compatible with stockpile
Change By:
Sebastian Miclea
PDB exports contains factsets, reports and catalogs with names in the fallowing format{code}-.json{code}for catalogs and reports and{code}.json{code}for fact sets.Stockpile is configured in PDB to accept files in the following format:{code}-< unit unix timestamp>___.json{code}e.g.:{code}4-1614247283080_catalog_9_host-1.json{code}We should change the names in the PDB export to be compatible with stockpile. We might add a flag to the work already done in PDB-5095 that will allow the file names to be changed in stockpile format or be kept as they are.
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
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
Jira (PDB-5159) Change filenames from PDB export to be compatible with stockpile
Title: Message Title
Sebastian Miclea updated an issue
PuppetDB / PDB-5159
Change filenames from PDB export to be compatible with stockpile
Change By:
Sebastian Miclea
PDB exports contains factsets, reports and catalogs with names in the fallowing format {code} -.json{code} for catalogs and reports and {code} .json{code} for fact sets. Stockpile is configured in PDB to accept files in the fallowing following format:{code} -___.json{code}e.g.:{code} 4-1614247283080_catalog_9_host-1.json{code} We should change the names in the PDB export to be compatible with stockpile. We might add a flag to the work already done in PDB-5095 that will allow the file names to be changed in stockpile format or be kept as they are.
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
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
Jira (PDB-5159) Change filenames from PDB export to be compatible with stockpile
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5159 Change filenames from PDB export to be compatible with stockpile Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.403562.1623830393000.69756.1625044980031%40Atlassian.JIRA.
Jira (PDB-5104) Fix schemas that don't handle to_string function data
Title: Message Title
Sebastian Miclea updated an issue
PuppetDB / PDB-5104
Fix schemas that don't handle to_string function data
Change By:
Sebastian Miclea
Validation done by the row-schema for fact-contents endpoint ( [ https://github.com/puppetlabs/puppetdb/blob/6.x/src/puppetlabs/puppetdb/query/fact_contents.clj#L10-L24 ] )fails for rows on which we apply the to_string function.We also need to make sure that there are no other schemas that might throw errors because of this.This can be reproduced with this query: {code:java} ["extract", [["function", "to_string", "value" , "999" ]], ["=","name", "uptime_seconds"]]{code}on the facts endpoint.If you add a formatting mask, like "9,999", the query won't fail, but no result is given. Do we need a default formatting mask for integers?*There is a disabled unit test with this ticket id. It has to be enabled once this is fixed.*
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
You received this message because you are
Jira (PDB-5104) Fix schemas that don't handle to_string function data
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5104 Fix schemas that don't handle to_string function data Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.394788.1617986536000.59101.1623916920033%40Atlassian.JIRA.
Jira (PDB-5061) Empty password causes schema exception for migrator-password
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5061 Empty password causes schema exception for migrator-password Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.390948.1615578764000.37187.1621493580042%40Atlassian.JIRA.
Jira (PDB-5094) Add some initial query tests
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5094 Add some initial query tests Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.394361.1617754897000.20324.1619608380042%40Atlassian.JIRA.
Jira (PDB-5053) Move sync expired resource_event filter to report ingest
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5053 Move sync expired resource_event filter to report ingest Change By: Sebastian Miclea Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.389887.1614814159000.4269.1617885900060%40Atlassian.JIRA.
Jira (PDB-5100) sub1
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5100 sub1 Change By: Sebastian Miclea Team: Ghost Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.394614.161788568.4265.1617885780238%40Atlassian.JIRA.
Jira (PDB-5053) Move sync expired resource_event filter to report ingest
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5053 Move sync expired resource_event filter to report ingest Change By: Sebastian Miclea Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.389887.1614814159000.4267.1617885780328%40Atlassian.JIRA.
Jira (PDB-5101) sub2
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5101 sub2 Change By: Sebastian Miclea Team: Ghost Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.394615.1617885694000.4266.1617885780284%40Atlassian.JIRA.
Jira (PDB-5100) sub1
Title: Message Title Sebastian Miclea created an issue PuppetDB / PDB-5100 sub1 Issue Type: Sub-task Assignee: Unassigned Created: 2021/04/08 5:41 AM Priority: Normal Reporter: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 (PDB-5101) sub2
Title: Message Title Sebastian Miclea created an issue PuppetDB / PDB-5101 sub2 Issue Type: Sub-task Assignee: Unassigned Created: 2021/04/08 5:41 AM Priority: Normal Reporter: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 (PDB-5053) Move sync expired resource_event filter to report ingest
Title: Message Title Sebastian Miclea commented on PDB-5053 Re: Move sync expired resource_event filter to report ingest On a more detailed look, when implementing the filter for resource_events we've noticed that there are a lot of tests that use hard coded dates (example [here|puppetdb/reports.clj at PDB-5053 · sebastian-miclea/puppetdb (github.com)]). This is quite a big problem because at the moment all resource-events are expired and we have about 600 tests failing for similar reasons. We need to find a way to have the timestamps dynamically created so they would be relevant to the tests. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.389887.1614814159000.35.1617353940031%40Atlassian.JIRA.
Jira (PDB-5053) Move sync expired resource_event filter to report ingest
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5053 Move sync expired resource_event filter to report ingest Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.389887.1614814159000.170341.1616157720037%40Atlassian.JIRA.
Jira (FACT-2963) Facter 4 outputs networking facts differently on AIX
Title: Message Title Sebastian Miclea commented on FACT-2963 Re: Facter 4 outputs networking facts differently on AIX This output is consistent with the other resolvers implemented for MacOs an Linux. For Solaris we've created FACT-2981 to address the inconsistency. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.390824.1615557133000.166957.1615901580031%40Atlassian.JIRA.
Jira (FACT-2981) Loopback IPv6 ip is not returned correctly
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2981 Loopback IPv6 ip is not returned correctly Issue Type: Bug Assignee: Unassigned Created: 2021/03/16 6:31 AM Priority: Normal Reporter: Sebastian Miclea In the IPv6 short notation `::` represents unspecified and `::1` represents loopback ip. Tested on solaris-11-x86_64 Output for networking.interfaces.lo0.bindings6.network and networking.interfaces.lo0.bindings6.address is `::` and should be `::1` according to the definition above. Facter3 does not output IPv6 on solaris at all. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2963) Facter 4 outputs networking facts differently on AIX
Title: Message Title Sebastian Miclea commented on FACT-2963 Re: Facter 4 outputs networking facts differently on AIX In the IPv6 short notation `::` represents unspecified and `::1` represents loopback ip. We've encountered this bug in Facter3 when implementing FACT-2878 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.390824.1615557133000.166930.1615900740030%40Atlassian.JIRA.
Jira (PDB-5023) Replace deprecated dujour check-for-updates!
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5023 Replace deprecated dujour check-for-updates! Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.387174.1613063499000.151598.1614239160027%40Atlassian.JIRA.
Jira (PDB-5019) Document setup creation
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5019 Document setup creation Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.386970.1612971013000.149023.1614065461155%40Atlassian.JIRA.
Jira (FACT-2878) Networking fact improvements for Aix
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-2878 Networking fact improvements for Aix Change By: Sebastian Miclea Release Notes: Bug Fix Release Notes Summary: Updated AIX networking resolver to use FFI to detect networking interfaces and IPs. Before this fix, VLANs and secondary IPs were not displayed. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379328.1606498722000.133053.1612435920028%40Atlassian.JIRA.
Jira (PDB-3418) Add a new-fact-time metric to complement the new-catalog-time metric
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-3418 Add a new-fact-time metric to complement the new-catalog-time metric Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.184154.1491345864000.130559.1612253880030%40Atlassian.JIRA.
Jira (FACT-2878) Networking fact improvements for Aix
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2878 Networking fact improvements for Aix Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379328.1606498722000.112642.1610438220029%40Atlassian.JIRA.
Jira (FACT-2861) Acceptance test for partial cache invalidation
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2861 Acceptance test for partial cache invalidation Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.378477.160552265.96933.1607943780032%40Atlassian.JIRA.
Jira (FACT-2857) Acceptance test for cache with user query
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-2857 Acceptance test for cache with user query Change By: Sebastian Miclea *Use case:* Create a custom group with a structured core fact and a custom fact. Add a long TTLS for the group. * request the core fact ** check if the value returned is correct ** check it is the only fact in cache ** check it cached the value that it printed * request the core fact again ** check it prints the value from the cache* request the custom fact ** check if the value is correct ** check it is the only value in the cache ** check it cached the value that it printed* request the custom fact again** check it prints the value from the cache * request both facts with to_hash ** check both facts are written to the cache file * request the custom fact ** check it prints the value from the cache ** check the cache did not change ** check the core fact value from the cache did not change * request the core fact ** check it prints the value from the cache ** check the cache did not change ** check the custom fact value from the cache did not change Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2865) Acceptance test for consistent caching
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2865 Acceptance test for consistent caching Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.378497.1605536748000.97862.1608016140033%40Atlassian.JIRA.
Jira (FACT-2895) Add networking.primary6 fact
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2895 Add networking.primary6 fact Issue Type: New Feature Assignee: Unassigned Components: Facter 4 Created: 2020/12/09 3:35 AM Priority: Normal Reporter: Sebastian Miclea Add a new fact that shows the primary interface for ipv6 only systems. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2887) retrieve_default_interface uses incorrect method and doesn't work when IPv6-only
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2887 retrieve_default_interface uses incorrect method and doesn't work when IPv6-only Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379995.1607224967000.92198.1607339280027%40Atlassian.JIRA.
Jira (FACT-2886) networking.interfaces fact not appearing
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2886 networking.interfaces fact not appearing Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379783.1606999223000.91378.1607070420044%40Atlassian.JIRA.
Jira (FACT-2858) Acceptance test for cache migration from Facter 3 to Facter 4
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2858 Acceptance test for cache migration from Facter 3 to Facter 4 Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.378290.1605282375000.86932.1606336920097%40Atlassian.JIRA.
Jira (FACT-2858) Acceptance test for cache migration from Facter 3 to Facter 4
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-2858 Acceptance test for cache migration from Facter 3 to Facter 4 Change By: Sebastian Miclea Create a cache file with a tested fact in the Facter 3 format. In facter.conf set the same fact to be cached by Facter 4 with a large TTLS * run Facter 4 with cache configured ** check if the cache file was invalidated and recreated by Facter 4 ** check the cache file contains "cache_format_version": 1 ** check the fact value was written to the cache ** check that the old value from the Facter 3 formatted cache is no longer in the cache * run Facter 4 with no config file ** check we have a fact value and it is read from the system ** check the cache file was not changed * run Facter 4 with config ** check the cache file did not changed change ** check it prints the value from the cache Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups
Jira (FACT-2306) Add support for AWS IMDSv2
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2306 Add support for AWS IMDSv2 Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.342859.1579626792000.86262.1606253640035%40Atlassian.JIRA.
Jira (FACT-2857) Acceptance test for cache with user query
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-2857 Acceptance test for cache with user query Change By: Sebastian Miclea *Use case:* Create a custom group with a structured core fact and a custom fact. Add a long TTLS for the group. * request the core fact ** check if the value returned is correct ** check it is the only fact in cache ** check it cached the value that it printed * request the core fact again ** check it prints the value from the cache ** request the custom fact ** check if the value is correct ** check it is the only value in the cache ** check it cached the value that it printed * request the custom fact again * * check it prints the value from the cache ** request both facts with to_hash * * * check both facts are written to the cache file * request the custom fact ** check it prints the value from the cache ** check the cache did not change ** check the core fact value from the cache did not change * request the core fact ** check it prints the value from the cache ** check the cache did not change ** check the custom fact value from the cache did not change Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2857) Acceptance test for cache with user query
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2857 Acceptance test for cache with user query Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.378287.1605280544000.82656.1605770400033%40Atlassian.JIRA.
Jira (FACT-2866) Acceptance test for uptime fact/group
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-2866 Acceptance test for uptime fact/group Change By: Sebastian Miclea Sprint: ghost-11.11 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.378647.1605598046000.80861.1605598080116%40Atlassian.JIRA.
Jira (FACT-2866) Acceptance test for uptime fact/group
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2866 Acceptance test for uptime fact/group Issue Type: Task Assignee: Sebastian Miclea Created: 2020/11/16 11:27 PM Priority: Normal Reporter: Sebastian Miclea Cache uptime. Request uptime_seconds. In cache you should have uptime_seconds. Then ask for uptime. The cache should first contain uptime_seconds and after the second call it must contain uptime. Request all facts with facter.conf. In uptime cache you should have all system_uptime facts and all legacy uptime facts. Request all facts with facter.conf again, cache must not change. Request different system_uptime facts and cache must not change. Cache some fact groups that contain missing facts on the current machine (i.e. networking with missing networking.dhcp), then request all facts repeatedly. The cache file’s modification date must not change. Add Comment
Jira (FACT-2847) Facter 4 breaks rspec on fact test
Title: Message Title Sebastian Miclea commented on FACT-2847 Re: Facter 4 breaks rspec on fact test If should also work fine for Puppet5 if you remove the constraint from .sync.yml. Puppet 6 should use the newest Facter gem and, Puppet 5 should download according to the constraint (>2.0.1, <4) Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376201.1603820546000.73765.1604648760030%40Atlassian.JIRA.
Jira (FACT-2850) Failed fact inside a structured custom fact is shown as null
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2850 Failed fact inside a structured custom fact is shown as null Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.377154.1604503217000.73764.1604648580027%40Atlassian.JIRA.
Jira (FACT-2296) Define block group that includes all legacy facts
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-2296 Define block group that includes all legacy facts Change By: Sebastian Miclea Release Notes Summary: We've added a new group called 'legacy' that can be blocked using facter.conf. This group contains all the legacy facts and can be found in: lib/facter/config.rb Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.342118.1579084428000.72756.1604583120111%40Atlassian.JIRA.
Jira (FACT-2296) Define block group that includes all legacy facts
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-2296 Define block group that includes all legacy facts Change By: Sebastian Miclea Release Notes: Not Needed Enhancement Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.342118.1579084428000.72752.1604582940031%40Atlassian.JIRA.
Jira (FACT-2847) Facter 4 breaks rspec on fact test
Title: Message Title Sebastian Miclea commented on FACT-2847 Re: Facter 4 breaks rspec on fact test Martin Alfke, yes unfortunately Facter 4 cannot run with Puppet5. Puppet5 has the Facter dependency locked to > 2.0.1, < 4 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376201.1603820546000.70260.1604415840033%40Atlassian.JIRA.
Jira (FACT-2847) Facter 4 breaks rspec on fact test
Title: Message Title Sebastian Miclea commented on FACT-2847 Re: Facter 4 breaks rspec on fact test Hi Martin Alfke, We had an other more in depth look at this case and understood what happens. My first suggestion for the fix (moving the Facter.fact(:os) the before block) is still correct and will be required in order to have this test working. We found out that the second failure you had, with uname being called, was caused by a bug in how values were reset. The good news is that that was already fixed in 4.0.43. Running the tests using the latest Facter should have this test passing. Let us know if you encounter any other issues. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376201.1603820546000.69123.1604329140029%40Atlassian.JIRA.
Jira (FACT-2847) Facter 4 breaks rspec on fact test
Title: Message Title Sebastian Miclea commented on FACT-2847 Re: Facter 4 breaks rspec on fact test Hi Martin Alfke, It looks to me that there is something else in your test framework that makes makes some extra calls to Facter::Core::Execution. I could not manage to reproduce the second error on my machine, but managed to have the test passing with a generic stub to Facter::Core::Execution. Try adding allow(Facter::Core::Execution).to receive(:execute) to your before block. If you have multiple tests failing, I would suggest adding it to spec_helper so it won't create any syscalls while running tests. Let me know if this works out for you. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376201.1603820546000.67965.1604054820027%40Atlassian.JIRA.
Jira (FACT-2847) Facter 4 breaks rspec on fact test
Title: Message Title
Sebastian Miclea commented on FACT-2847
Re: Facter 4 breaks rspec on fact test
Hi Martin Alfke, I had a look over your fact and noticed that the stub for Facter.fact('os') is defined in the after block and it's not getting stubbed before running the test. Moving it to the before block should fix it. The error occurs because Facter4 uses Facter::Core::Execution to detect the os in order to be able to confine the custom fact. It passed on previous versions of Facter because 2.x used RbConfig to detect the current os and Facter3 used CMake. Let me know if this works out.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
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.376201.1603820546000.67027.160397792%40Atlassian.JIRA.
Jira (FACT-2847) Facter 4 breaks rspec on fact test
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2847 Facter 4 breaks rspec on fact test Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376201.1603820546000.65951.1603878660030%40Atlassian.JIRA.
Jira (FACT-2839) Fix to_hash performance for OSX platform
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2839 Fix to_hash performance for OSX platform Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.375222.1603109274000.60205.1603288680079%40Atlassian.JIRA.
Jira (FACT-2836) Release 4.0.44
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2836 Release 4.0.44 Issue Type: Task Assignee: Bogdan Irimie Created: 2020/10/14 6:37 AM Priority: Normal Reporter: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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-10717) When query for a specific fact with puppet facts show there are 3 additional puppet specific facts displayed
Title: Message Title Sebastian Miclea updated an issue Puppet / PUP-10717 When query for a specific fact with puppet facts show there are 3 additional puppet specific facts displayed Change By: Sebastian Miclea Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.374909.1602681076000.55456.1602682560025%40Atlassian.JIRA.
Jira (PUP-10716) Fix json output of puppet facts show action
Title: Message Title Sebastian Miclea updated an issue Puppet / PUP-10716 Fix json output of puppet facts show action Change By: Sebastian Miclea Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.374908.160268028.55455.1602682260029%40Atlassian.JIRA.
Jira (PUP-10715) Make show action the default one for puppet facts
Title: Message Title Sebastian Miclea updated an issue Puppet / PUP-10715 Make show action the default one for puppet facts Change By: Sebastian Miclea Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.374906.1602680047000.55452.1602682020026%40Atlassian.JIRA.
Jira (FACT-2834) Hardcoded proc0 processor name in resolvers/aix/architecture_resolver.rb and related files
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-2834 Hardcoded proc0 processor name in resolvers/aix/architecture_resolver.rb and related files Change By: Sebastian Miclea Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.374371.1602155342000.55451.1602681780027%40Atlassian.JIRA.
Jira (FACT-1846) inconsistent results between facter and puppet facts
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-1846 inconsistent results between facter and puppet facts Change By: Sebastian Miclea Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.246793.1524245996000.55447.1602681300047%40Atlassian.JIRA.
Jira (FACT-2826) Implement Facter.flush
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2826 Implement Facter.flush Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.373811.1601648662000.53340.160250463%40Atlassian.JIRA.
Jira (FACT-2806) Investigate differences on EL
Title: Message Title Sebastian Miclea commented on FACT-2806 Re: Investigate differences on EL Double checked mountpoints and values are ok. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.372631.1600697197000.48494.1601878620035%40Atlassian.JIRA.
Jira (FACT-2810) Investigate differences on Sles
Title: Message Title Sebastian Miclea commented on FACT-2810 Re: Investigate differences on Sles Double checked mountpoints and values are ok. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.372635.1600697615000.48493.1601878560034%40Atlassian.JIRA.
Jira (FACT-2815) Timing on cached facts is inconsistent, sometime it is displayed, others it is not
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2815 Timing on cached facts is inconsistent, sometime it is displayed, others it is not Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.372973.1600962322000.47687.1601644020026%40Atlassian.JIRA.
Jira (FACT-2809) Investigate differences on Solaris
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2809 Investigate differences on Solaris Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.372634.1600697539000.46958.1601551920034%40Atlassian.JIRA.
Jira (FACT-2807) Investigate differences on Aix
Title: Message Title Sebastian Miclea commented on FACT-2807 Re: Investigate differences on Aix Everything is correct on Facter 4. Values are read from df. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.372632.1600697236000.46949.1601549400024%40Atlassian.JIRA.
Jira (FACT-2807) Investigate differences on Aix
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2807 Investigate differences on Aix Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.372632.1600697236000.46947.1601549160032%40Atlassian.JIRA.
Jira (FACT-2787) fact name are treated as regex and can lead to caching of unwanted facts
Title: Message Title Sebastian Miclea commented on FACT-2787 Re: fact name are treated as regex and can lead to caching of unwanted facts Works as expected. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.370595.159861601.45957.1601447460031%40Atlassian.JIRA.
Jira (FACT-2787) fact name are treated as regex and can lead to caching of unwanted facts
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2787 fact name are treated as regex and can lead to caching of unwanted facts Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.370595.159861601.44148.1601294100028%40Atlassian.JIRA.
Jira (FACT-2808) Investigate differences on OSX
Title: Message Title
Sebastian Miclea updated an issue
Facter / FACT-2808
Investigate differences on OSX
Change By:
Sebastian Miclea
osx1015-64a{"facterversion"=> \ \ {:facter4=>"\"4.0.38\"", :facter3=>"\"3.14.14\""} , "load_averages.15m"=> \{:facter4=>"0.97", :facter3=>"0.9736328125"}, "load_averages.1m"=> \{:facter4=>"1.42", :facter3=>"1.4951171875"}, "load_averages.5m"=> \{:facter4=>"1.31", :facter3=>"1.3173828125"}, "memory.system.available"=> \{:facter4=>"\"947.71 MiB\"", :facter3=>"\"953.27 MiB\""}, "memory.system.available_bytes"=> \{:facter4=>"993746944", :facter3=>"999579648"}, "memory.system.capacity"=> \{:facter4=>"\"76.86%\"", :facter3=>"\"76.73%\""}, "memory.system.used_bytes"=> \{:facter4=>"3301220352", :facter3=>"3295387648"}, "memoryfree"=> \{:facter4=>"\"947.71 MiB\"", :facter3=>"\"953.27 MiB\""}, "memoryfree_mb"=> \{:facter4=>"947.71", :facter3=>"953.2734375"}, " mountpoints./.available"=> \{:facter4=>"\"24.66 GiB\"", :facter3=>"\"29.72 GiB\""}, "mountpoints./.available_bytes"=> \{:facter4=>"26480476160", :facter3=>"31916617728"}, "mountpoints./.capacity"=> \{:facter4=>"\"38.04%\"", :facter3=>"\"57.25%\""}, "mountpoints./.options.0"=> \{:facter4=>"\"read-only\"", :facter3=>"\"readonly\""}, "mountpoints./.used"=> \{:facter4=>"\"15.14 GiB\"", :facter3=>"\"39.80 GiB\""}, "mountpoints./.used_bytes"=> \{:facter4=>"16259440640", :facter3=>"42739916800"}, "mountpoints./System/Volumes/Data.available"=> \{:facter4=>"\"24.66 GiB\"", :facter3=>"\"35.40 GiB\""}, "mountpoints./System/Volumes/Data.available_bytes"=> \{:facter4=>"26480476160", :facter3=>"38014808064"}, "mountpoints./System/Volumes/Data.capacity"=> \{:facter4=>"\"38.04%\"", :facter3=>"\"52.93%\""}, "mountpoints./System/Volumes/Data.used"=> \{:facter4=>"\"15.14 GiB\"", :facter3=>"\"39.80 GiB\""}, "mountpoints./System/Volumes/Data.used_bytes"=> \{:facter4=>"16259440640", :facter3=>"42739916800"}, "mountpoints./Volumes/puppet-agent-6.18.0.62.g8020ea999-1.osx10.15.capacity"=> \{:facter4=>"\"83.09%\"", :facter3=>"\"85.53%\""}, "mountpoints./Volumes/puppet-agent-6.18.0.62.g8020ea999-1.osx10.15.options.0"=> \{:facter4=>"\"read-only\"", :facter3=>"\"readonly\""}, "mountpoints./Volumes/puppet-agent-6.18.0.62.g8020ea999-1.osx10.15.options.2"=> \{:facter4=>"\"nodev\"", :facter3=>"\"local\""}, "mountpoints./Volumes/puppet-agent-6.18.0.62.g8020ea999-1.osx10.15.options.3"=> \{:facter4=>"\"local\"", :facter3=>"\"nodev\""}, "mountpoints./Volumes/puppet-agent-6.18.0.62.g8020ea999-1.osx10.15.used"=> \{:facter4=>"\"38.38 MiB\"", :facter3=>"\"46.19 MiB\""}, "mountpoints./Volumes/puppet-agent-6.18.0.62.g8020ea999-1.osx10.15.used_bytes"=> \{:facter4=>"40239104", :facter3=>"48431104"}, "mountpoints./private/var/vm.available"=> \{:facter4=>"\"24.66 GiB\"", :facter3=>"\"39.80 GiB\""}, "mountpoints./private/var/vm.available_bytes"=> \{:facter4=>"26480476160", :facter3=>"42738847744"}, "mountpoints./private/var/vm.capacity"=> \{:facter4=>"\"38.04%\"", :facter3=>"\"50.00%\""}, "mountpoints./private/var/vm.used"=> \{:facter4=>"\"15.14 GiB\"",
Jira (FACT-2432) Fix env dependant tests
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2432 Fix env dependant tests Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348803.1583426703000.40291.1600784520030%40Atlassian.JIRA.
Jira (FACT-2324) Extend Facter 4.x API with loadfacts
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2324 Extend Facter 4.x API with loadfacts Change By: Sebastian Miclea Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.344090.1580306242000.39444.1600698840029%40Atlassian.JIRA.
Jira (FACT-2811) Refactor unit tests so they can be run with --order rand
Title: Message Title
Sebastian Miclea created an issue
Facter / FACT-2811
Refactor unit tests so they can be run with --order rand
Issue Type:
Task
Assignee:
Unassigned
Created:
2020/09/21 7:30 AM
Labels:
platform_7
Priority:
Normal
Reporter:
Sebastian Miclea
I ran rspec 10 times and these are the aggregated results on which unit tests fail when running randomly. { "./spec/framework/core/options/option_store_spec.rb"=>[15], "./spec/facter/facts/linux/is_virtual_spec.rb"=>[154, 170, 139], "./spec/facter/facts/solaris/virtual_spec.rb"=>[62, 30], "./spec/facter/resolvers/windows/virtualization_resolver_spec.rb"=> [64, 220, 216, 116, 204, 208, 184, 36, 164, 68, 160, 88, 92, 40], "./spec/facter/facts/solaris/is_virtual_spec.rb"=>[30, 62, 148], "./spec/facter/facter_spec.rb"=>[234, 253], "./spec/facter/resolvers/virt_what_spec.rb"=>[44, 53, 29], "./spec/facter/resolvers/partitions_spec.rb"=>[148, 158, 119], "./spec/custom_facts/util/config_spec.rb"=>[83, 67, 55, 75, 16], "./spec/framework/logging/logger_spec.rb"=> [205, 83, 103, 195, 175, 149, 129, 245, 239, 213], "./spec/custom_facts/util/collection_spec.rb"=> [207, 51, 125, 133, 129, 287, 295, 235, 229, 262, 256, 248], "./spec/framework/config/config_reader_spec.rb"=> [116, 126, 22, 31, 41, 155, 145, 69, 59, 87, 97, 174, 184], "./spec/framework/core/fact/internal/internal_fact_manager_spec.rb"=> [102, 118, 108], "./spec/custom_facts/util/directory_loader_spec.rb"=> [18, 51, 70, 32, 77, 41, 109, 93], "./spec/facter/resolvers/open_vz_spec.rb"=>[65] }
Jira (FACT-2810) Investigate differences on Sles
Title: Message Title
Sebastian Miclea created an issue
Facter / FACT-2810
Investigate differences on Sles
Issue Type:
Task
Assignee:
Unassigned
Created:
2020/09/21 7:13 AM
Labels:
platform_7
Priority:
Normal
Reporter:
Sebastian Miclea
sles15-64a {"blockdevice_sda_size"=> \{:facter4=>"\"21474836480\"", :facter3=>"21474836480"} , "blockdevice_sr0_size"=> {:facter4=>"\"1073741312\"", :facter3=>"1073741312"}, "facterversion"=> {:facter4=>"\"4.0.38\"", :facter3=>"\"3.14.14\""}, "memory.swap.capacity"=> {:facter4=>"\"0.00%\"", :facter3=>"\"0%\""}, "memory.system.available"=> {:facter4=>"\"4.58 GiB\"", :facter3=>"\"5.21 GiB\""}, "memory.system.available_bytes"=> {:facter4=>"4913582080", :facter3=>"5589979136"}, "memory.system.capacity"=> {:facter4=>"\"2.42%\"", :facter3=>"\"10.46%\""}, "memory.system.used"=> {:facter4=>"\"144.35 MiB\"", :facter3=>"\"622.44 MiB\""}, "memory.system.used_bytes"=> {:facter4=>"151359488", :facter3=>"652673024"}, "memoryfree"=> {:facter4=>"\"4.58 GiB\"", :facter3=>"\"5.21 GiB\""}, "memoryfree_mb"=> {:facter4=>"4685.96", :facter3=>"5331.01953125"}, "memorysize_mb"=> {:facter4=>"5953.46", :facter3=>"5953.45703125"}, "mountpoints./dev.available_bytes"=> {:facter4=>"3113791488", :facter3=>"3113795584"}, "mountpoints./dev.capacity"=> {:facter4=>"\"0.00%\"", :facter3=>"\"0%\""}, "mountpoints./dev.used"=> {:facter4=>"\"4.00 KiB\"", :facter3=>"\"0 bytes\""}, "mountpoints./dev.used_bytes"=> {:facter4=>"4096", :facter3=>"0"}, "swapfree_mb"=> {:facter4=>"1208.98", :facter3=>"1208.9765625"}, "swapsize_mb"=> {:facter4=>"1208.98", :facter3=>"1208.9765625"}, "system_uptime.seconds"=> {:facter4=>"615", :facter3=>"613"}, "uptime_seconds"=> {:facter4=>"615", :facter3=>"613"}} sles12-POWERa {"blockdevice_sr0_size"=> \{:facter4=>"\"3215923200\"", :facter3=>"3215923200"} , "blockdevice_vda_size"=> {:facter4=>"\"32212254720\"", :facter3=>"32212254720"}, "facterversion"=> {:facter4=>"\"4.0.38\"", :facter3=>"\"3.14.14\""}, "load_averages.1m"=>
Jira (FACT-2809) Investigate differences on Solaris
Title: Message Title
Sebastian Miclea created an issue
Facter / FACT-2809
Investigate differences on Solaris
Issue Type:
Task
Assignee:
Unassigned
Created:
2020/09/21 7:12 AM
Labels:
platform_7
Priority:
Normal
Reporter:
Sebastian Miclea
solaris114-64a {"blockdevice_sd0_size"=> {:f4=>"0",:f3=>"0"}, "blockdevice_sd1_size"=> {:f4=>"21474836480",:f3=>"21474836480"}, "facterversion"=> {:f4=>"4.0.38",:f3=>"3.14.14"}, "hypervisors.zone.id"=> {:f4=>"0",:f3=>"0"}, "load_averages.15m"=> {:f4=>"0.14453125",:f3=>"0.140625"}, "load_averages.1m"=> {:f4=>"0.7109375",:f3=>"0.70703125"}, "load_averages.5m"=> {:f4=>"0.25390625",:f3=>"0.24609375"}, "memory.system.available"=> {:f4=>"3.63 GiB",:f3=>"3.64 GiB"}, "memory.system.available_bytes"=> {:f4=>"3902185472",:f3=>"3906961408"}, "memory.system.capacity"=> {:f4=>"39.43%",:f3=>"39.35%"}, "memory.system.used"=> {:f4=>"2.37 GiB",:f3=>"2.36 GiB"}, "memory.system.used_bytes"=> {:f4=>"2539737088",:f3=>"2534961152"}, "memoryfree"=> {:f4=>"3.63 GiB",:f3=>"3.64 GiB"}, "memoryfree_mb"=> {:f4=>"3721.41",:f3=>"3725.96875"}, "memorysize_mb"=> {:f4=>"6143.5",:f3=>"6143.49609375"}, "mountpoints./.available_bytes"=> {:f4=>"13541655040",:f3=>"13541670912"}, "mountpoints./.capacity"=> {:f4=>"20.68%",:f3=>"55.77%"}, "mountpoints./.size_bytes"=> {:f4=>"17071402496",:f3=>"17071421440"}, "mountpoints./.used"=> {:f4=>"3.29 GiB",:f3=>"15.90 GiB"}, "mountpoints./.used_bytes"=> {:f4=>"3529747456",:f3=>"17071421440"}, "mountpoints./export.available_bytes"=> {:f4=>"13541655040",:f3=>"13541670912"}, "mountpoints./export.capacity"=> {:f4=>"0.00%",:f3=>"50.00%"}, "mountpoints./export.size_bytes"=> {:f4=>"13541687808",:f3=>"13541703680"}, "mountpoints./export.used"=> {:f4=>"32.00 KiB",:f3=>"12.61 GiB"}, "mountpoints./export.used_bytes"=> {:f4=>"32768",:f3=>"13541703680"}, "mountpoints./export/home.available_bytes"=> {:f4=>"13541655040",:f3=>"13541670912"}, "mountpoints./export/home.capacity"=> {:f4=>"0.00%",:f3=>"50.00%"},
Jira (FACT-2808) Investigate differences on OSX
Title: Message Title
Sebastian Miclea created an issue
Facter / FACT-2808
Investigate differences on OSX
Issue Type:
Task
Assignee:
Unassigned
Created:
2020/09/21 7:07 AM
Labels:
platform_7
Priority:
Normal
Reporter:
Sebastian Miclea
osx1015-64a {"facterversion"=> \{:facter4=>"\"4.0.38\"", :facter3=>"\"3.14.14\""} , "load_averages.15m"=> {:facter4=>"0.97", :facter3=>"0.9736328125"}, "load_averages.1m"=> {:facter4=>"1.42", :facter3=>"1.4951171875"}, "load_averages.5m"=> {:facter4=>"1.31", :facter3=>"1.3173828125"}, "memory.system.available"=> {:facter4=>"\"947.71 MiB\"", :facter3=>"\"953.27 MiB\""}, "memory.system.available_bytes"=> {:facter4=>"993746944", :facter3=>"999579648"}, "memory.system.capacity"=> {:facter4=>"\"76.86%\"", :facter3=>"\"76.73%\""}, "memory.system.used_bytes"=> {:facter4=>"3301220352", :facter3=>"3295387648"}, "memoryfree"=> {:facter4=>"\"947.71 MiB\"", :facter3=>"\"953.27 MiB\""}, "memoryfree_mb"=> {:facter4=>"947.71", :facter3=>"953.2734375"}, "mountpoints./.available"=> {:facter4=>"\"24.66 GiB\"", :facter3=>"\"29.72 GiB\""}, "mountpoints./.available_bytes"=> {:facter4=>"26480476160", :facter3=>"31916617728"}, "mountpoints./.capacity"=> {:facter4=>"\"38.04%\"", :facter3=>"\"57.25%\""}, "mountpoints./.options.0"=> {:facter4=>"\"read-only\"", :facter3=>"\"readonly\""}, "mountpoints./.used"=> {:facter4=>"\"15.14 GiB\"", :facter3=>"\"39.80 GiB\""}, "mountpoints./.used_bytes"=> {:facter4=>"16259440640", :facter3=>"42739916800"}, "mountpoints./System/Volumes/Data.available"=> {:facter4=>"\"24.66 GiB\"", :facter3=>"\"35.40 GiB\""}, "mountpoints./System/Volumes/Data.available_bytes"=> {:facter4=>"26480476160", :facter3=>"38014808064"}, "mountpoints./System/Volumes/Data.capacity"=> {:facter4=>"\"38.04%\"", :facter3=>"\"52.93%\""}, "mountpoints./System/Volumes/Data.used"=> {:facter4=>"\"15.14 GiB\"", :facter3=>"\"39.80 GiB\""}, "mountpoints./System/Volumes/Data.used_bytes"=> {:facter4=>"16259440640", :facter3=>"42739916800"},
Jira (FACT-2807) Investigate differences on Aix
Title: Message Title
Sebastian Miclea created an issue
Facter / FACT-2807
Investigate differences on Aix
Issue Type:
Task
Assignee:
Unassigned
Created:
2020/09/21 7:07 AM
Labels:
platform_7
Priority:
Normal
Reporter:
Sebastian Miclea
aix61-POWERfa {"blockdevice_hdisk0_size"=> \{:facter4=>"\"32212254720\"", :facter3=>"32212254720"} , "facterversion"=> {:facter4=>"\"4.0.38\"", :facter3=>"\"3.14.14\""}, "load_averages.15m"=> {:facter4=>"3.10909", :facter3=>"3.1208343505859375"}, "load_averages.1m"=> {:facter4=>"1.86002", :facter3=>"1.9347686767578125"}, "load_averages.5m"=> {:facter4=>"2.83121", :facter3=>"2.8619842529296875"}, "memory.swap.available_bytes"=> {:facter4=>"529657856", :facter3=>"529653760"}, "memory.swap.used_bytes"=> {:facter4=>"7213056", :facter3=>"7217152"}, "memory.system.available_bytes"=> {:facter4=>"6091296768", :facter3=>"6092431360"}, "memory.system.capacity"=> {:facter4=>"\"29.09%\"", :facter3=>"\"29.07%\""}, "memory.system.used_bytes"=> {:facter4=>"2498637824", :facter3=>"2497503232"}, "memoryfree_mb"=> {:facter4=>"5809.11", :facter3=>"5810.1953125"}, "mountpoints./.capacity"=> {:facter4=>"\"11.44%\"", :facter3=>"\"53.03%\""}, "mountpoints./.used"=> {:facter4=>"\"234.22 MiB\"", :facter3=>"\"2.00 GiB\""}, "mountpoints./.used_bytes"=> {:facter4=>"245600256", :facter3=>"2147483648"}, "mountpoints./admin.capacity"=> {:facter4=>"\"0.28%\"", :facter3=>"\"50.07%\""}, "mountpoints./admin.used"=> {:facter4=>"\"364.00 KiB\"", :facter3=>"\"128.00 MiB\""}, "mountpoints./admin.used_bytes"=> {:facter4=>"372736", :facter3=>"134217728"}, "mountpoints./home.capacity"=> {:facter4=>"\"0.02%\"", :facter3=>"\"50.01%\""}, "mountpoints./home.used"=> {:facter4=>"\"984.00 KiB\"", :facter3=>"\"4.00 GiB\""}, "mountpoints./home.used_bytes"=> {:facter4=>"1007616", :facter3=>"4294967296"}, "mountpoints./opt.available_bytes"=> {:facter4=>"5966176256", :facter3=>"5965635584"}, "mountpoints./opt.capacity"=> {:facter4=>"\"7.39%\"", :facter3=>"\"51.92%\""},
