Public bug reported:
A port whose device_owner is floatingip has an IPv6 fixed_ip.
This is an old issue, but I haven't focused on it.
Steps to reproduce:
1.create an external network:
openstack network create --provider-network-type vlan
--provider-physical-network physnet1 --external pu
2.
Public bug reported:
As the title describes, we can support baremetal type vnic like sriov
vnic.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https:/
Public bug reported:
When create a subnet for a specific network, ovn_client would update
external_ids of metadata port.
We focus on these fileds of localport port: 'neutron:cidrs' and 'mac', because
those fields contain fixed_ips.
But any scenarios like batch create multiple subnets for one ne
Public bug reported:
Ovn driver is not support availability_zones earlier because ovn
distribute dhcp server.
Through this patch [1], neutron already support for Network Availability
Zones in ML2/OVN. But network's availability_zones is also empty.
neutron net-show ce361094-dcfa-42e7-a4b9-b4adf2
Public bug reported:
2021-10-12T14:11:45Z|290912|lflow|WARN|error parsing actions "reg0[3] =
put_dhcp_opts(offerip = 192.168.100.243, bootfile_name =
https://127.0.0.1/boot.ipxe, classless_static_route =
{169.254.169.254/32,192.168.100.2, 0.0.0.0/0,192.168.100.1}, dns_server =
{10.222.0.3}, l
Public bug reported:
Through this bug[1], we should upgrade the version of pyroute2 to 0.6.5
in requirement.txt.
[1]https://bugs.launchpad.net/ubuntu/+source/pyroute2/+bug/1904730
** Affects: neutron
Importance: Undecided
Status: New
** Tags: sriov
** Summary changed:
- The ve
Public bug reported:
With this patch[1], we avoid pre-populating flows for router to router
communication.
If we re-associated router interface with router, its mac has been
changed in neutron db and fixed_ip not, but we found that mac of lrp has
not been updated in MAC_Binding, vm also could not
Public bug reported:
The external_port only supported where network is vlan type, not geneve
network. So we should return it when create a sriov nic backed tunnel
net.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a mem
Public bug reported:
As the title describes, after remove gateway for a router, we could find the
qos binding is remain.
And if we delete this qos policy, we could meet the error of QosPolicyInUse.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug not
** 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/1928164
Title:
[OVN] Ovn-controller dose not update the flows table when localport
Public bug reported:
Hi everyone：
We want to define a new api that supports cloning a specified security_group.
Consider the following case:
If the user wants to create a new security_group with the same rules as a
created security_group, he should do some duplicate actions to create rules.
Public bug reported:
In some cases, customers want to specify a port list for 'source_port'(or
destination_port) when create a firewall rule.
Currently the api of firewall_rule could not meet the demand. So we want to
define a new api which could support it.
eg. api :
"firewall_rule":{
"nam
Public bug reported:
As we know, we can use ipv6 address end with '0' like 2001::.
But when we allocate ipv6 pool use neutron, we could find the error like
follows:
neutron net-create net-v6
neutron subnet-create --ip-version 6 --allocation-pool start=2001::,end=2001::2
net-v6 2001::/64
The all
Public bug reported:
We found that allocation_pools is empty list after update subnet with empty
'allocation_pools':
neutron subnet-show f84d8c24-251c-4a28-83a0-6c7f147c3da1
+---+--+
| Field | Value|
Public bug reported:
As the titile describes, there is no need running rpc notifier if no l2 agent
when use ml2/ovn driver.
Maybe we can provide one boolean flag like 'disable_rpc_notifier' which default
is 'True', and we can set it 'False' to disable rpc notifier when use ml2/ovn
driver.
**
Public bug reported:
When we use the bulk api to create ports use one subnet e.g.,
'935fe38e-743f-45e5-a646-4ebbbf16ade7', and then we found any errors occurred.
We use sql queries to find diffrent IPs between ipallocations and
ipamallocations:
ip_address in ipallocations but not in ipamallocat
Public bug reported:
I don't know how to reproduce it, and we have encountered it twice. The
errors are as follows:
2024-04-01 10:53:46.185 252 INFO neutron.wsgi
[req-3ed42a43-8895-4ad3-b675-af89c6d47631 9862b8ef431c43489ada1bb12f97be59
c2c9335342874b758aa6af2166fca837 - default default] 192.16
d it would not retry
after "_update_chassis" falied.
** Affects: neutron
Importance: Undecided
Assignee: Liu Xie (liushy)
Status: New
** Tags: ovn
** Changed in: neutron
Assignee: (unassigned) => Liu Xie (liushy)
** Description changed:
If the metadata age
Public bug reported:
When "debug" is set to True, some logs show "found 0 active agents" after
the agent_health_check.
It seems that the agent_health_check mechanism does not work for ovn agents.
** Affects: neutron
Importance: Undecided
Assignee: Liu Xie (liu
Public bug reported:
If we use an invalid CIDR as the source_ip_address, such as
2:3dc2:c893:514a:966b:7969:42b0:00900/108, it can still be successfully
submitted after creating a firewall rule. The main reason is that
netaddr formats this address.
The command is like:
openstack firewall group
Public bug reported:
As neutron-fwaas project is re-maintenance, and ovn become one of the main
driver for neutron project.
Maybe we could implement l3 firewall for ovn driver.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: fwaas
** Tags added: fwaas
--
You rec
Public bug reported:
Sometimes, we found that list az is empty at large scale environment.
Maybe it is a matter about ovsdbapp. But it would cause l3 re-schedule to wrong
candidates if az list is empty when ovsdb_monitor process ChassisEvent.
I have a workaround[1] to fix the matter that l3 re
** 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/1975658
Title:
[ovn]list_availability_zones is occasionally empty at large scale
Stat
Public bug reported:
As the title describes, we can use 'address set' of ovn to support the
feature that address group.
** Affects: neutron
Importance: Undecided
Assignee: Liu Xie (liushy)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Li
Public bug reported:
Currently, some users want to konow what time created (or updated) a
specific firewall group but it is not support show fields 'created_at'
nor 'updated_at'.
So we want to support standard_attrs for firewall_group.
Anyone has other ideas?
** Affects: neutron
Importance:
Public bug reported:
In some scenarios, the customers want to modify the fixed_ips of metadata port.
We can workaround it by follow steps:
1.Fisrt, update fixed_ips of metaadta_port:
neutron port-update --fixed-ip
subnet_id=e130a5c7-6f47-4c76-b245-cf05369f2161,ip_address=192.168.111.16
460dffa9
Public bug reported:
As the title describes, if we updated fixed_ips of one internal port
which associated a floatingip, but the dnat_adn_snat entry in ovn will
not changed.
** Affects: neutron
Importance: Undecided
Assignee: Liu Xie (liushy)
Status: New
** Changed in
Public bug reported:
Currently, many customers are using k8s for their VMs, and there is a
need to add or remove allowed_address_pairs. However, frequent update
neutron port is time-consuming. Can we provide an API only support CRUD
allowed_address_pairs?
** Affects: neutron
Importance: Unde
Public bug reported:
Currently, the IP address of the DHCP port is automatically assigned the
first available IP and cannot be specified when creating a subnet.
Therefore, can we provide an API that supports specifying the DHCP
address when creating a subnet?
** Affects: neutron
Importance:
Public bug reported:
As we know, ovn_l3 implements the DVR mode router.
For the DVR router interface, there is a patch[1] that allows multiple IPv6
ports on a router from the same network (ml2/ovs+dvr).
I believe this is also needed for the OVN plugin.
Does anyone have any opinions on this?
[1]
30 matches
Mail list logo
