| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
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
|
| | |
|
|\ \
| | |
| | | |
Merged by openshift-bot
|
| | | |
|
| |/
|/| |
|
|\ \
| | |
| | | |
Merged by openshift-bot
|
| | | |
|
|/ / |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
| |
* PetSets are deprecated in 3.5, replaced with StatefulSets
* We can not automatically migrate between the two
* Red Hat has never supported PetSets nor do we support StatefulSets
* Gracefully handles invalid resource queries if ran against 3.5+
clusters
* Fails out with explanation and ref docs if petsets are detected
Reference bug: https://bugzilla.redhat.com/show_bug.cgi?id=1428229
|
|\
| |
| | |
WIP: update excluders to latest by default, in non-upgrade scenarios do not update
|
| |
| |
| |
| |
| |
| | |
- check both available excluder versions are at most of upgrade target version
- get excluder status through status command
- make excluders enablement configurable
|
|\ \
| | |
| | | |
Add oc_objectvalidator to upgrade check
|
| |/ |
|
|\ \
| |/
|/| |
Adding changed_whens for role, rolebinding, and scc reconciliation ba…
|
| | |
|