Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-4308

Check whether pdb is unkillable when db is unavailable at startup

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 5.2.9, PDB 6.0.4, PDB 6.3.3
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      PuppetDB
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      Previously, if the database were inaccessible during startup, PuppetDB could become "unkillable", meaning that `kill PUPPETDB_PID` or Control-C from a terminal (for example) would no longer stop the server. Now PuppetDB should exit properly in those situations.
      Show
      Previously, if the database were inaccessible during startup, PuppetDB could become "unkillable", meaning that `kill PUPPETDB_PID` or Control-C from a terminal (for example) would no longer stop the server. Now PuppetDB should exit properly in those situations.
    • QA Risk Assessment:
      Needs Assessment

      Description

      While working on other things, I noticed that a "lein test ..." run might have become unkillable (i.e. C-c didn't kill it, kill wouldn't kill it, and I resorted to kill -9) when I tried this in a test:

      (with-test-db
        (svc-utils/call-with-single-quiet-pdb-instance
         (-> (svc-utils/create-temp-config)
             (assoc :database *db*)
             (assoc-in [:database :user ] "invalid-user")
             (assoc-in [:global :vardir] shared-vardir))
         (fn []
           ...)))
      

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                rob.browning Rob Browning
                Reporter:
                rob.browning Rob Browning
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support