summaryrefslogtreecommitdiffstats
path: root/playbooks/common
Commit message (Collapse)AuthorAgeFilesLines
* Move cert SAN update logic to openshift-etcdRussell Teague2018-02-051-23/+0
|
* Merge pull request #6980 from mtnbikenc/fix-upgradesScott Dodson2018-02-043-9/+9
|\ | | | | Fix version handling in 3.8/3.9 control plane upgrades
| * Fix version handling in 3.8/3.9 control plane upgradesRussell Teague2018-02-023-9/+9
| |
* | remove openshift_upgrade_{pre,post}_storage_migration_enabled from failed_whenKenjiro Nakayama2018-02-031-3/+0
| |
* | Merge pull request #6958 from vrutkovs/rework-full-upgradeOpenShift Merge Robot2018-02-023-56/+16
|\ \ | |/ |/| | | | | | | | | | | | | | | | | 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
| * Disable master controllers before upgrade and re-enable those when restart ↵Vadim Rutkovsky2018-01-312-6/+14
| | | | | | | | | | | | mode is system This removes a start/stop after control plane upgrade
| * upgrade: run upgrade_control_plane and upgrade_nodes playbooks during full ↵Vadim Rutkovsky2018-01-311-50/+2
| | | | | | | | upgrade
* | Upgrade to migrate to using push to DNS for registries.Kenny Woodson2018-02-011-0/+16
| |
* | Merge pull request #6955 from vrutkovs/upgrade-regex-version-matchOpenShift Merge Robot2018-02-011-1/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue. upgrades: use openshift_version as a regexp when checking openshift.common.version This would fix errors like 'Master running 3.9.0 must be upgraded to 3.9* before node upgrade can be run' during the upgrade Signed-off-by: Vadim Rutkovsky <vrutkovs@redhat.com>
| * | upgrades: use openshift_version as a regexp when checking ↵Vadim Rutkovsky2018-01-311-1/+1
| |/ | | | | | | | | | | | | | | | | openshift.common.version This would fix errors like 'Master running 3.9.0 must be upgraded to 3.9* before node upgrade can be run' during the upgrade Signed-off-by: Vadim Rutkovsky <vrutkovs@redhat.com>
* | Merge pull request #6876 from mgugino-upstream-stage/fix-restart-master-playScott Dodson2018-02-011-2/+0
|\ \ | | | | | | Remove master_ha bool checks
| * | Remove master_ha bool checksMichael Gugino2018-01-251-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Most of these checks are no longer applicable to the tasks on which they are applied. This commit removes incorrect ha checks to ensure services are restarted at appropriate times. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1500897
* | | Ignore openshift_pkg_version during 3.8 upgradeRussell Teague2018-01-301-0/+1
| |/ |/| | | | | | | | | | | | | | | | | Version 3.8 is an intermediate step when upgrading to 3.9 and openshift_pkg_version may be set in the inventory for 3.9. This will ensure there is not a conflict between the intermediate step and the final version requested. Bug 1540108 https://bugzilla.redhat.com/show_bug.cgi?id=1540108
* | Correct 3.7 to 3.9 upgrade openshift_image_tagMichael Gugino2018-01-261-3/+24
| | | | | | | | | | | | | | | | | | | | | | Due to complexities upgrading two versions at the same time, openshift_image_tag was being set incorrectly during control_plane upgrades. This commit ensures that openshift_image_tag is set correctly during this process. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1536839
* | Merge pull request #6821 from spadgett/remove-asset-configScott Dodson2018-01-262-1/+9
|\ \ | | | | | | Remove old assetConfig from master-config.yaml
| * | Remove old assetConfig from master-config.yamlSamuel Padgett2018-01-252-1/+9
| |/ | | | | | | | | | | | | | | The `assetConfig` is no longer used now that the console is split into its own pod. - Remove `assetConfig` on upgrades to 3.9 - Stop writing logging and metrics URLs to assetConfig for 3.9
* | Merge pull request #6859 from abutcher/bz1536217OpenShift Merge Robot2018-01-252-0/+46
|\ \ | |/ |/| | | | | Automatic merge from submit-queue. Bug 1536217: Need to validate etcd serving certs before 3.9 upgrade
| * Redeploy etcd certificates during upgrade when etcd hostname not present in ↵Andrew Butcher2018-01-242-0/+46
| | | | | | | | etcd serving cert SAN.
* | Merge pull request #6849 from vrutkovs/label-masters-with-upstream-standardOpenShift Merge Robot2018-01-252-20/+10
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Label masters with node-role.kubernetes.io/master This is controlled by `openshift_master_node_label` var in openshift_manage_node Related to https://bugzilla.redhat.com/show_bug.cgi?id=1535673
| * | Label masters with node-role.kubernetes.io/master. This PR also sets these ↵Vadim Rutkovsky2018-01-242-20/+10
| | | | | | | | | | | | | | | | | | | | | | | | labels and scheduling status during upgrades Signed-off-by: Vadim Rutkovsky <vrutkovs@redhat.com>
* | | Merge pull request #6842 from ↵Scott Dodson2018-01-249-1/+10
|\ \ \ | | | | | | | | | | | | | | | | mgugino-upstream-stage/protect-upgrade-master-version Protect master installed version during node upgrades
| * | | Protect master installed version during node upgradesMichael Gugino2018-01-239-1/+10
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | Master version is unprotected during all upgrades. During node-only upgrades, master version should remain protected to ensure correct image tag is set for node upgrades. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1536839
* | | Merge pull request #6541 from smarterclayton/move_gcp_inScott Dodson2018-01-242-0/+72
|\ \ \ | |/ / |/| | Allow openshift-ansible image to deploy to GCP
| * | Split control plane and component install in deploy_clusterClayton Coleman2018-01-232-0/+72
| | |
* | | Merge pull request #6812 from sdodson/bz1396350OpenShift Merge Robot2018-01-231-1/+1
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Ensure that node names are lowerecased before matching The name field is always lowercase whereas the nodename may not have been in the past. Ensure that we lowercase it before looking for matching nodes. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1396350
| * | Ensure that node names are lowerecased before matchingScott Dodson2018-01-221-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | The name field is always lowercase whereas the nodename may not have been in the past. Ensure that we lowercase it before looking for matching nodes. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1396350
* | | Install base_packages earlierMichael Gugino2018-01-221-1/+2
| |/ |/| | | | | | | | | | | | | | | | | | | | | Currently, openshift_facts requires pyyaml to be installed. This package is installed via init/base_packages.yml, which is currently called after init/facts.yml. This results in a situation where installs will fail due to missing python dependency. This commit splits init/facts.yml into two, and allows base_packages.yml to be run before the openshift_facts.py plugin is executed.
* | Fix node scaleup playsMichael Gugino2018-01-184-4/+4
|/ | | | | | | | Currently, users have no way to run preqrequisites.yml on just newly added nodes during scaleup. This commit ensures only the new nodes are changed during scaleup as well as ensure prerequisites are run.
* Add call to 3.8 playbook in 3.9 upgradeScott Dodson2018-01-175-6/+53
|
* Remove 3.8 and 3.9 specific steps right nowScott Dodson2018-01-175-27/+0
|
* Exclude 3.9 packages during 3.8 upgradeScott Dodson2018-01-172-2/+2
| | | | | | | | There are some obsoletes in 3.9 packages which lead yum to upgrade directly from 3.7 to 3.9 when you ask for 3.8 packages while 3.9 repos are enabled. Since we'd like to allow people to run one playbook to upgrade from 3.7 to 3.8 to 3.9 we need to exclude those packages when upgrading to 3.8
* fix typosScott Dodson2018-01-172-2/+2
|
* fix bug 1534271MENG Weihua2018-01-151-4/+4
|
* Install web console on upgradeSamuel Padgett2018-01-111-3/+9
|
* Merge pull request #5080 from sdodson/drain-timeoutsOpenShift Merge Robot2018-01-104-11/+29
|\ | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Add the ability to specify a timeout for node drain operations A timeout to wait for nodes to drain pods can be specified to ensure that the upgrade continues even if nodes fail to drain pods in the allowed time. The default value of 0 will wait indefinitely allowing the admin to investigate the root cause and ensuring that disruption budgets are respected. In practice the `oc adm drain` command will eventually error out, at least that's what we've seen in our large online clusters, when that happens a second attempt will be made to drain the nodes, if it fails again it will abort the upgrade for that node or for the entire cluster based on your defined `openshift_upgrade_nodes_max_fail_percentage`. `openshift_upgrade_nodes_drain_timeout=0` is the default and will wait until all pods have been drained successfully `openshift_upgrade_nodes_drain_timeout=600` would wait for 600s before moving on to the tasks which would forcefully stop pods such as stopping docker, node, and openvswitch.
| * Add the ability to specify a timeout for node drain operationsScott Dodson2018-01-104-11/+29
| |
* | Merge pull request #6666 from sdodson/fix_client_binaryScott Dodson2018-01-103-3/+8
|\ \ | | | | | | Ensure that openshift_facts role is imported whenever we rely on
| * | Ensure that openshift_facts role is imported whenever we rely onScott Dodson2018-01-093-3/+8
| | | | | | | | | | | | openshift_client_binary
* | | Merge pull request #6647 from ↵Scott Dodson2018-01-101-4/+4
|\ \ \ | | | | | | | | | | | | | | | | vrutkovs/3.9-upgrades-remove-openshift.common.service_type 3.9 upgrade: remove openshift.common.service_type
| * | | 3.9 upgrade: remove openshift.common.service_typeVadim Rutkovsky2018-01-081-4/+4
| | |/ | |/| | | | | | | See eb6b20fc9183cc2aae424c72efd1191b99110a93
* | | Merge pull request #6674 from mgugino-upstream-stage/remove-becomes2Scott Dodson2018-01-102-4/+5
|\ \ \ | | | | | | | | Remove become statements
| * | | Chmod temp dirs created on localhostMichael Gugino2018-01-091-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After remove become:no statements on local_action tasks, we need to ensure that the proper file permssions are applied to local temp directories. This reason for this is that the 'fetch' module does not use 'become' for the localhost, just the remote host. Additionally, users may not wish for the localhost to become during a fetch. local_action will execute with whatever permissions are specified in inventory or via cli.
| * | | Remove become statementsMichael Gugino2018-01-092-4/+0
| | |/ | |/| | | | | | | | | | This commit removes become:no statements that break the installer in various ways.
* / | Limit host group scope on control-plane upgradesMichael Gugino2018-01-095-0/+24
|/ / | | | | | | | | This commit limits common init code to exclude oo_nodes_to_config during upgrade_control_plane runs.
* | Merge pull request #6549 from mgugino-upstream-stage/node-meta-depends2OpenShift Merge Robot2018-01-082-6/+0
|\ \ | |/ |/| | | | | | | | | | | Automatic merge from submit-queue. Remove last of openshift_node role meta-depends Remove last non-taskless meta-depends from openshift_node role.
| * Remove last of openshift_node role meta-dependsMichael Gugino2018-01-022-6/+0
| | | | | | | | | | | | | | | | Remove last non-taskless meta-depends from openshift_node role. Remove variable 'openshift_node_upgrade_in_progress' as it is no longer used.
* | Migrate to import_role for static role inclusionScott Dodson2018-01-056-11/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In Ansible 2.2, the include_role directive came into existence as a Tech Preview. It is still a Tech Preview through Ansible 2.4 (and in current devel branch), but with a noteable change. The default behavior switched from static: true to static: false because that functionality moved to the newly introduced import_role directive (in order to stay consistent with include* being dynamic in nature and `import* being static in nature). The dynamic include is considerably more memory intensive as it will dynamically create a role import for every host in the inventory list to be used. (Also worth noting, there is at the time of this writing an object allocation inefficiency in the dynamic include that can in certain situations amplify this effect considerably) This change is meant to mitigate the pressure on memory for the Ansible control host. We need to evaluate where it makes sense to dynamically include roles and revert back to dynamic inclusion if and where it makes sense to do so.
* | Remove references to deployment_typeMichael Gugino2017-12-215-9/+4
| | | | | | | | | | | | | | Move openshift_deployment_type check into sanity_check action plugin. Remove compatibility for deployment_type. deployment_type has been deprecated for some time now.
* | Move validate_hosts to prerequisites.ymlMichael Gugino2017-12-201-3/+0
|/ | | | | | Move more checks outside of init/main.yml for speeding up upgrades and other operational plays that need to run.
* Remove openshift.common.{is_atomic|is_containerized}Michael Gugino2017-12-2010-20/+20
| | | | | We set these variables using facts in init, no need to duplicate the logic all around the codebase.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 23:26:48 +0000