-
Notifications
You must be signed in to change notification settings - Fork 23
zed: yoga merge #692
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
Merged
Merged
zed: yoga merge #692
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
Contributor
markgoddard
commented
Oct 6, 2023
- Add a custom playbook to fix OVN chassis priorities
- Document stackhpc_pulp_images_kolla_filter variable
- Use upper constraints to install openstackclient
- Add python and growpart to images (Add python and growpart to images #676)
- Bump Rocky 9 host image to 9.2
- Bump Rocky tag for python and growpart additions
- Bump Rocky 9 snapshots
- Change default to reboot one host at a time
- Bump Rocky 8 snapshots
- Add debugging info to tls deployment docs
- Fail container build workflow when no images build
- Update walled garden guide no_proxy defaults
- Moving bifrost config into its proper folder.
- docs: fix wazuh headings
Sometimes, typically after restarting OVN services, the priorities of entries in the ha_chassis and gateway_chassis tables in the OVN northbound database can become misaligned. This results in broken routing for external (bare metal/SR-IOV) ports. This playbook can be used to fix the issue by realigning the priorities of the table entries. It does so by assigning the highest priority to the "first" (sorted alphabetically) OVN NB DB host. This results in all gateways being scheduled to a single host, but is less complicated than trying to balance them (and it's also not clear to me how to map between individual ha_chassis and gateway_chassis entries). The playbook can be run as follows: kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/ovn-fix-chassis-priorities.yml If the 'controllers' group does not align with the group used to deploy the OVN NB DB, this can be overridden by passing the following: '-e ovn_nb_db_group=some_other_group'
Document stackhpc_pulp_images_kolla_filter variable
``` Traceback (most recent call last): File "/home/cloud-user/actions-runner/_work/stackhpc-kayobe-config/stackhpc-kayobe-config/venvs/kayobe/bin/openstack", line 5, in <module> from openstackclient.shell import main File "/home/cloud-user/actions-runner/_work/stackhpc-kayobe-config/stackhpc-kayobe-config/venvs/kayobe/lib64/python3.6/site-packages/openstackclient/shell.py", line 23, in <module> from osc_lib import shell File "/home/cloud-user/actions-runner/_work/stackhpc-kayobe-config/stackhpc-kayobe-config/venvs/kayobe/lib64/python3.6/site-packages/osc_lib/shell.py", line 32, in <module> from osc_lib.cli import client_config as cloud_config File "/home/cloud-user/actions-runner/_work/stackhpc-kayobe-config/stackhpc-kayobe-config/venvs/kayobe/lib64/python3.6/site-packages/osc_lib/cli/client_config.py", line 18, in <module> from openstack.config import exceptions as sdk_exceptions File "/home/cloud-user/actions-runner/_work/stackhpc-kayobe-config/stackhpc-kayobe-config/venvs/kayobe/lib64/python3.6/site-packages/openstack/__init__.py", line 58, in <module> import openstack.connection File "/home/cloud-user/actions-runner/_work/stackhpc-kayobe-config/stackhpc-kayobe-config/venvs/kayobe/lib64/python3.6/site-packages/openstack/connection.py", line 217, in <module> from openstack import _services_mixin File "/home/cloud-user/actions-runner/_work/stackhpc-kayobe-config/stackhpc-kayobe-config/venvs/kayobe/lib64/python3.6/site-packages/openstack/_services_mixin.py", line 6, in <module> from openstack.block_storage import block_storage_service File "/home/cloud-user/actions-runner/_work/stackhpc-kayobe-config/stackhpc-kayobe-config/venvs/kayobe/lib64/python3.6/site-packages/openstack/block_storage/block_storage_service.py", line 14, in <module> from openstack.block_storage.v3 import _proxy as _v3_proxy File "/home/cloud-user/actions-runner/_work/stackhpc-kayobe-config/stackhpc-kayobe-config/venvs/kayobe/lib64/python3.6/site-packages/openstack/block_storage/v3/_proxy.py", line 37, in <module> class Proxy(_base_proxy.BaseBlockStorageProxy): File "/home/cloud-user/actions-runner/_work/stackhpc-kayobe-config/stackhpc-kayobe-config/venvs/kayobe/lib64/python3.6/site-packages/openstack/block_storage/v3/_proxy.py", line 1592, in Proxy ignore_missing: ty.Literal[True] = True, AttributeError: module 'typing' has no attribute 'Literal' ``` See: https://github.com/stackhpc/stackhpc-kayobe-config/actions/runs/6341830858/job/17226310409
Use upper constraints to install openstackclient
…ies-playbook Add a custom playbook to fix OVN chassis priorities
* add python3 to images * add growpart
Hitting this issue with cloud-init in 9.1: ``` Unable to find a system nic for <MAC_ADDRESS> from cloud-init ``` This means that network interfaces are not configured properly. Newer cloud-init seems to fix the issue. See: https://askubuntu.com/questions/1400527/unable-to-find-a-system-nic-while-running-cloud-init
This brings in the CPU vulnerability fixes for: - Zenbleed - Downfall
This is safer if the playbook is run by accident. Existing behaviour can be retained by setting ANSIBLE_SERIAL=0.
This brings in the CPU vulnerability fixes for: - Zenbleed - Downfall
Bump Rocky 9 snapshots
Fail container build workflow when no images build
Change default to reboot one host at a time
Update walled garden guide no_proxy defaults
Add debugging info to tls deployment docs
Bump Rocky 8 snapshots
xena: fix Wazuh docs headings
Moving bifrost config into its proper folder.
yoga: xena merge
Alex-Welsh
approved these changes
Oct 6, 2023
jovial
approved these changes
Oct 6, 2023
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.