April 2011 - autoqa-devel - Fedora mailing-lists

[AutoQA] #251: Move autotest applications into /usr/*bin
by fedora-badges 26 Sep '12

26 Sep '12

#251: Move autotest applications into /usr/*bin -----------------------+---------------------------------------------------- Reporter: jlaska | Owner: Type: task | Status: new Priority: minor | Milestone: Packaging, Review, & Deployment Component: packaging | Keywords: -----------------------+---------------------------------------------------- The autotest package should supply binaries in /usr/bin/ ... so we can rely on PATH and not have to call autotest with the full-path (/usr/share/autotest/client/bin/autotest) when scheduling jobs in '/usr/bin/autoqa'. Alternatively, the autotest package could drop a script that updates PATH appropriately into /etc/profile.d/autotest. But yuck. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/251> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 2

[AutoQA] #191: Submit autotest for Fedora package approval
by fedora-badges 26 Sep '12

26 Sep '12

#191: Submit autotest for Fedora package approval -----------------------+---------------------------------------------------- Reporter: jlaska | Owner: Type: task | Status: new Priority: major | Milestone: Packaging and Review Component: packaging | Version: 1.0 Keywords: | -----------------------+---------------------------------------------------- * https://bugzilla.redhat.com/show_bug.cgi?id=548522 Currently stalled, pending packaging of the gwt package. This includes packaging all bundled .jar files included with gwt. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/191> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 3

[AutoQA] #157: conflicts: requested arch not respected
by fedora-badges 06 Aug '12

06 Aug '12

#157: conflicts: requested arch not respected --------------------+------------------------------------------------------- Reporter: kparal | Owner: Type: defect | Status: new Priority: major | Milestone: Component: tests | Version: 1.0 Keywords: | --------------------+------------------------------------------------------- This is a bug in the potential_conflict.py script in tests/conflicts/. Usage suggests using --arch options for specifying requested architecture to be tested. But if you look at the attached log, the first and second output match (that's correct), but the third doesn't match, even though it should. Everything was tested on x86_64 machine. Also from the usage line it is not clear whether --arch is related only to particular yum repository selection (replacing $basearch keyword), or whether it also relates to packages built for one architecture but being in different repo (e.g. i686 packages are very often in x86_64 repo). I have looked into the source code of the script and it seems that the --arch option is not used at all, just printed out in the usage help?? Seth, you're listed as script author. Any comments on that? Thanks. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/157> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 7

[AutoQA] #270: Package and submit for review - compat-Django-1.0.4
by fedora-badges 02 Aug '12

02 Aug '12

#270: Package and submit for review - compat-Django-1.0.4 -----------------------+---------------------------------------------------- Reporter: jlaska | Owner: Type: task | Status: new Priority: major | Milestone: Package Update Acceptance Test Plan Component: packaging | Keywords: -----------------------+---------------------------------------------------- Currently packaged so that it can coexist with the current Django package (see http://repos.fedorapeople.org/repos/fedora- qa/autoqa/fedora-14-testing/). I need to port existing security patches linked from http://www.djangoproject.com/weblog/2010/dec/22/security/ Once patched, submit for review ... and enjoy. Eventually autotest will be updated to use Django-1.2 ... but packaging Django-1.0.4 removes one more packaging obstacle to having autotest as an official Fedora package. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/270> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 2

[AutoQA] #206: Update bodhi to enforce Package Update Acceptance policy
by fedora-badges 26 Mar '12

26 Mar '12

#206: Update bodhi to enforce Package Update Acceptance policy ----------------------------+----------------------------------------------- Reporter: wwoods | Owner: Type: task | Status: new Priority: major | Milestone: Package Update Acceptance Test Plan Component: infrastructure | Version: 1.0 Keywords: | ----------------------------+----------------------------------------------- In order to enforce the Package Update Acceptance Test Plan, Bodhi will need be modified to reject the push of any package that fails acceptance testing. The acceptance tests may need to send status/data to bodhi in order for it to make decisions about policy (see e.g. ticket #205). Later bodhi might just get data from resultdb (see that milestone for details). -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/206> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 7

[AutoQA] #252: Provide all autotest client combinations that we need
by fedora-badges 16 Mar '12

16 Mar '12

#252: Provide all autotest client combinations that we need ------------------------+--------------------------------------------------- Reporter: kparal | Owner: Type: task | Status: new Priority: major | Milestone: 0.5.0 Component: production | Keywords: ------------------------+--------------------------------------------------- Currently our production server at http://autoqa.fedoraproject.org/ has 6 autotest clients assigned, all bare metals with Fedora 13 installed, with mixed architectures. But we need more. According to https://fedoraproject.org/wiki/Managing_autotest_labels we have two architecture labels, two fedora release labels (the two currently supported Fedora releases, I would omit Rawhide for now) and two virt labels (virtual machine or bare metal). We need machines for every combination of those labels (that is 8 IICC - if I count correctly). And we would like to see a bit more 64bit machines, because we use them for noarch tests. Currently the only test that really requires all those combinations is initscripts test. But there will be more in the future. It is quite some farm, but it seems we'll have to build it. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/252> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 3

[AutoQA] #255: Use Config class to simplify access to configuration options
by fedora-badges 07 Mar '12

07 Mar '12

#255: Use Config class to simplify access to configuration options --------------------+------------------------------------------------------- Reporter: kparal | Owner: Type: task | Status: new Priority: minor | Milestone: Component: core | Keywords: --------------------+------------------------------------------------------- Currently all our libraries and tests use ConfigParser and parse our configuration files (autoqa.conf, fas.conf, etc) directly. That is not ideal, it involves many lines of code, converting to correct variable types (int, bool), handling default values, and so on. We should create a Python class Config, which is initialized once in the beginning, and then can be access globally and easily from any other module. It will handle default values and type conversion centrally in one place. Also access will be much easier. PS: We already have autoqa.config module. Maybe we just don't use it? -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/255> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 6

[AutoQA] #186: Automate media kit sanity tests
by fedora-badges 05 Mar '12

05 Mar '12

#186: Automate media kit sanity tests --------------------+------------------------------------------------------- Reporter: jlaska | Owner: lili Type: task | Status: new Priority: major | Milestone: Automate installation test plan Component: tests | Version: 1.0 Keywords: | --------------------+------------------------------------------------------- This ticket is intended to track automating the mediakit sanity tests (http://fedoraproject.org/wiki/Category:Installer_Image_Sanity_Test_Cases) Discussion already underway, along with code in Liam's private branch. For details see https://fedorahosted.org/pipermail/autoqa- devel/2010-June/000595.html -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/186> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 9

[AutoQA] #194: Incorporate automated anaconda storage suite
by fedora-badges 05 Mar '12

05 Mar '12

#194: Incorporate automated anaconda storage suite --------------------+------------------------------------------------------- Reporter: jlaska | Owner: Type: task | Status: new Priority: major | Milestone: Automate installation test plan Component: tests | Version: 1.0 Keywords: | --------------------+------------------------------------------------------- Chris Lumens has developed a virt-based test suite to automate different disk/storage install scenarios. I've discussed this briefly with Chris, but I'd be interested in seeing his test suite incorporated within autoqa and run on a regular interval (perhaps along-side Liam's install tests). The tests are currently available at http://clumens.fedorapeople.org /anaconda-storage-test/ -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/194> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 1

[AutoQA] #311: Improve Koji call performance with koji.ClientSession.multiCall
by fedora-badges 03 Feb '12

03 Feb '12

#311: Improve Koji call performance with koji.ClientSession.multiCall -------------------------+-------------------------------------------------- Reporter: kparal | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Finger Food Component: core | Keywords: -------------------------+-------------------------------------------------- We use koji calls quite extensively in watchers/tests/libraries. Some of the calls may be sped up substantially by using multicalls (executing multiple calls at once and waiting for a grouped result). See docstring at koji.!ClientSession.multiCall: {{{ Execute a multicall (multiple function calls passed to the server and executed at the same time, with results being returned in a batch). Before calling this method, the self.multicall field must have been set to True, and then one or more methods must have been called on the current session (those method calls will return None). On executing the multicall, the self.multicall field will be reset to False (so subsequent method calls will be executed immediately) and results will be returned in a list. The list will contain one element for each method added to the multicall, in the order it was added to the multicall. Each element of the list will be either a one-element list containing the result of the method call, or a map containing "faultCode" and "faultString" keys, describing the error that occurred during the method call. }}} Go through our code and re-write standard Koji calls to multicalls whenever possible. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/311> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 4

[AutoQA] #289: Missing autotest debug logs
by fedora-badges 12 Jan '12

12 Jan '12

#289: Missing autotest debug logs ----------------------+----------------------------------------------------- Reporter: kparal | Owner: Type: defect | Status: new Priority: major | Milestone: Hot issues Component: autotest | Keywords: ----------------------+----------------------------------------------------- I've found a test run where autotest debug logs are missing. What's wrong? We need them. http://autoqa.fedoraproject.org/results/72107-autotest/qa06.c.fedoraproject… -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/289> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 7

[AutoQA] #182: Write virt management script
by fedora-badges 22 Nov '11

22 Nov '11

#182: Write virt management script ----------------------------+----------------------------------------------- Reporter: kparal | Owner: Type: task | Status: new Priority: major | Milestone: Virtualization Component: infrastructure | Version: 1.0 Keywords: | ----------------------------+----------------------------------------------- We must write a virt management script that will be able to the basic tasks for us: * query for available virt systems that we can use * switch between "real" disk and a disk snapshot for a virt system * revert a disk snapshot for a virt system * perform some command in a virt system - e.g. "yum update" for keeping it periodically up-to-date * install/reinstall a virt-system for us with specified distro * (some more to come?) We may want to use some pre-defined names syntax to recognize what virt systems do we have. For example: {{{ /dev/vg_autoqa/F12_i686_1 /dev/vg_autoqa/F12_i686_1-snap }}} -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/182> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

2 4

[AutoQA] #254: Trasnfer autoqa library to autotest clients
by fedora-badges 21 Nov '11

21 Nov '11

#254: Trasnfer autoqa library to autotest clients -------------------------+-------------------------------------------------- Reporter: kparal | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: autotest | Keywords: -------------------------+-------------------------------------------------- Currently autotest clients do not require autotest package installed, autotest server transfers all necessary files over rsync. But autotest clients require autoqa installed (because of our autoqa libraries), which in turn requires autotest. This creates quite a lot of confusion where to edit which files when testing new stuff. It would be much easier if we somehow transferred also the autoqa library together with autotest files. Can we bend autotest a little to rsync also our library to the client? Or, can we use similar approach as copying the config files to the test directory also with autoqa library? It would be great. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/254> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 14

[AutoQA] #196: Log failed job scheduling
by fedora-badges 11 Nov '11

11 Nov '11

#196: Log failed job scheduling -------------------------+-------------------------------------------------- Reporter: kparal | Owner: kparal Type: enhancement | Status: new Priority: major | Milestone: Component: harness | Version: 1.0 Keywords: | -------------------------+-------------------------------------------------- Currently when we schedule a job and it fails, we just print it out and forget about it: {{{ retval = schedule_job(control, email=email, name=testname, required_arch=arch, dryrun=opts.dryrun, labels=aq_labels) if retval != 0: print "ERROR: failed to schedule job %s" % testname }}} That should not be the case. We should: * use syslog and log important stuff to /var/log/autoqa.log or similar * send an email about failed scheduling to autoqa-results That way we will know something is wrong and will be able to fix it. Otherwise it just silently fails and we don't know about it. Feel free to reassign the ticket if you want to work on it. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/196> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 14

[AutoQA] #192: Submit autoqa for Fedora package approval
by fedora-badges 13 Oct '11

13 Oct '11

#192: Submit autoqa for Fedora package approval -----------------------+---------------------------------------------------- Reporter: jlaska | Owner: Type: task | Status: new Priority: major | Milestone: Packaging and Review Component: packaging | Version: 1.0 Keywords: | -----------------------+---------------------------------------------------- Currently stalled, pending packaging of the gwt and autotest package. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/192> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 2

[AutoQA] #180: Initscript review: vsftpd
by fedora-badges 10 Oct '11

10 Oct '11

#180: Initscript review: vsftpd ----------------------+----------------------------------------------------- Reporter: jskladan | Owner: Type: task | Status: new Priority: minor | Milestone: Initscripts review Component: tests | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- Check the test according to the <https://fedorahosted.org/autoqa/wiki/initscripts> -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/180> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 3

[AutoQA] #178: Initscript review: squid
by fedora-badges 10 Oct '11

10 Oct '11

#178: Initscript review: squid ----------------------+----------------------------------------------------- Reporter: jskladan | Owner: Type: task | Status: new Priority: minor | Milestone: Initscripts review Component: tests | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- Check the test according to the <https://fedorahosted.org/autoqa/wiki/initscripts> -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/178> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 1

[AutoQA] #177: Initscript review: setroubleshoot
by fedora-badges 10 Oct '11

10 Oct '11

#177: Initscript review: setroubleshoot ----------------------+----------------------------------------------------- Reporter: jskladan | Owner: Type: task | Status: new Priority: minor | Milestone: Initscripts review Component: tests | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- Check the test according to the <https://fedorahosted.org/autoqa/wiki/initscripts> -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/177> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 1

[AutoQA] #175: Initscript review: postgresql
by fedora-badges 10 Oct '11

10 Oct '11

#175: Initscript review: postgresql ----------------------+----------------------------------------------------- Reporter: jskladan | Owner: Type: task | Status: new Priority: minor | Milestone: Initscripts review Component: tests | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- Check the test according to the <https://fedorahosted.org/autoqa/wiki/initscripts> -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/175> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 4

[AutoQA] #174: Initscript review: openswan
by fedora-badges 10 Oct '11

10 Oct '11

#174: Initscript review: openswan ----------------------+----------------------------------------------------- Reporter: jskladan | Owner: Type: task | Status: new Priority: minor | Milestone: Initscripts review Component: tests | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- Check the test according to the <https://fedorahosted.org/autoqa/wiki/initscripts> -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/174> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 1

[AutoQA] #173: Initscript review: openldap
by fedora-badges 10 Oct '11

10 Oct '11

#173: Initscript review: openldap ----------------------+----------------------------------------------------- Reporter: jskladan | Owner: Type: task | Status: new Priority: minor | Milestone: Initscripts review Component: tests | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- Check the test according to the <https://fedorahosted.org/autoqa/wiki/initscripts> -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/173> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 1

[AutoQA] #171: Initscript review: nss-pam-ldapd
by fedora-badges 10 Oct '11

10 Oct '11

#171: Initscript review: nss-pam-ldapd ----------------------+----------------------------------------------------- Reporter: jskladan | Owner: Type: task | Status: new Priority: minor | Milestone: Initscripts review Component: tests | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- Check the test according to the <https://fedorahosted.org/autoqa/wiki/initscripts> -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/171> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 1

[AutoQA] #169: Initscript review: net-snmp
by fedora-badges 10 Oct '11

10 Oct '11

#169: Initscript review: net-snmp ----------------------+----------------------------------------------------- Reporter: jskladan | Owner: Type: task | Status: new Priority: minor | Milestone: Initscripts review Component: tests | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- Check the test according to the <https://fedorahosted.org/autoqa/wiki/initscripts> -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/169> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 3

[AutoQA] #125: initscripts: Choosing the right repo for dependencies
by fedora-badges 10 Oct '11

10 Oct '11

#125: initscripts: Choosing the right repo for dependencies -------------------------+-------------------------------------------------- Reporter: kparal | Owner: jskladan Type: task | Status: new Priority: major | Milestone: Component: tests | Version: 1.0 Keywords: initscripts | -------------------------+-------------------------------------------------- Currently after new Koji build the initscripts test downloads all relevant binary packages (related to the particular source package) and installs them. But the RPM dependencies are installed from stable/updates repos, not from Koji. Also the dependencies parsed out of Makefile are installed from stable/updates repos. We have to inquire a little more into this situation. Is it sufficient/desirable? Or is it desirable to download dependencies from updates-testing or bleeding edge Koji? May the initscripts test sometimes fail because of insufficient dependencies are in stable/updates repos? This also depends on cases when we are going to use initscripts test. If it will be used with Bodhi hook, it will be probably easier to solve it than when used with Koji hook. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/125> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 2

[AutoQA] #224: initscripts: installing older package then current fails
by fedora-badges 10 Oct '11

10 Oct '11

#224: initscripts: installing older package then current fails --------------------+------------------------------------------------------- Reporter: kparal | Owner: jskladan Type: defect | Status: new Priority: major | Milestone: Package Update Acceptance Test Plan Component: tests | Version: 1.0 Keywords: | --------------------+------------------------------------------------------- In initscripts test we install some packages. But if those packages are older than currently installed, the test crashes. Usually we test only very new package builds, but in same cases this can also happen and we should have it handled. {{{ [root@aqd autoqa]# autoqa post-koji-build --kojitag dist-f13 openssh-5.4p1-1.fc13 --local -t initscripts 14:28:27 INFO | Writing results to /usr/share/autotest/client/results /post-koji-build:initscripts.noarch 14:28:27 INFO | Initializing the state engine 14:28:27 DEBUG| Persistent state variable __steps now set to [] 14:28:27 INFO | Symlinking init scripts 14:28:27 DEBUG| Running 'grep :initdefault: /etc/inittab' 14:28:27 DEBUG| Running 'ln -sf /usr/share/autotest/client/tools/autotest /etc/init.d/autotest' 14:28:27 DEBUG| Running 'ln -sf /usr/share/autotest/client/tools/autotest /etc/rc3.d/S99autotest' 14:28:27 DEBUG| Dropping caches 14:28:27 DEBUG| Running 'sync' 14:28:27 DEBUG| Running 'echo 3 > /proc/sys/vm/drop_caches' 14:28:27 DEBUG| Running 'rpm -qa' 14:28:28 INFO | START ---- ---- timestamp=1284121708 localtime=Sep 10 14:28:28 14:28:28 DEBUG| Persistent state variable __group_level now set to 1 14:28:28 INFO | START initscripts initscripts timestamp=1284121708 localtime=Sep 10 14:28:28 14:28:28 DEBUG| Persistent state variable __group_level now set to 2 14:28:28 DEBUG| Crash handling system enabled 14:28:28 DEBUG| Running 'rpm -qa' 14:28:29 INFO | /etc/yum.repos.d/beakerlib.repo:baseurl=http://afri.fedorapeople.org/beakerlib/ 14:28:29 DEBUG| Running 'yum -y install beakerlib' 14:28:29 DEBUG| [stdout] Setting up Install Process 14:28:30 DEBUG| [stdout] Package beakerlib-1.3-1.fc13.noarch already installed and latest version 14:28:30 DEBUG| [stdout] Nothing to do 14:28:31 INFO | Test started. Number of iterations: 1 14:28:31 INFO | Executing iteration 1 of 1 14:28:31 INFO | Dropping caches between iterations 14:28:31 DEBUG| Running 'sync' 14:28:31 DEBUG| Running 'echo 3 > /proc/sys/vm/drop_caches' 14:28:31 INFO | ======================================== 14:28:31 INFO | openssh-5.4p1-1.fc13 14:28:31 INFO | ======================================== 14:28:32 INFO | Saving RPMs to /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms 14:28:32 INFO | Grabbing http://koji.fedoraproject.org/packages/openssh/5.4p1/1.fc13/x86_64/pam_ssh_… 14:28:34 INFO | Grabbing http://koji.fedoraproject.org/packages/openssh/5.4p1/1.fc13/x86_64 /openssh-askpass-5.4p1-1.fc13.x86_64.rpm 14:28:35 INFO | Grabbing http://koji.fedoraproject.org/packages/openssh/5.4p1/1.fc13/x86_64 /openssh-server-5.4p1-1.fc13.x86_64.rpm 14:28:37 INFO | Grabbing http://koji.fedoraproject.org/packages/openssh/5.4p1/1.fc13/x86_64 /openssh-clients-5.4p1-1.fc13.x86_64.rpm 14:28:39 INFO | Grabbing http://koji.fedoraproject.org/packages/openssh/5.4p1/1.fc13/x86_64/openssh-… 14:28:41 DEBUG| Running 'yum -y --nogpgcheck localinstall /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/pam_ssh_agent_auth-0.9.2-24.1.fc13.x86_64.rpm /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh- askpass-5.4p1-1.fc13.x86_64.rpm /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh- server-5.4p1-1.fc13.x86_64.rpm /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh- clients-5.4p1-1.fc13.x86_64.rpm /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-5.4p1-1.fc13.x86_64.rpm' 14:28:47 ERROR| Exception escaping from test: Traceback (most recent call last): File "/usr/share/autotest/client/common_lib/test.py", line 384, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/usr/share/autotest/client/common_lib/test.py", line 570, in _call_test_function return func(*args, **dargs) File "/usr/share/autotest/client/common_lib/test.py", line 279, in execute postprocess_profiled_run, args, dargs) File "/usr/share/autotest/client/common_lib/test.py", line 201, in _call_run_once self.run_once(*args, **dargs) File "/usr/lib/python2.6/site-packages/autoqa/decorators.py", line 71, in newf f_result = f(*args, **kwargs) #call the decorated function File "/usr/share/autotest/client/site_tests/initscripts/initscripts.py", line 158, in run_once utils.system_output(cmd) File "/usr/share/autotest/client/common_lib/utils.py", line 689, in system_output args=args).stdout File "/usr/share/autotest/client/common_lib/utils.py", line 425, in run "Command returned non-zero exit status") CmdError: Command <yum -y --nogpgcheck localinstall /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/pam_ssh_agent_auth-0.9.2-24.1.fc13.x86_64.rpm /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh- askpass-5.4p1-1.fc13.x86_64.rpm /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh- server-5.4p1-1.fc13.x86_64.rpm /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh- clients-5.4p1-1.fc13.x86_64.rpm /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-5.4p1-1.fc13.x86_64.rpm> failed, rc=1, Command returned non-zero exit status * Command: yum -y --nogpgcheck localinstall /usr/share/autotest/client/tmp/tmpS_K1om _initscripts/rpms/pam_ssh_agent_auth-0.9.2-24.1.fc13.x86_64.rpm /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh- askpass-5.4p1-1.fc13.x86_64.rpm /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh- server-5.4p1-1.fc13.x86_64.rpm /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh- clients-5.4p1-1.fc13.x86_64.rpm /usr/share/autotest/client/tmp/tmpS_K1om_i nitscripts/rpms/openssh-5.4p1-1.fc13.x86_64.rpm Exit status: 1 Duration: 0 stdout: Setting up Local Package Process Examining /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/pam_ssh_agent_auth-0.9.2-24.1.fc13.x86_64.rpm: pam_ssh_agent_auth-0.9.2-24.1.fc13.x86_64 Marking /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/pam_ssh_agent_auth-0.9.2-24.1.fc13.x86_64.rpm to be installed Examining /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms /openssh-askpass-5.4p1-1.fc13.x86_64.rpm: openssh- askpass-5.4p1-1.fc13.x86_64 Marking /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh- askpass-5.4p1-1.fc13.x86_64.rpm to be installed Examining /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms /openssh-server-5.4p1-1.fc13.x86_64.rpm: openssh- server-5.4p1-1.fc13.x86_64 /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh- server-5.4p1-1.fc13.x86_64.rpm: does not update installed package. Examining /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms /openssh-clients-5.4p1-1.fc13.x86_64.rpm: openssh- clients-5.4p1-1.fc13.x86_64 /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh- clients-5.4p1-1.fc13.x86_64.rpm: does not update installed package. Examining /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-5.4p1-1.fc13.x86_64.rpm: openssh-5.4p1-1.fc13.x86_64 /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-5.4p1-1.fc13.x86_64.rpm: does not update installed package. Resolving Dependencies --> Running transaction check ---> Package openssh-askpass.x86_64 0:5.4p1-1.fc13 set to be installed --> Processing Dependency: openssh = 5.4p1-1.fc13 for package: openssh- askpass-5.4p1-1.fc13.x86_64 --> Processing Dependency: libX11.so.6()(64bit) for package: openssh- askpass-5.4p1-1.fc13.x86_64 --> Processing Dependency: libatk-1.0.so.0()(64bit) for package: openssh- askpass-5.4p1-1.fc13.x86_64 --> Processing Dependency: libcairo.so.2()(64bit) for package: openssh- askpass-5.4p1-1.fc13.x86_64 --> Processing Dependency: libfontconfig.so.1()(64bit) for package: openssh-askpass-5.4p1-1.fc13.x86_64 --> Processing Dependency: libgdk-x11-2.0.so.0()(64bit) for package: openssh-askpass-5.4p1-1.fc13.x86_64 --> Processing Dependency: libgdk_pixbuf-2.0.so.0()(64bit) for package: openssh-askpass-5.4p1-1.fc13.x86_64 --> Processing Dependency: libgtk-x11-2.0.so.0()(64bit) for package: openssh-askpass-5.4p1-1.fc13.x86_64 --> Processing Dependency: libpango-1.0.so.0()(64bit) for package: openssh-askpass-5.4p1-1.fc13.x86_64 --> Processing Dependency: libpangocairo-1.0.so.0()(64bit) for package: openssh-askpass-5.4p1-1.fc13.x86_64 --> Processing Dependency: libpangoft2-1.0.so.0()(64bit) for package: openssh-askpass-5.4p1-1.fc13.x86_64 ---> Package pam_ssh_agent_auth.x86_64 0:0.9.2-24.1.fc13 set to be installed --> Running transaction check ---> Package atk.x86_64 0:1.30.0-1.fc13 set to be installed ---> Package cairo.x86_64 0:1.8.10-1.fc13 set to be installed --> Processing Dependency: libpng12.so.0(PNG12_0)(64bit) for package: cairo-1.8.10-1.fc13.x86_64 --> Processing Dependency: libpixman-1.so.0()(64bit) for package: cairo-1.8.10-1.fc13.x86_64 --> Processing Dependency: libXrender.so.1()(64bit) for package: cairo-1.8.10-1.fc13.x86_64 --> Processing Dependency: libpng12.so.0()(64bit) for package: cairo-1.8.10-1.fc13.x86_64 ---> Package fontconfig.x86_64 0:2.8.0-1.fc13 set to be installed ---> Package gtk2.x86_64 0:2.20.1-1.fc13 set to be installed --> Processing Dependency: libXrandr >= 1.2.99.4-2 for package: gtk2-2.20.1-1.fc13.x86_64 --> Processing Dependency: libtiff >= 3.6.1 for package: gtk2-2.20.1-1.fc13.x86_64 --> Processing Dependency: hicolor-icon-theme for package: gtk2-2.20.1-1.fc13.x86_64 --> Processing Dependency: libXrandr.so.2()(64bit) for package: gtk2-2.20.1-1.fc13.x86_64 --> Processing Dependency: libtiff.so.3()(64bit) for package: gtk2-2.20.1-1.fc13.x86_64 --> Processing Dependency: libXdamage.so.1()(64bit) for package: gtk2-2.20.1-1.fc13.x86_64 --> Processing Dependency: libXcursor.so.1()(64bit) for package: gtk2-2.20.1-1.fc13.x86_64 --> Processing Dependency: libcups.so.2()(64bit) for package: gtk2-2.20.1-1.fc13.x86_64 --> Processing Dependency: libXi.so.6()(64bit) for package: gtk2-2.20.1-1.fc13.x86_64 --> Processing Dependency: libjasper.so.1()(64bit) for package: gtk2-2.20.1-1.fc13.x86_64 --> Processing Dependency: libXext.so.6()(64bit) for package: gtk2-2.20.1-1.fc13.x86_64 --> Processing Dependency: libXcomposite.so.1()(64bit) for package: gtk2-2.20.1-1.fc13.x86_64 --> Processing Dependency: libXinerama.so.1()(64bit) for package: gtk2-2.20.1-1.fc13.x86_64 --> Processing Dependency: libXfixes.so.3()(64bit) for package: gtk2-2.20.1-1.fc13.x86_64 ---> Package libX11.x86_64 0:1.3.1-3.fc13 set to be installed --> Processing Dependency: libX11-common = 1.3.1-3.fc13 for package: libX11-1.3.1-3.fc13.x86_64 --> Processing Dependency: libxcb.so.1()(64bit) for package: libX11-1.3.1-3.fc13.x86_64 ---> Package openssh-askpass.x86_64 0:5.4p1-1.fc13 set to be installed --> Processing Dependency: openssh = 5.4p1-1.fc13 for package: openssh- askpass-5.4p1-1.fc13.x86_64 ---> Package pango.x86_64 0:1.28.0-1.fc13 set to be installed --> Processing Dependency: libthai >= 0.1.9 for package: pango-1.28.0-1.fc13.x86_64 --> Processing Dependency: libthai.so.0(LIBTHAI_0.1)(64bit) for package: pango-1.28.0-1.fc13.x86_64 --> Processing Dependency: libthai.so.0()(64bit) for package: pango-1.28.0-1.fc13.x86_64 --> Processing Dependency: libXft.so.2()(64bit) for package: pango-1.28.0-1.fc13.x86_64 --> Running transaction check ---> Package cups-libs.x86_64 1:1.4.4-5.fc13 set to be installed --> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: 1:cups-libs-1.4.4-5.fc13.x86_64 --> Processing Dependency: libavahi-common.so.3()(64bit) for package: 1 :cups-libs-1.4.4-5.fc13.x86_64 --> Processing Dependency: libgnutls.so.26()(64bit) for package: 1:cups- libs-1.4.4-5.fc13.x86_64 --> Processing Dependency: libavahi-client.so.3()(64bit) for package: 1 :cups-libs-1.4.4-5.fc13.x86_64 ---> Package hicolor-icon-theme.noarch 0:0.12-1.fc13 set to be installed ---> Package jasper-libs.x86_64 0:1.900.1-15.fc13 set to be installed ---> Package libX11-common.noarch 0:1.3.1-3.fc13 set to be installed ---> Package libXcomposite.x86_64 0:0.4.1-2.fc13 set to be installed ---> Package libXcursor.x86_64 0:1.1.10-4.fc13 set to be installed --> Processing Dependency: dmz-cursor-themes for package: libXcursor-1.1.10-4.fc13.x86_64 ---> Package libXdamage.x86_64 0:1.1.2-2.fc13 set to be installed ---> Package libXext.x86_64 0:1.1.2-2.fc13 set to be installed ---> Package libXfixes.x86_64 0:4.0.4-2.fc13 set to be installed ---> Package libXft.x86_64 0:2.1.14-1.fc13 set to be installed ---> Package libXi.x86_64 0:1.3.2-1.fc13 set to be installed ---> Package libXinerama.x86_64 0:1.1-2.fc13 set to be installed ---> Package libXrandr.x86_64 0:1.3.0-5.fc13 set to be installed ---> Package libXrender.x86_64 0:0.9.5-1.fc13 set to be installed ---> Package libpng.x86_64 2:1.2.44-1.fc13 set to be installed ---> Package libthai.x86_64 0:0.1.14-2.fc13 set to be installed ---> Package libtiff.x86_64 0:3.9.4-1.fc13 set to be installed ---> Package libxcb.x86_64 0:1.5-1.fc13 set to be installed --> Processing Dependency: libXau.so.6()(64bit) for package: libxcb-1.5-1.fc13.x86_64 ---> Package openssh-askpass.x86_64 0:5.4p1-1.fc13 set to be installed --> Processing Dependency: openssh = 5.4p1-1.fc13 for package: openssh- askpass-5.4p1-1.fc13.x86_64 ---> Package pixman.x86_64 0:0.18.0-1.fc13 set to be installed --> Running transaction check ---> Package avahi.x86_64 0:0.6.25-7.fc13 set to be installed --> Processing Dependency: libdaemon >= 0.11 for package: avahi-0.6.25-7.fc13.x86_64 --> Processing Dependency: dbus for package: avahi-0.6.25-7.fc13.x86_64 --> Processing Dependency: libdaemon.so.0()(64bit) for package: avahi-0.6.25-7.fc13.x86_64 ---> Package dmz-cursor-themes.noarch 0:0.4-3.fc13 set to be installed ---> Package gnutls.x86_64 0:2.8.6-2.fc13 set to be installed --> Processing Dependency: libtasn1.so.3(LIBTASN1_0_3)(64bit) for package: gnutls-2.8.6-2.fc13.x86_64 --> Processing Dependency: libtasn1.so.3()(64bit) for package: gnutls-2.8.6-2.fc13.x86_64 ---> Package libXau.x86_64 0:1.0.5-1.fc12 set to be installed ---> Package openssh-askpass.x86_64 0:5.4p1-1.fc13 set to be installed --> Processing Dependency: openssh = 5.4p1-1.fc13 for package: openssh- askpass-5.4p1-1.fc13.x86_64 --> Running transaction check ---> Package dbus.x86_64 1:1.2.24-1.fc13 set to be installed ---> Package libdaemon.x86_64 0:0.14-1.fc13 set to be installed ---> Package libtasn1.x86_64 0:2.4-2.fc13 set to be installed ---> Package openssh-askpass.x86_64 0:5.4p1-1.fc13 set to be installed --> Processing Dependency: openssh = 5.4p1-1.fc13 for package: openssh- askpass-5.4p1-1.fc13.x86_64 --> Finished Dependency Resolution You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest stderr: Error: Package: openssh-askpass-5.4p1-1.fc13.x86_64 (/openssh- askpass-5.4p1-1.fc13.x86_64) Requires: openssh = 5.4p1-1.fc13 Installed: openssh-5.4p1-3.fc13.x86_64 (@updates) openssh = 5.4p1-3.fc13 Available: openssh-5.4p1-1.fc13.x86_64 (fedora) openssh = 5.4p1-1.fc13 }}} -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/224> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 2

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

autoqa-devel April 2011