... because the Zed release is available for only 22.04.
Because Ruby 2 is no longer available in Ubuntu 22.04, this drops all
tests with Puppet 6, which supports only Ruby 2. (Ruby 3 is supported
since Puppet 7.8.0)
Also, this disables the separate ceph repository because the upstream
repository does not yet contain packages for Ubuntu Jammy. We install
ceph packages from UCA for the time being but would revisit this later.
Depends-on: https://review.opendev.org/c/openstack/puppet-nova/+/865105
Change-Id: Icbfe677dadb3dab96ea06afe650c524b4abbb753
puppetlabs-apache installs mariadb instead of mysql since 13.0.0.
mariadb translates utf8mb3 to utf8 contrary to the behavior of mysql
which translates utf8 to utf8mb3, and this breaks idempotency when
utf8mb3 is used.
This reverts the past changes to replace utf8 by utf8mb3 to fix
idempotency.
Change-Id: I7edcc6eee5b473076f0cd42efde97232289aaa01
Currently idempotency in Ubuntu is broken because of the below change
detected in collate in MySQL.
```
/Stage[main]/Keystone::Db::Mysql/Openstacklib::Db::Mysql[keystone]/
Mysql_database[keystone]/collate: collate changed 'utf8mb3_general_ci'
to 'utf8_general_ci'
```
Similarly to what we observed in the past about charset[1], it seems
MySQL in Ubuntu is automatically converting the collate value and that
is causing the "unexpected" change detected in the 2nd puppet run.
This fixes the idempotency by using utf8mb3_general_ci in Ubuntu to
avoid the mismatch caused by internal translation.
[1] 085d3569021441810c1dff7c8f4396003c690805
Change-Id: I56f31397669d3d7b08aa2e9808947141e003ab0b
We are observing the failure in Ubuntu integration job caused by
broken idempotency. It seems current mysql/mariadb in Ubuntu replaces
utf8 with uft8mb3 automatically and this behavior results in unexpected
change in second run.
This change ensures that we use utf8mb3 in Ubuntu to avoid such
mismatch caused by internal translation. Note this change is intended
to be a quick gate fix and the charset would be updated to utf8mb4
later.
Closes-Bug: #1929073
Change-Id: I7742120758057b5a00f1d093f355fda3791f4e02
* Deploy Self-Signed Certificates for both IPv6 & IPv4 deployments.
* Disable IPv6 for RabbitMQ now, for SSL reasons, will be enabled again
later in a next iteration.
* Deploy Ironic API under WSGI instead of eventlet.
* Switch Glance API, Ironic API and Keystone to SSL.
* Configure Tempest with SSL endpoints when needed.
* Reduce the Ironic tests because of [1].
[1] https://bugs.launchpad.net/ironic/+bug/1554237
Note #1: puppet-swift, and puppet-cinder will require some work to support SSL, so it's not
implemented in this patch.
Note #2: we don't enable SSL for Neutron because of
https://bugs.launchpad.net/neutron/+bug/1514424
Change-Id: Ib2b5289b6f5e82f43cf60dee3152b2c2ddd5a014
* Manage Puppet OpenStack CI CA and create a common certificate,
auto-signed.
* Configure RabbitMQ to activate SSL on scenario002
* Configure OpenStack services that run on scenario002 to connect to
RabbitMQ using SSL protocol.
Change-Id: Ic435078472ba4e0e0eaf04a64e5bcb7aabba7b3d
