sleads the users and
administartors about the extension.
The projects below are affected:
openstack/neutron-lib
openstack/python-openstackclient
openstack/ironic
Below are the related wrong codes.
http://ix.io/2upr
** Affects: neutron
Importance: Undecided
Assignee: Huang Cheng (pedh)
Public bug reported:
Environment:
OpenStack Rocky/Ussuri
compute node of libvirt/kvm on HP Proliant server with 24*cpu and 256GB mem
Reproduction steps:
1. Create an instance with flavor "m1.small";
2. Resize the instance to flavor "m1.medium";
3. In a while the instance enters "VERIFY_RESIZE" s
Public bug reported:
env: OpenStack Ocata, ml2 hierarchical port binding with openvswitch as
bottom driver
When the bottom segment already bound to a l2 driver is dynamiclly released,
the associated neutron.ml2_port_binding_levels.segment_id will be set "NULL",
and cause the local vlan tag of ope
Public bug reported:
We are expected to get the same partial segment allocated for specified
network and physical_network by calling
neutron.plugins.ml2.managers.TypeManager.allocate_dynamic_segment.
but there is a race condition:
1. Two processes call allocate_dynamic_segment function with spe
segment" object, which will be persisted
as ml2_port_binding_levels.segment_id after the binding process.
** Affects: neutron
Importance: Undecided
Assignee: Huang Cheng (hcpedh)
Status: New
** Tags: binding hierarchical ml2 port
** Description changed:
Related to: B
Public bug reported:
Description
===
RDO OpenStack Ocata
* rally result
Total durations
Action Min (sec) Median (sec)90%ile (sec)95%ile (sec)Max
(sec) Avg (sec) Success Count
neutron.create_floating_ip 4.2 18.946 71.561 91.803 131.663 29.769
** Also affects: openstack-manuals
Importance: Undecided
Status: New
--
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/1717707
Title:
EVENTLET_NO_GREENDNS is disa
** Description changed:
Related to bug #1696094.
An 'Timed out waiting for nova-conductor. Is it running? Or did this
service start before nova-conductor? Reattempting establishment of
nova-conductor connection...' error occurs in nova-compute.log when:
on compute node
1. no us
** No longer affects: openstack-requirements
--
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/1717707
Title:
nova-compute failed to communicate with nova-conductor on star
** Project changed: nova => openstack-requirements
** Also affects: nova
Importance: Undecided
Status: New
--
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/1717707
Public bug reported:
Related to bug #1696094.
An 'Timed out waiting for nova-conductor. Is it running? Or did this
service start before nova-conductor? Reattempting establishment of
nova-conductor connection...' error occurs in nova-compute.log when:
on compute node
1. no usable nameserver in
11 matches
Mail list logo
