Jira (PDB-5021) Investigate factsets getting repeatedly pulled in sync with benchmark data
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-5021 Investigate factsets getting repeatedly pulled in sync with benchmark data Change By: Zachary Kent Fix Version/s: PDB 6.16.2 Fix Version/s: PDB 7.3.2 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.386997.1612983565000.14842.1618953780213%40Atlassian.JIRA.
Jira (PDB-5109) Improve delete-reports scripts for upgrades to 2019.8
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-5109
Improve delete-reports scripts for upgrades to 2019.8
Change By:
Austin Blatt
Replace the old scripts in PE 2019.8 upgrade cautions (https://puppet.com/docs/pe/2019.8/upgrading_pe.html) with these new ones.Before 2019.3.0{code: SQL sql }BEGIN TRANSACTION;DO $$ DECLARE db_schema_version integer;BEGIN if exists (select from information_schema.tables where table_schema = 'public' and table_name = 'schema_migrations') thenselect max(version) into db_schema_version from schema_migrations;case when db_schema_version > 72 thenraise exception 'This version of the delete-reports.sql is for versions of PuppetDB before migration 73, your database is on migration % which is too new for this version of PuppetDB.', db_schema_version USING HINT = 'You may already be upgraded, or you may need a different version of the script.'; elseALTER TABLE certnames DROP CONSTRAINT IF EXISTS certnames_reports_id_fkey;UPDATE certnames SET latest_report_id = NULL;TRUNCATE TABLE reports CASCADE;ALTER TABLE certnames ADD CONSTRAINT certnames_reports_id_fkey FOREIGN KEY (latest_report_id) REFERENCES reports(id) ON DELETE SET NULL;end case; elseraise exception 'Could not find puppetdb schema_migrations table'; end if;end $$;COMMIT TRANSACTION;{code}2019.3.0 through 2019.6.0{code}BEGIN TRANSACTION;DO $$ DECLARE db_schema_version integer; r RECORD;BEGIN if exists (select from information_schema.tables where table_schema = 'public' and table_name = 'schema_migrations') thenselect max(version) into db_schema_version from schema_migrations;case when db_schema_version != 73 thenraise exception 'This version of the delete-reports.sql is for versions of PuppetDB on migration 73, your database is on migration %', db_schema_version USING HINT = 'You may already be upgraded, or you may need a different version of the script.'; elseALTER TABLE certnames DROP CONSTRAINT IF EXISTS certnames_reports_id_fkey;UPDATE certnames SET latest_report_id = NULL;FOR r IN (SELECT tablename FROM pg_tables WHERE tablename LIKE 'resource_events_%') LOOP EXECUTE 'DROP TABLE ' || quote_ident(r.tablename);END LOOP;TRUNCATE TABLE reports CASCADE;ALTER TABLE certnames ADD CONSTRAINT certnames_reports_id_fkey FOREIGN KEY (latest_report_id) REFERENCES reports(id) ON DELETE SET NULL;end case; elseraise exception 'Could not find puppetdb schema_migrations table'; end if;end $$;COMMIT TRANSACTION;{code}
Jira (PDB-5109) Improve delete-reports scripts for upgrades to 2019.8
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-5109
Improve delete-reports scripts for upgrades to 2019.8
Change By:
Austin Blatt
Replace the old scripts in PE 2019.8 upgrade cautions (https://puppet.com/docs/pe/2019.8/upgrading_pe.html) with these new ones.Before 2019.3.0{code:sql}BEGIN TRANSACTION;DO $$ DECLARE db_schema_version integer;BEGIN if exists (select from information_schema.tables where table_schema = 'public' and table_name = 'schema_migrations') thenselect max(version) into db_schema_version from schema_migrations;case when db_schema_version > 72 thenraise exception 'This version of the delete-reports.sql is for versions of PuppetDB before migration 73, your database is on migration % which is too new for this version of PuppetDB.', db_schema_version USING HINT = 'You may already be upgraded, or you may need a different version of the script.'; elseALTER TABLE certnames DROP CONSTRAINT IF EXISTS certnames_reports_id_fkey;UPDATE certnames SET latest_report_id = NULL;TRUNCATE TABLE reports CASCADE;ALTER TABLE certnames ADD CONSTRAINT certnames_reports_id_fkey FOREIGN KEY (latest_report_id) REFERENCES reports(id) ON DELETE SET NULL;end case; elseraise exception 'Could not find puppetdb schema_migrations table'; end if;end $$;COMMIT TRANSACTION;{code}2019.3.0 through 2019.6.0{code :sql }BEGIN TRANSACTION;DO $$ DECLARE db_schema_version integer; r RECORD;BEGIN if exists (select from information_schema.tables where table_schema = 'public' and table_name = 'schema_migrations') thenselect max(version) into db_schema_version from schema_migrations;case when db_schema_version != 73 thenraise exception 'This version of the delete-reports.sql is for versions of PuppetDB on migration 73, your database is on migration %', db_schema_version USING HINT = 'You may already be upgraded, or you may need a different version of the script.'; elseALTER TABLE certnames DROP CONSTRAINT IF EXISTS certnames_reports_id_fkey;UPDATE certnames SET latest_report_id = NULL;FOR r IN (SELECT tablename FROM pg_tables WHERE tablename LIKE 'resource_events_%') LOOP EXECUTE 'DROP TABLE ' || quote_ident(r.tablename);END LOOP;TRUNCATE TABLE reports CASCADE;ALTER TABLE certnames ADD CONSTRAINT certnames_reports_id_fkey FOREIGN KEY (latest_report_id) REFERENCES reports(id) ON DELETE SET NULL;end case; elseraise exception 'Could not find puppetdb schema_migrations table'; end if;end $$;COMMIT TRANSACTION;{code}
Jira (PDB-5109) Improve delete-reports scripts for upgrades to 2019.8
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-5109
Improve delete-reports scripts for upgrades to 2019.8
Change By:
Austin Blatt
Replace the old scripts in PE 2019.8 upgrade cautions (https://puppet.com/docs/pe/2019.8/upgrading_pe.html) with these new ones.Before 2019.3.0{code :SQL }BEGIN TRANSACTION;DO $$ DECLARE db_schema_version integer;BEGIN if exists (select from information_schema.tables where table_schema = 'public' and table_name = 'schema_migrations') thenselect max(version) into db_schema_version from schema_migrations;case when db_schema_version > 72 thenraise exception 'This version of the delete-reports.sql is for versions of PuppetDB before migration 73, your database is on migration % which is too new for this version of PuppetDB.', db_schema_version USING HINT = 'You may already be upgraded, or you may need a different version of the script.'; elseALTER TABLE certnames DROP CONSTRAINT IF EXISTS certnames_reports_id_fkey;UPDATE certnames SET latest_report_id = NULL;TRUNCATE TABLE reports CASCADE;ALTER TABLE certnames ADD CONSTRAINT certnames_reports_id_fkey FOREIGN KEY (latest_report_id) REFERENCES reports(id) ON DELETE SET NULL;end case; elseraise exception 'Could not find puppetdb schema_migrations table'; end if;end $$;COMMIT TRANSACTION;{code}2019.3.0 through 2019.6.0{code}BEGIN TRANSACTION;DO $$ DECLARE db_schema_version integer; r RECORD;BEGIN if exists (select from information_schema.tables where table_schema = 'public' and table_name = 'schema_migrations') thenselect max(version) into db_schema_version from schema_migrations;case when db_schema_version != 73 thenraise exception 'This version of the delete-reports.sql is for versions of PuppetDB on migration 73, your database is on migration %', db_schema_version USING HINT = 'You may already be upgraded, or you may need a different version of the script.'; elseALTER TABLE certnames DROP CONSTRAINT IF EXISTS certnames_reports_id_fkey;UPDATE certnames SET latest_report_id = NULL;FOR r IN (SELECT tablename FROM pg_tables WHERE tablename LIKE 'resource_events_%') LOOP EXECUTE 'DROP TABLE ' || quote_ident(r.tablename);END LOOP;TRUNCATE TABLE reports CASCADE;ALTER TABLE certnames ADD CONSTRAINT certnames_reports_id_fkey FOREIGN KEY (latest_report_id) REFERENCES reports(id) ON DELETE SET NULL;end case; elseraise exception 'Could not find puppetdb schema_migrations table'; end if;end $$;COMMIT TRANSACTION;{code}
Jira (PDB-5109) Improve delete-reports scripts for upgrades to 2019.8
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-5109
Improve delete-reports scripts for upgrades to 2019.8
Change By:
Austin Blatt
Replace the old scripts in PE 2019.8 upgrade cautions (https://puppet.com/docs/pe/2019.8/upgrading_pe.html) with these new ones.Before 2019.3.0{code}BEGIN TRANSACTION;DO $$ DECLARE db_schema_version integer;BEGIN if exists (select from information_schema.tables where table_schema = 'public' and table_name = 'schema_migrations') thenselect max(version) into db_schema_version from schema_migrations;case when db_schema_version > 72 thenraise exception 'This version of the delete-reports.sql is for versions of PuppetDB before migration 73, your database is on migration % which is too new for this version of PuppetDB.', db_schema_version USING HINT = 'You may already be upgraded, or you may need a different version of the script.'; elseALTER TABLE certnames DROP CONSTRAINT IF EXISTS certnames_reports_id_fkey;UPDATE certnames SET latest_report_id = NULL;TRUNCATE TABLE reports CASCADE;ALTER TABLE certnames ADD CONSTRAINT certnames_reports_id_fkey FOREIGN KEY (latest_report_id) REFERENCES reports(id) ON DELETE SET NULL;end case; elseraise exception 'Could not find puppetdb schema_migrations table'; end if;end $$;COMMIT TRANSACTION;{code}2019.3.0 through 2019.6.0{code}BEGIN TRANSACTION;DO $$ DECLARE db_schema_version integer; r RECORD;BEGIN if exists (select from information_schema.tables where table_schema = 'public' and table_name = 'schema_migrations') thenselect max(version) into db_schema_version from schema_migrations;case when db_schema_version != 73 thenraise exception 'This version of the delete-reports.sql is for versions of PuppetDB on migration 73, your database is on migration %', db_schema_version USING HINT = 'You may already be upgraded, or you may need a different version of the script.'; elseALTER TABLE certnames DROP CONSTRAINT IF EXISTS certnames_reports_id_fkey;UPDATE certnames SET latest_report_id = NULL;FOR r IN (SELECT tablename FROM pg_tables WHERE tablename LIKE 'resource_events_%') LOOP EXECUTE 'DROP TABLE ' || quote_ident(r.tablename);END LOOP;TRUNCATE TABLE reports CASCADE;ALTER TABLE certnames ADD CONSTRAINT certnames_reports_id_fkey FOREIGN KEY (latest_report_id) REFERENCES reports(id) ON DELETE SET NULL;end case; elseraise exception 'Could not find puppetdb schema_migrations table'; end if;end $$;COMMIT TRANSACTION;{code}
Jira (PDB-5109) Improve delete-reports scripts for upgrades to 2019.8
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5109 Improve delete-reports scripts for upgrades to 2019.8 Change By: Austin Blatt Acceptance Criteria: - Make a docs ticket once the scripts are tested/approved Release Notes: Not Needed Release Notes Summary: docs ticket Sprint: HA 2020-04-21 Team: HA Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PDB-5109) Improve delete-reports scripts for upgrades to 2019.8
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5109 Improve delete-reports scripts for upgrades to 2019.8 Issue Type: Improvement Assignee: Unassigned Created: 2021/04/20 11:13 AM Priority: Normal Reporter: Austin Blatt Replace the old scripts in PE 2019.8 upgrade cautions with these new ones. Before 2019.3.0 BEGIN TRANSACTION; DO $$ DECLARE db_schema_version integer; BEGIN if exists (select from information_schema.tables where table_schema = 'public' and table_name = 'schema_migrations')
Jira (PUP-10957) Support ruby 3
Title: Message Title Jim Richardson commented on PUP-10957 Re: Support ruby 3 I see the same error on my Archlinux systems that just updated to ruby 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.390422.161530306.14309.161893529%40Atlassian.JIRA.
Jira (FACT-3023) Facter 4 calls deprecated xen-toolstack script when resolving xen fact
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-3023 Facter 4 calls deprecated xen-toolstack script when resolving xen fact Change By: Mihai Buzgau Sprint: ready for triage Triaged tickets 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.396145.1618825029000.14127.1618930740035%40Atlassian.JIRA.
Jira (FACT-3022) `--json` flag inconsistencies between Facter 3 and Facter 4 when resolving external executable files
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-3022 `--json` flag inconsistencies between Facter 3 and Facter 4 when resolving external executable files Change By: Mihai Buzgau Sprint: Triaged tickets 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.396144.1618824316000.14132.1618930980027%40Atlassian.JIRA.
Jira (FACT-2993) Facter 4.0.52 does not provide trusted['hostname'] in Docker environments
Title: Message Title Manuel Laug commented on FACT-2993 Re: Facter 4.0.52 does not provide trusted['hostname'] in Docker environments Gheorghe Popescu, I've tried Facter 4.1.0 and the Spec tests work again with that version. I think this Issue can be closed. 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.391951.1616498838000.13820.1618918140052%40Atlassian.JIRA.
Jira (FACT-2993) Facter 4.0.52 does not provide trusted['hostname'] in Docker environments
Title: Message Title Manuel Laug updated an issue Facter / FACT-2993 Facter 4.0.52 does not provide trusted['hostname'] in Docker environments Change By: Manuel Laug Fix Version/s: FACT 4.1.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.391951.1616498838000.13821.1618918140072%40Atlassian.JIRA.
Jira (PUP-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Dorin Pleava commented on PUP-10844 Re: Agent failures with server_list when one puppetserver fails I think now I understand what the issue was: When puppet processes server_list and tries to find a functional server, it go through each server, and if it cannot connect it throws an error, but it still moves on to the next server in server_list. Now it only throws a warning for each server it cannot connect to, and if no server from server_list is functional, then it throws an error. [root@twin-federalism puppet]# puppet config print server_list full-maturation.delivery.puppetlabs.net,crash-leapfrog.delivery.puppetlabs.net [root@twin-federalism puppet]# puppet agent -t Warning: Unable to connect to server from server_list setting: Request to https://full-maturation.delivery.puppetlabs.net:8140/status/v1/simple/server failed after 0.002 seconds: Failed to open TCP connection to full-maturation.delivery.puppetlabs.net:8140 (Connection refused - connect(2) for "full-maturation.delivery.puppetlabs.net" port 8140) Trying with next server from server_list. Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Info: Caching catalog for twin-federalism.delivery.puppetlabs.net Info: Applying configuration version '1618915174'
Jira (FACT-3008) Make VirtualDetector static
Title: Message Title Luchian Nemes assigned an issue to Victor Bobosila Facter / FACT-3008 Make VirtualDetector static Change By: Luchian Nemes Assignee: Luchian Nemes Victor Bobosila 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.395139.1618309161000.13673.1618903020045%40Atlassian.JIRA.
Jira (FACT-2995) check.sh script failing randomly on Ubuntu 20.04
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Facter / FACT-2995 check.sh script failing randomly on Ubuntu 20.04 Change By: Luchian Nemes Assignee: Luchian Nemes 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.392573.1616600888000.13674.1618903020105%40Atlassian.JIRA.
