We also bump the hacking version and remove some unnecessary notes from
the top of the requirements files: these don't apply with the dependency
resolver introduced in pip 20.3.
Change-Id: Ifebaec916264bfd10eec13040295719fd47ae107
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
1.Add sqlalchemy-migrate dependence in test-requirements.txt.
It will remove the dependence after this project switchs to alembic.
Remove "check-requirements" temporarily.
2.Fix unit tests broken by olso.utils
Some of the object unit tests grub Mock object unintentionally, and
that results in failure during initializing an versioned object,
because the Mock object does not present its version correctly.
3.make functional jobs not voting
Fix functional jobs later.
Change-Id: Id3c952a54e77952cfd0d76d259f49a14edca1d8b
api-ref requires only doc requirements, not test.
Furthermore, some deps may not be installable due to lack of
binary deps in api-ref jobs, e.g. postgres [1].
[1] https://review.opendev.org/744343
Change-Id: Ie730a85ec2d05c3cdbab49da619f27982c14b9ce
Needed-By: https://review.opendev.org/744343
Suppress of policy deprecation warnings. oslo.policy logs the
deprecated policy warnings while loading the
policy rules. Flag to suppress the warning was set after load_rule()
was called. We do not need to log warnings for unit test where
every test initializes the policy and logs a warning.
Also use yaml format of policy file in unit test to avoid
more warnings for json file.
Bump a few l-c for Py38 testing, squashing parts of
https://review.opendev.org/744343
Fix unit tests compatibility with Py38, squashing parts of
https://review.opendev.org/748874
Change-Id: Ia54d29975347392cbb93c07969d7e3b48eca5d23
Co-Authored-By: Radosław Piliszek <radoslaw.piliszek@gmail.com>
flake8 new release 3.8.0 added new checks and gate pep8
job start failing. hacking 3.0.1 fix the pinning of flake8 to
avoid bringing in a new version with new checks.
Though it is fixed in latest hacking but 2.0 and 3.0 has cap for
flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also
break the pep8 job if new check are added.
To avoid similar gate break in future, we need to bump the hacking min
version.
- http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html
Change-Id: Ie0dda286eda1d4c955839f10b598b15fb5d95f19
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Fix problems found by updated hacking version.
Update local hacking checks to work with current flake8.
Remove hacking and friends from lower-constraints, they are not needed
there.
Change-Id: I89695a03791c2de36ab015b3831c85887b27f3b8
From last couple of months, the functional devstack job is broken.
Fixed the devstack job so that functional tests can run on multi-node
setup.
Note: Need to install SQLAlchemy-Utils explicitly as taskflow library
installs it using extra_requires which somehow is not working on the
devstack CI job setup.
Change-Id: I224b4a5615525862f73ced8ab9f5f396cb00ef0f
Due to the upper-constraints argument being hard coded in the
install_command, even jobs like lower-constraints will end up getting
the latest upper-constraints installed.
The correct way to handle the constraints is to separate it out into
deps. This allows the l-c job to properly set what constraints to use.
Also fixes constraints URL to the preferred static path.
Change-Id: I92b6ee8ea5afdb16367a5b6d939e65e2fa48190d
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
The oslosphinx package is not compatible with the current Sphinx 2.0
release. Migration has been happening to openstackdocstheme for some
time. To fix build failures for docs and releasenotes jobs, this
switches masakari jobs to use openstackdocstheme.
Uncapping jsonschema to pass requirements check so it matches global
requirements.
Change-Id: Ic74e8b075aa67d410617dac3346bf1c903995da7
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This patch uses taskflow's persistence feature to store recovery
workflows details into database.
Added a new microversion to return progress_details of the
notification in `GET /notifications/<notification_uuid>` API.
APIImpact:
GET /notifications/<notification_uuid> API includes details
of recovery workflow
Change-Id: I93c1b7d88823e02d9a02855cabb8b22c9e40a7d5
Implements: bp progress-details-recovery-workflows
This commit is a follow-up of "switch to using stestr"
which was merged already [1].
After switch to using stestr, testrepository is unnecessary
and should be removed.
[1] https://review.openstack.org/578515
Change-Id: I79855f50754d0e33d779c0762220019cb8649ba3
According to Openstack summit session [1] stestr is maintained
project to which all Openstack projects should migrate.
Let's switch it then.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: Ifb64df81f7684d5bf732afcbe594a38691a7286f
Signed-off-by: Chuck Short <chucks@redhat.com>
Added api specifications for versions, segments, hosts and
notifications as per OpenStack standards.
Change-Id: Iefc83254e22fc31d1f0d13f52e71d42c63e82b7d
Masakari should use ostestr instead of testr. ostestr is more
powerful and provide much prettier output than testr. Other
projects like cinder, nova, glance, neutron etc already uses
the ostestr wrapper.
Using ostestr shows each tests execution separately because of
which it has shown errors related to "KeyError" in existing test
cases. The error looks like below:
"Exception in string format operation: KeyError: u'id'"
This happens if we don't pass keyword argument like "id" to
exception which we expect to be raised from test through
side_effect [1]. This doesn't lead to test failure but it
appears in test logs. This patch fixes such issues by passing
expected keyword arguments to exceptions.
[1] https://github.com/openstack/masakari/blob/master/masakari/tests/unit/api/openstack/ha/test_hosts.py#L364
Change-Id: I91603ea3dcf35fd20a00dcf477b93d612edca362
DDT can ease up error tracing and auto generates tests on
basis of different input data.
Reduce test code data by using DDT for segments, hosts, and
notifications.
Co-author: Dinesh Bhor <dinesh.bhor@nttdata.com>
Change-Id: Ie3ce3316c6e2fc3f98df3a51db59ca7f1f1625b8
The older hacking library has a cap on pbr <2.0, with the recent 2.0.0
release of PBR it's causing failures in the pep8 job. hacking isn't
kept in sync via the typical proposal-bot updates. Do it manually to
clear the gate issue.
Please see gate logs for reference:
http://logs.openstack.org/31/406931/1/check/gate-masakari-pep8-ubuntu-xenial/1e8b199/console.html
Related-Bug: #1668848
Change-Id: I5fd77ca87266034c42dae59fd28ede7f6b9dd382
Added unit test cases for the merged WSGI framework patch.
WSGI framework:
https://review.openstack.org/#/c/340752/
Change-Id: I213aa07e19f1a35a7b758711aa15677000c7f0f6