stable/wallaby
stable/train
stable/zed
master
18.0.0
wallaby-em
17.0.0
victoria-eol
victoria-em
13.6.0
ussuri-eol
16.0.0
ussuri-em
12.4.6
15.1.0
13.5.0
14.3.0
12.4.5
stein-eol
13.4.0
14.2.0
queens-eol
15.0.0
12.4.4
14.1.2
train-em
11.6.0
13.3.0
14.1.1
14.1.0
12.4.3
11.5.0
13.2.0
rocky-eol
11.4.0
12.4.2
14.0.0
13.1.0
stein-em
13.0.0
12.4.1
12.7.0
12.6.0
12.5.0
12.4.0
12.3.0
12.2.0
rocky-em
12.1.0
11.3.1
10.6.2
12.0.0
queens-em
11.3.0
11.2.0
8.4.1
9.4.1
10.6.1
pike-eol
ocata-eol
11.1.0
10.6.0
8.4.0
9.4.0
11.0.0
pike-em
7.0.18
10.5.0
ocata-em
8.3.1
9.3.0
10.4.0
8.3.0
10.3.0
9.2.0
8.2.0
9.1.0
8.1.0
10.2.0
10.1.0
10.0.0
9.0.0
8.0.7
7.0.17
9.0.0.0rc2
8.0.6
7.0.16
9.0.0.0rc1
8.0.5
7.0.15
6.2.16
newton-eol
9.0.0.0b4
7.0.14
6.2.15
8.0.4
5.3.13
9.0.0.0b3
8.0.3
6.2.14
7.0.13
5.3.12
6.2.13
7.0.12
8.0.2
9.0.0.0b2
8.0.1
9.0.0.0b1
5.3.11
7.0.11
6.2.12
8.0.0
5.3.10
6.2.11
7.0.10
8.0.0.0rc1
7.0.9
6.2.10
8.0.0.0b3
6.2.9
7.0.8
5.3.9
7.0.7
5.3.8
6.2.8
7.0.6
6.2.7
5.3.7
8.0.0.0b2
7.0.5
5.3.6
6.2.6
6.2.5
7.0.4
5.3.5
7.0.3
6.2.4
5.3.4
8.0.0.0b1
5.3.3
7.0.2
6.2.3
6.2.2
5.3.2
7.0.1
7.0.0
7.0.0.0rc2
6.2.1
5.3.1
7.0.0.0rc1
7.0.0.0b3
6.2.0
7.0.0.0b2
mitaka-eol
6.1.0
5.3.0
2.2.0
7.0.0.0b1
6.0.0
6.0.0.0rc2
6.0.0.0rc1
5.2.0
6.0.0.0b2
liberty-eol
6.0.0.0b1
5.1.0
5.0.0
5.0.0.0rc3
5.0.0.0rc2
5.0.0.0rc1
5.0.0.0b3
2.1.0
5.0.0.0b2
5.0.0.0b1
2.0.0
0.8.14
0.8.13
0.8.12
0.8.11
0.8.10
0.8.9
0.8.8
0.8.7
1.0.0
0.8.6
0.8.5
0.8.4
0.8.3
0.8.2
0.8.1
0.8.0
0.7.9
0.7.8
0.7.7
0.7.6
0.7.5
0.7.4
0.7.3
0.7.2
0.7.1
0.7.0
0.6.4
0.6.3
0.6.2
0.6.1
0.6.0
0.5.6
0.5.5
0.5.4
0.5.3
0.5.2
0.5.1
0.5.0
0.4.4
0.4.3
0.4.2
0.4.1
0.4.0
0.3.4
0.3.3
0.3.2
0.3.1
0.3.0
0.2.0
0.1.1
0.1.0
0.0.1
${ noResults }
3 Commits (master)
Author | SHA1 | Message | Date |
---|---|---|---|
![]() |
019419463f |
Use community.general ansible collection instead of modules
Replace module calls by community.general ansible collection calls. Change-Id: Ie96b3d35cea61370b1f98d7e060d696c4807c6b7 |
2 years ago |
![]() |
d77fe55516 |
Ensure SELinux context persist across restorecon and reboot
Until now, we only relied on the ":z" flag in order to set container volumes label to container_file_t. While it works fine, it has multiple issues: - if an operator runs a restorecon, it might break the container service - if an SELinux related package is updated, it might reset the label, and break the container service - it requires a container stop&start to reset the label to the expected value - in case of deep tree or huge amount of file, relabelling takes time This change ensures the system sets the expected context on the specific locations, instead of following the content of selinux-policy-targeted rulesets. It has an equivalent for some locations in tripleo-ansible repository: https://review.opendev.org/c/openstack/tripleo-ansible/+/782393 Note about swift locations: Since openstack-selinux already sets fcontext rules for, at least, once swift location, we can't override it here. The following openstack-selinux patch is being pushed in order to work around this specific case: https://github.com/redhat-openstack/openstack-selinux/pull/73 Change-Id: Icb7f58004e281b42141c70a9a4895905dc32b45d Resolves: rhbz#1941922 |
2 years ago |
![]() |
bb8cb15d20 |
Update container-config-scripts/ folder content before update_tasks.
Currently, multiple scripts are being stored in /var/lib/container-config-scripts directory if any of theses scripts are being used during the update_tasks the content won't be up to date (or the script will be fully missing if added in a new release), as the content of this folder is being updated during the deploy tasks (step 1), which occurs after all the update_tasks. This patch gathers the tasks responsible for the folder creation and content update into a new playbook named common_container_config_scripts.yaml, this way we can reference the tasks from the deploy-tasks step1 playbook (as it was happening up to now) and invoke them before the update_tasks playbook gets called. Change-Id: I2ac6bb98e1d4183327e888240fc8d5a70e0d6fcb Related-Bug: #1904193 |
2 years ago |