| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| |
| |
| | |
This previously passed all CI tests, merge queue broke last night.
Merging, this is a blocker bug.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, in 1.5, 3.6, 1.7 upgrade-all plays, control
plane upgrades are not called correctly.
This commit ensures the master config hook is appropriately
applied during these upgrades to match the steps in
control plane only upgrades.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1486054
|
| |/
|
|
|
|
|
|
|
|
|
| |
Currently, base atomic-openshift package is
installed for versioning.
This doesn't appear to be necessary.
This commit removes this step.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1504196
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, upgrade_control_plane.yml will add any
missing sections to the openshift master's config.
These additions are only needed once. Users who
perform multiple upgrades to their clusters over
time do not need to have these variables re-inserted.
Currently, re-inserting these variables can cause
unwanted local changes.
This commit ensures that the variables are only
inserted into openshift master's config once.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1486054
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Currently, openshift_version installs RPM packages
on all nodes and masters to aid in determining and
setting the proper version across the cluster.
This commit limits the host groups to only
masters during upgrade_control_plane plays.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1495107
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
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}}
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Disable/reset excluders over requested hosts
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
* 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
|
| | |
|
| |
|
|
| |
Fixes Bug 1423425
|
| | |
|
| |
|
