| Age | Commit message (Collapse) | Author |
|---|
|
Automatic merge from submit-queue.
Fix Cinder Persistent Volume support
This documents how to use Cinder-backed persistent volumes with OpenStack.
It needed a change to the dynamic inventory because the "openstack" cloudprovider plugin does actually require internal name resolution -- and the `openshift_hostname` value must match the name of the Nova server.
In addition, we need to be able to specify the V2 of the Cinder API for now as described in: https://github.com/openshift/openshift-docs/issues/5730
|
|
|
|
Automatic merge from submit-queue.
Use webconsole.config.openshift.io/v1 API group
Update the install to use the new web console config API group and kind.
API change: openshift/api#29
Cluster up change: openshift/origin#18056
/assign @sdodson
@deads2k @jwforres cc
|
|
Automatic merge from submit-queue.
Update deployment and apiserver with new certs
Since new certificates are generated for every run, the apiservice
caBundle needs updating in order to have the on disk CA match what is in
Kubernetes.
Because the secrets are updated, the daemonset needs to do a rolling
update for the apiserver to pick up the new certs. Implemented here is
an added annotation to the api server such that the update occurs
automatically when the CA is changed.
---
There may be a better way to make the rolling update occur without adding an annotation, such as within ansible itself (I just didn't know how to do that). Also, I think that probably the controller needs to be updated too in order to ensure staying in sync with the api server.
Edit: I did not think that doing "oc apply" would cause the daemonset to pick up a change since the yaml may be exactly the same, but if it does then the annotation part can definitely be changed.
|
|
Automatic merge from submit-queue.
docker_upgrade_check: skip repoquery calls on containerized setups
Fedora/CentOS Atomic hosts don't have repoquery installed - also there
is no need to check available Docker rpms in the repos for Atomic
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1527256
Note, that this solution is pretty naive - a better idea would be splitting
the playbooks for rpm and containerized installs for clarity
|
|
Add missing v3.9 gluster templates
|
|
|
|
Bug 1527178 - installation of logging stack failed: Invalid version s…
|
|
Bug 1532787 - Add empty node selector to openshift-web-console namespace
|
|
Automatic merge from submit-queue.
logging: fix jinja filters to support py3
|
|
Automatic merge from submit-queue.
Update web console template
Update the web console template based on changes in
https://github.com/openshift/origin/pull/17575
/assign @sdodson
@deads2k fyi
|
|
coreydaley/trello_1435_default_tolerations_via_buildconfig_defaulter
Automatic merge from submit-queue.
Ability to specify default tolerations via the buildconfig defaulter
Trello: https://trello.com/c/LNxlMjjU/1435-5-ability-to-specify-default-tolerations-via-the-buildconfig-defaulter-builds
Dependent on:
https://github.com/openshift/origin/pull/17955
|
|
Updating tsb image names
|
|
Automatic merge from submit-queue.
Add the ability to specify a timeout for node drain operations
A timeout to wait for nodes to drain pods can be specified to ensure that the upgrade continues even if nodes fail to drain pods in the allowed time. The default value of 0 will wait indefinitely allowing the admin to investigate the root cause and ensuring that disruption budgets are respected. In practice the `oc adm drain` command will eventually error out, at least that's what we've seen in our large online clusters, when that happens a second attempt will be made to drain the nodes, if it fails again it will abort the upgrade for that node or for the entire cluster based on your defined `openshift_upgrade_nodes_max_fail_percentage`.
`openshift_upgrade_nodes_drain_timeout=0` is the default and will wait until all pods have been drained successfully
`openshift_upgrade_nodes_drain_timeout=600` would wait for 600s before moving on to the tasks which would forcefully stop pods such as stopping docker, node, and openvswitch.
|
|
Ensure that openshift_facts role is imported whenever we rely on
|
|
Fixes Bug 1532961
|
|
vrutkovs/3.9-upgrades-remove-openshift.common.service_type
3.9 upgrade: remove openshift.common.service_type
|
|
failure_summary: make sure msg is always a string
|
|
|
|
Add defaults for openshift_pkg_version
|
|
Fixing openshift_hosted variable.
|
|
Add vsphere provider
|
|
|
|
Add key existing check to collect facts for rolebidings
|
|
|
|
outside of the openshift_aws master provisioning tasks.
|
|
Since new certificates are generated for every run, the apiservice
caBundle needs updating in order to have the on disk CA match what is in
Kubernetes.
Because the secrets are updated, the daemonset needs to do a rolling
update for the api server to pick up the new certs. Implemented here is
an added annotation to the api server such that the update occurs
automatically when the CA is changed.
|
|
Automatic merge from submit-queue.
Don't hardcode the network interface in the openshift_logging_mux role
The openshift_logging_mux role hardcodes the 'eth0' interface alias
for determining the IP address to use for incoming external client
connections. This will cause the playbook to fail with an undefined
variable error on systems where an 'eth0' interface does not exist.
This patch changes the default IP address for external connections
to use the 'ansible_default_ipv4' fact. It also allows this to be
overridden by a new 'openshift_logging_mux_external_address' variable.
|
|
This commit continues moving plugins into lib_utils.
This commit does not move any plugins for add-on roles
such as logging and metrics.
|
|
|
|
|
|
This variable may or may not be defined by the users.
During deployments, it will be set to '-{{ openshift_version }}'
if undefined.
During upgrades, it will remain undefined.
This commit ensures that if the variable is undefined,
empty strings '' are set.
|
|
mgugino-upstream-stage/node-reduce-package-commands
Install node packages in one task instead of 3
|
|
Fixes:
Object of type 'bytes' is not JSON serializable
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
|
Solves this exception with python3:
TypeError: a bytes-like object is required, not 'str
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
|
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
|
|
|
Remove become statements
|
|
|
|
|
|
When deploying on OpenStack with internal DNS configured, this will set
`openshift_hostname` to the Nova server name instead of its IP address.
Without those two matching, the OpenStack cloud provider configuration
will fail and the OpenShift nodes will not start.
|
|
As described in[1], OpenShift currently only works with Block Storage
API v2 and the version autodetection is failing to figure that out.
[1]: https://github.com/openshift/openshift-docs/issues/5730
|
|
|
|
|
|
Automatic merge from submit-queue.
Limit host group scope on control-plane upgrades
This commit limits common init code to exclude
oo_nodes_to_config during upgrade_control_plane runs.
|
|
Since py3 returns `dict_items` for dict.keys() call instead of a list,
it should be converted into a list for compatibility
Signed-off-by: Vadim Rutkovsky <vrutkovs@redhat.com>
|
|
Automatic merge from submit-queue.
Adding logic to do a full cluster restart if we are incrementing our …
…major versions of ES
This will help with the upgrade from 2.x to 5.x for ES, it also fixes something I came across with the handler on 3.7 where it checks the prior deployed version of the ES pod rather than the new one.
|
|
Automatic merge from submit-queue.
Add iptables rules for flannel
[WIP] When using flannel there are iptables rules that need
to be added as stated here:
https://access.redhat.com/documentation/en-us/reference_architectures/2017/html-single/deploying_red_hat_openshift_container_platform_3.4_on_red_hat_openstack_platform_10/#run_ansible_installer
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1493955
|
|
Automatic merge from submit-queue.
ensure containerized bools are cast
|
|
Trello: https://trello.com/c/LNxlMjjU/1435-5-ability-to-specify-default-tolerations-via-the-buildconfig-defaulter-builds
|
