Skip to content

Password reset improvements

Ben Prescott_ requested to merge docs-bprescott/20210318-resetpassword into master

What does this MR do?

A customer was unable to successfully reset their root account password on a new self-managed Omnibus instance, and it ended up being resolved on a call with Support. (internal link)

  • they were on 13.0, so the rake task failed with:
Don't know how to build task 'gitlab:password:reset' (See the list of available tasks with `rake --tasks`) 
  • This was an assumption on my part, adding the release version to the docs helps with that.

  • on the call, resetting the password via rails didn't work. It turns out reconfirmation was blocking the root account, which as it was still admin@example.com would be unfixable.

MAde this groupdistribution to match the 13.9 rake task addition

Related issues

Author's checklist (required)

Do not add the feature, frontend, backend, ~"bug", or database labels if you are only updating documentation. These labels will cause the MR to be added to code verification QA issues.

When applicable:

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

  • Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

  • Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.

For more information about labels, see Technical Writing workflows - Labels.

For suggestions that you are confident don't need to be reviewed, change them locally and push a commit directly to save others from unneeded reviews. For example:

  • Clear typos, like this is a typpo.
  • Minor issues, like single quotes instead of double quotes, Oxford commas, and periods.

For more information, see our documentation on Merging a merge request.

3. Maintainer

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.

Merge request reports

Loading