summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Disable a config test if ran under the root userstable/yogaHervé Beraud2022-08-311-0/+3
| | | | | | | | | | | | | | | | | 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 (cherry picked from commit 7b838f5c31c3219d13661ec612d750e58683cbe6)
* Update TOX_CONSTRAINTS_FILE for stable/yogaOpenStack Release Bot2022-03-041-2/+2
| | | | | | | | | | | | 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/yoga branch, tests will continue to use the upper-constraints list on master. Change-Id: I533708f35d0223138a247b1bbfd507aea15a0a6e
* Update .gitreview for stable/yogaOpenStack Release Bot2022-03-041-0/+1
| | | | Change-Id: I3d62469a7b14ba4b167a601a16f31750535a957f
* Update python testing classifier8.8.0dengzhaosen2021-12-211-0/+1
| | | | | | | | | | | | | | 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
* Add Python3 yoga unit testsOpenStack Release Bot2021-09-101-1/+1
| | | | | | | | | | | 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
* Update master for stable/xenaOpenStack Release Bot2021-09-102-0/+7
| | | | | | | | | | | | 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
* setup.cfg: Replace dashes with underscoreslikui2021-09-021-1/+1
| | | | | | | | | | | | | | | | | | 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
* Merge "Replace deprecated UPPER_CONSTRAINTS_FILE variable"Zuul2021-08-201-1/+1
|\
| * Replace deprecated UPPER_CONSTRAINTS_FILE variablelikui2021-06-031-1/+1
| | | | | | | | | | | | | | | | 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
* | Fix tests for Python3.Cyril Roelandt2021-08-191-2/+8
|/ | | | Change-Id: Ifbf6f52a312929ac07154db8eeee976b0ab0d46a
* Merge "config-generator yaml format doesn't work with i18n fields"xena-em8.7.1Zuul2021-06-021-0/+14
|\
| * config-generator yaml format doesn't work with i18n fieldsDavid Vallee Delisle2021-05-161-0/+14
| | | | | | | | | | | | | | | | | | | | | | 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
* | Merge "Ussuri+ is python3 only"Zuul2021-06-011-1/+1
|\ \
| * | Ussuri+ is python3 onlydengzhaosen2021-05-051-1/+1
| | | | | | | | | | | | | | | | | | update python to python3 Change-Id: I83c8c9897678f8a0628987a071adda68062ac515
* | | Merge "setup.cfg: Replace dashes with underscores"Zuul2021-05-271-3/+3
|\ \ \ | |_|/ |/| |
| * | setup.cfg: Replace dashes with underscoressongwenping2021-04-291-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Merge "Add the version parameter."8.7.0Zuul2021-05-051-1/+1
|\ \ \ | |_|/ |/| |
| * | Add the version parameter.Daniel Bengtsson2021-05-041-1/+1
| |/ | | | | | | | | | | Call the parent with the version parameter. Change-Id: I20016e299077a7b678ecabceacb21cc0c7d306c8
* | Merge "Remove references to 'sys.version_info'"Zuul2021-05-041-6/+1
|\ \ | |/ |/|
| * Remove references to 'sys.version_info'dengzhaosen2021-04-251-6/+1
| | | | | | | | | | | | We support Python 3.6 as a minimum now, making these checks no-ops. Change-Id: I668c1bddba29a5e823734b1cad5116ba2fdb5f75
* | Merge "Adding the missing HostDomain config option"8.6.0Zuul2021-04-264-0/+61
|\ \ | |/ |/|
| * Adding the missing HostDomain config optionHervé Beraud2021-04-224-0/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Merge "tests: Add test for config file priority order"Zuul2021-04-211-6/+39
|\ \
| * | tests: Add test for config file priority orderStephen Finucane2021-04-141-6/+39
| | | | | | | | | | | | | | | | | | | | | | | | 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>
* | | Fix formatting of release listPierre Riteau2021-04-161-15/+15
| | | | | | | | | | | | Change-Id: Id0b62cae0e8d738ae379ff63b379b770278e65f2
* | | Merge "remove unicode from code"Zuul2021-04-164-11/+9
|\ \ \
| * | | remove unicode from codexuanyandong2021-04-164-11/+9
| |/ / | | | | | | | | | Change-Id: I062829a44a62014e88f285a82b6800e37f00ff28
* | | Merge "Add Python3 xena unit tests"Zuul2021-04-151-1/+1
|\ \ \
| * | | Add Python3 xena unit testsOpenStack Release Bot2021-03-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | Merge "Update master for stable/wallaby"Zuul2021-04-152-0/+7
|\ \ \ \ | |/ / / | | | / | |_|/ |/| |
| * | Update master for stable/wallabyOpenStack Release Bot2021-03-182-0/+7
| |/ | | | | | | | | | | | | | | | | | | | | | | 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
* | Merge "update doc url"Zuul2021-04-121-1/+1
|\ \
| * | update doc urllikui2020-10-301-1/+1
| | | | | | | | | | | | Change-Id: I227172cb51ea357a2c807fa080b0eaf7fd312e78
* | | Move flake8 as a pre-commit local target.Daniel Bengtsson2021-03-231-3/+7
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Bump minimum version for PyYAML to 5.18.5.0Ben Nemec2021-02-181-1/+1
| | | | | | | | | | | | | | | | | | 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
* | remove lower-constraints.txtlikui2021-01-162-86/+0
| | | | | | | | | | | | [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019390.html Change-Id: I407b2c9bc6e9c1cd5b070a1cdca7c0eabe19b0ca
* | Merge "Remove Babel from lower-constraints.txt"Zuul2021-01-161-1/+0
|\ \
| * | Remove Babel from lower-constraints.txtlikui2020-09-031-1/+0
| | | | | | | | | | | | Change-Id: I2012d7ceada837461b02a6041eb099d87306ed21
* | | Merge "Move zuul config file to root folder"Zuul2021-01-141-0/+0
|\ \ \
| * | | Move zuul config file to root folderMoisés Guimarães de Medeiros2021-01-121-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | inherit from object is not required for py3Moisés Guimarães de Medeiros2021-01-1210-16/+16
|/ / / | | | | | | | | | | | | Change-Id: I3f3b1dca78e2e9b2515231ccc6600b64f31039fb Signed-off-by: Moisés Guimarães de Medeiros <moguimar@redhat.com>
* | | Dropping lower constraints testingMoisés Guimarães de Medeiros2021-01-121-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We facing errors related to the new pip resolver, this topic was discussed on the ML and QA team proposed to to test lower-constraints [1]. I propose to drop this test because the complexity and recurring pain needed to maintain that now exceeds the benefits provided by this mechanismes. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019390.html Change-Id: I83e50eade2cf9924424d763421e464e559c16a08
* | | Merge "Adding --check-defaults to validator"8.4.0Zuul2020-11-264-9/+302
|\ \ \
| * | | Adding --check-defaults to validatorDavid Vallee Delisle2020-11-244-9/+302
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When troubleshooting, it's often interesting to see the deltas between the default or sample configs and the running configuration. The oslo_config.validator is a great tool to integrate this feature across all projects. It can also be easily captured by data collection tools like sosreports with the current deployment packages. Change-Id: I172d82f19a81282093b0d5f7ae4c1817801cd887 Signed-off-by: David Vallee Delisle <dvd@redhat.com>
* | | | Merge "tox: Enable parallel docs builds"Zuul2020-11-051-2/+2
|\ \ \ \
| * | | | tox: Enable parallel docs buildsStephen Finucane2020-09-101-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While we're here, specifying the doctree directory and configuring use of saved environments doesn't really make sense when we blast all previous doc build artefacts away on each build, so stop specifying those. Change-Id: I2b04a5c0ac121954aed91ae133e249a2e5813ee0 Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
* | | | | Use py3 as the default runtime for toxHervé Beraud2020-11-031-1/+1
| |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Moving on py3 as the default runtime for tox to avoid to update this at each new cycle. Wallaby support officially the following runtimes [1]: - Python 3.6 - Python 3.8 During Victoria Python 3.7 was used as the default runtime [2] however this version isn't longer officially supported. [1] https://governance.openstack.org/tc/reference/runtimes/wallaby.html#python-runtimes-for-wallaby [2] https://governance.openstack.org/tc/reference/runtimes/victoria.html#python-runtimes-for-victoria Change-Id: Iab5475c25b3ff1ffd0b10766ab0a5dbd4b1c821a
* | | | Merge "Add a new type HostDomain."Zuul2020-10-223-4/+76
|\ \ \ \ | |_|_|/ |/| | |
| * | | Add a new type HostDomain.Hervé Beraud2020-10-223-4/+76
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | HostDomain is like HostAddress with the support of _ character - RFC1033 openstack services are failing to start when a hostname with underscore _ is provided. Example: ``` overcloud-novacompute_edge1-0.internalapi.localdomain overcloud-novacompute_edge1-0.internalapi ``` Nova use `HostAddressOpt` to define `live_migration_inbound_addr`, and if a hostname with underscore is present in the config file then the service fail to start. Example: ``` /etc/nova/nova.conf live_migration_inbound_addr = overcloud-novacompute_edge1-0.internalapi.localdomain ``` FQDN is a domain name that specifies its exact location in the tree hierarchy of the Domain Name System (DNS). Underscore are allowed by RFC1033 [1][2][3]. Indeed, while a hostname may not contain other characters, such as the underscore character (_), other DNS names may contain the underscore.[1][2]. Systems such as DomainKeys and service records use the underscore. These changes allow us to use underscore with the `HostDomain`. [1] https://www.ietf.org/rfc/rfc1912.txt [2] https://www.ietf.org/rfc/rfc1033.txt [3] http://domainkeys.sourceforge.net/underscore.html Co-authored-by: Daniel Bengtsson <dbengt@redhat.com> Change-Id: I0a0670207f96a987996d329e5efa9a5eb2ce000c Closes-Bug: #1892044
* | | Merge "Convert rst to plaintext for oslo.config output"Zuul2020-10-123-3/+51
|\ \ \
View Lorry Controller Status