Skip to content

GitLab

  • Menu
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
  • #8157

Closed
Open
Created Oct 23, 2014 by Administrator@rootOwner

[7.4-stable] conflicting db migrate tasks from 7.0 -> 7.4

Created by: doublerebel

Hello,

Today I upgraded from 7.0 from git to 7.4 omnibus package. Creating a backup on 7.0-git and restoring to 7.0-omnibus was nearly flawless, I only had to discover the basically undocumented option to set postgresql db user before running the first reconfigure:

# config.rb
postgresql['sql_user'] = 'git'

Required because gitlab git installation instructions create git user for postgres, and omnibus-gitlab creates gitlab postgres user. I was unable to restore the db without errors until making this change.

But! The more important issue is with serialize_service_properties and move_slack_service_to_webhook.

I downloaded the 7.4 omnibus package to update from 7.0. Since 7.4 expects a Webhook property when saving the SlackService, serialize_service_properties fails with a Webhook can't be blank error.

Since we do not use the Slack integration in our installation, I worked around this by excluding SlackService from save during the migration:

serialize_service_properties.rb#L26

      unless service.type == "SlackService"
        service.save!
      end

This update case may be rare, but I want to report here in case anyone faces a similar issue.

Thanks again for Gitlab!

Assignee
Assign to
Time tracking