In Python3, assertRegexpMatches & assertNotRegexpMatches
are deprecated in favor of assertRegex and assertNotRegex
Change-Id: I5966bf52b86e3b7ce7fb0f75c662af15a50c122e
Zuul now supports including the file extension on the playbook path
and omitting the extension is now deprecrated. Update references
to include the extension.
Change-Id: Ib6213593f87b6fce2059e01123348d4951ecccd6
Migrate all functional jobs and gate to zuul v3.
We will have to migrate all other legacy jobs too later.
This patch do step 1 in the docs: Move Legacy Jobs to Projects.
Co-Authored-By: Dai Dang Van <daidv@vn.fujitsu.com>
Needed-By: If7dfc17ccc93cd5d99cc899abf7c7cbe08a738dd
Needed-By: I18b026fbfc1741ca397f36c8cbf24aa02c03f4b5
Change-Id: I5c230a5cdd9ee42eee218f84e678d4f155dfc953
When a session is first used for accessing database but fails, it
need to rollback before being used again.
Change-Id: I82065e4add3a9a5d0906734bb124617658491c31
Closes-bug: #1727667
get_or_create_project() first calls a get (query of the database).
If that fails, then it calls create. The issues is when
there are two threads and both fail the original get, then
each will call create. One of those creates will fail, resulting
in the traceback.
One way to protect this critical region is to call create first,
then if that fails, call get.
In this case, get_or_create_project() is called for every
Barbican API operation. The create action (which is slow), happens
once per project for the life of the cloud. The get action happens
every other time. For performance gains, I left call get first,
since that call succeeds almost always.
Change-Id: I2f13b495a6b45e226e0742291f76ee88dbcf52df
Closes-bug: #1726203
python-subunit is not used directly anywhere
and it is dependency of both testrepository
and os-testr
Change-Id: I3e17805d35dbf961ca154e14a34248f0504f1b71
KMIP by default tries to use PROTOCOL_TLSv1_2, but not all systems that
run the unit tests necessarily have this.
Dynamically determine the version to use.
Change-Id: Ia13841b3547332d6d5044b446b073dc2394bb8fb
This is a mostely complete solution. Ideally we could use the stevedore
entry point name 'barbican' instead of the full class name for cinder, but
I87926d6c95ac82b6f74c263c7441614f80348c1e needs to merge first.
Change-Id: I32ed528f585e790bc771473504ab7e4bfeb63de9
In order to make it simpler to use the default
configuration files when deploying services
from source, the files are added to pbr's
data_files section so that the files are
included in the built wheels and therefore
deployed with the code. Packaging and deployment
tools can then more easily use the default files
if they wish to.
This pattern is already established with similar
files for neutron and the glance metadefs as has
been mentioned in the related bug report.
Change-Id: Iacb17585a3235e95faa109ff11f1b039429ff770
Closes-Bug: #1718356
In Barbican stable branches, we run a gate job on Fedora 26.
devstack needs FORCE=yes flag to run on f26 for Pike and
earlier releases.
Change-Id: I9de812991c4476af4010cd6ecebb8e3c912abf52
The functional test that checks secret expiration fails
intermittently because sometimes, when the gate is slow,
the secret expires too quickly for the test.
This patch adds an extra 10 seconds so the test will pass
more consistently, while still maintaining the integrity
of the test.
Change-Id: I2f0df9b42dd2bf9dd600948164532fd31bb2a0d3
Closes-Bug: #1499673
Seems like keystone will ask barbican for its infomation
including endpoint. So barbican should handle general endpoint
e.g., 'http://localhost:9311' or 'http://localhost/key-manager'
Change-Id: Id7230198583355a83b1ee4acef3da7cde7118794
