| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Merged by openshift-bot
|
| |
| |
| |
| | |
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1428934
|
|\ \
| | |
| | | |
Merged by openshift-bot
|
| |/ |
|
|/ |
|
|\
| |
| | |
Merged by openshift-bot
|
| | |
|
|\ \
| |/
|/| |
run excluders over selected set of hosts during control_plane/node upgrade
|
| |
| |
| |
| | |
Disable/reset excluders over requested hosts
|
|\ \
| | |
| | | |
Merged by openshift-bot
|
| | | |
|
|\ \ \
| | | |
| | | | |
Merged by openshift-bot
|
| |/ /
| | |
| | |
| | |
| | | |
Without this we were pullining in unbounded dependencies and upgrading
to the latest version available in a repo.
|
|\ \ \
| | | |
| | | | |
Properly fail on empty repoquery version checks
|
| |/ / |
|
|/ /
| |
| |
| |
| |
| |
| | |
In a project where contributors are free to use whatever editor they
want and we have linting tools that verify the proper formatting of
Python files, it should not be required to have a vim-specific line in
Python files.
|
|\ \
| | |
| | | |
move etcdctl.yml from etcd to etcd_common role
|
| |/ |
|
|\ \
| |/
|/| |
Merged by openshift-bot
|
| |
| |
| |
| |
| |
| | |
The openshift_repos role is modified to clean the repo cache on first
run to ensure a clean cache in the situation where the repo files have been
changed manually, such as just prior to upgrades.
|
| |
| |
| |
| |
| |
| | |
* Renaming etcd_hosts_to_* to oo_etcd_hosts_to*
* Moving host group evaluation to evaluate_groups.yml
* Removing duplicate evaluate_groups.yml usage
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
ingvagabund/move-excluder-verification-code-under-excluders-role
[RFE] move excluder upgrade validation tasks under openshift_excluder role
|
| |/ |
|
| | |
|
|/
|
|
|
|
| |
In ansible 2.3 "[WARNING]: when statements should not include jinja2
templating delimiters such as {{ }} or {% %}. Found: {{
g_glusterfs_hosts is not defined }}"
|
|\
| |
| | |
Merged by openshift-bot
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Because containerized installs don't mount /var/lib/origin and we
switched to running the backup inside the container that meant that we
were backing up the etcd data into a directory inside the container
filesystem. Since we have no other volume mounted we need to backup into
/var/lib/etcd.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes
TASK [Copy etcd v3 data store]
*************************************************
fatal: [host.redhat.com]: FAILED! => {
"changed": true,
"cmd": [
"cp",
"-a",
"/var/lib/etcd//member/snap",
"/var/lib/origin/etcd-backup-pre-upgrade-20170407055413/member/"
],
"delta": "0:00:00.003152",
"end": "2017-04-07 01:54:17.584685",
"failed": true,
"rc": 1,
"start": "2017-04-07 01:54:17.581533",
"warnings": []
}
STDERR:
cp: cannot create directory
?/var/lib/origin/etcd-backup-pre-upgrade-20170407055413/member/?: No
such file or directory
|
| |
| |
| |
| | |
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1433272
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Two tasks for initializing group names for the byo playbooks was located
in the common folder in the std_include.yml file. Byo dependencies
should not be in the common folder. The two tasks have been removed
from common/openshift-cluster/std_include.yml to a new file
byo/openshift-cluster/initialize_groups.yml. All references where these
tasks were included from either std_include.yml or other various files
have been updated to use the byo initialize_groups.yml. The methodology
implemented follows the pattern of having groups set up in byo then
calling out to playbooks in common, which are common to all deployments.
|
|\ \
| | |
| | | |
Merged by openshift-bot
|
| | |
| | |
| | |
| | |
| | | |
The playbooks were crossing byo/common boundaries for task includes.
This moves all 'common' files/tasks into the 'common' folder.
|
|\ \ \
| | | |
| | | | |
Merged by openshift-bot
|
| | | | |
|
| |/ / |
|
|/ / |
|
|/ |
|
|
|
|
|
|
|
|
|
|
| |
In openshift_repos and everywhere, ensure deployment_type and
openshift_deployment_type are defined and the same.
We really want to set openshift_deployment_type, but users will likely
still have just deployment_type, so accept both. And don't make every
playbook default openshift_deployment_type to deployment_type.
This introduces the openshift_sanitize_inventory role to run before anything else.
|
|\
| |
| | |
Merged by openshift-bot
|
| | |
|
|\ \
| |/
|/| |
Merged by openshift-bot
|
| |
| |
| |
| |
| |
| |
| |
| | |
Dependencies for these, particularly the SDN package, can cause the
entire transaction to jump to a newer openshift than we requested, if
something newer is available in the repositories. By being specific for
multiple packages, we avoid this problem and get the actual version we
require.
|
|/ |
|
|\
| |
| | |
Only call excluder playbooks on masters and nodes
|