Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-5317

Master should return 74 when puppet user doesn't exist

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: PUP 4.1.0
    • Fix Version/s: PUP 4.2.3
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      1
    • Sprint:
      Client 2015-10-14
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      Prior to 4.1.0, running puppet master as root would exit with 74 if the `puppet` user or group did not exist (since we try to setuid/gid to that user/group). In 4.1.0, that behavior was accidentally changed to exit with 1. This ticket reinstates the original behavior of exiting with 74.
      Show
      Prior to 4.1.0, running puppet master as root would exit with 74 if the `puppet` user or group did not exist (since we try to setuid/gid to that user/group). In 4.1.0, that behavior was accidentally changed to exit with 1. This ticket reinstates the original behavior of exiting with 74.

      Description

      Previously, when trying to run a master and the puppet user didn't exist, we exited with 74.

      In commit 144ea123965, a change was made to more gracefully handle failing, but raised a Puppet::Error instead of exiting with 74 as before. This causes puppet_manages_own_configuration_in_robust_manner.rb to fail.

      We should go back to exiting with 74.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  whopper William Hopper
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: