| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|\
| |
| | |
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.
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
| |
Prevents playbooks from accidentally restarting the master service.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes a bug which reported that AFTER a cluster upgrade from OCP 3.5
to 3.6, any masters which are later added via the scaleup playbooks
are setting a value for OPENSHIFT_DEFAULT_REGISTRY which is
inconsistent with the already configured masters.
* OPENSHIFT_DEFAULT_REGISTRY value is saved from oo_first_master
* The new scaleup master has a fact set noting it is a scaleup host
* The saved OPENSHIFT_DEFAULT_REGISTRY value is used instead of the
default for 3.6, which is to use a hard-coded registry value of
'docker-registry.default.svc:5000'
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1469336
|
|
|
|
|
|
| |
Also add filter names of filters that failed me for to their error
messages so you can figure out which filter threw an exception when
you're debugging log files.
|
|
|
|
| |
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1466783
|
| |
|
|
|
|
| |
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1464011
|
|
|
|
|
| |
This would be the case if for instance they'd upgraded and then
migrated.
|
|
|
|
|
| |
If we have no master config assume that we're a clean install.
If we're a clean install and we're 3.6 or greater use etcd v3 storage.
|
|
|
|
| |
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
| |
|
|
|
|
| |
Disable/reset excluders over requested hosts
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
When detecting available OCP version via repoquery,
use yum.conf file with exclude= set to an empty array.
So the detection is independent of the OCP excluder.
|
|\
| |
| | |
Merged by openshift-bot
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
| |
d113f03 moved role dependencies out of playbooks. However, this ended up
causing the masters to not be configured before the nuage steps required
configured masters. This change moves the nuage specific change in
d113f03 back to the config.
Resolves #3583
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Discovered situations where the inventory hostname may not be resolvable
with operations. Switching to the ssh host (an IP) should always be
correct.
|
|
|
|
|
|
|
| |
The add_host: task does not change any data on the host and as practice
has been configured to changed_when: False. This commit standardizes
that usage in the byo and common playbooks. Additionally, taks names
are added to each task to improve troubleshooting.
|
| |
|
|\
| |
| | |
Serial master upgrade
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This was done far into the process potentially leaving the user in a
difficult situation if they had now considered they were running the
upgrade playbook on a host that would be restarted. Instead check
configuration and what host we're running on in pre-upgrade and allow
the user to abort before making any substantial changes.
This is a step towards merging master upgrade into one serial process.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This would fail in some environments where openshift.common.hostname was
not reachable from the local system running ansible. Additionally it is
also possible the API port would not be available even if the host were.
Instead we wait for master ssh connection to come back up, then wait for
the master API on the remote host just as we do for the "service" style
restart.
|
|/
|
|
|
|
| |
Deprecates use of 'create-master-certs' for generating master serving
certificate and loopback kubeconfig in order to reference the first
master's CA serial file.
|
|
|
|
|
|
|
| |
This makes it possible to use openshift-ansible configured nfs for
hosted components other than the registry while also configuring
empty-dir registry storage (no openshift_hosted_registry_storage_kind
set).
|
|\
| |
| | |
Return role dependencies to roles for openshift_{hosted,master,node}
|
| |
| |
| |
| | |
and openshift_hosted.
|
|/ |
|
|
|
|
|
|
|
| |
* Removed unneeded rules
* Moved etcd rule to conditional based on usage of embedded etcd
https://bugzilla.redhat.com/show_bug.cgi?id=1386329
|
|
|
|
|
| |
* Added checks to make ci for yaml linting
* Modified y(a)ml files to pass lint checks
|
|
|
|
|
|
|
| |
inventory_hostname
When using a dynamic inventory inventory_hostname isn't guaranteed to be usable. We should use openshift.common.hostname which
already copes with this
|
| |
|
|
|
|
|
|
|
| |
curl, prior to RHEL 7.2, did not properly negotiate up the TLS protocol, so
force it to use tlsv1.2
Fixes bug 1390869
|