Public bug reported:
In the below logs I observe that a port update is attempted with
duplicate extra_dhcp_opts. Since the values for extra_dhcp_opts are
dicts the _collect_duplicates() method[1] fails as it attempts to add
dict's to a set.
[1] https://opendev.org/openstack/neutron-
lib/src/branc
Public bug reported:
Description of problem:
The routes put in route6-$DEVICE by cloud-init is in an invalid format.
The schema[1] for network_matadata uses a non-converntinal format for
the IPv6 netmask. It is stored as an IPv6 address, similar to how IPv4
netmasks are written 255.255.255.0 the
** 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 cloud-init.
https://bugs.launchpad.net/bugs/1959148
Title:
cloud-init writes route6-$DEVICE config with a HEX netm
Public bug reported:
When ML2 driver receive NetworkContext after adding network segment
with:
openstack network segment create \
--network e686a356-58d7-4cf0-bdf9-e720d9925ac0 \
--physical-network net3 \
--network-type vlan \
--segment 300 provision-net3
In `update_network_postcommit`,
Public bug reported:
Network initially created with:
{'network': {'provider:physical_network': 'external',
'provider:network_type': 'flat'}
Network is then updated with:
{'network': {'provider:physical_network': 'external',
'provider:network_type': 'flat',
Public bug reported:
OS distributions started to disable the nf_conntrack_helper
functionality by default. (Ubuntu Bionic) Without the
nf_conntrack_helper traffic such as tftp and other protocols that
require a nf_conntrack module will not work. (This became apparent with
Openstack Ironic which us
Public bug reported:
More details in: https://storyboard.openstack.org/#!/story/1304673
Similar to how Nova can be notified (neutron/notifiers/nova.py) Ironic
should also be notified on relevant port status changes.
** Affects: neutron
Importance: Undecided
Status: New
--
You rec
Public bug reported:
When subnets are created using a cidr the value provided is
normalized/converted to a proper subnet
https://opendev.org/openstack/neutron/src/branch/master/neutron/db/db_base_plugin_v2.py#L818-L820
818# turn the CIDR into a proper subnet
819net = net
Public bug reported:
For ports on normal networks (non-Routed Provider Networks) it is
possible to change the fixed-ip of a port. When a port is on a Routed
Provider Network the same operation return an error: "Invalid input for
operation: IP allocation requires subnets for network." Since this is
** Also affects: tripleo
Importance: Undecided
Status: New
** Changed in: tripleo
Importance: Undecided => High
** Changed in: tripleo
Status: New => Triaged
** Changed in: tripleo
Milestone: None => train-3
--
You received this bug notification because you are a member
Public bug reported:
I have a usecase where we need to put a hostname in the tags field. This
fails for hosts with very long hostnames because the tags elemtents are
limited to 60 character strings.
Invalid input for operation: 'tripleo_hostname=centos-8-stream-vexxhost-
ca-ymq-1-0023709342' exce
Public bug reported:
When attempting to verify neutron change[1], we discovered that despite
options in DHCPv6 ADV and REQ/REPLY are correct network booting still
fails.
When comparing traffic capture between openvswitch+neutron-dhcp-agent setup to
the ovn setup a significant difference is that:
Public bug reported:
neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.ovn_db_sync.OvnSbSynchronizer
When the `sync_hostname_and_physical_networks` method run's it will
compare host physical_networks to mappings in neutrons
`segmenthostmappings` table. Any mappings in neutron that is not seen on
Public bug reported:
The atteched devstack configuration `local.conf` can be used to
reproduce this issue.
In networking-baremetal CI we are seeing an issue where the DHCP agent
does not create a namespace for subnets on a routed provider network. No
DHCP namespace is created because this test[1]
Public bug reported:
$ openstack subnet show 48c8407b-7ef3-4047-82dd-ca6d671c2162 -c
ipv6_address_mode -c ipv6_ra_mode
+---+--
Public bug reported:
def subnet_is_ipv6(subnet):
"""Common helper for checking network_state subnets for ipv6."""
# 'static6' or 'dhcp6'
if subnet['type'].endswith('6'):
# This is a request for DHCPv6.
return True
elif subnet['type'] == 'static' and is_ipv6_addr(sub
Public bug reported:
Neuton currently only support configuring the DHCP agent with static
/fixed-address allocations. The DHCP client id (the client MAC address
in neutron's case) is mapped to a specific IP address in the dhcp server
configuration. No range of addresses are made available for clie
This was fixed in neutron. We can close this in tripleo.
** Changed in: tripleo
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/1844124
Title:
Not
Public bug reported:
In the api reference documentation dns_assignment is documented as:
"dns_assignment": {
"hostname": "myport",
"ip_address": "172.24.4.2",
"fqdn": "myport.my-domain.org"
},
Is it not in actually a list?
ans dnsmasq will only ever lease
fd12:3456::aa04. As it will always find that as the first valid
configuration for mac fa:16:3e:58:42:ed. In other words, the _current
behaviour is broken_.
New behaviour
-
dhcp-host=fa:16:3e:58:42:ed,myport02.my-domain.org,[fd12:3456::aa02][fd12:3456::aa04]
Public bug reported:
Network 45b993b2-5224-409e-9756-0be190a19cf5 with two segments and two
subnets:
$ openstack network segment list --network provider -f yaml
- ID: 612f96f0-7682-49f7-bfc2-c52437f6e948
Name: provider-segment1
Network: 45b993b2-5224-409e-9756-0be190a19cf5
Network Type: fla
Public bug reported:
$ openstack port create \
--network provider test-port-deferred \
-c fixed_ips -f yaml
fixed_ips: []
$ openstack subnet create \
--ipv6-ra-mode dhcpv6-stateless \
--ipv6-address-mode dhcpv6-stateless \
--network provider \
--network-segment provider-segment2 \
-
Public bug reported:
File "/opt/stack/neutron/neutron/services/segments/plugin.py", line 556, in
_update_routed_network_host_routes
(subnet.id, subnet.network_id))
Public bug reported:
A provider network with 3 stateless subnet, on different segments.
(NOTE, this output is from a dev environment with WIP fixes for bug/1864333 and
bug/1864333)
$ for subnet in $(openstack subnet list --network providernet -f value -c ID);
do openstack subnet show $subnet -f
Public bug reported:
2020-03-24 00:12:05.019 35 ERROR neutron_lib.callbacks.manager
[req-be6ef908-8d3c-4e20-84b5-80ef1d8ab94e 8a8ad2f8e3f7478b8ce5e84f620cb4db
255eb2ea84ed4b29a55aceffcecf2a5d - default default] Error during notification
for
neutron.services.segments.plugin.NovaSegmentNotif
Public bug reported:
When using routed networks[1] on an instance connected to multiple
networks the traffic from a segmant_a to segment_b within a L3 network
might be routed via a different network if the default router/gateway is
not on the interface connecting to the routed networks.
It would
Public bug reported:
Openstack Ironic need to set the mac address of neutron port to the
actual mac address of the hardware for DHCP/PXE deployment to work. When
using pre-created neutron ports there is an issue where previously used
ports cause a conflict when a new instance is scheduled onto the
** 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/1694120
Title:
routed-networks - segments subnet dhcp port bind to wrong segment
Stat
Public bug reported:
When the update request contains segment_id and the provided segment_id
is equal to the id currently on the subnet, the update request will fail
if any of the checks in _validate_segment fail with
NoUpdateSubnetWhenMultipleSegmentsOnNetwork or
SubnetsNotAllAssociatedWithSegmen
Public bug reported:
On a routed provider network IP allocation will be deffered if
insufficent binding information is available.
When a port is updated with binding_host_id only this works as expected:
$ openstack port cre
Public bug reported:
FakeNotifier class 'topic' argument need to be updated to 'topics'. The
Notifyer class in oslo.messaging was changed in Change-Id:
Id89957411aa219cff92fafec2f448c81cb57b3ca
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notifica
Public bug reported:
When multiple host agents rapidly report_state for the first time we get
StaleDataError and _update_segment_host_mapping_for_agent does not
complete for all hosts.
Attached is a file with logs as well as reproducer script and
instruction on how to set up devstack environment
Public bug reported:
When using Neutron Segments we would like dhcp agent to configure DHCP
servers to serve clients on remote(non-local) subnets. The remote(non-
local) subnet will need to have a DHCP-relay/forwarder configured. The
relay agent will run on ToR switch or router in the routed under
Public bug reported:
With Neutron segments it is not possible to mix subnets with segment_id:
None and subnets with a segment_id. In some cases a network will be
created, a subnet added without creating a segment. tTen later this
network need to scale, and dividing it onto multiple routed segments
Public bug reported:
When using routed networks and a subnet is associated with a segment ip-
allocation will be deferred unless binding:host_id is provided. This is
all fine for ports that will end up on a nova host, we want to make sure
the ip-allocation is for a subnet on a segment that is loca
** Summary changed:
- Unable to create port with fixed-ips allocation for 'baremetal' ironic
instance
+ Routed Networks - Ironic Port Binding - baremetal node on remote non-local
subnet
** Description changed:
When using routed networks and a subnet is associated with a segment ip-
allocat
Public bug reported:
$ openstack network list -f json
[]
$ openstack network create ctlplane
Network created, and we have 1 default segment:
$ openstack network segment list --network ctlplane -f json
[
{
"Network": "89e4aa6c-06f2-4348-9576-bec17c7526d6",
"Network Type": "local",
Public bug reported:
Segments, routed-networks, IPAM only usecase regression
Code[1] will defer IP allocation if host is not specified.
Issues:
a) This breaks the use case where Neutron is used for IPAM only with
routed network.
b) A user can no longer create a port and specify a fixed IP,
Public bug reported:
To complete the DHCP support for remote routed networks via relay agent
the dhcp agent must configure the in the --dhcp-range
option. This was previously not requred becuase dnsmasq can determine it
from the local interface information. For remote networks we need to set
this
Hi Rico Lin,
The following change in Neutron was released:
https://review.openstack.org/#/c/470788/
With this we can close both the Heat and Neutron part of this bug.
--
Harald
** Changed in: neutron
Status: New => Fix Released
** Changed in: heat
Status: Incomplete => Fix Releas
is.
** Affects: neutron
Importance: Undecided
Assignee: Harald Jensås (harald-jensas)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1668145
Title:
Public bug reported:
The following code in neutron/agent/linux/dhcp.py will create on-link
/link-local routes to all subnets in a network.
host_routes.extend(["%s,0.0.0.0" % (s.cidr) for s in
self.network.subnets
if (s.ip_ve
Public bug reported:
The Nova interface-attach API needs be enhanced to support SR-IOV.
There is a Newton blueprint for this:
https://review.openstack.org/#/c/139910/
It has been abandoned, and need to be picked up for ocata/pike.
** Affects: nova
Importance: Undecided
Status: New
Public bug reported:
The resolv.conf gets populated with whatever the last interface that
came up over DHCP provided.
Even if the 2nd network/subnet in neutron doesn’t define DNS, it still
overwrites resolv.conf.
By default the dnsmasq agent will use itself, and it's pairs as DNS servers if
no
Public bug reported:
Description of problem:
When a tenant creates a v2 HAProxy load balancer without a listener, minimally
$ neutron lbaas-loadbalancer-create
below kind of messages are then logged on every 10 seconds in lbaas-
agent.log for each such load balancer of any tenant:
2016-04-07 1
45 matches
Mail list logo
