fix: typo in playbook run command #1231
Closed
Conversation
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
Build Horizon from stackhpc fork
Q2 2024 zed security patch
Update Wazuh docs
This change adds a new playbook, stackhpc-openstack-tests.yml, that uses the new stackhpc-openstack-tests repository to perform testing of the deployment that is not covered by Rally or Tempest. Currently this includes Prometheus and OpenSearch. The all-in-one CI test has been updated to run this new test suite, and the results are included in the test results artifact.
Previously an erroneous 'False' was appended to the artifact name.
AIO Improvements
zed: yoga merge
This fixes failures of the Kolla image build GitHub workflow.
CI: Pin requests below 2.32.0
This brings in a useful idempotency fix for Vault deployment.
This change modifies the overcloud HashiCorp Vault playbooks to use the local Vault service rather than via HAProxy. This makes it possible to deploy and use Vault without HAProxy. This eliminates the previous bootstrapping issue where HAProxy needed to be deployed without TLS enabled while generating initial certificates. To make this work in environments with a proxy configured, https_proxy is overridden.
In the previous HAProxy config for Vault, 200, 501 and 503 were treated as healthy. This allowed for bootstrapping Vault via HAProxy, but made standby backends appear as unhealthy, leading to a Prometheus alert. We no longer bootstrap Vault via HAProxy, so we can treat 200 (active) and 429 (standby) as healthy. Co-Authored-By: Dawud Mehmood <dawud@stackhpc.com>
Typically the certificate is only valid for the FQDN. This will not cause a problem usually because the internal API generally uses the VIP directly rather than an FQDN.
The overrides were for Yoga, and aren't required for Antelope.
docs: Update release train image
They're encrypted automatically now: #1171
Remove docs to encrypt wazuh secrets
Magnum CAPI docs update
Bump up Hashicorp collection version
rocky: update ovn to 24.03 (LTS) and OVS to 3.3
Defining set of special characters to omit "`" and "'" which leads to issues More description: #1226
Allow reboot playbook to run with bootstrap user
Fixing wazuh password generation
Make linter happy
2023.1: zed merge
jackhodgkiss
added
bug
|
@jackhodgkiss could you target this at Yoga first then we'll merge it up |
Any reason why? Most PRs open are against |
In general new features go to antelope, fixes go to yoga |
|
You don't need to close the pull request, you can force push and target |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.