Public bug reported:
when using routed provided network there is condition which is bypassing the
option dhcp_agents_per_network, which results that in a env with 3 agents and
dhcp_agents_per_network=2, for a given network already well handled by 2
agents. if you restart the third agent It will
Public bug reported:
When call driver enable is called. the cleanup_stale_devices function is
invoked to remove stale devices
within the namespace. The method cleanup_stale_devices examines the
ports in the network to prevent the unintentional removal of
legitimate devices.
In a multisegment con
Public bug reported:
When removing network for agent, dnsmask constantly tries to revive.
This has been observed when using multisegment. The external process
monitor is not well unregistered for that service.
This is because the correct helper to get the process identifier is not
used for unreg
Public bug reported:
With the new support of multi-segments some code has been added to clean
old dhcp setup for a network. that clean should happen first and clean
segment index == 0.
As list of segment for a given network does not come ordered by segment
index, in the process we can be in that
Public bug reported:
On a deployment with multi availability zones. When the operator adds a
new compute host, the service gets registered as part of
“default_availability_zone”.
This is an undesirable behavior for users as they see a new AZ appearing
which may not be related to the deployment th
load balancer has been deprecated and removed I guess we can close this
one.
** Changed in: neutron
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1619002
*** This bug is a duplicate of bug 2012510 ***
https://bugs.launchpad.net/bugs/2012510
dup 2012510
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://
Public bug reported:
ft1.1:
neutron.tests.functional.plugins.ml2.drivers.macvtap.agent.test_macvtap_neutron_agent.MacvtapAgentTestCase.test_get_all_devicestesttools.testresult.real._StringException:
Traceback (most recent call last):
File "/home/zuul/src/opendev.org/openstack/neutron/neutron/t
I think one of the first step that we can have is to remove the ORDER BY
as it creates the temporary filesort that you have mentioned in #9.
I may missing something, an order by UUID does not bring any kind value?
A second step would be to understand why the possible key object_id is
not used.
T
Public bug reported:
The current behavior for an evacuated instance at destination node is to
have the virt-driver starting the virtual machine, then a compute API
call if needed to stop the instance.
A cleaner solution would be to have virt driver API handling an expected
state when spawned on
Public bug reported:
During some investigations regarding segments we may have noticed
performance issues related to the current algorithm that schedules
network segments on hosts.
When an agent is reporting a change in segment, the process goes to the
function `auto_schedule_new_network_segments
I also proposed a fix for nova since 'nova-manage cellv2 update_cell' is
bugged for cell0.
https://review.opendev.org/#/c/672045/
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
affects: neutron
Importance: Undecided
Status: New
** Changed in: neutron
Assignee: (unassigned) => Sahid Orentino (sahid-ferdjaoui)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.
** Changed in: cloud-archive
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1667736
Title:
gate-neutron-fwaas-dsvm-functional failure after recent
The patch which reverts the problematic change in Nova has been released
in our packages for version 2:16.1.6-0ubuntu1~cloud0 [0]. Let's mark
this bug has Fix Released [1].
For upstream Nova, the community are against the revert, it should
probably be marked as won't fix.
[0]
https://git.launchp
Basically the issue is related to 'find_multipaths "yes"' in
/etc/multipath.conf. The patch I proposed fix the issue but adds more
complexity to the algorithm which is already a bit tricky. So let see
whether upstream is going to accept it.
At least we should document something that using multipat
Patch proposed against os-brick here [0]
[0] https://review.openstack.org/#/c/638639/
** Also affects: os-brick
Importance: Undecided
Status: New
** Changed in: os-brick
Assignee: (unassigned) => Sahid Orentino (sahid-ferdjaoui)
** Changed in: nova
Status: New => I
17 matches
Mail list logo
