Skip to content

PG::CheckViolation: ERROR: new row for relation "jira_connect_installations" violates check constraint "check_dc0d039821

Summary

Customers are experiencing PG::CheckViolation: ERROR when trying to set up a new Jira integration.

"cause_class": "PG::CheckViolation",
        "class": "ActiveRecord::StatementInvalid",
        "message": "PG::CheckViolation: ERROR:  new row for relation \"jira_connect_installations\" violates check constraint \"check_dc0d039821\"\nDETAIL:  Failing row contains (84534, fb96b1f6-26b6-3613-871d-87a745714fb8, 43DBRlr1LMiMe8Ka9+7JUAvA4LQG8o7Brbct1XIsrol+YjKYDnNR85KxXi3m\nMdT..., t61xi6aa8COqdf+t\n, https://xxx.atlassian.net, https://xxxx.com null).\n",
        "sql": "/*application:web,correlation_id:01K5RMC2WJC4JTNCSM619TCFN8,endpoint_id:JiraConnect::InstallationsController#update,db_config_database:gitlabhq_production,db_config_name:main*/ UPDATE \"jira_connect_installations\" SET \"instance_url\" = $1 WHERE \"jira_connect_installations\".\"id\" = $2"
      },

Steps to reproduce

  • In Jira, click on the Jira Cloud app and click on Get started.
  • Select GitLab.com (SaaS)
  • Click save.

image

Zendesk:

https://gitlab.zendesk.com/agent/tickets/657774

Example Project

What is the current bug behavior?

What is the expected correct behavior?

Relevant logs and/or screenshots

https://log.gprd.gitlab.net/app/r/s/SIUrF

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 

(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`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(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)

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.

Edited by 🤖 GitLab Bot 🤖