Bug #16893
closed
- Description updated (diff)
- Description updated (diff)
- Has duplicate Bug #16972: dead jobs - provisioning nodes (Command 'openstack flavor list -f json') added
- Description updated (diff)
- Status changed from 12 to Fix Under Review
- Assignee set to Loïc Dachary
I can trigger Error 429 in OVH even with the throttling patches, by running a single test 10 times (--num 10). For example:
cw -v ceph-qa-suite --simultaneous-jobs 10 --teuthology-git-url http://github.com/SUSE/teuthology --teuthology-branch wip-opensuse --ceph-qa-suite-git-url http://github.com/SUSE/ceph-qa-suite --suite-branch wip-opensuse-jewel --suite rados --ceph-git-url http://github.com/ceph/ceph --ceph jewel --filter 'rados/objectstore/objectstore.yaml' --upload --num 10
Yeah... the jobs I scheduled after merging immediately died. :-/
- Status changed from Fix Under Review to In Progress
Trying to reproduce the problem to analyze the logs.
ceph-workbench ceph-qa-suite --num 10 --verbose --ceph-qa-suite-git-url http://github.com/ceph/ceph-qa-suite --suite-branch jewel --ceph-git-url http://github.com/ceph/ceph --ceph jewel --suite rados/objectstore/alloc-hint.yaml
ceph-workbench ceph-qa-suite --simultaneous-jobs 100 --num 200 --verbose --ceph-qa-suite-git-url http://github.com/ceph/ceph-qa-suite --suite-branch jewel --ceph-git-url http://github.com/ceph/ceph --ceph jewel --suite rados/objectstore/alloc-hint.yaml
2016-08-30T10:59:41.851 DEBUG:teuthology.misc::sh: openstack -q token issue -c id -f value
2016-08-30T10:59:43.385 DEBUG:teuthology.misc:585bb4248906465994a797afec95696a
2016-08-30T10:59:43.522 INFO:teuthology.openstack:caching OS_TOKEN and setting OS_AUTH_TYPE=v2token during 3600 seconds
...
2016-08-30T11:00:33.580 DEBUG:teuthology.provision:ProvisionOpenStack:create
2016-08-30T11:00:33.580 DEBUG:teuthology.misc::sh: openstack --quiet image list -f json --property name='teuthology-ubuntu-14.04-x86_64'
2016-08-30T11:00:39.760 DEBUG:teuthology.misc:HTTP Client Error (HTTP 429)
I don't understand where the 429 error comes from. Since there is a token available in the environment, it won't query the auth server to obtain a new token, therefore it should not fail with 429.
- Status changed from In Progress to Fix Under Review
- Status changed from Fix Under Review to 12
- Assignee deleted (
Loïc Dachary)
- Status changed from 12 to New
- Status changed from New to Resolved
Also available in: Atom
PDF