| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| | |
Fix docker rpm upgrade install task wording
|
| | |
| |
| |
| | |
This commit corrects wording of task name.
|
| | |
| |
| |
| |
| |
| | |
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
|
| | | |
| | |
| | |
| | | |
This ensures required labels for master would be set
|
| |\ \ \
| |_|/
|/| | |
Update code to not fail when rc != 0
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Automatic merge from submit-queue.
Es 5.x opt in
FYI @richm @jcantrill
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
parameterize various master/infra scale group bits
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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)
|
| | | |_|_|/
| |/| | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
cri-o: export variables defined in crio-network
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
so that the cri-o process can use them.
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1529478
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
| | |_|/ / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Created by command:
/usr/bin/tito tag --debug --accept-auto-changelog --keep-version --debug
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
add S3 bucket cleanup
|
| | | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | | |
Default to just cleaning out all the objects in the S3 bucket (IFF openshift_aws_create_s3 is 'true').
If you really, trully want to delete the S3 bucket and free up the bucket name, you can set openshift_aws_really_delete_s3_bucket to 'true' ('false' by default).
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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.
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Automatic merge from submit-queue.
check for restart on atomic
fix atomic host storage
|
| | | |/ / / /
| |/| | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Automatic merge from submit-queue.
Parameterize user and disable_root options in cloud config
This commit will allow the user to login as root. By default the
user is set to openshift and disable_root is set to true.
|
| | | |_|/ / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | | |
This commit will allow the user to login as root. By default, the
user is set to openshift and disable_root is set to true.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Created by command:
/usr/bin/tito tag --debug --accept-auto-changelog --keep-version --debug
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Automatic merge from submit-queue.
Adding requirements for logging and metrics
To address
https://github.com/openshift/openshift-ansible/issues/5293
|
| | |/ / / / / |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Automatic merge from submit-queue.
Don't use 'omit' for package module
'name' param is required and can't be skipped. 'when' is used instead
Fixes #6968
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
'name' param is required and can't be skipped. 'when' is used instead
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Automatic merge from submit-queue.
Upgrade playbook improvements
Two changes in this PR:
* Avoid duplication in upgrade.yml - it now would simply run upgrade_control_plane and upgrade_nodes playbooks
* Restart controllers instead of start/stop if restart mode is 'services'
* For 'system' restart mode controllers are disabled before master upgrade and re-enabled after upgrades are finished
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
mode is system
This removes a start/stop after control plane upgrade
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
upgrade
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Created by command:
/usr/bin/tito tag --debug --accept-auto-changelog --keep-version --debug
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Add missing tasks file
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Was errantly removed in 4f7d963986a1e28ecc6abd15532b0c1aece99be1
|
