opendev/system-config
Code Issues Proposed changes

Cleanup tempest-logs.html

Browse Source 
Correct a few typos and update the link to this file.

Change-Id: Ia8f22d458f7f985861050a52235230dc84c257e2
This commit is contained in:
Joe Gordon 2014-08-27 16:19:05 -07:00
parent 8dd8fa366c
commit bec894a53d
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
modules/openstack_project/files/logs/help/tempest-logs.html
View File

@ -4,7 +4,7 @@
the <a href="../console.html">current tempest run</a>. Within them the <a href="../console.html">current tempest run</a>. Within them
should be everything you need to get to the bottom of a test should be everything you need to get to the bottom of a test
failure. The screen-* logs will be your most valuable tools in this failure. The screen-* logs will be your most valuable tools in this
process. Use the timestamp of a the failed test in process. Use the timestamp of the failed test in
the <a href="../console.html">current tempest run</a>. the <a href="../console.html">current tempest run</a>.
</p> </p>
<h2>Nova Compute Fails</h2> <h2>Nova Compute Fails</h2>
@ -15,7 +15,7 @@
<ul> <ul>
<li><a href="screen-n-api.txt.gz">screen-n-api.txt.gz</a> - the nova <li><a href="screen-n-api.txt.gz">screen-n-api.txt.gz</a> - the nova
api log, which will show top level failures. Make sure the request api log, which will show top level failures. Make sure the request
that was being sent in actually suceeded. that was being sent in actually succeeded.
<li><a href="screen-n-cpu.txt.gz">screen-n-cpu.txt.gz</a> - the nova <li><a href="screen-n-cpu.txt.gz">screen-n-cpu.txt.gz</a> - the nova
compute log. If a libvirt or qemu issue happened during guest compute log. If a libvirt or qemu issue happened during guest
creation it will be here. creation it will be here.
@ -32,7 +32,7 @@
<ul> <ul>
<li><a href="screen-c-api.txt.gz">screen-c-api.txt.gz</a> - the <li><a href="screen-c-api.txt.gz">screen-c-api.txt.gz</a> - the
cinder api log, which will show top level failures. Make sure cinder api log, which will show top level failures. Make sure
the request that was being sent in actually suceeded. the request that was being sent in actually succeeded.
<li><a href="screen-c-vol.txt.gz">screen-c-vol.txt.gz</a> - the <li><a href="screen-c-vol.txt.gz">screen-c-vol.txt.gz</a> - the
cinder agent log. If there was a local allocation error it will be cinder agent log. If there was a local allocation error it will be
here. here.
@ -48,8 +48,8 @@
<a href="https://git.openstack.org/cgit/openstack-infra/config"> <a href="https://git.openstack.org/cgit/openstack-infra/config">
openstack-infra/config</a> openstack-infra/config</a>
project, and can be found at project, and can be found at
<a href="https://git.openstack.org/cgit/openstack-infra/config/tree/modules/openstack_project/files/logs/help/tempest_logs.html"> <a href="https://git.openstack.org/cgit/openstack-infra/config/tree/modules/openstack_project/files/logs/help/tempest-logs.html">
modules/openstack_project/files/logs/help/tempest_logs.html modules/openstack_project/files/logs/help/tempest-logs.html
</a>. </a>.
The file can be updated via the standard OpenStack Gerrit Review process. The file can be updated via the standard OpenStack Gerrit Review process.
</p> </p>