summaryrefslogtreecommitdiffstats
path: root/playbooks/common/openshift-cluster/upgrades
Commit message (Collapse)AuthorAgeFilesLines
...
* Merge pull request #5508 from sdodson/disable-image-streamsOpenShift Merge Robot2017-09-281-1/+3
|\ | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Allow examples management to be disabled By setting openshift_install_examples=false the image stream and quick start templates will not be installed https://trello.com/c/zLaSgxig/436-2-customers-need-a-way-to-opt-out-of-openshift-ansible-template-and-imagestream-mangement Fixes #5061
| * Allow examples management to be disabledScott Dodson2017-09-221-1/+3
| |
* | Merge pull request #5549 from ingvagabund/fix-etcd-backup-tagOpenShift Merge Robot2017-09-271-1/+1
|\ \ | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue evaluate etcd_backup_tag variable Bug: 1495545
| * | evaluate etcd_backup_tag variableJan Chaloupka2017-09-271-1/+1
| | |
* | | Merge pull request #5518 from ingvagabund/set-quota-backend-bytes-explicitlyOpenShift Merge Robot2017-09-272-6/+6
|\ \ \ | |/ / |/| | | | | | | | | | | | | | Automatic merge from submit-queue set the etcd backend quota to 4GB by default Bug: 1492891
| * | Set the etcd backend quota to 4GB by defaultJan Chaloupka2017-09-262-6/+6
| | |
* | | Merge pull request #5470 from ingvagabund/consolidate-etcd-common-roleOpenShift Merge Robot2017-09-262-9/+11
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue Consolidate etcd common role The last PR toward a single etcd role
| * | | consolidate etcd_common roleJan Chaloupka2017-09-252-9/+11
| | | |
* | | | make difference filter output a list for Python3Jan Chaloupka2017-09-262-3/+3
| |/ / |/| |
* | | Merge pull request #5520 from ingvagabund/check-etcd-storage-backendOpenShift Merge Robot2017-09-252-0/+26
|\ \ \ | |/ / |/| | | | | | | | | | | | | | Automatic merge from submit-queue check if the storage backend is set to etcd3 before upgrading to 3.7 SSIA
| * | check if the storage backend is set to etcd3 before upgrading to 3.7Jan Chaloupka2017-09-252-0/+26
| | |
* | | Merge pull request #5451 from ingvagabund/consolidate-etcd-upgradeOpenShift Merge Robot2017-09-253-15/+21
|\ \ \ | |/ / |/| | | | | | | | | | | | | | Automatic merge from submit-queue Consolidate etcd upgrade Consolidates `etcd_upgrade` into the `etcd` role.
| * | consolidate etcd_upgrade roleJan Chaloupka2017-09-213-15/+21
| | |
* | | Merge pull request #5413 from ingvagabund/disable-excluders-after-pre-checksOpenShift Merge Robot2017-09-233-20/+20
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue Move some pre-checks before excluders are disabled Some pre-checks needs an OCP version which is detected by a set of tasks that need the excluders to be disabled. So at the best I can move some pre-checks before the excluders are disabled. However, there will be still some checks that can fail with excluders updated to the newer version. Bug: 1484304
| * | | disable excluders after all pre-checksJan Chaloupka2017-09-213-20/+20
| | | |
* | | | Remove debugging statements and pause moduleScott Dodson2017-09-221-3/+0
| |_|/ |/| | | | | | | | | | | How on earth did the bot merge this? The upgrade test should've stalled indefinitely.
* | | Merge pull request #5478 from sdodson/bz1490677OpenShift Merge Robot2017-09-222-4/+10
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue Default openshift_pkg_version to full version-release during upgrades Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1490677 The versioning scheme for 3.7 pre-releases has changed and now all versions are 3.7.0 and the release is incremented on builds, ie: 3.7.0-0.124.0 upgraded to 3.7.0-0.125.0. If we know we're an upgrade and they haven't requested a specific package version defer the defaulting of openshift_pkg_version until the upgrade playbooks and there set it to the available version including the release.
| * | Default openshift_pkg_version to full version-release during upgradesScott Dodson2017-09-202-4/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1490677 The versioning scheme for 3.7 pre-releases has changed and now all versions are 3.7.0 and the release is incremented on builds, ie: 3.7.0-0.124.0 upgraded to 3.7.0-0.125.0. If we know we're an upgrade and they haven't requested a specific package version defer the defaulting of openshift_pkg_version until the upgrade playbooks and there set it to the available version including the release.
* | | Merge pull request #5474 from simo5/noreconcileOpenShift Merge Robot2017-09-201-4/+3
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue Do not reconcile in >= 3.7 Starting with 3.7 we use kube's RBAC which happens to do a forceful reconcile at server startup. Explicit reconciles are not needed anymore.
| * | | Do not reconcile in >= 3.7Simo Sorce2017-09-201-4/+3
| | |/ | |/| | | | | | | | | | | | | | | | | | | Starting with 3.7 we use kube's RBAC which happens to do a forceful reconcile at server startup. Explicit reconciles are not needed anymore. Also drop obsolete version checks and simplify 'when' conditional Signed-off-by: Simo Sorce <simo@redhat.com>
* | | Merge pull request #5357 from ↵OpenShift Merge Robot2017-09-204-0/+16
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | juanvallejo/jvallejo/add-health-checks-upgrade-path Automatic merge from submit-queue add health checks 3_6,3_7 upgrade path Related BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1483931 Adds health checks to `upgrade_control_plane` and `upgrade_nodes` in 3_6 and 3_7. cc @sosiouxme @rhcarvalho @brenton
| * | | add health checks 3_6,3_7 upgrade pathjuanvallejo2017-09-114-0/+16
| | | |
* | | | Merge pull request #5014 from ↵OpenShift Merge Robot2017-09-201-0/+1
|\ \ \ \ | |_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | juanvallejo/jvallejo/add-additonal-checks-upgrade-path Automatic merge from submit-queue Adding additonal checks upgrade path Depends on https://github.com/openshift/openshift-ansible/pull/4960 TODO - Possibly handle `upgrade` playbook context on `etcd_volume` check cc @sosiouxme @rhcarvalho
| * | | add additional preflight checks to upgrade pathjuanvallejo2017-08-281-0/+1
| | | |
* | | | Cleanup old deployment typesMichael Gugino2017-09-201-2/+2
| |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, openshift-ansible supported various types of deployments using the variable "openshift_deployment_type" Currently, openshift-ansible only supports two deployment types, "origin" and "openshift-enterprise". This commit removes all logic and references to deprecated deployment types.
* | | more retries on repoquery_cmdLuke Meyer2017-09-191-0/+4
| | |
* | | openshift_sanitize_inventory: Check for required varsSteve Milner2017-09-151-15/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | Moved the checks for osm_cluster_network_cidr, osm_host_subnet_length, openshift_portal_net from upgrade to openshift_sanitize_inventory as we now consider it a required variable for install, updrade, or scale up. Signed-off-by: Steve Milner <smilner@redhat.com>
* | | Merge pull request #5389 from tremble/storage_migrationScott Dodson2017-09-141-9/+9
|\ \ \ | | | | | | | | Don't assume storage_migration control variables are already boolean
| * | | Don't assume storage_migration control variables are already booleanMark Chappell2017-09-131-9/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | openshift_upgrade_pre_storage_migration_enabled openshift_upgrade_pre_storage_migration_fatal openshift_upgrade_post_storage_migration_enabled openshift_upgrade_post_storage_migration_enabled because the 4 variables are not already defaulted/evaluated there's no guarantee that they're actually the boolean type at this point. Example: if they're passed in on the command line
* | | | Merge pull request #5386 from ashcrow/fix-wording-in-upgrade-noticeOpenShift Bot2017-09-131-1/+1
|\ \ \ \ | | | | | | | | | | Merged by openshift-bot
| * | | | upgrade: Updates warning on missing required variablesSteve Milner2017-09-121-1/+1
| |/ / / | | | | | | | | | | | | Signed-off-by: Steve Milner <smilner@redhat.com>
* / / / double the required disk space for etcd backupJan Chaloupka2017-09-121-1/+1
|/ / /
* | | Merge pull request #5256 from ashcrow/1451023Scott Dodson2017-09-111-0/+15
|\ \ \ | |_|/ |/| | upgrade: Verify required network items are set
| * | upgrade: Verify required network items are setSteve Milner2017-09-081-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When upgrading osm_cluster_network_cidr, osm_host_subnet_length, and openshift_portal_net must be set to avoid SDN initialization errors. This was found when the default parameters were changed between Openshift versions. This meant users who upgraded and did not specify either mentioned variable at install/upgrade time ended up getting SDN errors post upgrade. When osm_cluster_network_cidr, osm_host_subnet_length, and openshift_portal_net are not set the upgrade will fail telling the user that the variables must be set and how to find the current values in the current install. References: https://github.com/openshift/openshift-ansible/commit/b50b4ea0b03feb9431abd7294fe4fb6b549ddfc0 Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1451023
* | | Fix include path for docker upgrade tasksRussell Teague2017-09-081-2/+4
|/ /
* | Remove openshift-commonMichael Gugino2017-09-062-2/+0
| | | | | | | | | | | | | | | | | | Most of this role's purpose was to set facts. The vast majority of these facts were simply redefining user-supplied variables. This commit also removes various artifacts leftover from previous versions, as well as variables that seem to be entirely unused.
* | Merge pull request #5259 from mtnbikenc/fix-upgrade-auth-checkRussell Teague2017-08-311-0/+1
|\ \ | | | | | | [BZ1486450] Only run migrate auth for < 3.7
| * | Only run migrate auth for < 3.7Russell Teague2017-08-291-0/+1
| | |
* | | Merge pull request #5247 from mgugino-upstream-stage/fix-master-upgradesOpenShift Bot2017-08-301-4/+1
|\ \ \ | | | | | | | | Merged by openshift-bot
| * | | Fix openshift_master upgradeMichael Gugino2017-08-291-4/+1
| |/ / | | | | | | | | | | | | | | | | | | | | | Currently, openshift_master upgrade play imports tasks directly from the openshift_master role. This method does not honor role defaults. This commit changes sets openshift_master_config_dir if undefined.
* / / Test: Fail on entry point playbooks in commonRussell Teague2017-08-2920-17/+17
|/ /
* | Merge pull request #5182 from mtnbikenc/upgrade-orphansOpenShift Bot2017-08-261-13/+0
|\ \ | | | | | | Merged by openshift-bot
| * | Remove unused upgrade playbookRussell Teague2017-08-231-13/+0
| |/
* / Upgrade check for OpenShift authorization objectsRussell Teague2017-08-241-0/+10
|/ | | | | | | Adds task to run `oc adm migrate authorization` to ensure OpenShift authorization objects are in sync. Fixes #5021
* Remove orphan filesRussell Teague2017-08-152-15/+0
|
* Fix syntax for when statementRodolfo Carvalho2017-08-1016-44/+66
| | | | | | | | Without that, playbook runs print warnings such as this: [WARNING]: when statements should not include jinja2 templating delimiters such as {{ }} or {% %}. Found: {{ g_etcd_hosts is not defined and g_new_etcd_hosts is not defined}}
* Merge pull request #4832 from smarterclayton/stop_using_old_modeOpenShift Bot2017-08-094-11/+5
|\ | | | | Merged by openshift-bot
| * Remove remaining references to openshift-master.serviceClayton Coleman2017-08-082-2/+0
| | | | | | | | Prevents playbooks from accidentally restarting the master service.
| * Disable old openshift-master.service on upgradeClayton Coleman2017-08-081-0/+3
| |
| * Remove the origin-master.service and associated filesClayton Coleman2017-08-081-9/+2
| | | | | | | | | | | | From now on, all master configurations use the api / controller split, regardless of HA mode or previous configuration. This will be our only supported configuration starting in 3.7 or 3.8.