Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2024.1: 2023.1 merge #1287

Merged
merged 32 commits into from
Sep 16, 2024
Merged

2024.1: 2023.1 merge #1287

merged 32 commits into from
Sep 16, 2024

Conversation

markgoddard
Copy link

  • Fix prometheus_blackbox_exporter_endpoints to allow truthy values
  • Add bool to rabbitmq endpoint
  • Correct horizon_public_endpoint
  • Add merge.py
  • Fix CVE-2024-44082 / OSSA-2024-003
  • Add select
  • CI: Bump multinode.yml reusable workflow to 1.1.0
  • CI: Add 2024.1 to nightly multinode test matrix
  • Add hook for fixing hostname bug in Multinode
  • Reboot hosts after fix-hostname changed
  • Reboot with bootstrap user in ci-aio env
  • Reference controller IP for backend TLS certificates
  • kolla-images.py: Add a check-image-map command
  • kolla-images.py: Fix image to container exceptions using check-image-map
  • kolla-images.py: Misc fixes
  • CI: Add check-image-map and check-hierarchy to check-tags workflow
  • CI: Trigger build-kayobe-image for check-tags job
  • kolla-images.py: Add image map exception for neutron_eswitchd
  • Fix growroot when using software raid (Fix growroot when using software raid #818)

MoteHue and others added 30 commits September 5, 2024 10:03
horizon_public_port is dependent on backend_tls being enabled, rather
than external tls.
This script can be used for merging from one release branch of SKC into
the next.
Fixes CVE-2024-44082 [1] with updated container images for Ironic
services.

Note that Ironic Python Agent images also need to be updated to fully
fix this vulnerability. If this is not possible, a new configuration
option ``[conductor]conductor_always_validates_images`` is available.
See the OSSA-2024-003 announcement [2] for more details.

[1] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-44082
[2] https://security.openstack.org/ossa/OSSA-2024-003.html
2023.1: CI: Bump multinode.yml reusable workflow to 1.1.0
Further fixes to Prometheus blackbox exporter endpoints
CI: Add 2024.1 to nightly multinode test matrix
Add hooks for fixing hostname bug in Multinode for Caracal upgrade job
Reboot with bootstrap user in ci-aio env
vault: Reference controller IP for backend TLS certificates
This command checks the image mapping against Kolla Ansible variables.

The *_image variables in Kolla Ansible define the mapping between
containers and images. Ensure that the mapping defined in this script
matches the one in Kolla Ansible.
We recently had an issue where images were built for ironic, but this
did not include dnsmasq due to not matching the regex. The 'ironic' tag
was updated in kolla-image-tags.yml, which matches ironic_dnsmasq
container, but no such dnsmasq image existed. This issue would have been
caught the check-tags workflow with the correct mapping added in this
change.
These commands ensure that the image map and hierarchy defined in
kolla-images.py matches Kolla Ansible.

Also update the path filter to run the check-tags workflow when pulp.yml
or kolla-images.py is modified.
This was not caught because neutron-mlnx-agent is not in the list of
supported images in pulp.yml.
* Fix growroot when using software raid

Using @markgoddard's suggestion from: #770 (comment)

* Add a release note

* Update releasenotes/notes/fixes-growroot-for-software-raid-3852bdea5415a0be.yaml

Co-authored-by: Alex-Welsh <alex@stackhpc.com>
Co-authored-by: Michał Nasiadka <michal@stackhpc.com>
zed: Fix image mapping in kolla-images.py, add tests and CI
@markgoddard markgoddard requested a review from a team as a code owner September 12, 2024 11:42
@markgoddard markgoddard self-assigned this Sep 12, 2024
@markgoddard markgoddard merged commit 5114b09 into stackhpc/2024.1 Sep 16, 2024
12 checks passed
@markgoddard markgoddard deleted the 2024.1-2023.1-merge branch September 16, 2024 12:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants