Public bug reported:
A TypeError was thrown during a synchronization
command(eutron-ovn-db-sync-util) execution. By checking the error call stack,
it was found that it was an error during the creation of QoS. After analysis,
there should be a port in the Neutron database, but not in the ovn-nb
** Changed in: neutron
Status: New => Invalid
** Changed in: neutron-dynamic-routing (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
Description of problem:
In the past (OSP less then 17.1 +SRBAC configuration)
we were able to use only the rc file if we wanted to source the user, without
the need to update the clouds.yml and with no obligation to put other value in
the OS_CLOUD filed.
Version-Release
Public bug reported:
The ``OVNClient.update_floatingip`` method deletes and creates again the
OVN NAT rules when a FIP is updated. However, this process is not
necessary if only the QoS policy is updated. Only the QoS driver call is
needed. That speeds up the FIP process and avoids the
** Also affects: neutron-dynamic-routing (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/2024510
Title:
Address on SNAT port won't be
Public bug reported:
Description
---
When the DvrLocalRouter object is instantiated, it calls the the
_load_used_fip_information() function. In some cases this function will
try to add ip rules in a specific network namespace however that
namespace may not exist at the time. This results
Public bug reported:
Since some time, periodic jobs neutron-functional-with-oslo-master and
neutron-functional-with-sqlalchemy-master are failing with one test
failed:
neutron.tests.functional.db.test_migrations.TestModelsMigrationsMySQL.test_models_sync
Stacktrace:
ft1.4:
7 matches
Mail list logo