44af704836
Back in the Ussuri release, we changed the Bifrost kernel location to use ipa.kernel instead of ipa.vmlinuz. While this works fine for newly discovered nodes, any node added to Bifrost in Train or earlier will have kept ipa.vmlinuz as its deploy kernel. This can cause issues since upgrading Bifrost or building new deployment images will update ipa.kernel, but not ipa.vmlinuz, resulting in nodes booting with an old kernel and a new ramdisk. Fix by adding a new rule updating the legacy kernel location and documenting how to update node information. Change-Id: I6ae44dcae78424b4638762d015cf24336444707f
21 lines
1.1 KiB
YAML
21 lines
1.1 KiB
YAML
---
|
|
- name: Ensure introspection rules are registered in Bifrost
|
|
hosts: seed
|
|
tags:
|
|
- introspection-rules
|
|
roles:
|
|
- role: ironic-inspector-rules
|
|
os_openstacksdk_install_epel: "{{ dnf_install_epel }}"
|
|
os_openstacksdk_state: "latest"
|
|
ironic_inspector_venv: "{{ virtualenv_path }}/openstacksdk"
|
|
ironic_inspector_upper_constraints_file: "{{ openstacksdk_upper_constraints_file }}"
|
|
ironic_inspector_cloud: bifrost
|
|
ironic_inspector_rules: "{{ kolla_bifrost_inspector_rules }}"
|
|
# These variables may be referenced in the introspection rules.
|
|
inspector_rule_var_ipmi_username: "{{ kolla_bifrost_inspector_ipmi_username }}"
|
|
inspector_rule_var_ipmi_password: "{{ kolla_bifrost_inspector_ipmi_password }}"
|
|
inspector_rule_var_lldp_switch_port_interface: "{{ kolla_bifrost_inspector_lldp_switch_port_interface }}"
|
|
inspector_rule_var_deploy_kernel: "{{ kolla_bifrost_inspector_deploy_kernel }}"
|
|
inspector_rule_var_deploy_ramdisk: "{{ kolla_bifrost_inspector_deploy_ramdisk }}"
|
|
inspector_rule_var_legacy_deploy_kernel: "{{ kolla_bifrost_inspector_legacy_deploy_kernel }}"
|