This bug was fixed in the package python-keystonemiddleware -
5.2.0-0ubuntu2
---
python-keystonemiddleware (5.2.0-0ubuntu2) cosmic; urgency=medium
* d/p/bug1789351.patch: Cherry pick fix for dict iteration issue under
Python 3 (LP: #1789351).
-- James Page Fri, 07 Sep 2018
** Also affects: python-keystonemiddleware (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-keystonemiddleware (Ubuntu)
Status: New => In Progress
** Changed in: python-keystonemiddleware (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
** Changed
Reviewed: https://review.openstack.org/599744
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=63c10d2d536c3ffed68ccfb6bd393f317111d903
Submitter: Zuul
Branch:master
commit 63c10d2d536c3ffed68ccfb6bd393f317111d903
Author: Matt Riedemann
Date: Tue Sep 4 14:53:25 2018
Reviewed: https://review.openstack.org/599744
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=63c10d2d536c3ffed68ccfb6bd393f317111d903
Submitter: Zuul
Branch:master
commit 63c10d2d536c3ffed68ccfb6bd393f317111d903
Author: Matt Riedemann
Date: Tue Sep 4 14:53:25 2018
Public bug reported:
When browsing to Admin -> System -> System information, as an admin
user, if there's no Neutron installed, then Horizon just crashes:
[ ... snip ... ]
File "/usr/lib/python3/dist-packages/horizon/utils/memoized.py" in wrapped
176. args.insert(request_index,
Public bug reported:
env: OpenStack Ocata, ml2 hierarchical port binding with openvswitch as
bottom driver
When the bottom segment already bound to a l2 driver is dynamiclly released,
the associated neutron.ml2_port_binding_levels.segment_id will be set "NULL",
and cause the local vlan tag of
Public bug reported:
Supposing the tenant network type is vlan. And we have a neutron network whose
vlan id is 1000 (CIDR: 192.168.111.0/24, gateway IP: 192.168.111.1).
We aslo have a physical switch (SWITCH-1), which connect the compute NODE-1,
NODE-2.
For these compute nodes, we set the l3
Public bug reported:
We lost some changes of doc/source/user/launch-instance-from-volume.rst
in openstack-manuals after ocata
We need upload the latest doc from manuals repo [1], and
merge all later changes[2][3][4] into this doc.
[1] I4a556b6a596a28c0350c7411c147459c3f06d084
[2]
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
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
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
11 matches
Mail list logo
