Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1211542

Summary:	"FOREIGN KEY constraint failed" trying to delete contact
Product:	Red Hat Enterprise Linux 7	Reporter:	Milan Crha <mcrha>
Component:	evolution-data-server	Assignee:	Matthew Barnes <mbarnes>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.1	CC:	jkoten, mcrha, vbenes, vrutkovs
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	evolution-data-server-3.12.11-2.el7	Doc Type:	Bug Fix
Doc Text:	Cause: Cannot delete contacts in local books Consequence: Trying to delete contacts with multiple emails fails with an error "FOREIGN KEY constraint failed" Fix: correct data migration from an older version, to setup tables properly and track of this connection between data and the tables Result: the contacts with multiple emails can be deleted	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-19 07:58:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Milan Crha 2015-04-14 09:30:53 UTC

As was discussed upstream at [1], the contact deletion after an update can fail with a "FOREIGN KEY constraint failed" error, for which the upstream bug [1] has a fix, which I'd like to commit together with the rebase to 3.12.11.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=743996

Comment 1 Milan Crha 2015-04-14 09:43:22 UTC

Steps:
a) restore from a backup from any of 3.6, 3.8, 3.10 with an address book which
   contains contains with emails
b) close evolution, make sure also evolution-addressbook-factory was closed (it
   takes up to 10 seconds to be automatically closed when all clients are
   disconnected)
c) run evolution again
d) try to delete (cut (and paste) also works) one of the contacts with an email

The attempt to delete the contact fails with the "FOREIGN KEY constraint failed" error, while it should just delete the contact.

The upstream patch fixes both things:
1) already broken summary
2) update from older versions of the summary

Comment 5 errata-xmlrpc 2015-11-19 07:58:04 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2226.html