Public bug reported:
We are expected to get the same partial segment allocated for specified
network and physical_network by calling
neutron.plugins.ml2.managers.TypeManager.allocate_dynamic_segment.
but there is a race condition:
1. Two processes call allocate_dynamic_segment function with spe
Reviewed: https://review.openstack.org/599936
Committed:
https://git.openstack.org/cgit/openstack/keystonemiddleware/commit/?id=4fb7fef1eab2a981b8e366091073b6ee2d80ee6a
Submitter: Zuul
Branch:master
commit 4fb7fef1eab2a981b8e366091073b6ee2d80ee6a
Author: wangxiyuan
Date: Wed Sep 5 10:21:5
Public bug reported:
Description
===
Volume-backed instances fails to live-migrate when config-drive is enabled, the
config drive uses iso9660 format. When the instance booted from volume, the
libvirt raised an exception: pre-creation of storage targets for incremental
storage migrati
Reviewed: https://review.openstack.org/599861
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=a4f1274f40513d0a350a38c6e389c9a76c272379
Submitter: Zuul
Branch:master
commit a4f1274f40513d0a350a38c6e389c9a76c272379
Author: Matt Riedemann
Date: Tue Sep 4 18:28:21 2018 -04
Bug a duplicate of https://launchpad.net/bugs/1791178
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1791218
Title:
neutron
** Changed in: neutron
Status: In Progress => Invalid
** Changed in: neutron
Importance: High => Undecided
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1791206
Title:
Bandit
Public bug reported:
The release of eventlet 0.24.1 changed the number of arguments to the
function eventlet.wsgi.HttpProtocol.__init__() from 4 to 3. This led to
pylint errors and other problems.
** Affects: neutron
Importance: Undecided
Assignee: Nate Johnston (nate-johnston)
Public bug reported:
Bandit 1.5.1 was released earlier today [1], and the pep8 tests started
failing with references to error B111. The error was not very easy to
see in the zuul logs [2][3] but when running locally was easy to pick
out [4]. Since test B111 is supposed to have been deleted in th
Public bug reported:
In order to test HA for controller node: shudown one controller node and
then vip switch to another node. Creating instance at this situation got
the Traceback in conductor:
2018-09-06 18:51:29.223 25 ERROR oslo_messaging.rpc.server
[req-503920a4-f2d8-47a8-a8d2-f9e4297be0ed
Public bug reported:
Example of failure: http://logs.openstack.org/37/382037/73/gate
/openstack-tox-pep8/7f200e6/job-
output.txt.gz#_2018-09-06_17_48_34_700485
It is probably because of new eventlet = 0.24.0 used now.
** Affects: neutron
Importance: Critical
Assignee: Slawek Kaplonski
Public bug reported:
There are scenarios where a VNF wishes to to have the same MAC address
in different VLANs or different provider_network types.
Tested so far:
1. Same MAC address used between 2 different VLAN networks > Success
2. Same MAC address used between 2 different SR-IOV networks
This was fixed by https://review.openstack.org/#/c/598365/
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/17
** Changed in: charm-nova-compute
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1750829
Title:
RFE: libvirt: Add ability to
** Changed in: charm-neutron-api
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1788631
Title:
KeyError: 'used' securit
Public bug reported:
It's impossible to reset your password in user level if
"change_password_upon_first_use" is set.
keystone.conf:
[security_compliance]
change_password_upon_first_use = True
For new users it's impossible to reset your password via keystone. You
can only reset the password via
Reviewed: https://review.openstack.org/597144
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=19635237b388dcc9199081a740ee9829feb67bee
Submitter: Zuul
Branch:master
commit 19635237b388dcc9199081a740ee9829feb67bee
Author: PrivateRookie <996514...@qq.com>
Date: Tue Aug
Can you give more detail in your example? What is the curl call and the
openstackclient invocation you are using? (minus sensitive data)
** Changed in: keystone
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which i
I'm going to mark this as invalid. If you want some help debugging your
code, you can post it to gerrit and get some help there to identify what
is wrong in your change, but it looks like you're trying to send the
SchedulerReportClient over RPC and that object is not serializable.
** Changed in: n
Yeah this is working as designed. Cold migration doesn't change the
flavor, so if you modify the flavor extra specs that change isn't
reflected in the instance when it moves. It's generally better to create
a new flavor with the new extra specs rather than modify old ones that
existing instances ar
Public bug reported:
Current _update_usage_from_migrations code takes into account only
REBUILDING task state, while not handling properly rebuilding spawn and
rebuilding volume attachments. This can cause issues with numa
topologies or pci devices if several instances are being evacuated and
some
In your log:
"OperationalError: (pymysql.err.OperationalError) (1040, u'Too many
connections')"
Increase the max_connections in your mysql config.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Public bug reported:
Hi,
When you change the meta-data on a flavor this change is not migrated
into the nova table instance_extra. So when you change the flavor and
you cold migrate the instance, it still uses the old meta-data spec set
during initial creation.
The behaviour creates inconsistanc
Public bug reported:
When openstack_dashboard/wsgi/django.wsgi was moved in rocky to
openstack_dashboard/wsgi.py path in there was unchanged and this causes
initioalization error as it cannot find openstack_dashboard.settings
module. I believe that
sys.path.insert(0, os.path.normpath(os.path.join
23 matches
Mail list logo
