Bug 602005 - enable tests repository in every provisioned system
Summary: enable tests repository in every provisioned system
Alias: None
Product: Beaker
Classification: Community
Component: lab controller
Version: 0.5
Hardware: All
OS: Linux
high vote
Target Milestone: ---
Assignee: Raymond Mancy
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-09 01:14 UTC by Hushan Jia
Modified: 2015-05-04 03:28 UTC (History)
5 users (show)

Clone Of:
Last Closed: 2010-08-10 03:03:24 UTC

Attachments (Terms of Use)

Description Hushan Jia 2010-06-09 01:14:34 UTC
Description of problem:
It is very often that we take a system, install some tests, and run them manually, to make things convenient, so could you add the harness repo and the tests repo when install the system, just as like beaker-os repo.

I think it is simply add

repo --name="beaker-harness" --baseurl=http://download.devel.redhat.com/yum/redhat/rhts/harness/
repo --name="rhts tests development" --baseurl=http://rhts.redhat.com/rpms/development/noarch/noarch

into the anaconda kickstart file for installation.

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Marian Csontos 2010-06-09 06:55:52 UTC
This works as you said when "Schedule > Reserve" is used instead of System > Take.

Is there any particular reason for not using Reserve?

Comment 2 Hushan Jia 2010-06-10 07:20:53 UTC
I am not sure how the system list is generated when I click the show systems button, but I cant find the many system I want to reserve, the only way is to goto machine page and take, or use legacy rhts reserve workflow.

Comment 3 Raymond Mancy 2010-06-10 08:08:56 UTC
Hushan, can you give specific details so we verify it is/isn't working as expected ?


Comment 4 Hushan Jia 2010-06-10 10:19:57 UTC
Hi Raymond, the problem is the system list showed by show systems in scheduler/reserve is less than I search the systems/available, so that I met this problem, the machine I wnat to reserve is not in the list.

Comment 5 Raymond Mancy 2010-06-10 23:32:52 UTC
Hi Hushan,
There are other factors at play though,like what distro's a machine can support.

Comment 6 Hushan Jia 2010-06-11 00:47:28 UTC
This is an example, at scheduler/reserve page, select the Reserve Criteria:
Arch: i386
Distro Family: RedHatEnterpriseLinux6
Method: nfs
Select Distro: RHEL6.0-20100603.1_nfs server i386

then do show systems, there is no amd-dinar systems which is I want to reserve.

Comment 7 Raymond Mancy 2010-06-11 01:55:52 UTC
Hi Hushan,
I didn't check all the dinar machines, but at least on amd-dinar-01.lab.bos.redhat.com you need to be in one of the following groups

 Kernel Hardware  	   	
 Release Test Team 	
 Kernel QE 	
 Virt QE 		

I had a quick look and I couldn't see you were in any of them.

Comment 8 Hushan Jia 2010-06-11 02:01:34 UTC
Hi Raymond, I am in Kernel QE, and I can take it in the machine page...

Comment 9 Raymond Mancy 2010-06-11 03:50:40 UTC
Ok, this looks like it could be a bug. 
The following query:
return query.filter(and_(

Says to me that a machine that has a group is never available,even to those who are part of a group that has the system.
Is this expected behaviour Bill ?

Comment 10 Hushan Jia 2010-07-14 01:43:09 UTC
Hi, still not able to queue reservation on those machine which I am in the group, the only way to reserve these machine is to use legacy rhts reserve workflow, so would you consider this a blocker? any update on this?

Comment 11 Bill Peck 2010-07-20 14:58:14 UTC
I'm denying the beaker-blocker on this.  Since we didn't have that functionality previously.

I recognise there is an issue with the reservation code, I believe thats covered by this bz 612710

Comment 12 Marian Csontos 2010-08-09 12:08:37 UTC
Folks, this BZ diverted from what's in Subject/Description. Clean it up please.


Comment 13 Raymond Mancy 2010-08-10 03:03:24 UTC
Closing,the original problem described in this bug is fixed in the current release

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