You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Tree:
885715855b
master
stable/train
stable/victoria
stable/wallaby
0.0.1
0.1.0
0.1.1
0.2.0
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.5.6
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.7.7
0.7.8
0.7.9
0.8.0
0.8.1
0.8.10
0.8.11
0.8.12
0.8.13
0.8.14
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
0.8.8
0.8.9
1.0.0
10.0.0
10.1.0
10.2.0
10.3.0
10.4.0
10.5.0
10.6.0
10.6.1
10.6.2
11.0.0
11.1.0
11.2.0
11.3.0
11.3.1
11.4.0
11.5.0
11.6.0
12.0.0
12.1.0
12.2.0
12.3.0
12.4.0
12.4.1
12.4.2
12.4.3
12.4.4
12.4.5
12.4.6
12.5.0
12.6.0
12.7.0
13.0.0
13.1.0
13.2.0
13.3.0
13.4.0
13.5.0
13.6.0
14.0.0
14.1.0
14.1.1
14.1.2
14.2.0
14.3.0
15.0.0
15.1.0
16.0.0
2.0.0
2.1.0
2.2.0
5.0.0
5.0.0.0b1
5.0.0.0b2
5.0.0.0b3
5.0.0.0rc1
5.0.0.0rc2
5.0.0.0rc3
5.1.0
5.2.0
5.3.0
5.3.1
5.3.10
5.3.11
5.3.12
5.3.13
5.3.2
5.3.3
5.3.4
5.3.5
5.3.6
5.3.7
5.3.8
5.3.9
6.0.0
6.0.0.0b1
6.0.0.0b2
6.0.0.0rc1
6.0.0.0rc2
6.1.0
6.2.0
6.2.1
6.2.10
6.2.11
6.2.12
6.2.13
6.2.14
6.2.15
6.2.16
6.2.2
6.2.3
6.2.4
6.2.5
6.2.6
6.2.7
6.2.8
6.2.9
7.0.0
7.0.0.0b1
7.0.0.0b2
7.0.0.0b3
7.0.0.0rc1
7.0.0.0rc2
7.0.1
7.0.10
7.0.11
7.0.12
7.0.13
7.0.14
7.0.15
7.0.16
7.0.17
7.0.18
7.0.2
7.0.3
7.0.4
7.0.5
7.0.6
7.0.7
7.0.8
7.0.9
8.0.0
8.0.0.0b1
8.0.0.0b2
8.0.0.0b3
8.0.0.0rc1
8.0.1
8.0.2
8.0.3
8.0.4
8.0.5
8.0.6
8.0.7
8.1.0
8.2.0
8.3.0
8.3.1
8.4.0
8.4.1
9.0.0
9.0.0.0b1
9.0.0.0b2
9.0.0.0b3
9.0.0.0b4
9.0.0.0rc1
9.0.0.0rc2
9.1.0
9.2.0
9.3.0
9.4.0
9.4.1
liberty-eol
mitaka-eol
newton-eol
ocata-em
ocata-eol
pike-em
pike-eol
queens-em
queens-eol
rocky-em
rocky-eol
stein-em
stein-eol
train-em
ussuri-em
ussuri-eol
victoria-em
${ noResults }
tripleo-heat-templates/common
The problem we want to selve is that the change https://review.opendev.org/#/c/631486/ (moving iptables creation to the host) never really worked. The reason it never worked and we never noticed is two-fold: A) It ran: -e include ::tripleo::profile::base::haproxy the problem is that without quoting puppet basically does a noop B) Once the quoting is fixed it breaks because 'export FACTER_step' exports a custom fact but does not export a hiera key per-se (so calls to hiera('step') would fail So we add proper quoting only on the variables that are arguments to a parameter so that there is no risk of ansible doing the wrong thing and puppet gets the correct arguments. We also explicitely set the step for hiera in the deploy_steps_tasks. The reason we need it is because in non-HA the iptables rules would be created at step 1. But since the deploy_steps_tasks run before the actual tasks that set the step hieradata.we would get the following error: Error: Function lookup() did not find a value for the name 'step' We can just write out the step hiera key during the deploy_steps_tasks, it will be enforced again shortly afterwards once the common/deploy-steps-tasks.yaml gets invoked. We also switch back to puppet_execute: ::tripleo::profile::base::haproxy even for the pacemaker profile. This was broken by the flattening of the haproxy service (Id55ae44a7b1b5f08b40170f7406e14973fa93639) Co-Authored-By: Luca Miccini <lmiccini@redhat.com> Change-Id: Iab310207ca17a6c596470dda30a39e029c4fe09c Closes-Bug: #1828250 |
3 years ago | |
---|---|---|
.. | ||
services | Introduce scale_tasks | 3 years ago |
container-puppet.py | Gracefully handle empty config json data | 3 years ago |
deploy-steps-tasks.yaml | Evaluating ansible_check_mode as a boolean | 3 years ago |
deploy-steps.j2 | Fix haproxy firewall rules | 3 years ago |
post.j2.yaml | Consolidate puppet/docker deployments with one deploy steps workflow | 5 years ago |