Public bug reported:
Reproduce this bugļ¼
1.create a port with no qos policy.
2.update this port with a qos policy.
Since 'qos_options' does not have the 'direction' key, this bug is
caused.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notificatio
Reviewed: https://review.opendev.org/705859
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=da28046944aaa5b6068d2cc8f14e72ef1de6c012
Submitter: Zuul
Branch:master
commit da28046944aaa5b6068d2cc8f14e72ef1de6c012
Author: Colleen Murphy
Date: Tue Feb 4 14:06:41 2020 -
Reviewed: https://review.opendev.org/706499
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=b85c273639f30cbffd95bfb92564adc8fb586465
Submitter: Zuul
Branch:master
commit b85c273639f30cbffd95bfb92564adc8fb586465
Author: Lucas Alvares Gomes
Date: Thu Feb 6 13:28:34 20
Public bug reported:
Running Rocky, in a DVR environment
We are seeing repeated errors like this in neutron-server logs. Not sure
at this point what the effect is, or harmless. This is in a build test
environment where a lot of automated VMs get spawned and deleted then
associated/disassociated w
Public bug reported:
Integration test for validating create and delete server group is
missing and hence new test need to be added.
** Affects: horizon
Importance: Undecided
Assignee: Akshay (aw4825)
Status: New
** Changed in: horizon
Assignee: (unassigned) => Akshay (a
This error is similar to the one reported in Octavia
https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1826875 , but in
the case of neutron the table firewall_group_port_associations_v2 has a
primary key defined:
firewall_group_port_associations_v2 | CREATE TABLE
`firewall_group_port_associa
Public bug reported:
When trying to delete a heat stack in Stein fails, because neutron-
server couldn't update firewall groups, the stack trace found in the
logs is:
2020-02-11 13:14:21.356 1998511 ERROR neutron_lib.callbacks.manager Traceback
(most recent call last):
2020-02-11 13:14:21.356 19
Public bug reported:
We should issue an exception here since if a v3 call does not explicitly
specify the domain_id in the entity, it should be using a domain scoped
token. However, the current tempest heat tests issue a v3 call without
this. This is raised as bug #1283539. Once this is fixed, w
Public bug reported:
Description
===
Execute Tobiko functional test cases [1] against an OpenStack cloud
based on Ubuntu Bionic and deployed using DevStack (master branch).
Steps to reproduce
==
1) Create a new Nova server instance with a CirrOS[2] image
2) Wait for serv
Public bug reported:
hypervisor_version of z/VM driver returned '' but
in fact it is defined as fields.IntegerField() which
means it should be int value by default.
so in case some error occured, the '' will be reported and
may lead to other potential issue
** Affects: nova
Importance: Low
This shouldn't be accepted.
If you create an instance by asking a specific AZ, the design is that you can't
migrate it to another AZ unless you force it.
When calling live-migrate by the latest API microversion, even with
asking to go to a specific host, Nova wouldn't accept it.
See https://doc
11 matches
Mail list logo
