** Description changed:
Hit a race with the Antelope (22.0.0) version of NDR in one of our
functional test runs:
1) neutron-bgp-dragent got restarted right before creating a speaker and
adding an external network and tenant network to it;
- 2) As can be seen in the service log below,
Public bug reported:
Hit a race with the Antelope (22.0.0) version of NDR in one of our
functional test runs:
1) neutron-bgp-dragent got restarted right before creating a speaker and adding
an external network and tenant network to it;
2) As can be seen in the service log below, just after
When it comes to the NDR charm we enabled it in the charms (neutron-api-
plugin-ovn specifically needed a code change) documenting those
limitations in the charm-guide.
https://review.opendev.org/q/topic:2023-enable-ndr
https://review.opendev.org/q/topic:2023-ovn-ndr
Also we are adding some data
Public bug reported:
With https://bugs.launchpad.net/neutron/+bug/1995974 fixed and
https://review.opendev.org/c/openstack/neutron/+/864051 merged extra
attributes such as `distributed` and `ha` are now created for OVN
routers as well.
Their default values are taken from the global configuration
Public bug reported:
Context:
* Neutron is configured to use OVN
* An external provider network with one segment is created
* A subnet with a default gateway IP set is associated with this segment
explicitly (segment_id != None)
* A router's gateway port is set to use the provider network
Public bug reported:
Some network designs include multiple L3 gateways to:
* Share the load across different gateways;
* Provide independent network paths for the north-south direction (e.g. via
different ISPs).
Having multi-homing implemented at the instance level imposes additional burden
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1973276
Title:
OVN port loses its virtual type after port
Public bug reported:
VPD capability handling was added in
https://opendev.org/openstack/nova/commit/ab49f97b2c08294234c7bfd3dedb75780ca519e6
and now does a device dict update as follows
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1884723
Title:
[OVS] multicast between VM instances on
** Changed in: maas
Status: Invalid => 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/1517180
Title:
No support for adding custom certificate chains
Status in cloud-init:
** Also affects: keystone (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity
Public bug reported:
When a trust is created a trustor user is required to have a role on a
project in question. This is verified via a call to the keystone
database without looking at roles that can be inferred from federated
groups present in a token.
In this scenario a federated user does not
Ran into a related problem during debugging of dashboard errors ("Unable
to retrieve key pairs") with a Rocky cloud & identity federation.
There was no clear indication as to why failures occurred.
https://paste.ubuntu.com/p/v5HXyyWXC2/ (full pdb trace)
At a high level I was getting validation
Public bug reported:
[Version]
Rocky (UCA)
[Problem Description]
(see the User Scenario section below for a description of the
environment)
When no direct role assignments to federated users are done and only
federated group role assignments are present, application credential
creation via
Public bug reported:
[Overview]
The relevant part of the federated authentication process after the IdP and SP
token parsing stages is as follows:
1) WSGI environment variables created based on token attributes (e.g. SAML
token attributes) are passed down to Keystone;
2) Keystone creates a
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1774710
Title:
DHCP agent doesn't do anything with a
I do not think Neutron is related in any way here by the way because it
is not responsible for bringing OVS bridge interface links up => moving
to invalid for Neutron.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1751396
Title:
DVR: Inter Tenant Traffic between two
Affects Pike and Queens UCA.
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1759971
Title:
Public bug reported:
OpenStack Queens from UCA (xenial, GA kernel), 2 external subnets (one
routed provider network), 1 tenant subnet added to a router.
Tenant subnet cidr: 192.168.100.0/24
Relevant agent configs:
http://paste.openstack.org/show/718514/
Commands and outputs:
Affects pike and queens UCA packages.
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Changed in: neutron (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
OpenStack Queens from UCA (xenial, GA kernel), 2 external subnets (one
routed provider network), 2 tenant subnets, all subnets in the same
address scope to trigger "fast exit" logic.
Tenant subnet cidr: 192.168.100.0/24
Other tenant subnet cidr: 192.168.200.0/24
Relevant
Public bug reported:
OpenStack Queens from UCA (xenial, GA kernel), 2 external subnets (one
routed provider network), 2 tenant subnets, all subnets in the same
address scope to trigger "fast exit" logic.
Tenant subnet cidr: 192.168.100.0/24
Other tenant subnet cidr: 192.168.200.0/24
Relevant
Public bug reported:
Overall, similar scenario to
https://bugs.launchpad.net/neutron/+bug/1759956 but a different problem.
OpenStack Queens from UCA (xenial, GA kernel, deployed via OpenStack
charms), 2 external subnets (one routed provider network), 1 tenant
subnet, all subnets in the same
-
packages/neutron/agent/linux/utils.py:92
** Affects: neutron
Importance: Undecided
Assignee: Dmitrii Shcherbakov (dmitriis)
Status: In Progress
** Tags: cpe-onsite
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
Public bug reported:
# OS_USERNAME=user OS_USER_DOMAIN_NAME=admin_domain OS_PROJECT_NAME=admin
# OS_PROJECT_DOMAIN_NAME=admin_domain
openstack user list --domain testdomain -> users returned for testdomain
# OS_USERNAME=user OS_USER_DOMAIN_NAME=testdomain OS_DOMAIN_NAME=testdomain +
policy
27 matches
Mail list logo