This variable was configuring enable_host_ntp in kolla-ansible, which
was removed in the Xena release.
Change-Id: I737598d3bbe40b933b4b727eccc3b2a76ed97cdb
The docker Python package was dropped from kolla requirements [1], but
we still need to install it to build container images.
[1] https://review.opendev.org/c/openstack/kolla/+/896644
Change-Id: I241884497f4fb707385eb12d5fcc187ed839f754
If inline Ansible vault encryption is used to define an encrypted
variable in kayobe-config, running 'kayobe configuration dump -l <host>'
fails with the following:
Failed to decode config dump YAML file /tmp/tmp_fg1bv_j/localhost.yml:
ConstructorError(None, None, "could not determine a constructor for
the tag '!vault'", <yaml.error.Mark object at 0x7f1e5c7404c0>)
This change fixes the error by using the Ansible YAML loader which
supports the vault tag. Any vault encrypted variables are sanitised in
the dump output. Note that variables in vault encrypted files are not
sanitised.
Change-Id: I4830500d3c927b0689b6f0bca32c28137916420b
Closes-Bug: #2031390
This fix was added when upgrading from CentOS Linux 8.2 to 8.3. This is
likely not required on currently supported operating systems.
Change-Id: Ic2c47ae4514d98ff18c5d17ba62b50c47f3929c1
I missed this when I refactored the code to fallback
to templating. We need to deduplicate before picking
the strategy for the fallback to work for symlinked files.
Change-Id: Iddd6c90a6daa41e1d1cdaa6b598491792c13394d
Closes-Bug: #2042689
Updating requirements.yml with latest os-networks role
Following up:
Ia3550644e5fc3e83f792e46d42b4c35d5eec4705
Change-Id: I9cb1b4c5329dc9db8562cf317616101d35f13edb
This is a backwards compatability improvement, since it was previously
permitted to have a config file that templated to invalid yaml/ini.
Change-Id: I53a0894cc64e83c7342a82ad987b7e5a4696ece2
Closes-Bug: #2042690
I8bf75ce44b9ec1fdd477fcddf2deebf2929d9fc1 added a workaround to remove
incorrectly named DNF repository files.
This workaround has been in place since the Antelope release and can now
be removed.
Change-Id: I7ba61ffa8aaabcedf1c5249e5f39f39257410f9a
Ie59f0c729381e5bea112ab7f5d0c738a9488b772 changed the provision-net and
cleaning-net to be non-shared when they are VLAN networks. It also
added some transitional tasks to modify existing VLAN networks to unset
the shared property.
This change removes the transitional code since it has been in place for
over 3 years.
This change also slightly refactors the code to use only a 'tasks' list.
Change-Id: I6d358502d37e6a2d0098ad4733840613e93b4279
We no longer support EL8 or network-scripts.
Debian systems never used this role, so also removing those tasks.
Change-Id: I17b93c75a1ff8eb8d636247696f4a1709ca486d5
Kayobe has fairly coarse-grained default groups - controller, compute,
etc, which work well in the majority of cases. Kolla Ansible allows much
more fine-grained placement on a per-service basis, e.g.
ironic-conductor. If the operator has taken advantage of this
fine-grained placement, then it is possible that some of the assumptions
in Kayobe may be incorrect. This is one downside of the split between
Kayobe and Kolla Ansible.
For example, Ironic conductor services may have been moved to a subset
of the top level 'controllers' group. In this case, we would not want
the Ironic networks to be mapped to all hosts in the controllers group -
only those running Ironic conductor services. The same argument can be
made if the loadbalancer services (HAProxy & keepalived) or Neutron
dataplane services (e.g. L3 & DHCP agents) have been separated from the
top level 'network' group.
This change abstracts the placement of Ironic conductor Ironic
inspector, loadbalancer and network services into separate variables,
rather than referencing the top level 'controllers' and 'network' groups
directly. These variables may be updated by the operator to match the
service placement.
Change-Id: Idbf181c795ee98ad653f11ae483f9dab4ef1b599
Fixes an issue when user forgot to combine
'kolla_ansible_custom_passwords',
'kolla_ansible_default_custom_passwords' and own dictionary with
custom passwords in configuration files. Now
'kolla_ansible_extra_custom_passwords' should provide only user
custom passwords to add or override in the passwords.yml.
Change-Id: I4813a1f6ab9cb566596e806bd0ada6dff342d119
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
Kolla Ansible renamed kolla_internal_fqdn_cacert to
kolla_admin_openrc_cacert in Victoria, after which we no longer set the
variable correctly in globals.yml. This would lead to a missing
OS_CACERT in admin-openrc.sh and public-openrc.sh.
This change fixes the issue by renaming the relevant Kayobe variables to
match and passing through the correct variable. Backwards compatibility
is provided until the end of the deprecation period.
kolla_public_openrc_cacert -> kolla_external_fqdn_cacert
kolla_admin_openrc_cacert -> kolla_internal_fqdn_cacert
Story: 2010486
Task: 47054
Change-Id: I9e1cc20579cf80525d6ef732a1aac99a65bc171b
Co-Authored-By: Maksim Malchuk <maksim.malchuk@gmail.com>
