This is already fixed in master:
https://github.com/mitmproxy/mitmproxy/pull/2435
So it'll hopefully in the next release.
Because the pyOpenSSL package name and requirement name do not match we
also add code to lower the name for comparison.
Also the check-uc only complains about a single issue but there are 3.
Change-Id: I6657802908ac4052eeb6c73fb03098b0c3557eb2
In marathon 0.9.1, python3 support is broken,
it is fixed in master. It breaks any python3 job,
if 0.9.1 is used.
Issue:
https://github.com/thefactory/marathon-python/issues/217
Change-Id: If802ae734d0a9eba48dcfcfa370f3a2bca0ece17
This commit bumps the minimum requirement of os-testr to 1.0.0. This new
release changes the test runner used internally to stestr. Since this is
a major internal change it'll be better to switch it early in the cycle
to shake loose any potential bugs.
Change-Id: Iabe4217c6aa52cb4d3a715756e0b8c46a6d553d0
oslo.privsep gained many new constants with I1e6f7bff66495cdb83428a6c3b62804e5d20fc3b
which is included in the 1.23.0 release. In [1] those values are simple
open coded. Raising the minimum allows nova to use the new constants.
[1]: https://review.openstack.org/#/c/459166/33/nova/privsep/__init__.py@30
Change-Id: Icaeb2800a009b996c8eefe91916eeefcd5bca6a2
pypowervm 1.1.7 contains a number of bugfixes and important features
needed in nova for PowerVM, including support for I/O slot usage
information (needed by
https://blueprints.launchpad.net/nova-powervm/+spec/pci-passthrough).
Change-Id: Icb7a5c0804e6722170b973d8522987b413dd5f3f
pypowervm 1.1.7 contains a number of bugfixes and important features
needed in nova for PowerVM, including support for I/O slot usage
information (needed by
https://blueprints.launchpad.net/nova-powervm/+spec/pci-passthrough).
Change-Id: I4b0eb68779bef4bf56c48093b2706aa521d174fc
Excludes pika 0.11.0 which breaks Keystone.
Excludes castellan 0.13.0 which breaks Cinder, see bug 1715451.
Excludes kubernetes 3.0.0 which requires older websocket-client.
Excludes oslo.messaging since we handle that via another bot update
Excludes iso8601 for known cinder issue (being looked into now)
Depends-On: Ic022bdc0291ce1498abdfe1acd3cc51adf7db7c6
Depends-On: Ida4b8c33e8b3bbd03548648f8e57d923b255f35c
Depends-On: Ic12df8b12b1379f902137d49b605daaf0b89801d
Change-Id: Ica3837877c70f161e384021b10c973b670e72113
Once the gate issue is sorted in openstack-ansible_os_tempest
we should undo this patch, as requirements and upper-constraints are actually correct.
This reverts commit afd39d8ac3464e280c964cfc4336298c2729ca8d.
Change-Id: I3bd3a5485f1b54adef4a4be7d3edc05a43af4aad
Shade 1.23.0 has a bug that causes ansible os_image module
to fail. Reverting to 1.22.2 would solve our issue.
This reverts the bump and blacklists the impacted version.
Change-Id: I1387b538b96e428dd3dc6d2e3f9e9fbb6fd2e9cf
Closes-Bug: #1715603
Based on testing against the g-r set of cross checks, which includes
dsvm, grenade, unit and functional tests of glance, cinder, nova, neutron
and swift, these seem to be the lower bounds that are actually coinstallable
and passing all tests.
Change-Id: I4a193295081593a9df6c34b5c263b1b8becadbda
Most of them were neglected and pointed to versions released
a year ago and more, which are typically not installable anymore
(they used to have a pbr<2.0 requirement which is incompatible
with the pbr>=2.0 requirement we enforce globally).
So for all of the openstack affine projects, update to a release
that is less than 4 months old (in some cases even newer versions
were required upon trial and error).
Change-Id: I69472a6a99b857e9e5dad9052eda7172ae2c9525
whereto is developed on OpenStack infrastructure. I am in the process
of having the docs team adopt it for maintenance.
Is the library actively maintained? - Yes. This is an OpenStack
community product.
Is the library good code? - Only the best.
Is the library python 3 compatible? - Yes. It has the standard python
3 unit test jobs in its gate.
Is the library license compatible? - Yes, Apache 2.
Is the library already packaged in the distros? - No, but it's a doc
build tool so it may not need to be.
Is the function of this library already covered by other libraries? -
I was unable to find any similar tool that could be downloaded and run
in CI anywhere at all, so no.
Is the library required for OpenStack project or related dev or
infrastructure setup? - It is a tool for testing redirect rules and
will be an optional component in doc CI jobs. The documentation team
is already using it (the openstack-manuals repo does not follow the
global requirements process).
If the library release is managed by the Openstack release process
does it use the cycle-with-intermediary release type? - It will likely
continue to use the independent release model after being formally
adopted, but that is not decided.
Change-Id: I67e9453367cfd26b862a18a87a0b135a28ca756c
Signed-off-by: Doug Hellmann <doug@doughellmann.com>