[pull] master from openstack:master#3386
Merged
pull[bot] merged 48 commits intoMu-L:masterfrom Jan 18, 2024
Merged
Conversation
* Update neutron from branch 'master'
to 290cb630035099be81ae571e4cd84e31d502c752
- Merge "dhcp: improving log level of cleanup stale devices"
- dhcp: improving log level of cleanup stale devices
Process of cleaning stale devices is now logged at an informational
level, not just for debugging as operator should be aware of any
action on its platform. Also, the removal of stale devices which
should never occur, is marked as a warning. This change aids operators
in identifying unusual behavior on their platform.
Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@industrialdiscipline.com>
Change-Id: I8f878e50983cf0664a80ff8dbdfb0b6db68b6cd3
* Update manila-ui from branch 'master'
to de047b0cf755270b0d21b1f523100ce7d27ddbb9
- Merge "Fix python shebang"
- Fix python shebang
The current shebang requires /usr/bin/python which is not available in
Ubuntu Jammy by default.
This also removes unnecessary shebangs.
Change-Id: I046542e43d993ba201cc035554b4dcc4d364ed0a
* Update neutron from branch 'master'
to 12115302944293b7d6b022f5acb68fe9c649a53e
- Merge "Add firewall_v2 to extensions supported by ovn"
- Add firewall_v2 to extensions supported by ovn
This addition is required to run a devstack setup with ovn
that includes firewall_v2 from the proposed patch [1]
[1]https://review.opendev.org/c/openstack/neutron-fwaas/+/845756
Related-Bug: #1971958
Change-Id: Id370e86e470c160c38cfb5126bbfa0f0babe4485
* Update neutron from branch 'master'
to b28bf2d3a14a8dcba90e9f72413121da7730f8c0
- Merge "Cleanup setup.py and requirements"
- Cleanup setup.py and requirements
- Python 2 is no longer supported
- setup.py is no longer managed by the global tooling
- Recent pip does not require appropriate order in requirement files
Change-Id: Iaa1aa0022e207cceb26ed45474bc6edfbbec4faa
* Update requirements from branch 'master'
to 3cdc42978debef079a68dd9c73e08dd184b7e8ee
- Merge "update constraint for yaql to new release 2.0.1"
- update constraint for yaql to new release 2.0.1
meta: version: 2.0.1
meta: diff-start: -
meta: series: independent
meta: branch: master
meta: release-type: release
meta: pypi: yes
meta: first: no
meta: release:Author: Takashi Kajinami <kajinamit@oss.nttdata.com>
meta: release:Commit: Takashi Kajinami <kajinamit@oss.nttdata.com>
meta: release:Change-Id: I60d42268b3d5517300dc98f675d8bb87cfea0587
meta: release:Workflow+1: Thierry Carrez <thierry@openstack.org>
meta: release:Code-Review+2: Elod Illes <elod.illes@est.tech>
meta: release:Code-Review+2: Thierry Carrez <thierry@openstack.org>
Change-Id: I6f8cfd01ac9d224e3b83afbfc69b45e1493e98ee
* Update openstacksdk from branch 'master'
to 9137a8c41760d1dc62950219f6138fd183c0dc96
- Merge "[baremetal] Add some missing fields to node object"
- [baremetal] Add some missing fields to node object
Adds the lessee, and description fields to the
node object, and adds basic testing to the conductor_group object
to just ensure it is populated when available.
Also, adds a test entry for is_automated_clean_enabled, as the value's
population was previously not set.
Change-Id: Ia1d9232400b679b82f1dfbeef55db3f9a4116862
* Update ironic-lib from branch 'master'
to 87a739fe178c241d640238c9d162036c02ab2a31
- Raise on non-existing file in qemu_img_info
I'm not sure why we silence the exception, right now it causes us a very
hard to debug failure. No code in Ironic seems to rely on this behavior.
Change-Id: I3740b600c60ed1b39808d18af2b5074e7e07a149
* Update ironic from branch 'master'
to e1a8e4ba6cbf36071091860b39b906d100b8385f
- Merge "Revert "Revert "RBAC: Fix allocation check"" to use Unauthorized"
- Revert "Revert "RBAC: Fix allocation check"" to use Unauthorized
In the backports to fix the policy of the original change, Dmitry
noted that it was actually wrong, because we should have instead
raised NotAuthorized. Dmitry was absolutely correct, because in hind
sight I made the change trying to keep exactly the same behavior,
but the reality is this is a case where we should be explicit,
and tell the user they have done something forbidden.
This revert of the revert fixes that change.
Original Change: https://review.opendev.org/c/openstack/ironic/+/905038
Dmitry's Review Feedback: https://review.opendev.org/c/openstack/ironic/+/905088
Change-Id: I5727df00b8c4ae9495ed14b5cea1c0734b5f688d
* Update oslo.messaging from branch 'master'
to 800c58826ebc0effe00664f68aa5fe929899a971
- Utilize the new RequestContext redacted_copy method
We now expect context objects to support returning a redacted copy of
themselves.
As a related cleanup, removed the practice entirely of using
dictionaries to represent contexts in unit tests and the logging driver.
As part of developing this change, I discovered code in Glance (and
potentially other services) which explicitly pass {} in lieu of a
context when notifying; so we now properly handle dictionaries as
contexts.
To ensure we have the method required; require oslo.context 5.3.0 or
newer.
Change-Id: I894f38cc83c98d3e8d48b59864c0c7c2d27e7dcd
* Update releases from branch 'master'
to 2123c359b731a751403baa8f56ca0f3c868637c8
- Merge "[neutron] Transition Ussuri to End of Life"
- [neutron] Transition Ussuri to End of Life
With the new resolution '2023-07-24 Unmaintained status replaces
Extended Maintenance' [1] the last 3 EM branches (Xena, Wallaby,
Victoria) will transition to Unmaintained, but older branches (Ussuri,
Train) should move to End of Life unless someone steps up as maintainer
of this branch for this project.
To signal this, please add a -1 for this patch if you or the team want
to keep this branch open for further maintenance.
If there is no response from anyone within a reasonable time frame,
then PTLs/release liaisons will be asked to confirm the EOL transition
with their +1.
[1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
Change-Id: I3f6bf9e50e6eba8ab6fc0bb1e466468d6925c776
* Update neutron from branch 'master'
to b5f5f3def3cec69558f7eb6edb04b95ede34b0d3
- ovn-l3 scheduler: calculate load of chassis per priority
previously we calculated the "load" of a chassis across the highest
priority of each of the chassis. This can lead to suboptimal results in
the following situation:
* you have gateway chassis: hv1, hv2, hv3
* you have routers:
* g1: with priority 3 on hv1, priority 2 on hv2, priority 1 on hv3
* g2: with priority 3 on hv1, priority 2 on hv2, priority 1 on hv3
* g3: with priority 3 on hv3, priority 2 on hv2, priority 1 on hv1
* g4: with priority 3 on hv3, priority 2 on hv2, priority 1 on hv1
When now creating a new router the previous algorythm would have placed
prio 3 of it either on hv1 or hv3 since their count of highest
priorities (2 of prio 3) is lower than the count of the higest priority
of hv2 (4 of prio 2). So it might have looked like:
* g5: with priority 3 on hv3, priority 2 on hv1, priority 1 on hv3
(This case has been implemented as `test_least_loaded_chassis_per_priority2`).
However this is actually a undesired result. In OVN the gateway chassis
with the highest priority actually hosts the router and processes all of
its external traffic. This means it is highly important that the highest
priority is well balanced.
To do this now we no longer blindly use the count of routers of the
highest priority per chassis, but we only count the routers of the
priority we are currently searching a chassis for. This ensures that in
the above case we would have picked hv2 for priority 3, since it has not
actually active router running.
The algorithm implemented now is based upon the assumption, that amount
of priorities scheduled per router is equal over all routers. This means
it will perform suboptimally if some phyiscal network is available on 5
gateway chassis, while another one is only available on 2. (It is
however unclear if the previous implementation would have been better
there).
In this commit we also adopt the testcases in test_l3_ovn_scheduler to match
to this assumption. Previously the distribution data used for testing
had been unrelasitic as it mostly scheduled one gateway chassis for each
router.
It also fixes the previously broken priority calculation in the
testcase, that would just assign prio 0 to all gateways.
Partial-Bug: #2023993
Change-Id: If2afcd546a1da9964704bcebbfa39d8348e14fe8
* Update neutron from branch 'master'
to 3d5d82a197f985ad9e08fd31a7d7548b875386c0
- ovn-l3: reschedule lower priorities
if a gateway chassis is removed we previously only plugged the hole it
left in the priorities of the lrps. This can lead to bad choice since we
are bound by all other currently used chassis.
By allowing us to also reschedule the lower priorities we get
significantly more freedom in choosing the most appropriate chassis and
prevent overloading an individual one.
As an example from the new testcase:
previously we would have had all prio 2 schedules on chassis3, but with
this change now this distributes better also to chassis4.
Partial-Bug: #2023993
Change-Id: I786ff6c0c4d3403b79819df95f9b1d6ac5e8675f
* Update glance from branch 'master'
to 5378396b84755dedbba2a34d2e9c93add8c27176
- Fix test failures with oslo.limit 2.3.0
The oslo.limit 2.3.0 release contains the validation to ensure
the [oslo_limit] endpoint_id option is set[1]. This fixes the test
failures caused by that validation by overriding the option in all
test cases where unified quota implementation is used.
[1] https://review.opendev.org/c/openstack/oslo.limit/+/897509
Closes-Bug: #2049064
Change-Id: I704393892799ee0d5edf45fabe07afe01473e38d
* Update releases from branch 'master'
to 680a914b47dd2c06cbf5a5f60af0c42197cc1ce2
- Merge "Caracal-2 release for oslo.utils"
- Caracal-2 release for oslo.utils
This is the Caracal-2 milestone release for oslo.utils.
Clients and libraries following the cycle-with-intermediary release
model are encouraged to release each milestone to make sure updates
are made available.
If the team is happy with the current release hash, please +1 this
patch and we will process the release. If you need to get some
important changes merged first, leave a -1 and update the patch with
a new commit hash to use once it is ready.
If a release is definitely not wanted at this time, please -1 and
leave a comment explaining that and we can abandon the patch.
Any patches with no response will be assumed to be OK and will be
processed after January 11th.
Change-Id: Iccc767cee67fdf090c060ab7c9bd68942ecc5bc1
Signed-off-by: Elod Illes <elod.illes@est.tech>
* Update neutron-lib from branch 'master'
to c69701eb73fa478dc96449230353dfa6172e9d5d
- Bump hacking
hacking 3.0.x is really old. Let's bump it to the latest version
available.
This also fixes some errors detected but some rules are excluded now.
See the comments in tox.ini for further details.
Change-Id: I2565e5f5e791dfdd9bbc1890b35c413965d83626
* Update puppet-glance from branch 'master'
to 23d579d51549c8e98e2be20c036fad3021c294c3
- Merge "healthcheck: Expose allowed_source_ranges"
- healthcheck: Expose allowed_source_ranges
... which was added to puppet-oslo recently.
Depends-on: https://review.opendev.org/905557
Change-Id: I1c02af63f31696be7cd9fbd859c81f9f0a919416
* Update releases from branch 'master'
to 15475955c499dac87c8ca2cc738b31c95c01affd
- Merge "Add EOM tag option to new-release command"
- Add EOM tag option to new-release command
With the new TC resolution the community replaces Extended Maintenance
with Unmaintained status [1].
This patch introduces the new <series>-eom tag option for the
new-release command. The tag applies at the tip of the given
stable/<series> branch and the new unmaintained/<series> branch can be
cut from that tag.
[1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
Change-Id: Ie67da6f4857f0d438733799bf40f8ece66f67d32
* Update releases from branch 'master'
to 2d469290db1c3462d15eefb5f3fbd1bce0a49e92
- Merge "Add EOM tag option to transition_series.sh"
- Add EOM tag option to transition_series.sh
With the new TC resolution the community replaces Extended Maintenance
with Unmaintained status [1].
This patch introduces the new <series>-eom tag option in the
transition_series.sh script. The tag applies at the tip of the given
stable/<series> branch and the new unmaintained/<series> branch can be
cut from that tag.
[1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
Change-Id: Ia7064e36a2d92ef02f60b7371ebf3e4772abcc80
* Update releases from branch 'master'
to 3bdb2416d777cf4847835d870b5a44b416f7d751
- Merge "Test EOM tag on release-test repository"
- Test EOM tag on release-test repository
Change-Id: Ic04601797ce13507fd174f73898b7e5513701fe7
* Update puppet-cinder from branch 'master'
to 3103c6c52d9015b372e9c05d780e40ac02954f2b
- Merge "healthcheck: Expose allowed_source_ranges"
- healthcheck: Expose allowed_source_ranges
... which was added to puppet-oslo recently.
Depends-on: https://review.opendev.org/905557
Change-Id: I70429bf90889b3dd8ecf88a140539b073e35e6a9
* Update networking-generic-switch from branch 'master'
to 0af727bee327d9f91990d454b2a28f750047dc04
- bump eventlet to latest version that support python 3.12
Change-Id: I498c0000e321ffd0fd054ffbfa6a5ad15509f8ee
* Update releases from branch 'master'
to 51e8036b952659106421bceddfaaa62c492e27d8
- Merge "Test unmaintained branch cut from eom tag"
- Test unmaintained branch cut from eom tag
Change-Id: I7e4b401c33248887538431532cfb6f41d07fae74
* Update neutron-vpnaas from branch 'master'
to 87859a399765ce3dcf3f9a64775636fa45acaba5
- Update python classifier with py3.10 & py3.11 in setup.cfg
Change-Id: I6a1435c3d2660a6f008cee6f62f641abab0a7ec2
* Update senlin from branch 'master'
to c2d0b6584dbbbf879dd4ca1d9a5c787914ab6b93
- bump eventlet to latest version that support python 3.12
Change-Id: I4d9d5db934739213f07aadedfb590630913640ed
* Update python-openstackclient from branch 'master'
to 37b420142852c3875097859c47ceba7c5e4cc0b6
- Update python classifier in setup.cfg
As per the current release tested runtime, we test
python version from 3.8 to 3.11 so updating the
same in python classifier in setup.cfg
Change-Id: Ic137b2eecee65d43afeca2c936e195a8652237af
* Update neutron from branch 'master'
to e6a7cc26a0c8d8ae43dd825d713bf13283914943
- Merge "[OVN] Update lsp host id when virtual parent moves"
- [OVN] Update lsp host id when virtual parent moves
When a virtual port is moved from one port to another port the
PortBindingUpdateVirtualPortsEvent event would only update the binding
host id in the neutron database, while it is also usefull to keep the
information in the OVN database up to date with the host information
Other plugins that connect to the OVN database can then also rely on the
information stored in the OVN DB's
Closes-Bug: #2038413
Change-Id: I59c6c4b2c8b023b9c9c3bab1741d957fa1f738fc
* Update mistral from branch 'master'
to e0628604428d84bdeaaf76049cfd65f6e976a32b
- bump eventlet to latest version that support python 3.12
Change-Id: Ie5bed1492de2200d7df35e0ae320a081d897cdae
* Update neutron from branch 'master'
to 52781954c2f36088c133188fecc4c66e4b299fd6
- Merge "Make get_ports RPC method common for the DHCP and Metadata agent"
- Make get_ports RPC method common for the DHCP and Metadata agent
This patch is the initial implementation on the suggestion
from this patch[1].
The DHCP agent can query the existing `get_ports` RPC method because
this method is already exposed in the MetadataRpcCallback(server side)
which runs under the same topic(PLUGIN) and namespace(None). The benefit
here is that there is no change needed to the API, however it does
go against how we historically setup the RPC layer between a server and client.
[1] https://review.opendev.org/c/openstack/neutron/+/903572/comments/3d4e0453_4b4d2ab6
Related-Bug: #1982569
Change-Id: Icd7c55d2a5103bdbd90907b1dbfb9ccfe34c020a
* Update networking-generic-switch from branch 'master'
to a387971ef0a87ee83f60e9e51c3c59571689f7a1
- Revert "bump eventlet to latest version that support python 3.12"
This reverts commit 0af727bee327d9f91990d454b2a28f750047dc04.
Reason for revert: Seems like this is going to be rolled back. It definitely doesn't pass on downstreams.
Change-Id: Ia2938f6440ea33670a942e0a275c8471326ef800
* Update ironic from branch 'master'
to ebd8381dbf66ba85c23d10fffacd8f3f86cab556
- Corrected IP_ADDRESS to IP_VERSION
Validated IP_VERSION is the correct key for devstack.
Change-Id: Id73a6c1b41cb86dab37fe650bf7bdae60d697bf6
* Update devstack from branch 'master'
to 6091df25a39c9b17883d86ccb091bf2b9c39aa15
- [OVN] Add support for the Neutron OVN agent service
The Neutron OVN agent is a service that could run in any node. The
functionality will depend on the extensions configured. This new
agent is meant to be the replacement for the Neutron OVN metadata
agent once the "metadata" extension is implemented in this service
[1].
[1]https://review.opendev.org/c/openstack/neutron/+/898238
Related-Bug: #2017871
Change-Id: I8f82f0047e89aac122a67f59db84f03e1a6bf519
* Update glance from branch 'master'
to f429b53e0474553992f43c7045498156ee36d5cb
- Merge "Update python classifier in setup.cfg"
- Update python classifier in setup.cfg
As per the current release tested runtime, we test
till python 3.11 so updating the same in python
classifier in setup.cfg
Change-Id: I703ff8cdebd2e929ab775f9b601a8542fb413153
* Update neutron from branch 'master'
to 5ce17647c60448c9cae00ffc886d4e17a9fe0890
- Merge "Router flavors and service type for OVN"
- Router flavors and service type for OVN
Support is added to the OVN L3 service plugin for the router
flavors and service type framework
Partial-Bug: #2020823
Change-Id: If40d7b39e7b59a39ff7622bd823dbdb14bfc69d2
* Update swift-bench from branch 'master'
to e8eb9511d285f0ed04a1bce239ee8c9411036565
- Catch connection errors and count them as failures
Previously we'd get tracebacks like this during a proxy reload:
Traceback (most recent call last):
File ".../urllib3/connectionpool.py", line 791, in urlopen
response = self._make_request(
File ".../urllib3/connectionpool.py", line 537, in _make_request
response = conn.getresponse()
File ".../urllib3/connection.py", line 461, in getresponse
httplib_response = super().getresponse()
File ".../http/client.py", line 1375, in getresponse
response.begin()
File ".../http/client.py", line 318, in begin
version, status, reason = self._read_status()
File ".../http/client.py", line 287, in _read_status
raise RemoteDisconnected("Remote end closed connection without"
http.client.RemoteDisconnected: Remote end closed connection without response
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File ".../requests/adapters.py", line 486, in send
resp = conn.urlopen(
File ".../urllib3/connectionpool.py", line 845, in urlopen
retries = retries.increment(
File ".../urllib3/util/retry.py", line 470, in increment
raise reraise(type(error), error, _stacktrace)
File ".../urllib3/util/util.py", line 38, in reraise
raise value.with_traceback(tb)
File ".../urllib3/connectionpool.py", line 791, in urlopen
response = self._make_request(
File ".../urllib3/connectionpool.py", line 537, in _make_request
response = conn.getresponse()
File ".../urllib3/connection.py", line 461, in getresponse
httplib_response = super().getresponse()
File ".../http/client.py", line 1375, in getresponse
response.begin()
File ".../http/client.py", line 318, in begin
version, status, reason = self._read_status()
File ".../http/client.py", line 287, in _read_status
raise RemoteDisconnected("Remote end closed connection without"
urllib3.exceptions.ProtocolError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File ".../eventlet/greenpool.py", line 88, in _spawn_n_impl
func(*args, **kwargs)
File ".../swiftbench/bench.py", line 477, in _run
client.get_object(self.url, self.token,
File ".../swiftclient/client.py", line 1252, in get_object
conn.request(method, path, '', headers)
File ".../swiftclient/client.py", line 416, in request
self.resp = self._request(method, url, headers=headers, data=data,
File ".../swiftclient/client.py", line 400, in _request
return self.request_session.request(*arg, **kwarg)
File ".../requests/sessions.py", line 589, in request
resp = self.send(prep, **send_kwargs)
File ".../requests/sessions.py", line 703, in send
r = adapter.send(request, **kwargs)
File ".../requests/adapters.py", line 501, in send
raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
Change-Id: Idd1a83afd2c4dbf7305c19d3ec3974961e500620
* Update puppet-manila from branch 'master'
to 63d7b6e8c43ca5a3757cddb376ae50ac4fff1dba
- healthcheck: Expose allowed_source_ranges
... which was added to puppet-oslo recently.
Depends-on: https://review.opendev.org/905557
Change-Id: Ide8acee8656c5d19c9deeb7ee7053f9b3a8cf6c5
* Update requirements from branch 'master'
to 1f793ce34dbfec164152157809bdad718eb3a611
- update constraint for oslo.utils to new release 7.0.0
meta: version: 7.0.0
meta: diff-start: -
meta: series: caracal
meta: branch: master
meta: release-type: release
meta: pypi: yes
meta: first: no
meta: release:Author: Elod Illes <elod.illes@est.tech>
meta: release:Commit: Elod Illes <elod.illes@est.tech>
meta: release:Change-Id: Iccc767cee67fdf090c060ab7c9bd68942ecc5bc1
meta: release:Code-Review+2: Elod Illes <elod.illes@est.tech>
meta: release:Workflow+1: Elod Illes <elod.illes@est.tech>
meta: release:Code-Review+2: Hervé Beraud <herveberaud.pro@gmail.com>
Change-Id: I9b94592f88f90b0598915b721a3f96a55e528f19
* Update openstack-helm-infra from branch 'master'
to d0c93b5648704b9d9999412d932f8329c80362c0
- Merge "Change default ingress path type to prefix"
- Change default ingress path type to prefix
Due to CVE-2022-4886 the default pathType for an ingress should be
either "Exact" or "Prefix". This allows for more strict path validation by
the admission controller. This PS changes the default pathType to Prefix.
This value can be overridden.
In a separate PS I will add the pathType parameter to the ingressOpts
for all helm charts that create an ingress.
See:
https://github.com/kubernetes/ingress-nginx/issues/10570
Change-Id: I8f1df594f0c86f2de6cdd7cf2ee56637bd508565
* Update requirements from branch 'master'
to da82fe614247dcab41ba2b8bf7f544404b1e7580
- Merge "move mistral to nonvoting for eventlet revert"
- move mistral to nonvoting for eventlet revert
Change-Id: Id21d685894a9ae0d88c6005cc554b2f9c5366310
* Update senlin from branch 'master'
to cb8b8f7676df8481e4b5915e682adca798ebd1a1
- Revert "bump eventlet to latest version that support python 3.12"
This reverts commit c2d0b6584dbbbf879dd4ca1d9a5c787914ab6b93.
Reason for revert: This is too aggressive and needs wider community consultation. The constraints change is being reverted.
Please revert ASAP.
Change-Id: I74bc67eb66f19e1eb2ac9d328eefafb7289fc1e7
* Update requirements from branch 'master'
to ba515b84bdfcf240ec69d2a5b4b1c9aa2f895d6a
- Revert "Update eventlet to 0.34.3"
This reverts commit 3728e28a91f25f7c1023c07f563dc0e0ce688312.
Reason for revert: This is breaking somw swift and manila jobs, will
need further work and likely another eventlet release
The following changes should be merged first but given timing is
critical I'll just annotate them:
* https://review.opendev.org/c/openstack/mistral/+/905907
Not essential because of:
- https://review.opendev.org/c/openstack/requirements/+/906008
* https://review.opendev.org/c/openstack/networking-generic-switch/+/905904
Actually merged
* https://review.opendev.org/c/openstack/senlin/+/905908
Approved and in gate pipeline
Change-Id: I062be5c503775d138eb65989c2c9788e58ed0e95
* Update requirements from branch 'master'
to b353fd308448e510faaca9a068d22b51858d68a4
- Move mypy to blacklist
mypy is a linter, not something that is used at runtime. Move it to the
blacklist.
This also reverts commit 2bbbdb9991b69052c80d83be7ec21985eb01bafd as a
cross-project job no longer makes sense with the newly blacklisted
dependency.
Change-Id: Iaf6d2c4aed92f35240b393939bbf76fd7d5d9aa2
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Update requirements from branch 'master'
to 8d67991af046bb5a5c5a172440588f4b0bcf6249
- update constraint for python-tackerclient to new release 2.0.0
meta: version: 2.0.0
meta: diff-start: -
meta: series: caracal
meta: branch: master
meta: release-type: release
meta: pypi: yes
meta: first: yes
meta: release:Author: Elod Illes <elod.illes@est.tech>
meta: release:Commit: Elod Illes <elod.illes@est.tech>
meta: release:Change-Id: I05ab405e457c0f35bd5ac66a227348333da189a2
meta: release:Code-Review+1: Yasufumi Ogawa <yasufum.o@gmail.com>
meta: release:Code-Review+2: Hervé Beraud <herveberaud.pro@gmail.com>
meta: release:Code-Review+2: Elod Illes <elod.illes@est.tech>
meta: release:Workflow+1: Elod Illes <elod.illes@est.tech>
Change-Id: Ifaec6f13a15ae0a6c78816a545e2a5062bb7d3ab
* Update swift from branch 'master'
to 7e3925aa9c004a0add738f2ed14c466c92a3f88d
- tests: Fix probe test when encryption is enabled
Change-Id: I94e8cfd154aa058d91255efc87776224a919f572
* Update senlin from branch 'master'
to 032eea8fda719df9f86e9295cc265d9c37c2b78d
- Merge "Fix: `TrustMiddleware` unable to fetch trusts/credentials from identity service"
- Fix: `TrustMiddleware` unable to fetch trusts/credentials from identity service
When using token to init a new openstacksdk connection, the SDK try to fetch
another token from it, causing keystone raise exception and return 500 status
response. Refer: https://bugs.launchpad.net/keystone/+bug/1959674
Switch from `token` to `admin_token` to make the SDK session use the provided
token directly instead of fetching a new one.
Closes-bug: #2048452
Depends-On: https://review.opendev.org/c/openstack/senlin/+/905555
Change-Id: I8f9b2db3d4851cf54c2113b2fb0ae97ae38ac286
* Update senlin from branch 'master'
to 7fa6ae780cb7e9c72a2df1ef0c11d543cd1ffca0
- Merge "Removing CLUSTER_RESIZE from pre-op skip List at min threshold"
- Removing CLUSTER_RESIZE from pre-op skip List at min threshold
Excluding CLUSTER_RESIZE from the list of actions that skip
pre-operation checks if the cluster is already at the minimum threshold.
When the cluster is at the minimum threshold, pre-op LB will function
with actions such as CLUSTER_DEL_NODES, CLUSTER_SCALE_IN, NODE_DELETE,
and will skip actions like CLUSTER_REPLACE_NODES and CLUSTER_RESIZE.
Closes-Bug: #2049191
Change-Id: I00a7ea40f69bafc94ca2bba9f268af7b03344997
* Update cinder from branch 'master'
to 2d6f89c7a255aac9664204f7faa2e853d4c2b90a
- Merge "HPE 3par - Add ipv6 support"
- HPE 3par - Add ipv6 support
This patch adds ipv6 support to the iscsi driver.
Closes-Bug: #2045411
Change-Id: I8a65c2c3f3017e041f6b3be629ce54c27566cf6b
* Update swift from branch 'master'
to 569525a93724ae3d47ccca847104cc6f4e452d94
- Merge "tests: Get test_handoff_non_durable passing with encryption enabled"
- tests: Get test_handoff_non_durable passing with encryption enabled
Can't make assertions on object-meta values when we're making direct
requests; those have all been shifted to transient sysmeta. Use
Content-Type instead, since we don't encrypt it.
Change-Id: If2bb773cf428dfa3c23c634b3c046ba282053c02
* Update nova from branch 'master'
to fd1ec1b913ef93fb24e3a72b500b986e199405ce
- Merge "Fix test failures with oslo.limit 2.3.0"
- Fix test failures with oslo.limit 2.3.0
The oslo.limit 2.3.0 release contains the validation to ensure
the [oslo_limit] endpoint_id option is set[1]. This fixes the test
failures caused by that validation by overriding the option in all
test cases where unified quota implementation is used.
[1] https://review.opendev.org/c/openstack/oslo.limit/+/897509
Closes-Bug: #2049064
Change-Id: Iffc7a66033a9c09e850890bb380b6667412f0d98
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
13 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )