Bug 794482 - repeated installations of the same test
Summary: repeated installations of the same test
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Beaker
Classification: Retired
Component: beah
Version: 0.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: Nick Coghlan
QA Contact:
URL:
Whiteboard: MC
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-16 22:46 UTC by Gurhan Ozen
Modified: 2013-11-04 02:02 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-07 07:24:15 UTC


Attachments (Terms of Use)

Description Gurhan Ozen 2012-02-16 22:46:51 UTC
Description of problem:

There is a good possibility that i have screwed something up here, but i can't find it out and I want to find out the root cause of this. 
If you look at the job:

https://beaker.engineering.redhat.com/jobs/193895

the raw beah logs for the test /distribution/virt/install/scratch4test 	 show that, it's trying to reinstall tmp-distribution-virt-install-scratch4test package in a loop. 
http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2012/02/1938/193895/409859/4584408/debug/.task_beah_raw
http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2012/02/1938/193895/409859/4584408/debug/task_log

I have intervened manually and did a yum search for the test, and there only was one package for it. 

Version-Release number of selected component (if applicable):


How reproducible:
For the job given above it should be everytime. Just clone the job.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Nick Coghlan 2012-10-17 04:39:56 UTC
Bulk reassignment of issues as Bill has moved to another team.

Comment 2 Min Shin 2012-11-07 07:24:15 UTC
This bugs is closed as it is either not in the current Beaker scope or we could not find sufficient data in the bug report for consideration.
Please feel free to reopen the bug with additional information and/or business cases behind it.


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