| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
Merged by openshift-bot
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, the variable openshift_pkg_version is defined
by the first master unless specified by the user. The role
openshift_version attempts to set this value on all other
hosts after setting it on the first master.
During normal installation, openshift_pkg_version is not
initially defined, therefor each host will utilize the
most recent rpm available. This creates a problem
during later operations of a cluster if a node is added
or replaced by a new node.
This commit ensures that the value for openshift_pkg_version
set by the first master is respected by subsequent hosts.
Fixes: #5341
|
|\ \
| | |
| | | |
upgrade: Verify required network items are set
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|\ \ \
| | | |
| | | | |
Correct include path to not follow symlink
|
| | |/
| |/| |
|
|\ \ \
| | | |
| | | | |
Merged by openshift-bot
|
| |/ / |
|
|/ / |
|
|\ \
| |/
|/| |
Provisioning updates.
|
| | |
|
| | |
|
|\ \
| |/
|/| |
Merged by openshift-bot
|
| | |
|
|\ \
| | |
| | | |
Merged by openshift-bot
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
A new role for installing prometheus on openshift.
Depends on `openshift_hosted_prometheus_deploy` flag
role creates:
- prometheus namespace
- prometheus clusterrolebinding and service account
- pvs for prometheus, alertmanager and alertbuffer for internal nfs
- prometheus pod with prometheus behind oauth-proxy, alertmanager and alert-buffer behind oauth-proxy
- prometheus and alertmanager configmaps
- prometheus and alerts services and direct routes
- prometheus, alertmanager and alert-buffer pvcs
|
| |
|
|
|
|
|
|
|
|
|
| |
Added byo/openshift-master/config.yml as a new entry point for
performing master installation.
Excluder disable/enable for master has been moved to
common/openshift-master/config.yml to follow a standard pattern that
could be used for both installation and scaleup playbooks.
|
|\
| |
| | |
Merged by openshift-bot
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Added byo/openshift-node/config.yml as a new entry point for performing
node installation. This playbook must be run after masters have already
been deployed.
Excluder disable/enable for both nodes and masters has been moved their
respective config.yml. This created a common pattern that could be used
for both installation and scaleup playbooks.
|
|\ \
| | |
| | | |
Merged by openshift-bot
|
| |/ |
|
|\ \
| |/
|/| |
[BZ1486450] Only run migrate auth for < 3.7
|
| | |
|
|\ \
| | |
| | | |
Merged by openshift-bot
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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 common
|
| | |/
| |/| |
|
|\ \ \
| | | |
| | | | |
Merged by openshift-bot
|
| | |/
| |/| |
|
|\ \ \
| | | |
| | | | |
Merged by openshift-bot
|
| | |/
| |/| |
|
|\ \ \
| | | |
| | | | |
Move firewall install and fix scaleup playbooks
|
| |/ / |
|
|\ \ \
| |/ /
|/| | |
Fix scaleup on containerized installations
|
| | |
| | |
| | |
| | |
| | |
| | | |
The output from member add had quotes added that caused etcd to fail.
Also there were some places that needed to have retries added because
containerized start/stop/restart are slower than rpm based installs.
|
|\ \ \
| |_|/
|/| | |
Remove unsupported playbooks and utilities
|
| |/ |
|
|\ \
| | |
| | | |
Add playbook to run adhoc health checks or list existing checks
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is a simple mechanism to learn what health checks are available.
Note that we defer task_vars verification, so that we can compute
requested_checks and resolved_checks earlier, allowing us to list checks
even if openshift_facts has not run.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is useful on its own, and also aids in developing/testing new
checks that are not part of any playbook.
Since the intent when running this playbook is to execute checks, opt
for a less verbose explanation on the error summary.
|
| |/ |
|
|\ \
| | |
| | | |
Merged by openshift-bot
|
| | | |
|
|\ \ \
| | | |
| | | | |
System images registry followup
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Merged by openshift-bot
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
openshift_cli_facts only runs a single task, and otherwise
the only existence is to serve as a link in the dependency
chain towards openshift_facts.
This commit flattens openshift_cli into one role.
|