| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 32d554906c56e5bd522b5affe19d54c8c4131a07.
Keeping Python 3.10 in setup.cfg classifier and zuul.yaml changes.
Reason for revert:
Needed-By: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/882175
TC has been discussing about re-adding the python 3.8
testing in current master 2023.2 release testing.
- https://meetings.opendev.org/meetings/tc/2023/tc.2023-04-25-18.00.log.html#l-191
- https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033469.html
While governance changes are under review, TC agreed to add py3.8 testing
so that we do not see more project/lib dropping python 3.8 and make them
uninstalable on python 3.8
- https://meetings.opendev.org/meetings/tc/2023/tc.2023-05-02-18.00.log.html#l-17
- https://review.opendev.org/c/openstack/governance/+/882165
Also adding py3.8 testing back in job https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/882175
Change-Id: I9becb9a67b07f260741c5fcc8bdb6c96cbbbe1d7
|
|
|
|
|
|
|
|
| |
Within 2023.2 python version 3.9 and 3.10 are the
supported python runtimes [1].
[1] https: //review.opendev.org/c/openstack/governance/+/872232
Change-Id: Ibd9c332ea54bc225887ceb60e77622432793726f
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add file to the reno documentation build to show release notes for
stable/2023.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.1.
Sem-Ver: feature
Change-Id: I709b3871b07a1b5eeb711916d4af75dcbe06b78e
|
|
|
|
| |
Change-Id: I7be9a22796f484df79f0f509a2cf4f47e3a00128
|
|
|
|
|
|
|
|
| |
Change the assertion kind to support all versions of cliff.
The previous related fix 78098e6b18026ff9ef03a948b57348f02d42e13b
was only compatible with cliff>3.4.0.
Change-Id: I7ac27919b0d58929b4c975ebb308f33124a6060f
|
|
|
|
|
|
|
|
|
|
|
| |
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for antelope.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: I032790c6e4a19bd5e0ef32e0f6f5d0372f43640a
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add file to the reno documentation build to show release notes for
stable/zed.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/zed.
Sem-Ver: feature
Change-Id: I82608453f5edf65bbd8ab42ef1e5106f536142eb
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The `test_conf_file_permission_denied` is designed to test
if a config file can't be read due to missing file permissions.
However if we run unit tests with the root user we will beneficiat
from the root privileges and so this test will fails. This can
be reproduced by running `tox` with `sudo`.
These changes propose to skip this test if root privileges are
detected.
Closes-bug: #1983358
Change-Id: Idd124082265032c30f83242b612d002d7093aa61
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since cliff > 3.4.0 we can see mismatch errors with unit tests, this
patch fix this error.
Also this patch fix some issues with deprecation messages.
All these issues needs to be fixed together to unlock our gates.
Closes-bug: #1908934
Change-Id: I8396b4f3ba74a9ea023bff2e3027710f16a74af4
|
|
|
|
|
|
|
|
|
|
| |
In Zed cycle testing runtime, we are targetting to drop the
python 3.6/3.7 support, project started adding python 3.8 as minimum,
example nova:
- https://github.com/openstack/nova/blob/56b5aed08c6a3ed81b78dc216f0165ebfe3c3350/setup.cfg#L13
Change-Id: I18f643d5a7b6283b72c0cd3caeadf0d14f6ed713
|
|
|
|
|
|
|
|
|
|
|
| |
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for zed.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: Ia9a793cf2f8eed8afc231aa32f7a0f12b3b2cec7
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add file to the reno documentation build to show release notes for
stable/yoga.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/yoga.
Sem-Ver: feature
Change-Id: I64f5023e8f9f4c49d4d7d08b4ea339af4ac9a7a8
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Yoga testing runtime[1] has been updated to add py39
testing as voting. Unit tests update are handled by the
job template change in openstack-zuul-job
- https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/820286
this commit updates the classifier in setup.cfg file.
[1] https://governance.openstack.org/tc/reference/runtimes/yoga.html
Change-Id: Ia1cd4536ecf6a0b0e86796dffb5ca04197bd5abe
|
|
|
|
|
|
|
|
|
|
|
| |
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for yoga.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: I178e86fe8646c0c91b982670c5fd12264c1ee05d
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add file to the reno documentation build to show release notes for
stable/xena.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/xena.
Sem-Ver: feature
Change-Id: I31fff76861e961754fef2d65a6938e6a028d702b
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Setuptools v54.1.0 introduces a warning that the use of
dash-separated options in 'setup.cfg' will not be supported
in a future version [1].
Get ahead of the issue by replacing the dashes with underscores.
Without this, we see 'UserWarning' messages
like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: Iceaa69d80eef75db5bac67463a59fd615ae0e895
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
UPPER_CONSTRAINTS_FILE is old name and deprecated
[1] https://zuul-ci.org/docs/zuul-jobs/python-roles.html#rolevar-tox.tox_constraints_file
Change-Id: Ie7971577aeba299aaf9406fc97793d946342eaeb
|
|/
|
|
| |
Change-Id: Ifbf6f52a312929ac07154db8eeee976b0ab0d46a
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is because there's no yaml representer for i18n Messages object.
This patch aims to add this representer and allow the generation of
configurations using oslo.i18n strings.
One example of this is cinder.
Closes-bug: #1928582
Change-Id: I70ab87c9bed093cad883b6301b8a09753fc470d9
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
update python to python3
Change-Id: I83c8c9897678f8a0628987a071adda68062ac515
|
|\ \ \
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: Icc9b9a3af1c8cf58b3a2b9626065cb2fcd074a42
|
|\ \ \
| |_|/
|/| | |
|
| |/
| |
| |
| |
| |
| | |
Call the parent with the version parameter.
Change-Id: I20016e299077a7b678ecabceacb21cc0c7d306c8
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| | |
We support Python 3.6 as a minimum now, making these checks no-ops.
Change-Id: I668c1bddba29a5e823734b1cad5116ba2fdb5f75
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The ``HostDomain`` config type have been added few months ago [1]
however the config option have been forgotten and this new type
isn't importable.
When we try to import this type without defining a new related cfg
option we get the following issue:
```
AttributeError: module 'oslo_config.cfg' has no attribute 'HostDomain'
```
These changes allow us to import this new type and allow us to use
it in our configs:
```
>>> from oslo_config import cfg
>>> foo = cfg.HostDomain('foo')
>>> foo.type.__call__("1")
...
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "~/oslo.config/oslo_config/types.py", line 893, in __call__
raise ValueError(
ValueError: 1 is not a valid host address
>>> foo.type.__call__("host_name")
'host_name'
```
Also properly initialize HostDomain because The HostDomain class wasn't
calling super in it's __init__() method, which resulted in the type_name not
being set properly for instances of that class.
[1] https://opendev.org/openstack/oslo.config/commit/6480356928c9ae6169ea1e5a5b5f1df3d6e0dc75
Change-Id: Ie947803f61ba0ef080018e0447de894a400d7975
Closes-Bug: 1924283
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This was documented in the docstring but we had nothing to assert it in
tests. Correct that gap.
Change-Id: I4002e7fe18c43eb5f9ba2eae16022d7da87f790d
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
|
| | |
| | |
| | |
| | | |
Change-Id: Id0b62cae0e8d738ae379ff63b379b770278e65f2
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | | |
Change-Id: I062829a44a62014e88f285a82b6800e37f00ff28
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for xena.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: I2e13ad1b86ad303d07f446985e3bb159667c2c0c
|
|\ \ \ \
| |/ / /
| | | /
| |_|/
|/| | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add file to the reno documentation build to show release notes for
stable/wallaby.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/wallaby.
Sem-Ver: feature
Change-Id: Ieef544f34d5291ed300a14801d73e2419f9db0cf
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I227172cb51ea357a2c807fa080b0eaf7fd312e78
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The goal here is to avoid conflicts between flake8 and hacking version each
2 days.
Inspired from nova's approach[1].
The flake8 version to install will be determined by hacking and
requirements[2] will stay aligned instead of relying on different versions.
[1] https://opendev.org/openstack/nova/src/branch/master/.pre-commit-config.yaml#L26-L35
[2] https://opendev.org/openstack/hacking/src/branch/master/requirements.txt#L1
Change-Id: I383111df27815708b60bf93ab565e402bb42d230
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This addresses CVE-2017-18342. I doubt anyone is actually using an
old version of PyYAML with oslo.config at this point, but that means
it shouldn't hurt to bump the minimum either.
Change-Id: I4f440eb9511333ce70db4184857dcbcdd0ed1b97
Closes-Bug: 1839398
|
| |
| |
| |
| |
| |
| | |
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019390.html
Change-Id: I407b2c9bc6e9c1cd5b070a1cdca7c0eabe19b0ca
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I2012d7ceada837461b02a6041eb099d87306ed21
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Moving .zuul.d/project.yaml to .zuul.yaml as it is the only file in
that folder and to look similar to other oslo repos.
Change-Id: I787f57e57e5dd83d08dfaecca2405bf064c9f924
|
|/ / /
| | |
| | |
| | |
| | | |
Change-Id: I3f3b1dca78e2e9b2515231ccc6600b64f31039fb
Signed-off-by: Moisés Guimarães de Medeiros <moguimar@redhat.com>
|