It was bumped as seen with pbr in [1] but puppet modules version is
defined in metadata.json.
[1] https://review.opendev.org/#/c/653763/
Change-Id: I4633d96a0bb7375b95f3fa5f2423325add3b8f4f
We no longer support ntp so we should remove the puppet classes and
puppet-ntp usage.
Change-Id: I8d813fdccb45a464e5bbecda2de0f322299cf6e3
Depends-On: https://review.opendev.org/#/c/656999/
Related-Blueprint: tripleo-chrony
Along the same lines of https://review.opendev.org/#/c/603996/.
This commits expoxes one more knob to the operators, allowing them
to tweak the value of innodb_lock_wait_timeout (default = 50).
From upstream docs:
~~~
Time in seconds that an InnoDB transaction waits for an InnoDB
row lock (not table lock) before giving up with the error
ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction.
When this occurs, the statement (not transaction) is rolled back.
~~~
As for the other parameters it defaults to 'undef' so to keep the
default value of 50.
Change-Id: Ic2e1666ad39762caf9bf68272fdb00ee42658bb8
Hit the following during a deployment:
"Error: Evaluation Error: Error while evaluating a Function Call
'length' parameter 'arg' expects a value of type Collection, String,
or Binary, got Undef"
This commit adds a safeguard to skip the length check if
$driver_devices is 'Undef'.
Closes-bug: #1827091
Change-Id: Ide850ab917736f066c38e2e55960a03e1fcd3523
/var/run/redis is bind-mounted from the host, and on every reboot
that directory is recreated with default context for the host.
Configure the bind-mount so that /var/run/redis is relabelled
with a container context every time the redis container is started,
so that kolla can copy its config file and update the owner and
attributes as expected without SELinux denials.
Change-Id: Iaa8a99eb9ced21fb6c7c87c5b56dec55383af9a9
Partial-Bug: #1826554
We no longer use puppet 4.x so lets drop that job. Additionally we made
the 6.0 version voting but forgot to add it to the gate.
Change-Id: I1e891b8d7b4be7fc679cc352473079354a917c4b
This commit extends the stonith generation logic to allow operators
to make use of fencing levels.
Given a fence.yaml file like the following:
parameter_defaults:
EnableFencing: true
FencingConfig:
devices:
level1:
- agent: fence_agent1
host_mac: aa:bb:cc:dd:ee:ff
params:
someparam: somevalue
level2:
- agent: fence_agent2
host_mac: aa:bb:cc:dd:ee:ff
params:
someotherparam: someothervalue
The code iterates over the "levelX" key and creates the respective
stonith resources and adds them to the specified stonith level.
It should be backwards compatible since it checks if "devices" is
an array (no level specified) and reconducts this case to level=1.
Example results below.
* without levels:*
hieradata:
"tripleo::fencing::config": {
"devices": [
{
"agent": "fence_ipmilan",
"host_mac": "e4:43:4b:4b:c8:19",
[root@overcloud-controller-0]# pcs status
...
stonith-fence_ipmilan-e4434b4bc819 (stonith:fence_ipmilan): Started overcloud-controller-1
[root@overcloud-controller-0]# pcs stonith level
Target: overcloud-controller-0
Level 1 - stonith-fence_ipmilan-e4434b4bc819
* with levels: *
hieradata:
"tripleo::fencing::config": {
"devices": {
"level1": [
{
"agent": "fence_ipmilan",
"host_mac": "e4:43:4b:4b:c8:19",
...
"level2": [
{
"agent": "fence_kdump",
"host_mac": "e4:43:4b:4b:c8:19",
[root@overcloud-controller-0 ]# pcs status
...
stonith-fence_ipmilan-e4434b4bc819 (stonith:fence_ipmilan): Started overcloud-controller-1
stonith-fence_kdump-e4434b4bc819 (stonith:fence_kdump): Started overcloud-controller-2
[root@overcloud-controller-0 ]# pcs stonith level
Target: overcloud-controller-0
Level 1 - stonith-fence_ipmilan-e4434b4bc819
Level 2 - stonith-fence_kdump-e4434b4bc819
Change-Id: I42033be840ba41e9944af65815a63059834144e9
The tests were failing under puppet 6 due to some missing hieradata.
This change pulls in the now seperated selinux and augeas core modules
and adds the missing bootstrap node hieradata.
It also update data structure testing for haproxy testing.
Depends-On: https://review.opendev.org/#/c/655273/
Change-Id: Id59f3759652d8c1efea46918a9dc5c84fac361e3
This is managed via ansible now and should no longer be managed via
puppet since we need to have it setup prior to configuring all the
containers items.
Change-Id: Id8d340072ec2941b99b5bc3c6a0511af506ea50b
Depends-On: https://review.opendev.org/#/c/653625/
Add file to the reno documentation build to show release notes for
stable/stein.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/stein.
Change-Id: I3ebb1467744db803b645972b08225e649579807d
Sem-Ver: feature
When using ovn provider unless set, it would try to
connect to 127.0.0.1.
Change-Id: If8eb685dd21791b65845afd44fb483592b8bcc0c
Depends-On: https://review.openstack.org/653673
Closes-Bug: #1825146
In order to get a more complete container logging, we now enable
the file logging for the podman containers.
This will output container stdout/stderr in a file located in the
new /var/log/containers/stdouts location.
This follows the other efforts already made with paunch[1] and
docker-puppet.py (now named container-puppet.py)[2]
Notes:
- podman supports only "json-file", allowing to push files in the
location we want via the "path" log option
- docker doesn't have the "path" log option and push its log in
/var/lib/docker/containers/ID/ID-json.log - unusable since it's
destroyed upon container removal.
[1] https://review.openstack.org/635437
[2] https://review.openstack.org/635438
Change-Id: Ibaa8bca52ea2f68afa1effc989b04d2e6213813a
This commit extends the fencing class allowing operators to use
fence_rhevm for nodes running on oVirt / RHV.
Change-Id: I1499ef2efce2b5708262d587bf5786a329e10b09
The 4.2.x was apparently removed at some point, and this makes the
unit tests fails.
This patch will need to be backported down to Queens.
Change-Id: I6a5a0541d2cccc2e210954c4d3b3c45d24d1d649
Closes-Bug: #1823838
It seems that CentOS 7 does not have C.UTF-8 locale. Since we need
UTF-8-based locale, use en_US.UTF-8 instead.
Change-Id: I25d2b9a227a7c5de127bdfd9d2f387be9eea01e0
Partial-Bug: #1823062
