** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1790255
Title:
Multiple IPs from ipv6 subnets on the associated network are allocated
all of the v6 subnets.
[1]https://specs.openstack.org/openstack/neutron-specs/specs/kilo/multiple-ipv6-prefixes.html
** Affects: neutron
Importance: Undecided
Assignee: sunzuohua (zuohuasun)
Status: New
** Changed in: neutron
Assignee: (unassigned) => sunzuohua (zuohuasun)
-
** 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://bugs.launchpad.net/bugs/1789824
Title:
One single ip is allocated for a port in the network with
d
instead of "append"
for s in subnets])
[1]https://github.com/openstack/neutron/blob/master/neutron/db/ipam_pluggable_backend.py#L223
** Affects: neutron
Importance: Undecided
Assignee: sunzuohua (zuohuasun)
Status: New
** Changed in: n
Public bug reported:
1. openstack version: newton(same with master)
2. neutron --version 11.0.1
3. ovs-vsctl (Open vSwitch) 2.7.2
4. iperf3
The ovs config is as follow:
[root@cdpm04 common]# ovs-vsctl list qos
_uuid : b90a11e9-ea70-4908-8cb2-bab21e117312
external_ids:
Public bug reported:
DVR
l3 agent mode on network nodes : dvr_snat
l3 agent mode on compute nodes : dvr_no_external
Reproduction steps:
1.Create a dvr.
2.Create a vm and associate a floating ip.
3.Restart l3 agent on the compute node which hosting the vm or add a new
interface to the router.
Public bug reported:
DVR+HA
l3 agent service: killmode=process
1.Restart l3 agent which is backup.
2.Because the value of killmode is process, the keepalived processes are alive
all the time.
4.When l3 agent starts, all the ha interfaces on this host are set down and the
ha network is
Public bug reported:
Reproduce steps:
l3 agent mode:
network node:dvr_snat
compute node:dvr_no_external
1、Create dvr+ha.
2、Set router gateway and add router interface.
3、Create vm and associate fip.
4、Restart l3 agent.
5、Restart l3 agent again.
After step 3, fip can be found in snat ns
Public bug reported:
Reproduction steps:
The l3 agent mode is as follows:
Network:dvr_snat
Compute:dvr_no_external
1、Create a DVR(HA). Then add interface and gateway to the DVR.
2、Create a vm and associate a floating ip to the vm.
3、Check the keepalived.conf and snat ns on the master and
Public bug reported:
Reproduction steps:
The l3 agent mode is as follows:
Network:dvr_snat
Compute:dvr_no_external
1、Create a DVR(HA). Then add interface and gateway to the DVR.
2、Create a vm and associate a floating ip to the vm.
3、Check the keepalived.conf and snat ns on the master and
** Project changed: fuel-plugin-contrail => neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1735866
Title:
Snat namespace misses iptables rules for floating ip.
Status in
[2]https://github.com/openstack/neutron/blob/master/neutron/services/segments/db.py#L315
[3]https://github.com/openstack/neutron/blob/master/neutron/db/db_base_plugin_v2.py#L435
** Affects: neutron
Importance: Undecided
Assignee: sunzuohua (zuohuasun)
Status: New
** Changed
Public bug reported:
I have a devstack with following configuration:
network nodes:
/etc/neutron/l3_agent.ini
[default]
agent_mode = dvr_snat
compute nodes:
/etc/neutron/l3_agent.ini
[default]
agent_mode = dvr_no_external
The reproduction steps
1.Launch VM and assign
github.com/openstack/neutron/blob/master/neutron/agent/l3/dvr_local_router.py#L569
Mybe DvrLocalRouter should not create fip namespace on nodes with
"dvr_no_external" and "dvr_snat" mode.
** Affects: neutron
Importance: Undecided
Assignee: sunzuohua (zuohuasun)
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1691674
Title:
Restarting l3 agent causes split-brain in HA router
Status in
, these keepalived processes
will vote a real master, and other keepalived processes become backup and
remove their vips.
** Affects: neutron
Importance: Undecided
Assignee: sunzuohua (zuohuasun)
Status: New
** Tags: l3-bgp
** Tags added: l3-bgp
** Changed in: neutron
** Changed in: neutron
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1647912
Title:
Unit is not consistent for max-burst-rate
Status in neutron:
Public bug reported:
For qos in neutron:
QosBandwidthLimitRule: defines the instance-egress bandwidth limit rule type,
characterized by a max kbps and a max burst kbits.
API parameters are as follows:
max_kbps
max_burst_kbps
But for qos in openvswitch:
"ingress_policing_rate": the maximum
table 0 or check all the default flow tables in
check_ovs_status().
Or add the default flow table 23 first and then add the default table 0 in
setup_default_table()
Thanks
** Affects: neutron
Importance: Undecided
Assignee: sunzuohua (zuohuasun)
Status: New
** Changed in: neutron
the default table 0 or check all the default flow tables in
check_ovs_status().
Or add the default flow table 23 first and then add the default table 0 in
setup_default_table()
Thanks
** Affects: neutron
Importance: Undecided
Assignee: sunzuohua (zuohuasun)
Status: New
** Changed
20 matches
Mail list logo
