In one of the places where endpoint_override is used we did not strip the /v1 suffix, resulting in doube /v1/v1 sometimes. This patch also corrects the way we strip this suffix (str.rstrip accepts a set of symbols, not a substring; use regex instead). It remains unclear why the breakage passed the gate initially. I assume it was not on the active code path until some Nova change. Story: #2005723 Task: #31051 Change-Id: I3b25f4fb170aa93159ffa8074dc74fa6f50671b7 (cherry picked from commit 4565af8ccd8aaa35868fae6ae31216c3e57014f3)
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
Change [1] introduced the usage of endpoint_filter when deciding which endpoint to use during version negotiation. This requires properly setting interface/region/service_type in order to properly pick the endpoint. But, sometimes (for example in Kolla-ansible), the endpoint url is explicitly defined. In the event of the endpoint being explicitly defined, it should take priority here. It should be noted that even though SessionClient extends from keystoneauth1's adapter.LegacyJsonAdapter, the `request` function within _make_simple_request is being called on the nested Session object, not the Adapter itself. If it was called on the Adapter this problem wouldn't exist, as the `endpoint_override` (or `endpoint`) kwarg passed in to the constructor of the SessionClient would already take precedence. Additionally: Adds a release note to the older branch as this is a fix that needs to be released and is worthy of change visibility in release notes. [1]: I42b66daea1f4397273a3f4eb1638abafb3bb28ce Change-Id: I69dc2c88648ba1d09a9ad3ab3435662e8d1ea6ff Related-Bug: #1818295 (cherry picked from commit 8071d5de57c728ce09d25d04c8c9fe48cd7db42e)
-Switch functional job to run under python3 -Create a functional job to run under python2 -Create a tempest job to run under python2 -Create tox env to run functional tests under python3 -Validate if `USE_PYTHON3` is set to `True` to call the correct env for tests -Remove hardcoded path for client when running functional tests - Update tests failures to work for python2 and python3 Change-Id: I96d418f08c46add8bf61bf8d1b4e45b6083b8d84 (cherry picked from commit 9b881cb973bc2219df90c2b71e2a1d0e18dcd98a)
To move ironicclient legacy jobs to zuulv3 the the following changes were necessary: - Change `tox.ini` to pass envrioment variables - Clean `post_test_hook.sh` to avoid legacy variables (`$USER` and `$BASE`), removing `generate_testr_results` function since we only get `testrepository.subunit` in logs and the results of the tests are present in job-output file. - Convert `post_test_hook.sh` and `run_functional.sh` into `playbooks/functional/run.yaml` to run after the setup. Also includes the changes from commit 9cd6ce7eb2d96a8f58a4d00f85b405babf67d28f Change-Id: I6a5b3f82c238083b66bdf6f379092260d367d82d (cherry picked from commit 2c349cc8930897052e66d29a70e1e7f1c4d40d79)
This is a mechanically generated change to replace openstack.org git:// URLs with https:// equivalents. This is in aid of a planned future move of the git hosting infrastructure to a self-hosted instance of gitea (https://gitea.io), which does not support the git wire protocol at this stage. This update should result in no functional change. For more information see the thread at http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html Change-Id: Ia27139cf22ac11803855bd6c52cae8a8a2fbc3ba
Change-Id: I55be8c175cb9d3c63d2b6f17120dee6680a51473
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/stein branch, tests will continue to use the upper-constraints list on master. Change-Id: I875d54770405597d91c32155e3699e536824a5e6
The exception raised in the Ironic side has changed and the test need to be updated. This commit only cherry picked the test file to unblock the gate in `stable/stein` Change-Id: I55abc999f6f397b171d05fd9e9b39d833ca95e55 (cherry picked from commit 9b881cb973bc2219df90c2b71e2a1d0e18dcd98a)