Release 1.3.0 of stackhpc.linux fixes configuration of kernel parameters
for IOMMU when the GRUB_CMDLINE_LINUX_DEFAULT variable is absent from
/etc/default/grub.
Include a release note about a notable change in the sriov role.
[1] https://github.com/stackhpc/ansible-collection-linux/releases/tag/v1.3.0
Change-Id: I43295cd21fc4947fa877aa242070e3c132532fab
Closes-Bug: #2083874
This fixes IPA and host disk image build failures when Git was not
installed on the build host.
Change-Id: I057aefc45d1a8efe133fec9921e5c84cad556429
Closes-Bug: #2058922
This updates the group and mode set on the /var/log/journal directory to
match default ownership and permissions used by systemd-journald.
Closes-Bug: #2083494
Change-Id: I15323b95199b9ef19504c7408dd89720f9ba9c32
Use correct system scope - all - while getting the list of ironic
nodes in ipa-images role.
Closes-Bug: #2083014
Change-Id: I4da3a3739d57817ffbd094caea0fc80c3ad8eff8
When kolla_base_arch and ansible_facts.architecture differs
we need to run multiarch/qemu-user-static image - see [1].
[1]: https://github.com/multiarch/qemu-user-static
Co-Authored-By: Bartosz Bezak <bartosz@stackhpc.com>
Change-Id: If149418f509c687c3e5d1072cc39a80af33dec5a
There is a race condition in Ansible that can result in this failure:
msg: |-
MODULE FAILURE
See stdout/stderr for the exact error
rc: -13
Disabling SSH pipelining prevents the issue at the cost of Ansible
execution duration.
See:
- https://github.com/ansible/ansible/issues/78344
- https://github.com/ansible/ansible/issues/81777
Change-Id: I62221df4650ddd02afdbc0993e783bf66b706a1c
Some network devices may use SSH key exchange algorithms that are no
longer supported by the Ansible control host. This will cause
ssh-keyscan to fail, preventing Kayobe from configuring the devices.
This change makes it possible to work around the issue by setting
switch_skip_keyscan to true for the affected devices. The SSH known
hosts file on the Ansible control host will need to be populated
manually.
Change-Id: I4e3394cff1fd86eb5c1a4be55d6fd7fd080b2944
eos_config does not support provider, nor connection: local from at
least 2022 [1] - since ansible>=7 (ansible-core 2.14).
[1]: 588d94b2ed
Closes-Bug: #2058365
Change-Id: Ief37b7bee758e34dddb881a9e68728013861c0ec
During the ``kayobe overcloud inventory discover`` command, Kayobe
queries the Bifrost ironic node list and updates the Kayobe inventory.
If the nodes have a driver_info.ipmi_address field set, an ipmi_address
variable will be defined in the Kayobe inventory for the host.
This does not work for Redfish based hosts, which use
driver_info.redfish_address in the Ironic node. This change adds a new
``redfish_address`` variable and extends the command to discover the
address from the Bifrost node inventory.
Change-Id: Ieb1e61ddadb542732739d1f478b1e5a176e0ac88
Previously Kolla Ansible hard-coded Neutron physical networks starting
at physnet1 up to physnetN, matching the number of interfaces in
neutron_external_interface and bridges in neutron_bridge_name.
Sometimes we may want to customise the physical network names used.
This may be to allow for not all hosts having access to all physical
networks, or to use more descriptive names.
For example, in an environment with a separate physical network for
Ironic provisioning, controllers might have access to two physical
networks, while compute nodes have access to one.
This change extends the 'physical_network' network attribute to make it
possible to customise the Neutron physical network names used for the
OVS, OVN, Linux bridge and OVS DPDK plugins. The default behaviour is
unchanged.
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/922320
Change-Id: I214444c60653f484fcda6275cc725879d14f9e7a
This bumps the hacking library, which is used to enforce OpenStack code
guidelines, to the latest released version. No code changes are required
to pass checks with this version.
Change-Id: I05ab9cb5db5c30cf537476cb494f707338ea67e9
