* Update kayobe from branch 'master'
to e8adce409395a05a07f78670e49363949c25f05d
- Merge "Fix container image build issues with letsencrypt"
- Fix container image build issues with letsencrypt
The kolla_enable_letsencrypt variable was undefined, which was causing
overcloud container image build to fail when the variable was not
defined in Kayobe configuration.
The bool filter was missing for kolla_enable_letsencrypt, which was
causing letsencrypt images to be built when kolla_enable_letsencrypt was
set to "false" or "no".
Change-Id: I234b7a0434ba3d533a66b766331fd489078fbcf8
* Update telemetry-tempest-plugin from branch 'master'
to 68adef732be33219cd3cf2da66117f393c22add6
- Drop devstack-gate
This completely broke telemetry gating.
Change-Id: Ia9a1d5c72bdc437104ec519961c8626669bca075
* Update rpm-packaging from branch 'master'
to 5a88e4ccd23adba8303f9ec9529b1570ed6b2c28
- Update to latest versions
Change-Id: If58fab9226d0297dc6f4783ccfb1b84d6b52e50e
* Update monasca-notification from branch 'master'
to 841dcc0fb120e13198ca594c7f768d5b5fe6bba1
- fix orm to compatible with sqlalchemy 2
Change-Id: Ia462750553e3f0ab1a33d439508c4a08c3e71778
* Update monasca-api from branch 'master'
to c36c2c69a4227e0c1da04f3044bfa4b059a55781
- Merge "Remove redundant or removed setuptools option"
- Remove redundant or removed setuptools option
tag_svn_revision was removed some time ago[1]. Also definition of
the other two options is equivalent to using defaults.
[1] https://github.com/pypa/setuptools/issues/619
Change-Id: I27da77ad475704e91c27dd4f9fc1ae579823c485
* Update neutron from branch 'master'
to bee9bde18219a7a90fdbf9e3e85c0ff49c8e85d6
- Merge "Add a default goto table=94 for openvswitch fw"
- Add a default goto table=94 for openvswitch fw
If enable explicitly_egress_direct=True and set port as
no security group and port_security=False, the ingress
flood will reappear. The pipleline is:
Ingress
table_0 -> table_60 -> NORMAL -> VM
Egress
table_0 -> ... -> table_94 -> output
Because ingress final action is normal, the br-int will learn the
source MAC, but egress final action is output. So VM's mac will
never be learnt by the br-int. Then ingress flood comes again.
This patch adds a default direct flow to table 94 during the
openflow security group init and explicitly_egress_direct=True, then
the pipleline will be:
Ingress
table_0 -> table_60 -> table_94 -> output VM
Egress
table_0 -> ... -> table_94 -> output
And this patch adds the flows coming from patch port which will
match local vlan then go to table 94 do the same direct actions.
Above flood issue will be addressed by these flows.
Closes-Bug: #2051351
Change-Id: Ia61784174ee610b338f26660b2954330abc131a1
* Update charm-ceph-mon from branch 'master'
to 8d9304aeed279370d782c2daaa2fe3a6fab1c4fc
- Update for Ceph Squid
Change default origin to caracal to pick Squid packages.
Add noble bundle, remove old focal bundles and update associated
test configuration files.
Change-Id: I3f09703a25b364f974b5fc10c61662d4a5c0af56
* Update ironic from branch 'master'
to 8bdf1fca9122095ea3c72ba6ee400b32901a8134
- Merge "docs: augment security docs"
- docs: augment security docs
A quick review of the security documentation yielded a need
to revise and clarify the security documentation a little,
which includes a couple security related features.
And also fix the syntax on the example policy entries while
adding a missing third, ! results in a "default false" response.
Change-Id: I3d10ca4631703051109c443d5591a7e86f858c66
* Update kayobe from branch 'master'
to afa0b75cf543ad67bca88cf64a8de8cbfcf4952c
- Merge "Remove use of get_md5 when using stat module"
- Remove use of get_md5 when using stat module
This was missed from I2ea9b2ec58913722c4defffbeee88cc420dcbdab.
Change-Id: I84971f8daa4caf2227863810c7b12e59192c2515
* Update monasca-api from branch 'master'
to 908815723b8bed0d7a7c2e57411c34377512dfb6
- change cassandra repo and fix sqlalchemy 2
- change list colum to single colum of select command
- optimize concat test case
- change row mapping to dict method
- remove sysbase testcase because of removing from sqlalchemy
- use jammy in vagrant for dev env
- remove retired project in zuul
- add not found test for notification with find by name
Change-Id: Ie77ccf6b15593520ae4f486843cdc46d7e25c628
* Update openstack-ansible from branch 'master'
to 9057332db0ee889937e390a977535b04127fb55c
- Merge "Update deploy guide title"
- Update deploy guide title
Having `OpenStack-Ansible Documentation` for the deploy guide is
confusing and it's worth to have a proper name for the deploy Guide.
Change-Id: I7744ed1046f860566c438b7f0c3719b3b736e13b
* Update openstack-ansible from branch 'master'
to 194af2ca786935b72bccaa4c251918b949b795d7
- Merge "Build PDF for deployment guides"
- Build PDF for deployment guides
Change-Id: I5a566942de5ce0ddc6d2d240c44e9781ddb23372
* Update neutron-tempest-plugin from branch 'master'
to c76727b97c04016ee0d65d8d11623adbd8d60c69
- Use RE2 compatible regex for irrelevant-files
Zuul has deprecated the usage of negative regex[1] and
reports WARNINGs when these are used.
This patch switches the branches regex to the supported
one.
[1] https://review.opendev.org/c/zuul/zuul/+/916141
Change-Id: I3cae6a14044010ee16f328036278a0542a03a701
* Update neutron from branch 'master'
to 42ea2b28e190949da0184c5f098cd8dd16347521
- Merge "Use RE2 compatible regex for irrelevant-files"
- Use RE2 compatible regex for irrelevant-files
Zuul has deprecated the usage of negative regex[1] and
reports WARNINGs when these are used.
This patch switches the branches regex to the supported
one.
[1] https://review.opendev.org/c/zuul/zuul/+/916141
Change-Id: I56a286cf33afb574436039128095e260539f63d9
* Update manila-tempest-plugin from branch 'master'
to 26fe97cd3b80c55bb5581ad0c5f36ac941b26388
- Use devstack's OSCaaS in test jobs
I28e6159944746abe2d320369249b87f1c4b9e24e introduced
OSCaaS and enabling it offers a good amount of speedup
in our test jobs. So lets enable it in the base jobs.
Change-Id: I4a1c8d75faa8151fb94cd227e24967a06d02ff4b
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
* Update puppet-openstack-integration from branch 'master'
to 51dcea308556358c071777f549735ae434bb90d2
- Merge "aio: Enable nova-cinder integration"
- aio: Enable nova-cinder integration
AIO has both nova and cinder enabled, so we can enable the integration
between these services.
Change-Id: Id4dca3ac05ca2f69bb6da48ab8ef224af09c1502
* Update puppet-nova from branch 'master'
to 08312cd7f390d1d4919893b9ff324162c01061c3
- Merge "Refactor unit tests for nova::compute::libvirt::services"
- Refactor unit tests for nova::compute::libvirt::services
... and improve the test coverage.
Change-Id: I4fa79abd5868bb380d9ed2bf322ca27738c86e02
* Update puppet-nova from branch 'master'
to 35006301fb3516c9355f1a97add44276e8743464
- Merge "CentOS: Install libvirt-daemon only when needed"
- CentOS: Install libvirt-daemon only when needed
When libvirt service name is false then the core libvirt package is not
managed. So the libvir-daemon package should be also unmanaged.
Change-Id: I89ca6864ae476f5081fca65512caafae7642802e
* Update openstack-helm-images from branch 'master'
to 59de48379bd7162338d5e94ab3ee794424ad3a32
- [elasticsearch-s3] Prepare recipes for v7/v8
Create common Dockerfiles for the latest major ES versions
Change-Id: I5b1232e41e6713cdf89b832262ec5a703cfaf81d
* Update puppet-openstack-integration from branch 'master'
to 97c38a3801ffee1cbde9981388656d45fcbdc5c1
- Merge "CentOS: Use built-in resource to enable crb"
- CentOS: Use built-in resource to enable crb
Change-Id: I97911c6d287379d1c4ff1ea33626fc1a0099bf25
* Update puppet-nova from branch 'master'
to 39bc5b435b0b2c1f5cd67ed881463edd87687b52
- Refactor unit tests of nova::compute::libvirt
Create a common shared example so that all options are tested for
RHEL/CentOS.
Change-Id: I208534f8d00a643522b553924c99e1d3e794aac8
* Update puppet-nova from branch 'master'
to 85f09f284c3ab75d06087a996dbb4cc7871113a9
- Avoid testing details of included class
Avoid testing details of nova::compute::libvirt::services in the unit
tests for nova::compute::libvirt, so that we don't have to maintain
test implementations about the same resources in two places.
Change-Id: I2702ce1ac20e68a933a10a5b9066661d96f56fe7
* Update puppet-nova from branch 'master'
to 7617973329a50b22e5a67b2e51fd7810b267c0f8
- CentOS: Drop unused libvirt-daemon-config-nwfilter
The package is no longer used by nova, since the firewall feature was
removed from nova during ussuri cycle[1].
[1] 9b321e41f60be5d4111c8312b40c826454386c53
Closes-Bug: #2067867
Change-Id: I9fb3193d10b8c23dcf7eb1d4549ee04776d9959d
* Update ironic from branch 'master'
to b64a8ff6ef74a7b26580d7af44c3376600daf17b
- Follow-up: minor wording change from 920706
Just changing "deployment or cleaning operations" to
"inband operations", since the agent can run in many
different inband operational steps.
Change-Id: Iaaa03ebc3dab724eb7afb0ee686bd22c8a2879be
* Update manila from branch 'master'
to 76d032969848fa409f3b7da499cc2da3de67f6be
- Fix leak of ports on share server deletion
- Manila share server deletion happens asynchronously. If deletion of
share server fails in between, share server network ports remained as
it is. So we should better delete share network ports first and then
continue share server deletion.
- It may be possible, that there are ports existing without a
corresponding manila network allocation entry in the manila db, because
port create request may have been successfully sent to neutron, but not
stored in db. So query(and delete) those from neutron after db entries
are deleted.
Closes-bug: #2067266
Change-Id: Id86dade1194494e599aea9adad06e4ca6cb119b6
* Update neutron-lib from branch 'master'
to 61302221f03905052ec9599c7ceb1c31fc635019
- typos: suport -> support; suports -> subports
Found by command: openstack extension list --network
Change-Id: I51fb7b59097094e6762ce2b0a31fece693d3f0aa
* Update openstack-ansible-os_cloudkitty from branch 'master'
to a213aaa40517f59bf100ca0f95f36018a907a953
- Merge "Define region and interface for collector/fetcher"
- Define region and interface for collector/fetcher
It appears, that produced gnocchiclient does not respect region_name
from the auth_section, thus it needs to be defined directly for the
fetcher.
We align collector for now with fetcher, to make change backportable.
Closes-Bug: #2067084
Change-Id: If3a37b6190449e18446e65ce3b8cb70cd9038c37
* Update kayobe from branch 'master'
to 3b0a74dfc46392c1611b060c3048e3d990476548
- CI: Fix kayobe-tox-molecule job
We were still using stream8 images which cannot install packages
anymore, due to the end of life of CentOS Stream 8.
Change-Id: I8604c342e4dbc41dd5bee0f28a92c3c3cd37d631
* Update octavia from branch 'master'
to 541682314693ab543b148a9ed7703192f1673e00
- Merge "String conversion to f-strings"
- String conversion to f-strings
Ran `flynt octavia` in order to replace old style string format with
f-strings.
Manually corrected lines that got too long and some occurences that were
not converted to f-strings.
Change-Id: I228a78baf2f4b6c47229d7dce1fcd81ef27c0030
* Update charm-vault from branch 'master'
to 99db369a33f5988471eeb007bf78b353035aa02a
- Remove lunar/23.04 as a target release
lunar/23.04 is no longer supported. charmcraft builds fail because charmcraft cannot retrieve lunar/23.04 images.
Closes-Bug: 2064518
Change-Id: I2da60799ccf004477dc8d0b6b380d3ce6dc38c40
* Update releases from branch 'master'
to 72922bc6b58b2e136da03234904febe42baad495
- Merge "Create new heat release for Caracal"
- Create new heat release for Caracal
We recently merged a few bug fixes in 2024.1 . Create a new release so
that these fixes are consumable more easily.
Change-Id: Ie27c6fffbfa40a8aba1fdb6f8c52b9ae017efd17
* Update tempest from branch 'master'
to 89a6811cd060bdec92f5efa1e53fd90b3961982a
- Bump http_timeout in devstack-tempest
In the gate we occasionally see failures like the following:
urllib3.exceptions.ReadTimeoutError:
HTTPSConnectionPool(host='10.209.0.62', port=443):
Read timed out. (read timeout=60)
urllib3.exceptions.ReadTimeoutError:
HTTPSConnectionPool(host='10.209.99.246', port=9696):
Read timed out. (read timeout=60)
where Tempest gives up waiting for an HTTP response after 60 seconds.
It doesn't appear to be related only to one service, as it has been
seen when calling Nova API or Neutron API (the port=9696 example is a
call to Neutron API).
We could try bumping the http_timeout from the default 60 seconds to 90
seconds to see if it helps in slow environments.
Related-Bug: #1999893
Change-Id: I2b2a6a4dee40ee86ca89f6f7f9a83409f8312617
* Update neutron from branch 'master'
to 9b89f518521c7d903608b7bc1083abfff09c4c17
- Merge "Bump neutron-lib to 3.12.0"
- Bump neutron-lib to 3.12.0
At a minimum this should fix the undefined rule check seen
running the pep8 job, something like this:
.../neutron/.tox/pep8/lib/python3.10/site-packages/neutron_lib/
db/model_base.py:119: MovedIn20Warning: Deprecated API features
detected! These feature(s) are not compatible with SQLAlchemy 2.0.
Depends-on: https://review.opendev.org/c/openstack/requirements/+/919836
Change-Id: I637c377ab639ff49a75fbf4b926464464d888c44
* Update kayobe from branch 'master'
to 31728a180330e666bc4477262583f8ac9b757a15
- Merge "docs: fix link to global variable defaults"
- docs: fix link to global variable defaults
Change-Id: I2737c200ba33d9eabe2c9815766b2a3555827ef5
* Update neutron-tempest-plugin from branch 'master'
to c007b81f70f394e3391dc08a458e34837414b1bf
- Merge "Remove old excludes"
- Remove old excludes
These are detected as errors since the clean up was done[1] in
the requirements repository.
[1] 314734e938f107cbd5ebcc7af4d9167c11347406
Also remove the note about old pip's behavior because the resolver
in recent pip no longer requires specific order.
Change-Id: Ic32aa7a18054c128efb9094154f055a2cf55c1f0
* Update neutron from branch 'master'
to 0397b307c29178995d2f1b9aacbe4f7fe41c2850
- Merge "Increase code coverage for safe_configure_dhcp_for_network()"
- Increase code coverage for safe_configure_dhcp_for_network()
This can be called just like configure_dhcp_for_network(),
but can also handle exceptions.
TrivialFix
Change-Id: Ia8b8c9def5ed708afc9f55e54156149232af55e1
* Update neutron from branch 'master'
to 5554613d53fd3274ef294f618aeac93d92bcb05f
- Merge "Revert "[OVN] Prevent Trunk creation/deletion with parent port bound""
- Revert "[OVN] Prevent Trunk creation/deletion with parent port bound"
There are three reasons to revert this patch.
1. It broke RPC push API for trunks because it added port db model to
event payload that is not serializeable.
2. It also broke the callback event payload interface, which requires
that all entries in .states attribute belong to the same core object.
To quote from neutron-lib,
```
# an iterable of states for the resource from the newest to the oldest
# for example db states or api request/response
# the actual object type for states will vary depending on event caller
self.states = ...
```
3. There is no good justification why ml2/ovn would not allow this
operation. The rationale for the original patch was to align the
behavior with ml2/ovs, but we don't such parity requirements. The 409
error that can be returned by the API endpoints is backend specific.
To quote api-ref,
```
409 The operation returns this error code for one of these reasons:
A system configuration prevents the operation from succeeding.
```
AFAIU there is nothing that prevents ml2/ovn to create a trunk in this
situation.
This will have to be backported in all supported branches (the original
patch was backported down to Wallaby).
Conflicts:
neutron/services/trunk/drivers/ovn/trunk_driver.py
This reverts commit 833a6d82cd705548130cdac73a88d388f52c7824.
Closes-Bug: #2065707
Related-Bug: #2022059
Change-Id: I067c2f7286b2684b67b4389ca085d06a93f856ce
* Update neutron from branch 'master'
to 2f351d9e64552cefb6ef7a5706c7be4eea69953f
- Merge "tests: Don't except error 400 from allocation_pools=None"
- tests: Don't except error 400 from allocation_pools=None
A recent change in neutron-lib [1] changed the behavior somewhat,
handling the None value explicitly passed as `allocation_pools` the same
way as if the field was not passed at all (meaning, setting pools from
start/end IP addresses for the subnet.)
This new behavior seems reasonable, so instead of reverting to the
original behavior, I'm making the test cases here not check an error
happens when None is passed.
[1] If768ab6a5f92d200841a734087bbc8fba8870dc6
Change-Id: I938ffabe7e74fa129c58dd4786153a0b4f374194
* Update mistral from branch 'master'
to 0e03f2db5ea144e5ea840cd31ba26d1061df869e
- Replace deprecated assertDictContainsSubset
The method was deprecated in Python 3.2[1] was removed in Python 3.12.
[1] https://docs.python.org/3/whatsnew/3.2.html#unittest
Related-Bug: #1938103
Change-Id: I1a4e43235a019c9296c1554add5b36f6fc705267
* Update ansible-role-systemd_networkd from branch 'master'
to 8a4a59afd916bfd7667723f24359b0ac50d1c694
- reno: Update master for unmaintained/zed
Update the zed release notes configuration to build from
unmaintained/zed.
Change-Id: I235a406ba7d75b15bc68cbffa9a21f6910eb7424
* Update openstack-ansible-os_designate from branch 'master'
to 19cd4a066a33870d26b7049f4321a5b4b471e299
- Merge "reno: Update master for unmaintained/zed"
- reno: Update master for unmaintained/zed
Update the zed release notes configuration to build from
unmaintained/zed.
Change-Id: I68b10c703a4c838f606f92bc67cc567e506bc1f9
* Update openstack-ansible-os_keystone from branch 'master'
to 4fa9f4f675d7159bdbafc18b4dd210a69de4af7e
- Merge "reno: Update master for unmaintained/zed"
- reno: Update master for unmaintained/zed
Update the zed release notes configuration to build from
unmaintained/zed.
Change-Id: I404f88d37439b215be950f36d8867fe5efcdc87e
* Update openstack-ansible-os_neutron from branch 'master'
to a53b28c8daed01b0623bc26b753bc1a318db8c64
- Merge "reno: Update master for unmaintained/zed"
- reno: Update master for unmaintained/zed
Update the zed release notes configuration to build from
unmaintained/zed.
Change-Id: I52fdcd4b955dee90ecc71a7f436d85e2306fc0b2
* Update openstack-ansible-os_blazar from branch 'master'
to 9200a922070960dcc1cf5334cba5bb5a3f232aa2
- Merge "reno: Update master for unmaintained/zed"
- reno: Update master for unmaintained/zed
Update the zed release notes configuration to build from
unmaintained/zed.
Change-Id: Ic812f905fc05f44d97329f7c377b3850733214e6
* Update openstack-ansible-os_sahara from branch 'master'
to efce7b4470d9ce3600a9dabff745781677db409d
- reno: Update master for unmaintained/zed
Update the zed release notes configuration to build from
unmaintained/zed.
Change-Id: Ic437f4ee919e9f38f0093477d4a7822b3b521428
Zuul
yatinkarel
OpenStack Release Bot