Public bug reported:
neutron version 10.0.2
Neutron is configured to have a couple of workers.
When trying to report tracing information to Jaeger using osprofiler, neutron
doesn't send to Jaeger.
Basic debugging shows jaeger-client's tornado ioloop doesn't spawn the
reporting methods.
**
@mriedem Thank you for your response.
We don't have to detach the volume from the server, or deleting anything from
the DB. The problem is simply that the volumes are stayed connected to the
node, because initialize_connection was called, but when spawning failed, and
the VM is not on the node,
Public bug reported:
When creating and instance and it is being spawned for the first time
fails, the instance's volumes' initialize_connection is being rolled-
back, but when unshelving an shelved-offloaded instance, there's no
rollback in case of failure.
The reason is that when spawning an
Public bug reported:
When RPC between services fails, because of a bug in the RPC service,
network faults etc., the server gets stuck in a task, and never exits
it.
For example, when powering up a server, nova-api sets the task_state of
the server to 'powering-on', and then sends nova-compute an
Public bug reported:
shelve_offloading a server, and then resetting it state, makes it
unavailable for any command:
shoham@ubuntu:~/devstack$ nova list
nova
s+--+--+++-+--+
| ID
Public bug reported:
When the service starts for the first time, nova-compute fails to register
itself to the DB. It seems that a nova-compute service of that node has already
registered to the DB, so it's a duplicate entry.
Could be a race condition, and nova-compute tries to write itself to
** Project changed: nova => openstack-api-site
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1548815
Title:
Documentation mistaken when creating a server without
Public bug reported:
The documentation says here:
http://developer.openstack.org/api-ref-compute-v2.1.html#createServer
That if you don't specify networks to attach the new server to:
"By default, the API provisions the server instance with all isolated networks
for the tenant"
But when
volumes, and they are now connected to 2 hosts.
The correct behaviour is to call terminate_connection on the VM's
volumes when it's being shelved_offloaded
** Affects: nova
Importance: Undecided
Assignee: Shoham Peller (shoham-peller)
Status: In Progress
--
You received this bug
9 matches
Mail list logo
