| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1494357
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1490677
The versioning scheme for 3.7 pre-releases has changed and now all
versions are 3.7.0 and the release is incremented on builds, ie:
3.7.0-0.124.0 upgraded to 3.7.0-0.125.0. If we know we're an upgrade and
they haven't requested a specific package version defer the defaulting
of openshift_pkg_version until the upgrade playbooks and there set it to
the available version including the release.
|
|
|
|
|
|
|
|
|
|
|
| |
Recent refactoring to remove openshift_common resulted
in base openshift rpm's being installed on more hosts
than previous. This situation results in hosts that
would otherwise not need access to openshift repositories
to require them.
This patch set results in only openshift_masters and
openshift_nodes to have the openshift base package installed.
|
|
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| | |
crio: rename openshift_docker_use_crio to openshift_use_crio
|
| |
| |
| |
| |
| |
| |
| | |
It is confusing to have _docker_ in the name, since they are two
different backends.
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
|/
|
|
|
|
|
| |
Example: v3.7.0-0.104.0
Resolves 5192
Fixes: https://github.com/openshift/openshift-ansible/issues/5192
|
|
|
|
| |
cluster build.
|
|\
| |
| | |
Merged by openshift-bot
|
| |
| |
| |
| | |
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
|/
|
|
|
|
|
| |
It can happen the openshift_version is set to an empty string.
Which results in openshift_pkg_version set to "-".
Thus, failing installation of base and excluder packages.
For more info see https://bugzilla.redhat.com/show_bug.cgi?id=1474871
|
|
|
|
| |
Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1458653
|
|\
| |
| | |
relax check for rpm version and docker image version equality
|
| |
| |
| |
| | |
openshift_pkg_version and openshift_image_tag are not defined
|
|/
|
|
|
|
|
|
|
| |
This commit allows to specify imageConfig.format specifically for master
or for nodes.
One use case of this could be if you want to use customer builder
images. In this case imageConfig.format only needs to be changed in the
master-config.yml but not in the node-config.yml.
|
|
|
|
|
|
| |
since there is no repoquery installed on Atomic Host.
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
| |
|
| |
|
|
|
|
|
|
|
| |
This role often provides the first failure messages when users'
inventory parameters are not going to work out. So, make sure the task
names and messages are informative to someone who may not have very much
context for what this role does.
|
| |
|
|
|
|
|
| |
- openshift_image_tag must start with a v unless it's set to latest
- openshift_pkg_version must start with a -
|
| |
|
|
|
|
|
| |
- origin examples: v1.2.3, v1.2.3-alpha, v1.2.3-beta.1, v1.5.0-rc.0
- openshift-enterprise examples: v3.5, v3.5.3, v3.5.3.4, v3.5.3.4-1
|
| |
|
| |
|
|\
| |
| | |
Merged by openshift-bot
|
| | |
|
|\ \
| |/
|/| |
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.
|
|/
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
| |
* Applies the chomp_commit_offset logic to container version detection
https://bugzilla.redhat.com/show_bug.cgi?id=1389137
|
|
|
|
|
|
|
|
| |
This improves the situation further and prevents configuration changes
from accidentally triggering docker restarts, before we've evacuated
nodes. Now in two places, we skip the role entirely, instead of previous
implementation which only skipped upgrading the installed version.
(which did not catch config issues)
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes : startswith first arg must be str, unicode, or tuple, not float
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
enter wrong.
|
| |
|
| |
|
| |
|
| |
|