Actions
Bug #11374
closedwip-subset: yaml assembly is putting tasks out-of-order
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):
Description
Here's one example; I am seeing many: http://qa-proxy.ceph.com/teuthology/gregf-2015-04-12_16:25:14-fs-greg-fs-testing-1-testing-basic-multi/844780/config.yaml
tasks: - internal.check_packages: null - internal.lock_machines: - 3 - plana,mira,burnupi - internal.save_config: null - internal.check_lock: null - internal.connect: null - internal.push_inventory: null - internal.serialize_remote_roles: null - internal.check_conflict: null - internal.check_ceph_data: null - internal.vm_setup: null - kernel: *id001 - internal.base: null - internal.archive: null - internal.coredump: null - internal.sudo: null - internal.syslog: null - internal.timer: null - chef: null - clock.check: null - mds_thrash: null - install: null - ceph: null - ceph-fuse: null - workunit: clients: all: - suites/fsstress.sh
Notice that the mds_thrash task is placed ahead of "install". Obviously things go terribly wrong.
As far as I can tell, nothing in the yaml fragments which this job is generated from have changed in more than a year, which leads me to believe that the teuthology code for assembling these must have changed. I'm not sure if it's consistently certain jobs being mis-ordered or if something else is going on.
Actions