Bug 769531 - After the beaker upgrade more jobs cannot be installed.
Summary: After the beaker upgrade more jobs cannot be installed.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Beaker
Classification: Retired
Component: lab controller
Version: 0.8
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
Assignee: Bill Peck
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 593663 769286 832523
TreeView+ depends on / blocked
 
Reported: 2011-12-21 08:45 UTC by Petr Sklenar
Modified: 2012-06-15 16:19 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-21 13:24:27 UTC
Embargoed:


Attachments (Terms of Use)

Description Petr Sklenar 2011-12-21 08:45:36 UTC
Description of problem:
After the beaker upgrade much more jobs cannot be installed.

Version-Release number of selected component (if applicable):
Beaker has been upgraded to relase 0.8 running on RHEL 6

How reproducible:
20x more than before upgrade

Steps to Reproduce:
1. try to schedule any job
  
Actual results:
20% of my job ends with /distribution/install issues

External watchdog expired
Recipe ID 362460 does not match any systems 

https://beaker.engineering.redhat.com/jobs/172921
https://beaker.engineering.redhat.com/jobs/173471
https://beaker.engineering.redhat.com/jobs/173150

Expected results:
1% is failure

Additional info:

Comment 1 Bill Peck 2011-12-21 13:24:27 UTC
Hi Petr,

These jobs failed because of the issue where the TLV lab controller imports the distros under a different name.  I manually deleted the bad distros and we are investigating why this happens in the first place.

https://beaker.engineering.redhat.com/jobs/173471
https://beaker.engineering.redhat.com/jobs/173150

The first job that failed on the kvm host is harder to figure out.  If the console had worked it might have given me a clue.  But as it stands I don't have enough info to know why.


In the future please file install issues like this as rt tickets.


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