Bug 514797 - stage repomd.xml regeneration doesn't play nice with RHEL-QE and TPS
Summary: stage repomd.xml regeneration doesn't play nice with RHEL-QE and TPS
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/Backend
Version: RHN Stable
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bryan Kearney
QA Contact: Red Hat Network Quality Assurance
URL:
Whiteboard: Rally DE1
Depends On:
Blocks: rhn-sprint30
TreeView+ depends on / blocked
 
Reported: 2009-07-30 19:55 UTC by Chris Duryee
Modified: 2013-01-10 09:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-09 18:11:03 UTC
Embargoed:


Attachments (Terms of Use)

Description Chris Duryee 2009-07-30 19:55:10 UTC
Description of problem:

In the stage environment, repodata is regenerated using the same method that we used to use in prod. However, during heavy RHEL testing, the following scenario plays out:

* someone pushes new packages to stage channels
* TPS gets run, and hammers XMLRPC
* stage xmlservers attempt to regenerate repodata, and become overwhelmed with requests from TPS
* stage xmlservers become unresponsive
* RHEL-QE complains to Eng Support that stage is down

Ideally, we could use the new repodata regen process in stage, but have some kind of email or trigger that tells TPS when it can run.


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