256e605938
This release picks up new commits to bifrost since the last release from stable/wallaby. This is being proposed as a convenience to help make sure stable changes are being released. If the team is good with this going out, please respond with a +1 to let the release team know it is OK to proceed. If it is not wanted at this time, or if there are more changes that would be good to get merged before doing a stable release, please leave a -1 with a comment with what the team would prefer. We can then either abandon this patch, or wait for an update with a new commit hash to use instead. $ git log --oneline --no-merges 10.2.0..38a71741 a30b9093 Fix incompatibility with recent rich library d79d8981 Do not make password files world-readable 304a441c Catch all exceptions from pbr when importing the root package 092476f1 Revert "Install libvirt-python from source instead of a wheel" 11be6cd5 Fix the DHCP port in iptables (68 vs 67 and TCP vs UDP) b31845d6 Use stable/wallaby branch to install dependencies 164bfc9b Improve main function 3b0240c8 bifrost-cli: fix relative paths in --extra-vars a46d2833 Install sushy-oem-idrac for idrac-redfish-virtual-media a645ff65 Fix Redeploy Playbook 12080fb3 Install libvirt-python from source instead of a wheel d4a26277 Revert "libvirt: pin edk2-ovmf for CentOS Stream" 717865d7 Move the network-interface checks to bootstrap 3176e04c Reasonable error message if network_interface is not found 1980b32b Fix upper-constraints reference d953dddd Install DIB dependencies in bifrost-ironic-install role 5dbee7d6 Add OFTC network channel to contributor docs b131c78f libvirt: pin edk2-ovmf for CentOS Stream e629573c Install squashfs-tools for Ubuntu image builds d28cc542 [CI] Make Kolla job running again 99c1107b Use explicit path for which 9346bfb3 Update TOX_CONSTRAINTS_FILE for stable/wallaby c9b793fc Update .gitreview for stable/wallaby Signed-off-by: Elod Illes <elod.illes@est.tech> Change-Id: Ic94443ca627ed100a8f293f2e57ae66b02ba1426
OpenStack Releases
This repository is used to drive release automation for OpenStack release deliverables, ultimately publishing them on the https://releases.openstack.org/ website.
Changes to this repository are proposed using Gerrit at https://review.opendev.org. This repository is managed by the OpenStack Release Management team.
For more information on how to use this repository, please read our reference documentation.
Who should use this repository
All official OpenStack software should go through the OpenStack Release Management team team to produce releases. Exceptions to this rule are granted by the Technical Committee and documented in the openstack/governance repository ('release-management' key in reference/projects.yaml).
Deliverables managed by teams not under OpenStack governance should follow the tagging instructions in the infra manual.
More information
You can reach the Release Management team on the #openstack-release channel on OFTC IRC <https://www.oftc.net/>, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.