Public bug reported:
Use case: many trunk ports each with many subports.
Problem: port list takes much time.
Reason: for each port trunk extension adds a DB call to retrieve subports mac
addresses.
Solution: retrieve subports info once when having a full list of trunk ports
and hence full list o
Public bug reported:
The aim of this bug is just to document known issue when using L2
population and OVS agent. L2 population is needed, for example, when
using tunnel protocol and DVR.
If the OVS agent (compute node) is overloaded (too many ports VS one
single threaded OVS agent), the polling c
I tested this locally and it works for me, meaning I'm not able to
delete such a router interface. I also checked the patch
https://review.opendev.org/#/c/763198/ and it doesn't reach the part
where it tries to delete the interface, it fails much earlier:
2020-11-18 21:09:23.518 94641 INFO tempest
Public bug reported:
In some deployments, hostnames can be different between hosts and resource
provider records. For example in deployment managed by TripleO we use short
host name (without domain name) in host, while we use FQDN for resource
provider records (this comes from the FQDN set to t
OK, In fact I didn't mention a few important things, sorry for that :-((
1) Tested on: RHOS-16.1-RHEL-8-20201110.n.1
2) This bug is about API only, you aren't able to delete the External Gateway
using Openstack CLI commands, so I guess that this is why Jacub wasn't able to
reproduce the issue.
Source node
https://zuul.opendev.org/t/openstack/build/d50877ae15db4022b82f4bb1d1d52cea/log/logs/subnode-2/libvirt/qemu/instance-001a.txt
2020-11-20 14:25:24.887+: starting up libvirt version: 6.0.0,
package: 0ubuntu8.4~cloud0 (Openstack Ubuntu Testing Bot Tue, 15 Sep 2020 20:36:28 +
Public bug reported:
I'd like to bring the following idea to the drivers' meeting. If this
still looks like a good idea after that discussion, I'll open a spec so
this can be properly commented on in gerrit. Until then feel free to
comment here of course.
# Problem Description
A general router c
Marking 'Won't Fix" because fo the deprecation of the neutron-fwaas
project.
** 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/1848851
Public bug reported:
On a test system I configured a machine with a bond. Curtin successfully
installed CentOS 8 but the deployment failed in MAAS. When I dug in it
is because the bond never comes up so the machine has no way to
communicate with MAAS. I can deploy the same machine with a bond on
C
9 matches
Mail list logo
