or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Do you want to remove this version name and description?
Syncing
xxxxxxxxxx
Debug tempest timeout in baremetal jobs
Issue:-
Tempest is timing out on fs001 running on real baremetal job in 16.2(component pipeline)
Impacted jobs:
This is happening from a while now, Build history , Baremetal jobs are currently not in 16.2 critera, Removed after they faced some infra issue last month, but we would like to add them back in criteria.
https://sf.hosted.upshift.rdu2.redhat.com/logs/openstack-component-baremetal/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-rhel-8-bm_envB-3ctlr_1comp-featureset001-baremetal-rhos-16.2/03f88a7/job-output.txt
Observation:-
But if we take a look at tempest.log we can see tempest run logs only started at 2021-09-23 06:39 (this may be because of timezone difference between nodepool node and undercloud node)
https://sf.hosted.upshift.rdu2.redhat.com/logs/openstack-component-baremetal/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-rhel-8-bm_envB-3ctlr_1comp-featureset001-baremetal-rhos-16.2/03f88a7/logs/undercloud/home/zuul/tempest/tempest.log
No error observed in tempest_run.log, but we can see tempest_run was not completed till logs were collected:-
https://sf.hosted.upshift.rdu2.redhat.com/logs/openstack-component-baremetal/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-rhel-8-bm_envB-3ctlr_1comp-featureset001-baremetal-rhos-16.2/03f88a7/logs/undercloud/var/log/tempest/tempest_run.log
While checking directly on baremetal node, we can see that tempest run was actually completing successfully, and it didn't took much longer only ~15 mins.
Comparision
https://sf.hosted.upshift.rdu2.redhat.com/logs/openstack-component-baremetal/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-rhel-8-ovb-3ctlr_1comp-featureset001-internal-baremetal-rhos-16.2/6255192/job-output.txt
https://sf.hosted.upshift.rdu2.redhat.com/logs/openstack-component-baremetal/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-rhel-8-ovb-3ctlr_1comp-featureset001-internal-baremetal-rhos-16.2/6255192/logs/undercloud/home/zuul/tempest/tempest.log.txt.gz
What's done:-
Confirmed manually tempest test run is not slow, completing within ~15mins
Possible explanation of 4 hours difference between "TASK [os_tempest : Execute tempest tests]" and tempest.log start time.