Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 591413 - bkr task-add stopped working
Summary: bkr task-add stopped working
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Beaker
Classification: Community
Component: command line
Version: 0.5
Hardware: All
OS: Linux
high
high vote
Target Milestone: ---
Assignee: Bill Peck
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-12 08:12 UTC by Karel Srot
Modified: 2010-05-12 09:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-12 09:28:56 UTC


Attachments (Terms of Use)

Description Karel Srot 2010-05-12 08:12:04 UTC
Description of problem:
Probably a week ago bkr task-add (make bkradd) stopped working. It seems like everything is fine but the test is not uploaded to (cannot be found in) beaker.

Version-Release number of selected component (if applicable):
beaker-client-0.5.32-2.el6.noarch

How reproducible:
always for me :-(

Steps to Reproduce:
1. make brkadd  or   bkr task-add test.rpm

Additional info:
[ksrot@dhcp-30-102 sandbox-sanity-test]$ bkr task-add rh-tests-policycoreutils-Sanity-sandbox-sanity-test-1.0-0.noarch.rpm 
rh-tests-policycoreutils-Sanity-sandbox-sanity-test-1.0-0.noarch.rpm
Success
[ksrot@dhcp-30-102 sandbox-sanity-test]$ bkr list-labcontrollers
['lab-stage.rhts.eng.bos.redhat.com', 'lab-devel.rhts.eng.bos.redhat.com']
[ksrot@dhcp-30-102 sandbox-sanity-test]$ cat ~/.beaker_client/config 
HUB_URL = "https://beaker-stage.app.eng.bos.redhat.com"

AUTH_METHOD = "krbv"
KRB_REALM = "REDHAT.COM"

Comment 1 Marian Csontos 2010-05-12 09:28:56 UTC
Using beaker-stage in conf file. Task submitted fine to the stage server and was missing on production server only.


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