If a custom CA file is configured via nova_ca_certificates_file,
currently communication with Keystone will fail, since the session is
not created using this CA file. The same is true for nova_api_insecure.
This change fixes the issue by using a keystoneauth session loader.
Closes-Bug: #1873736
Change-Id: I54a4f398a06c61e0f6f8f3efd3e4b6214bca756b
(cherry picked from commit 3bd82c776c91bdd1caee474f3fc9cda18927da7f)
(cherry picked from commit fc7546a2aed061f661fc4e975343f32a6fdc27d8)
Occasionally, there would be notifications which will remain 'new',
'error' or 'running' status all times, and not to be processed again.
Due to this, operator can not update the segment or host.
This patch add one task to periodically check unfinished notifications.
If one unfinished notification is expired, just set its status to
'failed'.
Conflicts:
masakari/tests/unit/engine/test_engine_mgr.py
- difference of import mock and import unittest.mock
Closes-Bug: #1773765
Change-Id: If49635639dd976aeec3ea73e702ad2636fcf1e0a
(cherry picked from commit 3a4f782441f6bdcfb8ee49a393937267fc246c56)
The Exception notification code calls inspect.trace(), which returns an
empty list if called outside of an except clause. The returned list is
then indexed, causing an IndexError. In fact, every use of this
exception in the engine is from outside of an except clause.
This can affect notification processing, causing notifications to get
stuck in a running state, requiring manual DB deletion.
This change addresses the issue by checking whether the list returned by
inspect.trace() is empty.
A more complete solution would involve checking every call path to the
exception notification, and ensuring that it is made from an except
clause.
Change-Id: I01af664d53db20041ac7306d2bca63254ffc9ede
Partial-Bug: #1889765
(cherry picked from commit 69a9a41802edf21c8e4784835654697e13db9ca2)
df08881...
by
OpenDev Sysadmins <email address hidden>
OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:
Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
Below patch move the legacy base jobs to bionic which will move the derived jobs
automatically to bionic. These jobs are modified with branch variant so that they will use
Bionic node from stein onwards and xenial for all other stable branches
until stable/rocky.
- https://review.openstack.org/#/c/639096
This commit modify the nodeset of multinode job to bionic
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
d77510e...
by
OpenStack Release Bot <email address hidden>
Update UPPER_CONSTRAINTS_FILE for stable/stein
Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.
Until the requirements repository has as stable/stein branch, tests will
continue to use the upper-constraints list on master.
