Linux JIRA installer fails to create user if group already exists

XMLWordPrintable

    • Type: Bug
    • Resolution: Timed out
    • Priority: Low
    • None
    • Affects Version/s: 7.0.11, 7.2.8, 7.3.6
    • Component/s: Installation
    • None
    • 7
    • 1
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 12 February 2020

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,
      Jira Server Bug Fix team

      Show
      Atlassian Update – 12 February 2020 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Jira Server Bug Fix team

      Summary

      JIRA installer silently fails to create dedicated JIRA user if jira group already exists.

      Environment

      • Linux
      • Tested with JIRA Software 7.0.11, 7.2.8, and 7.3.6 installers.

      Steps to Reproduce

      1. Setup a clean Linux environment to install JIRA
      2. Create a group called jira
      3. Run the JIRA installer and install JIRA

      Expected Results

      JIRA will startup normally.

      Actual Results

      JIRA does not start. If you attempt to invoke it manually with start-jira.sh or something to the effect of service jira start, you will see the following:

      To run JIRA in the foreground, start the server with start-jira.sh -fg
executing using dedicated user: jira
runuser: user jira does not exist
root@ghs83027:/opt/atlassian/jira/logs#

      Workaround

      Manually create the appropriate user afterwards and update permissions/ownership as needed.

      As an alternative, remove the pre-existing group and re-perform the installation.

            Assignee:
            Unassigned
            Reporter:
            Russell Stadler (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: