c2.test_api.ApiEc2TestCase.test_create_delete_security_group
nova.tests.unit.api.ec2.test_api.ApiEc2TestCase.test_xmlns_version_matches_request_version
I've seen it in other EC2 related test cases too. Usually running again
will produce a failure in a different test case or none.
** Affects
n in group database: backend
This appears to be because of an incorrect use of conf_fixture
** Affects: nova
Importance: Undecided
Assignee: Johannes Erdfelt (johannes.erdfelt)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Eng
Public bug reported:
While analyzing the slow query log in our public cloud, we ran across
this slow query:
# Query_time: 21.113669 Lock_time: 0.000485 Rows_sent: 46 Rows_examined:
848516
SET timestamp=1412484367;
SELECT anon_1.instances_created_at AS anon_1_instances_created_at,
anon_1.insta
Public bug reported:
While looking at some new code, I noticed this test has a bug.
It's easy to reproduce, just remove the call to logging.mask_password
(but keep the LOG.debug) in nova/virt/vmwareapi/vmops.py:spawn. The test
will still pass.
The reason is because failed assertions raise except
Public bug reported:
Nova used to allow a hard reboot when an instance is already being soft
rebooted. However, with commit cc0be157d005c5588fe5db779fc30fefbf22b44d,
this is no longer allowed.
This is because two new task states were introduced, REBOOT_PENDING and
REBOOT_STARTED (and correspondin
Column('product_id', String(4)),
Column('vendor_id', String(4)),
Column('dev_type', String(8)),
It appears that the model is correct in all cases and a database
migration should be added to make the applied schema match the model
** Affects: nova
Public bug reported:
The model in nova/db/sqlalchemy/model.py defines the compute_node_id
column has a foreign key on to compute_nodes.id
However, neither the 213 migration (which initially introduced the
pci_devices table) nor the collapsed 216 migration actually create that
foreign key.
It loo
Public bug reported:
A recent change changed the task_state behavior of instance deletes:
https://review.openstack.org/#/c/58829/
This leaves the task_state unmodified after a failed delete. Since the
task_state is unmodified, subsequent attempts to delete the instance are
skipped with the messa
Public bug reported:
Doing a return from a finally block will end up silently dropping
exceptions.
This can cause unexpected behavior at runtime where unhandled exceptions
are silently dropped when not intended.
This has caused some tests that would should fail because of API
changes, to end up
Public bug reported:
The compute API allows optionally setting adminPass and key_name for
server creates, but only allows optionally setting adminPass for server
rebuilds.
This means that the key_data for an instance is effectively immutable.
The key pair is retrieved during a server create and s
Public bug reported:
It appears to be because the plugins themselves don't have a filename
that ends in .py so they get skipped. Only the few files in there that
end .py are being checked.
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification bec
Public bug reported:
This was seen during a gate run. It appears to be the root cause of many
of the failures:
2014-03-31 11:38:23.941 1498 ERROR nova.virt.libvirt.driver [-]
[instance: c2399029-14b2-4b32-aa9c-b28d5c036d8b] During wait destroy,
instance disappeared.
http://logs.openstack.org/96/
ignee: Johannes Erdfelt (johannes.erdfelt)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => Johannes Erdfelt (johannes.erdfelt)
** Changed in: nova
Status: New => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engin
st of uuid references. "swap" will never match a uuid,
so that test will always be true, even if the code is broken.
** Affects: nova
Importance: Undecided
Assignee: Johannes Erdfelt (johannes.erdfelt)
Status: New
** Changed in: nova
Assignee: (unassigned) => Johan
Public bug reported:
Both execute_get_output() and execute() don't wait until the process is
finished running.
execute_get_output() probably hasn't caused a problem since it at least
does one read and the commands it runs likely would finish (but this
isn't guaranteed).
execute() sets up a PIPE
15 matches
Mail list logo
