multinode-oooq-container scenarios and Fs016/17/20 periodic jobs fails on validate-tempest: Unexpected response code received
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Juan Antonio Osorio Robles |
Bug Description
In most of the fs016 periodic jobs once tempest run finishes, the validate-tempest role fails to generate tempest.html result. It makes very hard to user to debug and go to check tempest.log file for the tempest errors.
https:/
2018-09-20 02:35:29.598462 | primary | TASK [validate-tempest : Generate testrepository.
2018-09-20 02:35:29.615521 | primary | Thursday 20 September 2018 02:35:29 +0000 (0:00:00.672) 0:18:53.370 ****
2018-09-20 02:35:30.688127 | primary | fatal: [undercloud]: FAILED! => {"changed": true, "cmd": "set -o pipefail && testr last --subunit | subunit-1to2 > /home/zuul/
2018-09-20 02:35:30.688196 | primary | ...ignoring
2018-09-20 02:35:30.712744 | primary |
2018-09-20 02:35:30.712900 | primary | TASK [validate-tempest : Generate HTML results file] *******
2018-09-20 02:35:30.733215 | primary | Thursday 20 September 2018 02:35:30 +0000 (0:00:01.117) 0:18:54.488 ****
2018-09-20 02:35:31.726561 | primary | fatal: [undercloud]: FAILED! => {"changed": true, "cmd": "set -o pipefail &&\n subunit2html $(find /home/zuul/
I think we need to seperate the html generation part. otherwise it is very hard to go through logs and find issue.
summary: |
- Fs020 periodic jobs fails to generate tempest results once tempest run - finishes + Fs016/17 periodic jobs fails to generate tempest results once tempest + run finishes |
tags: | added: alert |
tags: | added: ci |
summary: |
- Jobs fails on validate-tempest: Unexpected response code received + multinode-oooq-container scenarios and Fs016/17/20 periodic jobs fails + on validate-tempest: Unexpected response code received |
Changed in tripleo: | |
assignee: | nobody → Juan Antonio Osorio Robles (juan-osorio-robles) |
status: | Triaged → In Progress |
FS 16/17 master seem to work now, however the issue can be found in FS20 rocky promotion job.
In 50% cases of legacy- periodic- tripleo- ci-centos- 7-ovb-1ctlr_ 1comp-featurese t020-rocky runs tempest-validation fails on tempest execution [1] getting Unexpected response code received error [2] and the same in a different run [3].
[1] https:/ /logs.rdoprojec t.org/openstack -periodic/ git.openstack. org/openstack- infra/tripleo- ci/master/ legacy- periodic- tripleo- ci-centos- 7-ovb-1ctlr_ 1comp-featurese t020-rocky/ 6760f43/ job-output. txt.gz# _2018-10- 01_19_30_ 12_985131
[2] https:/ /logs.rdoprojec t.org/openstack -periodic/ git.openstack. org/openstack- infra/tripleo- ci/master/ legacy- periodic- tripleo- ci-centos- 7-ovb-1ctlr_ 1comp-featurese t020-rocky/ 6760f43/ logs/undercloud /var/log/ extra/errors. txt.gz# _2018-10- 01_21_02_ 49_899
[3] https:/ /logs.rdoprojec t.org/openstack -periodic/ git.openstack. org/openstack- infra/tripleo- ci/master/ legacy- periodic- tripleo- ci-centos- 7-ovb-1ctlr_ 1comp-featurese t020-rocky/ 375cc2f/ logs/undercloud /var/log/ extra/errors. txt.gz# _2018-10- 02_16_03_ 18_850