| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
juanvallejo/jvallejo/skip-yum-update-check-on-fedora
Merged by openshift-bot
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
| |
Bring in openshift_repos to provide Origin repo before checks on Origin.
For OCP we want the check to fail if both version 3.3 and version 3.4
are available - they shouldn't have both channels enabled.
For Origin everything is in one repo so it's not surprising to find 1.4
and 1.5 versions available.
Added unit tests as well.
|
|
|
|
|
| |
The intention is to set a starting point and let another team member
work on the code to gain experience with tests.
|
| |
|
|
|
|
|
|
|
|
| |
It is a function/callable, the name should imply action, should be a
verb and not a noun.
Keep supporting the old name while we have PRs in-flight that use the
old name.
|
|
|
|
|
|
|
|
| |
This patch adds a check to ensure that required docker images are
available in at least one of the registries supplied in an installation
host. Images are available if they are either already present locally,
or able to be inspected using Skopeo on one of the configured
registries.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It turns out the code in
roles/openshift_health_checker/openshift_checks/__init__.py had a
mistake in the import statement, and not the case that `add_metaclass`
is not available in the embedded `six` from `ansible.module_utils`.
The fix is to correct the import and do not require python-six to be
installed on target hosts.
Note: now that we have some unit tests in the role, errors like that
would have been caught.
|
| |
|
|
|
|
|
| |
Embedded version of six in Ansible 2.2.1 does not support add_metaclass,
so revert to using python-six.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This allows us to refer to a group of checks using a single handle.
|
|
This approach should make it easier to add new checks without having to
write lots of YAML and doing things against Ansible (e.g.
ignore_errors).
A single action plugin determines what checks to run per each host,
including arguments to the check. A check is implemented as a class with
a run method, with the same signature as an action plugin and module,
and is normally backed by a regular Ansible module.
Each check is implemented as a separate Python file. This allows whoever
adds a new check to focus solely in a single Python module, and
potentially an Ansible module within library/ too.
All checks are automatically loaded, and only active checks that are
requested by the playbook get executed.
|