Public bug reported:
Tested vs OpenStack master + OVN:
Traceback (most recent call last):
File
"/usr/lib/python3.8/site-packages/neutron_tempest_plugin/api/test_trunk.py",
line 238, in test_add_subport
self.assertEqual(expected_subports, trunk['sub_ports'])
File "/usr/lib/python3.8/site-
It seems like we've got reasonable consensus that this is expected
behavior and have public documentation (at least in the Security Guide
as linked above, but likely also elsewhere), indicating that OpenStack
API servers on the whole do not make any attempt to mitigate excessively
rapid calls to ex
Reviewed: https://review.opendev.org/662522
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=c29f382f69ed0bfe2c8782913e2a882344ff461f
Submitter: Zuul
Branch:master
commit c29f382f69ed0bfe2c8782913e2a882344ff461f
Author: Stephen Finucane
Date: Fri Jun 7 16:57:31 2019 +01
Reviewed: https://review.opendev.org/704520
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=bfb8dcded66eb2ea702c12b8620db4aae58545db
Submitter: Zuul
Branch:master
commit bfb8dcded66eb2ea702c12b8620db4aae58545db
Author: Kobi Samoray
Date: Mon Jan 27 12:03:35 2020 +0200
I mark this as Invalid as it is not related to the API reference
apparently. Even if comment #1 describes the bug, it looks like a
support request. binding_failed happens due to various reasons including
your deployment constraints or situations. If you believe it is a bug of
neutron after checking
Public bug reported:
When the network segmentation ID is changed [1][2][3][4][5], the project
ID should be passed as an argument. If network-segment-range plugin is
enabled, the method [6] filtering the network segments should be able to
find those ones with the specified project_id.
This project
Public bug reported:
Cinder allows encrypted volumes to be uploaded as images to Glance.
Nova has never supported the direct boot of such images; instead, the
user is supposed to use the image to create a volume, which can then be
booted from.
NOTE: Allowing such an instance to go 'active' allows
Public bug reported:
We introduced vpmem support in Train release, including
create/resize/cold migration, but not live migration(with libvirt/qemu).
Since live migration will essentially rely on an libvirt xml, for vpmem there
will be backend files configued in xml, if we live migrate an instan
This bug was fixed in the package dmidecode - 3.0-2ubuntu0.2
---
dmidecode (3.0-2ubuntu0.2) xenial; urgency=medium
* Restrict /dev/mem scanning for entry point to x86, fixing crashes
on certain ARM platforms (LP: #1858615):
- New debian/patches/0140-Fix_scan_entry_point.patc
This bug was fixed in the package dmidecode - 3.1-1ubuntu0.1
---
dmidecode (3.1-1ubuntu0.1) bionic; urgency=medium
* Restrict /dev/mem scanning for entry point to x86, fixing crashes
on certain ARM platforms (LP: #1858615):
- New debian/patches/0140-Fix_scan_entry_point.patc
This bug was fixed in the package horizon - 3:16.0.0-0ubuntu1.1
---
horizon (3:16.0.0-0ubuntu1.1) eoan; urgency=medium
[ Corey Bryant ]
* d/gbp.conf: Create stable/train branch.
[ Hemanth Nakkina ]
* Fix users/projects list when domain context is changed (LP: #1826114)
-
This bug was fixed in the package dmidecode - 3.2-2ubuntu0.1
---
dmidecode (3.2-2ubuntu0.1) eoan; urgency=medium
* Restrict /dev/mem scanning for entry point to x86, fixing crashes
on certain ARM platforms (LP: #1858615):
- New debian/patches/0140-Fix_scan_entry_point.patch
Public bug reported:
Neutron fails with the following error:
2020-02-14 15:08:21.663 29 CRITICAL neutron
[req-b7615e16-e470--8342-86fca030273c - - - - -] Unhandled error:
oslo_db.exception.DBError: (pymysql.err.InternalError) (1047, 'WSREP has not
yet prepared node for application use')
[SQ
Public bug reported:
In job neutron-ovn-tempest-slow tests from module
tempest.scenario.test_network_v6.TestGettingAddress are failin 100% of
times.
Example of failure:
https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_2c7/707248/2/check
/neutron-ovn-te
** Changed in: kolla-ansible/train
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/1856296
Title:
upgrade to Train might fail
there is no actual bug description, so it looks like a spam or reported
by a mistake.
** Changed in: neutron
Status: New => 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/18
16 matches
Mail list logo