[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
Certain flows are missing in a distributed openstack setup after restart of
openvswitch.
I have tested this on openstack ussuri deployed with kolla-ansible on ubuntu
bionic, so there is a chance that this has been either been fixed or is caused
by specifics of the
Please can you provide full details of your deployment; specifically
which charms and channels you are using and on which base version of
Ubuntu.
** Project changed: keystone => charm-keystone
** Changed in: charm-keystone
Status: New => Incomplete
--
You received this bug notification
Public bug reported:
In a deployment of Openstack Yoga, I have the following policy.json
configured in Keystone: https://paste.ubuntu.com/p/F2PMP857mG/.
When I create a new domain, a project inside that domain, a user with
the role:Admin, and I set the context for that user/project/domain for
** Changed in: cinder
Importance: Undecided => Critical
** Changed in: cinder
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1996188
Title:
That's why the statement contains the phrase "as applicable". If you
have a unit that is "WantedBy=multi-user.target" then by definition, you
don't want it running after cloud-init.target, so this advice isn't
applicable to your use case. The advice is provided to inform a user how
to order
https://review.opendev.org/c/openstack/nova/+/871612 is now merged,
putting the bug report to Fix Released.
** Changed in: nova
Importance: Undecided => Critical
** Changed in: nova
Status: New => Confirmed
** Changed in: nova
Status: Confirmed => Fix Released
--
You received
Public bug reported:
Failed test: tearDownClass
(neutron_tempest_plugin.api.admin.test_shared_network_extension.RBACSharedNetworksTest)
Error:
ft7.1: tearDownClass
(neutron_tempest_plugin.api.admin.test_shared_network_extension.RBACSharedNetworksTest)testtools.testresult.real._StringException:
Public bug reported:
Failed test:
neutron_tempest_plugin.api.admin.test_routers_flavors.RoutersFlavorTestCase.test_create_router_with_flavor
Error
ft1.2:
Public bug reported:
Failed test
neutron_tempest_plugin.api.admin.test_tag.TagFilterQosPolicyTestJSON.test_filter_qos_policy_tags
Traceback (most recent call last):
File "/opt/stack/tempest/tempest/common/utils/__init__.py", line 89, in
wrapper
return func(*func_args, **func_kwargs)
Public bug reported:
Failed tests:
neutron_tempest_plugin.api.test_qos.QosTestJSON.test_get_policy_that_is_shared
neutron_tempest_plugin.api.test_qos.RbacSharedQosPoliciesTest.test_policy_sharing_with_wildcard
Public bug reported:
Failed test:
neutron_tempest_plugin.api.test_security_groups.RbacSharedSecurityGroupTest.test_regular_client_shares_to_another_regular_client
Error:
Traceback (most recent call last):
File
Public bug reported:
Failed test:
neutron_tempest_plugin.api.admin.test_shared_network_extension.RBACSharedNetworksTest.test_tenant_can_delete_port_on_own_network
Traceback (most recent call last):
File
Public bug reported:
Description
===
The SQLAlchemy package has recently had a major update, moving its version up
to 2.0. Problem is, the change seems to break compatibility with version 1 of
the library as now the sqlalchemy-migrate package, which is dependent on it, is
reporting
Public bug reported:
Neutron version: 13.0.6 (I will try to test this with version Zed as well)
ML2: OVS
1. create a provider network (eg. named: public)
2. create a subnet pool (eg. 100.100.100.32/27)
3. create a 1st subnet /29 from that subnetpool on network "public":
100.100.100.32/29
Public bug reported:
Stateful security group API extension is supported by OVN backend since [1] and
[2] but it works properly only with OVN >= 21.06 which added support for
"allow-stateless" action in ACL rules.
Neutron currently supports still e.g. Ubuntu 20.04 which delivers OVN 20.03. In
Public bug reported:
In core OVN, LBs on switches with localnet ports (i.e., neutron
provider networks) don't work if traffic comes from localnet [1]
In order to force NAT to happen at the virtual router instead
of the LS level, when the VIP of the LoadBalancer is associated
to a provider
17 matches
Mail list logo
