© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Would you be able to update the description using the reporting guidelines listed below?
Specifically I'd like to understand which volume backend is being used, what commands were used etc.
OpenStack Compute (nova) bug reporting guidelines:
!!!!!!!
Each bug report needs to provide a minimum of information without
we are not able to address the issue you observed. It is crucial
for other developers to have this information. You can use the
template below, which asks for this information.
"Request for Feature Enhancements" (RFEs) are collected:
* with the blueprint process [1][2][3] (if you're a developer) OR
* via the liason with the operator (ops) community [4].
This means "wishlist" bugs won't get any attention anymore.
You can ask in the #openstack-nova IRC channel on freenode, if you have questions about this.
References:
[1] https:/
[2] https:/
[3] https:/
[4] http://
!!!!!!!
Description
===========
Some prose which explains more in detail what this bug report is
about. If the headline of this report is descriptive enough, skip
this section.
Steps to reproduce
==================
A chronological list of steps which will bring off the
issue you noticed:
* I did X
* then I did Y
* then I did Z
A list of openstack client commands (with correct argument value)
would be the most descriptive example. To get more information use:
$ nova --debug <command> <arg1> <arg2=value>
or
$ openstack --debug <command> <arg1> <arg2=value>
Expected result
===============
After the execution of the steps above, what should have
happened if the issue wasn't present?
Actual result
=============
What happened instead of the expected result?
How did the issue look like?
Environment
===========
1. Exact version of OpenStack you are running. See the following
list for all releases: http://
If this is from a distro please provide
$ dpkg -l | grep nova
or
$ rpm -ql | grep nova
If this is from git, please provide
$ git log -1
2. Which hypervisor did you use?
(For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
What's the version of that?
2. Which storage type did you use?
(For example: Ceph, LVM, GPFS, ...)
What's the version of that?
3. Which networking type did you use?
(For example: nova-network, Neutron with OpenVSwitch, ...)
Logs & Configs
==============
The tool *sosreport* has support for some OpenStack projects.
It's worth having a look at it. For example, if you want to collect
the logs of a compute node you would execute:
$ sudo sosreport -o openstack_nova --batch
on that compute node. Attach the logs to this bug report. Please
consider that these logs need to be collected in "DEBUG" mode.
For tips on reporting VMware virt driver bugs, please see this doc: https:/