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 #1385

Merged
merged 41 commits into from
Nov 25, 2024
Merged

2024.1: 2023.1 merge #1385

merged 41 commits into from
Nov 25, 2024

Conversation

priteau
Copy link
Member

@priteau priteau commented Nov 22, 2024

  • Add opensearch logs to the openstack dashboard
  • Change metric to retrieve hostname
  • Add release note
  • Update package update testing instructions (Update and supplement missing information on instructions #830)
  • Configure IPA with useful inspection settings
  • Fix upgrade-prerequisites
  • Add conditional choice of kolla/globals.yml path
  • Redfish exporter: Fixes scrape group
  • Fix Rabbit upgrade script conditional evaluation
  • Redfish exporter: Decrease sensitivity of alert (Redfish exporter: Decrease sensitivity of alert #1358)
  • fix!: manage the physical interface in ci-aio
  • fix!: manage the physical interface in ci-aio
  • fix: test if admin-openrc.sh exists before deploying os-capacity
  • fix!: manage the physical interface in ci-aio
  • CIS: Stop recursively setting permissions on logs files
  • Add upgrade host configure warning for ceph nodes
  • Update Blazar image (Update Blazar image #1334)
  • Pin os-capacity to v0.5 release (Pin os-capacity to v0.5 release #1365)
  • docs: fix link to release train page
  • Bump kayobe-automation

technowhizz and others added 30 commits April 23, 2024 14:25
Add configuration to include extra-hardware and mellanox elements, with
other useful collectors and kernel settings.
We were only including the scrape group `overcloud` in the prometheus
config. This change allows the scrape group to work as intended.
The redfish exporter is prone to failed scrapes. Lets wait for mulitple
failed scrapes before triggering an alert. This should still catch the
case where it is completely dead, but reduce the false positives from
failed scrapes.
Treat the physical interface as network interface inside of the `ci-aio` environment. This
is to ensure the network interface files are created correctly with the appropriate permissions
otherwise we will lose connection after the DHCP lease expires. Also this approach enables us
to include the interface within the firewall configuration ensuring we maintain SSH access through
the firewall via this interface.
fix!: manage the `physical` interface in `ci-aio`
Treat the physical interface as network interface inside of the `ci-aio` environment. This
is to ensure the network interface files are created correctly with the appropriate permissions
otherwise we will lose connection after the DHCP lease expires. Also this approach enables us
to include the interface within the firewall configuration ensuring we maintain SSH access through
the firewall via this interface.
During service deploys using Kayobe Automation this playbook will fail
as the `admin-openrc.sh` file is not generated during the deployment
process.

This in turn causes the workflow to be reported as a failure even though
the service deployment succeeded.
fix!: manage the `physical` interface in `ci-aio`
Treat the physical interface as network interface inside of the `ci-aio` environment. This
is to ensure the network interface files are created correctly with the appropriate permissions
otherwise we will lose connection after the DHCP lease expires. Also this approach enables us
to include the interface within the firewall configuration ensuring we maintain SSH access through
the firewall via this interface.
This suffers from a time-of-check to time-of-use race condition and in
general recursively setting file permissions seems to be a bad idea.
fix!: manage the `physical` interface in `ci-aio`
fix: test if `admin-openrc.sh` exists before deploying os-capacity
CIS: Stop recursively setting permissions on logs files
Switch to using the StackHPC fork - master branch - when building blazar
Configure IPA with useful inspection settings
Pin os-capacity to v0.5 release

---------

Co-authored-by: Jake Hutchinson <[email protected]>
@priteau priteau requested a review from a team as a code owner November 22, 2024 14:48
@priteau priteau self-assigned this Nov 22, 2024
jackhodgkiss
jackhodgkiss previously approved these changes Nov 25, 2024
@priteau priteau enabled auto-merge November 25, 2024 10:23
@priteau priteau merged commit 1eef82c into stackhpc/2024.1 Nov 25, 2024
12 checks passed
@priteau priteau deleted the 2024.1-2023.1-merge branch November 25, 2024 11:53
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.

9 participants