| Age | Commit message (Collapse) | Author |
|
Automatic merge from submit-queue.
3.9 upgrade: fix typos in restart masters procedure
* 'rolling_restart_mode' should be 'services', not 'service'
* use 'state: restarted' to properly restart services
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1540054
Signed-off-by: Vadim Rutkovsky <vrutkovs@redhat.com>
|
|
Correct master certificates list checked by openshift_master_certificates
|
|
Automatic merge from submit-queue.
Quick installer: run prerequistes first and update path to main playbook
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1542895
|
|
Automatic merge from submit-queue.
tag fix without ose-
incorrect tag when trying to deploy efs
|
|
Created by command:
/usr/bin/tito tag --debug --accept-auto-changelog --keep-version --debug
|
|
Automatic merge from submit-queue.
GlusterFS: Minor documentation update
|
|
Automatic merge from submit-queue.
Make sure to include upgrade_pre when upgrading master nodes
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1542399
|
|
* 'rolling_restart_mode' should be 'services', not 'service'
* use 'state: restarted' to properly restart services
Signed-off-by: Vadim Rutkovsky <vrutkovs@redhat.com>
|
|
Allow OVS 2.7 in OCP 3.10
|
|
|
|
|
|
|
|
|
|
Created by command:
/usr/bin/tito tag --debug --accept-auto-changelog --keep-version --debug
|
|
add deprovisioning for ELB (and IAM certs)
|
|
Automatic merge from submit-queue.
[6632] fix indentation of terminationGracePeriodSeconds var
This is a PR to fix [6632](https://github.com/openshift/openshift-ansible/issues/6632).
|
|
Automatic merge from submit-queue.
health checks: tolerate ovs 2.9
fixes https://bugzilla.redhat.com/show_bug.cgi?id=1541313
|
|
|
|
Initial support for 3.10
|
|
Fix docker rpm upgrade install task wording
|
|
Created by command:
/usr/bin/tito tag --debug --accept-auto-changelog --keep-version --debug
|
|
|
|
Upgrades: pass openshift_manage_node_is_master to master nodes during upgrade
|
|
Update code to not fail when rc != 0
|
|
|
|
This commit corrects wording of task name.
|
|
Automatic merge from submit-queue.
Es 5.x opt in
FYI @richm @jcantrill
|
|
parameterize various master/infra scale group bits
|
|
Automatic merge from submit-queue.
bug 1540799: openshift_prometheus: update alertmanager config file flag
Prometheus alertmanager as of 0.13.0 requires double dashes (posix) for
command line flags. The double dashes should be backwards compat
with earlier versions of alertmanager.
|
|
Automatic merge from submit-queue.
daemonset config modifications to allow monitoring.
Modifications that allow custom secrets, configmaps, and shared setup between containers for config and monitoring.
|
|
Automatic merge from submit-queue.
Move cert SAN update logic to openshift-etcd
Recent additions for checking certificate SAN validation were added to the upgrade playbooks and should be moved to the openshift-etcd playbooks to ensure this check is performed when the openshift-etcd upgrade playbook is run directly, vice only when running a full control plane upgrade. Additionally, the formerly included playbook for redeploying certificates called the main entry point playbook which caused the initialization playbooks to be called twice.
|
|
Use rollout instead of deploy (deprecated)
|
|
This ensures required labels for master would be set
|
|
cri-o: export variables defined in crio-network
|
|
Created by command:
/usr/bin/tito tag --debug --accept-auto-changelog --keep-version --debug
|
|
|
|
|
|
s.t. masters do not incorrectly report that master certs are missing.
|
|
|
|
|
|
|
|
Prometheus alertmanager as of 0.13.0 requires double dashes (posix) for
command line flags. The double dashes should be backwards compat
with earlier versions of alertmanager.
|
|
Automatic merge from submit-queue.
Fix broken softlink
I think d3fefc32a727fe3c13159c4e9fe4399f35b487a8 moved dirs and failed to correct the symlinks inside
|
|
Moving upgrade sg playbook to 3.9
|
|
|
|
allow selectively overriding master scale group bits:
instance type: openshift_aws_master_group_instance_type
scale group min size: openshift_aws_master_group_min_size
scale group max size: openshift_aws_master_group_max_size
scale group desired size: openshift_aws_master_group_desired_size
and overriding infra scale group bits:
instance type: openshift_aws_infra_group_instance_type
scale group min size: openshift_aws_infra_group_min_size
scale group max size: openshift_aws_infra_group_max_size
scale group desired size: openshift_aws_infra_group_desired_size
and overriding compute scale group bits:
instance type: openshift_aws_compute_group_instance_type
scale group min size: openshift_aws_compute_group_min_size
scale group max size: openshift_aws_compute_group_max_size
scale group desired size: openshift_aws_compute_group_desired_size
also consolodate the health check for master/infra/compute since they are all the same
|
|
add S3 bucket cleanup
|
|
Automatic merge from submit-queue.
dynamic inventory bug when group exists but its empty
@jarrpa output from my test for the gluster block
I use dynamic inventory. And the result of this is that ansible see all possible groups available, but some of them are empty [1]. Because group exists, fist condition is evaluated as true and it fails with the array is an empty error...
```
...
'all': [u'54.144.5.175',
u'52.200.175.54',
u'54.237.208.252',
u'52.55.224.72',
u'52.207.103.246',
u'34.227.95.191',
u'34.238.127.160'],
u'bastion': [u'34.227.95.191'],
u'bastion.0': [u'34.227.95.191'],
u'etcd': [u'34.238.127.160'],
u'glusterfs': [u'52.200.175.54', u'52.207.103.246', u'54.144.5.175'],
u'glusterfs.0': [u'52.200.175.54'],
u'glusterfs.1': [u'52.207.103.246'],
u'glusterfs.2': [u'54.144.5.175'],
u'glusterfs_registry': [],
u'infra': [u'52.55.224.72'],
u'infra.0': [u'52.55.224.72'],
u'masters': [u'34.238.127.160'],
u'masters.0': [u'34.238.127.160'],
...
```
|
|
Fix version handling in 3.8/3.9 control plane upgrades
|
|
Automatic merge from submit-queue.
remove openshift_upgrade_{pre,post}_storage_migration_enabled from failed_when
When `openshift_upgrade_{pre,post}_storage_migration_enabled` was
enabled, `oadm migrate storage` was called. After that, failed_when is
evaluated, so `openshift_upgrade_{pre,post}_storage_migration_enabled`
is always true and not necessary in the failed_when list. This patch
remove them from failed_when list.
|