] SQL0964C The transaction log for the database is full.
SQLSTATE=57011 SQLCODE=-964 'DELETE FROM token WHERE token.expires < ?'
(datetime.datetime(2013, 11, 18, 8, 10, 37, 519596),)
** Affects: keystone
Importance: Undecided
Assignee: John Warren (jswarren)
Status
Public bug reported:
The fix for bug #1243195 added upper-bound checking for flavor fields
based on sys.maxint. The problem is that the value of maxint varies by
platform (either 32- or 64-bit signed integers), while the INTEGER type
in databases is limited to 32-bit signed integers. This means
Public bug reported:
In the nova.virt.libvirt.driver.LibvirtDriver. _get_new_connection
method two different libvirt event handlers are registered, one for
lifecycle events (_event_lifecycle_callback) and one for connection
events (_close_callback). These callbacks are called by a native thread
Public bug reported:
Libvirt's close callback causes deadlocks
Unlike libvirt's lifecycle event callback which is triggered every time
an event occurs, the close callback is only triggered when an attempt is
made to use a connection that has been closed. In that case, the
sequence of events is u
Public bug reported:
When launching several VMs in rapid succession, it is possible that libvirt's
image caching
will fetch the same image serveral times. This can occur when all of the VMs
in question
are using the same base image and this base image has not been previously
fetched. The inlin
Public bug reported:
The errors_out_migration decorator in nova/compute/manager.py is
attempting to use positional arguments to get the migration parameter.
However, at run time, the decorated methods are called via RPC calls
which specify all of their arguments as keyword arguments. The
decorato
Public bug reported:
If an instance is deleted while a resize operation is in progress (i.e.
before the VM state is RESIZED), the temporary files created during the
resize operation (e.g. _resize with libvirt) are not
cleaned up. This would seem to be related to bug 1285000, except in
that case t
Public bug reported:
When a live migration (task state = migrating) task is running, and the
compute service goes down, the instance remains in migrating state when
the compute service restarts. The compute/manager.py _init_instance
method seems to handle all states except migrating. It handles
8 matches
Mail list logo
