2019-05-05 18:10:48 +05:30
|
|
|
<!---
|
|
|
|
|
Please read this!
|
|
|
|
|
|
|
|
|
|
Before opening a new issue, make sure to search for keywords in the issues
|
2019-12-21 20:55:43 +05:30
|
|
|
filtered by the "regression" or "bug" label:
|
2019-05-05 18:10:48 +05:30
|
|
|
|
2019-12-21 20:55:43 +05:30
|
|
|
- https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression
|
|
|
|
|
- https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=bug
|
2019-05-05 18:10:48 +05:30
|
|
|
|
|
|
|
|
and verify the issue you're about to submit isn't a duplicate.
|
|
|
|
|
--->
|
|
|
|
|
|
|
|
|
|
### Summary
|
|
|
|
|
|
|
|
|
|
(Summarize the bug encountered concisely)
|
|
|
|
|
|
|
|
|
|
### Steps to reproduce
|
|
|
|
|
|
|
|
|
|
(How one can reproduce the issue - this is very important)
|
|
|
|
|
|
|
|
|
|
### Example Project
|
|
|
|
|
|
2019-09-04 21:01:54 +05:30
|
|
|
(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)
|
2019-05-05 18:10:48 +05:30
|
|
|
|
2019-09-04 21:01:54 +05:30
|
|
|
(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)
|
2019-05-05 18:10:48 +05:30
|
|
|
|
|
|
|
|
### What is the current *bug* behavior?
|
|
|
|
|
|
|
|
|
|
(What actually happens)
|
|
|
|
|
|
|
|
|
|
### What is the expected *correct* behavior?
|
|
|
|
|
|
|
|
|
|
(What you should see instead)
|
|
|
|
|
|
|
|
|
|
### Relevant logs and/or screenshots
|
|
|
|
|
|
|
|
|
|
(Paste any relevant logs - please use code blocks (```) to format console output,
|
2019-09-04 21:01:54 +05:30
|
|
|
logs, and code as it's tough to read otherwise.)
|
2019-05-05 18:10:48 +05:30
|
|
|
|
|
|
|
|
### Output of checks
|
|
|
|
|
|
|
|
|
|
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
|
|
|
|
|
|
|
|
|
|
#### Results of GitLab environment info
|
|
|
|
|
|
|
|
|
|
<details>
|
|
|
|
|
<summary>Expand for output related to GitLab environment info</summary>
|
|
|
|
|
<pre>
|
|
|
|
|
|
|
|
|
|
(For installations with omnibus-gitlab package run and paste the output of:
|
|
|
|
|
`sudo gitlab-rake gitlab:env:info`)
|
|
|
|
|
|
|
|
|
|
(For installations from source run and paste the output of:
|
|
|
|
|
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
|
|
|
|
|
|
|
|
|
|
</pre>
|
|
|
|
|
</details>
|
|
|
|
|
|
|
|
|
|
#### Results of GitLab application Check
|
|
|
|
|
|
|
|
|
|
<details>
|
|
|
|
|
<summary>Expand for output related to the GitLab application check</summary>
|
|
|
|
|
<pre>
|
|
|
|
|
|
|
|
|
|
(For installations with omnibus-gitlab package run and paste the output of:
|
|
|
|
|
`sudo gitlab-rake gitlab:check SANITIZE=true`)
|
|
|
|
|
|
|
|
|
|
(For installations from source run and paste the output of:
|
|
|
|
|
`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`)
|
|
|
|
|
|
|
|
|
|
(we will only investigate if the tests are passing)
|
|
|
|
|
|
|
|
|
|
</pre>
|
|
|
|
|
</details>
|
|
|
|
|
|
|
|
|
|
### Possible fixes
|
|
|
|
|
|
|
|
|
|
(If you can, link to the line of code that might be responsible for the problem)
|
|
|
|
|
|
|
|
|
|
/label ~bug
|
