Skip to content

GitLab

  • Menu
    • Projects Groups Snippets
      Help
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #5311

Closed
Open
Created 11 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

404 pages on Merge Requests, Issues... after a GitLab 6.1 upgrade

Closed

404 pages on Merge Requests, Issues... after a GitLab 6.1 upgrade

Created by: iKiKi

For all pages that requires access to old "objects" (observed with merge requests and issues), created before migration, 404 web pages are displayed.

Example 404 web page after a click on Merge Requests (1) mergerequestserror

The problem has been observed also with Issues. I also noticed that a 404 web page on projects home page (for projects with objects not fetched correctly). Another user has the same problem with Issues. He has also a 404 web page on his "User Activity" page.

Summary After migration, it seems we have issues with old objects (Issues, Merge Requests...) maybe not found or something like that, that lead to 404 web pages.

Are there any scripts or patches that could solve the problem ? I'm ready to remove previous Issues or Merge Requests to make thoses pages displayed ?

Please find below a log from production.log file regarding Merge Requests 404 web page:

Started GET "/dashboard/merge_requests" for 127.0.0.1 at 2013-10-10 21:34:05 +0200
Processing by DashboardController#merge_requests as HTML
Rendered shared/_filter.html.haml (105.8ms)
Rendered projects/merge_requests/_merge_request.html.haml (4.9ms)
Rendered shared/_merge_requests.html.haml (9.2ms)
Rendered dashboard/merge_requests.html.haml within layouts/application (116.9ms)
Completed 500 Internal Server Error in 126ms

ActionController::RoutingError (No route matches {
    :action=>"show",
    :controller=>"projects/merge_requests",
    :project_id=>#<Project id: 8, name: "NFModalController", path: "nfmodalcontroller", description: nil, created_at:     "2013-06-16 05:52:48", updated_at: "2013-06-16 05:54:14",
                           creator_id: 2, default_branch: "master", issues_enabled: true, wall_enabled: false, merge_requests_enabled: true, wiki_enabled: true, namespace_id: 3,
                       public: false, issues_tracker: "gitlab", issues_tracker_id: nil, snippets_enabled: false, last_activity_at: "2013-10-07 09:58:22", imported: false,
                       import_url: nil>, :id=>#<MergeRequest id: 16, target_branch: "master", source_branch: "hideWithCompletion", source_project_id: 8, author_id: 2, 
                       assignee_id: 7, title: "Added a completion block on show/hide animated meth...", created_at: "2013-07-18 08:12:47", updated_at: "2013-09-02 12:04:16",
                       st_commits: blahblahblah...
app/views/projects/merge_requests/_merge_request.html.haml:4:in `_app_views_projects_merge_requests__merge_request_html_haml__11211096841922939_70185118911560'
app/views/shared/_merge_requests.html.haml:9:in `block (2 levels) in _app_views_shared__merge_requests_html_haml___951893817875884211_70185118068820'
app/views/shared/_merge_requests.html.haml:8:in `each'
app/views/shared/_merge_requests.html.haml:8:in `block in _app_views_shared__merge_requests_html_haml___951893817875884211_70185118068820'
app/views/shared/_merge_requests.html.haml:2:in `each'
app/views/shared/_merge_requests.html.haml:2:in `_app_views_shared__merge_requests_html_haml___951893817875884211_70185118068820'
app/views/dashboard/merge_requests.html.haml:13:in `_app_views_dashboard_merge_requests_html_haml__2357998383459815759_70185152433260'

Linked issues
...

    Related merge requests

    • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
    Please register or sign in to reply
    0 Assignees
    Assign to
    Milestone
    No milestone
    None
    None
    Time tracking
    Due date
    None
    None
    0
    Labels
    None
    Assign labels
    • No matching results
    • Manage project labels
    Confidentiality
    Not confidential

    You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

    Lock issue
    Unlocked
    participants
    Reference:

    Menu

    Projects Groups Snippets
    Help