Jira (PDB-4707) Provide a subcommand to list the available migrations
Title: Message Title Claudia Petty updated an issue PuppetDB / PDB-4707 Provide a subcommand to list the available migrations Change By: Claudia Petty Labels: new-feature Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.356932.1588029202000.2444.1687359428581%40Atlassian.JIRA.
Jira (PDB-4707) Provide a subcommand to list the available migrations
Title: Message Title Nick Burgan commented on PDB-4707 Re: Provide a subcommand to list the available migrations If we can get PE-28943 done through the pe_install::upgrade::puppetdb class, we shouldn't need this command. 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.356932.1588029202000.63001.1589492520139%40Atlassian.JIRA.
Jira (PDB-4707) Provide a subcommand to list the available migrations
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4707 Provide a subcommand to list the available migrations Change By: Austin Blatt Acceptance Criteria: - subcommand exits 0 when no new migrations are available- subcommand exits non-zero when no migrations will be applied- Print the available migrations to stdout (optional) 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.356932.1588029202000.61474.1589389980199%40Atlassian.JIRA.
Jira (PDB-4707) Provide a subcommand to list the available migrations
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4707 Provide a subcommand to list the available migrations Change By: Austin Blatt Acceptance Criteria: - subcommand exits 0 when no new migrations are available- subcommand exits n non-zero when n no migrations will be applied- Print the available migrations to stdout 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.356932.1588029202000.61473.1589389980155%40Atlassian.JIRA.
Jira (PDB-4707) Provide a subcommand to list the available migrations
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4707 Provide a subcommand to list the available migrations Change By: Austin Blatt Fix Version/s: PDB 6.11.0 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.356932.1588029202000.57013.1588873620129%40Atlassian.JIRA.
Jira (PDB-4707) Provide a subcommand to list the available migrations
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4707 Provide a subcommand to list the available migrations Issue Type: New Feature Assignee: Unassigned Created: 2020/04/27 4:13 PM Priority: Normal Reporter: Austin Blatt Setting the systemd START_TIMEOUT to 14400 is only useful for long migrations, but is not long enough for some installs, and it can mask startup issues with puppetdb when no-migrations are present. The end goal of this work is to enable the installer to upgrade PuppetDB via the upgrade subcommand, thus bypassing the systemd timeout, and start the puppetdb service with a shorter systemd start timeout, like 5 minutes. To do this PuppetDB upgrade will be triggered by a Puppet exec iff this subcommand exits non-zero before it is restarted by the full service restart that normally happens during Puppet applied PE infrastructure changes. Add Comment
