Bug 240348 – Deadlocks on errata import.

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 240348 - Deadlocks on errata import.

Summary:	Deadlocks on errata import.

Status:	CLOSED EOL

Aliases:	None

Product:	Red Hat Network
Classification:	Red Hat
Component:	RHN/Backend (Show other bugs)
Sub Component:
Version:	rhn500
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	rhn-dev-list
QA Contact:	Red Hat Network Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-05-16 12:56 EDT by James Bowes
Modified:	2017-07-05 11:19 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-07-05 11:19:56 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description James Bowes 2007-05-16 12:56:46 EDT

In stage, three users tried to import errata at close to the same time. One of
them failed due to an oracle deadlock. The logs don't say much more than that,
so it's possible the cause was all three being done at a similar time. Still, we
should look into this, as this was supposedly fixed by the kickstart index.

Comment 1 David Kovalsky 2007-05-17 08:18:35 EDT

I'm one of them :-) I tried to push procmail errata - 2007:9165-2.

Today I pushed 2 erratas simultaniously, 2007:9208 & 2007:9165 both from
errata.devel, without any issues.

Comment 2 David Kovalsky 2007-05-17 08:31:12 EDT

Scratch the second paragraph, my fingers are writing something totally different
from what my brain wants. 

Today pushing two erratas at once from errata.devel RHBA-2007:9208 - rusers bug
fix update and RHBA-2007:9154 - mgetty bug fix update (1 second after the first)
I got the deadlock error after waiting for a few minutes. Seems easily reproduceble.

...
Done Pushing Files
Updating issue and update dates to 2007-05-17.
Pushing to RHN (this could take a while)....

Error Message:
    ORA-00060: deadlock detected while waiting for resource
Error Class Code: 23
Error Class Info: Could not update database entry.

pushing to RHN (qa):

Server was http://scripts.vip.stage.redhat.com/BUGZILLA/
Content-Type: text/html

Error 	Push to Red Hat Network failed 1.

Please contact errata-maint@redhat.com if you believe this to be in error.
...

Comment 3 Bret McMillan 2007-05-24 11:50:37 EDT

Grant, please track this with the other db stuff

Comment 6 Thomas "Shea" DeAntonio 2017-07-05 11:19:56 EDT

As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).

Note You need to log in before you can comment on or make changes to this bug.