This reverts commit f2a9daaab9474db50219d27d8ba43e1ef00a279b.
Reason for revert: TinyIPA images from master are working again
Change-Id: Ibef45fad608eecf76c398339a9c21a5cf7ba3b15
With NetworkManager, the MichaelRigart.interfaces role only creates an
interface with the dummy type if it is called dummy*, otherwise it is
created as ethernet.
The default dev configuration was using eth1 for the bridge port, which
was causing issues on Rocky Linux 9, for example when following the
automated setup [1]. Switch to dummy1 to ensure a dummy port is created.
[1] https://docs.openstack.org/kayobe/latest/contributor/automated.html
Change-Id: Ib61a62e126c66d4133d8e80dff5643ebc6966bd1
RHEL 9 and Ubuntu Jammy are being compiled for the x86_64-v2
architecture which is newer than the qemu default of qemu64.
Nehalem is apparently the oldest model that works for x86_64-v2
and is expected to work on Intel and AMD cpus with kvm or qemu.
See devstack change [0].
[0]: Ibd6e11b59f3c8655bc60ace7383a08458b2177f2
Depends-on: https://review.opendev.org/c/openstack/kayobe/+/872981
Change-Id: I09567b4cce95ff1fe2fe4e9e91e49d5f5082f7d0
This is generally not necessary in development environments, and makes
for an awkward development workflow.
Change-Id: I7191779c1fb3a192b401886cd591f12c4b0ab2b0
This reverts commit da6623c0849bf5572ff2574103195d38d72158ae.
Reason for revert: Tenks now supports UEFI boot mode.
Change-Id: I988a46b19a7dbad827466d9702d8f63f47d1d838
Hosts used for development, test or CI may not have Virtualization
Technology (VT) enabled. Don't fail if it's disabled.
Story: 2009858
Task: 44496
Change-Id: Ie7f9e5f6682985e08c5bd22441f9ba6aee34b64a
In Ubuntu baremetal CI testing, we saw issues with IPMI commands
failing, resuling in job failures:
Error setting Chassis Boot Parameter 5
A metal3.io commit [1] was found that fixes the issue by moving IPMI
retries from ironic to ipmitool, which has a side-effect of increasing
the timeout. This change applies the same configuration.
[1] 6bc1499d8b
Change-Id: Ib4fce74cebebe85c31049eafe2eeb6b28dfab041
In Yoga, Ironic changed its default boot mode to UEFI [1]. Tenks does
not support it yet, so this is breaking overcloud baremetal testing.
[1] https://review.opendev.org/c/openstack/ironic/+/810249
Change-Id: I472177aa4d750cd5b83cde4d2629fe3c449e1373
The kolla_internal_vip_address variable was added in Wallaby, and the
vip_address attribute is now deprecated.
Depends-On: https://review.opendev.org/c/openstack/kayobe/+/805245
Change-Id: I747d9acc649f18206cbb23c0df6995bade335331
If using separate branches for each environment, it can be useful to
read the environment name from a file committed to each branch. Or, if
sharing the same branch for all environments, it can be useful to set
the default environment to one with lower impact, e.g. dev or staging.
If no --environment option is specified and a .environment file exists
at the root of the directory, use its content as KAYOBE_ENVIRONMENT.
Change-Id: I22b2b466e47a3b4d96931d754a4de7544f0ada5d
(cherry picked from commit 2af2c3a3b5387c577801b165ecd749fe782fddb9)
This also includes a cherry-pick of
I9a44578196086ec24de80b992fed385826778feb, Stop accessing unbound
variables.
The kayobe-env script would try accessing $1 which is an unbound
variable if no argument is passed. This fails when `set -u` is set.
Also refactor usage output into a function. As a side effect, a missing
argument to --environment now causes the script to properly exit with an
error.
Change-Id: I604c2ae6c47ef16fdc98e0598cad820e49e2ff26
Story: 2002009
Task: 41577
(cherry picked from commit 75b6402f8b0d4e39c40a1d11091ca760d8b99dee)
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: Iff0025bc13162397e6fabbc4b9674daa2e44091d
Use /etc/os-release on the Ansible control host. This makes sense for an
all-in-one configuration.
Change-Id: I7f7f22504e4bda1a7f4c984e97e7b86f7a95e4f0
This reverts to the default value of 'controller_bootstrap_user',
'seed_bootstrap_user' and 'seed_hypervisor_bootstrap_user' prior to the
addition of the os_distribution variable in Kayobe
(https://review.opendev.org/c/openstack/kayobe/+/787352). In an
all-in-one environment, using the current user as the bootstrap user
makes sense.
Story: 2004960
Task: 42386
Change-Id: I814cd3d97e850a9b0062f92ec5622a756bed0347
