| Age | Commit message (Collapse) | Author |
|
We did this for install but not upgrade, leading to situations where the
service restarts after upgrade could take much longer than expected as
docker pulls down the new image. Now the images are present when we
restart services and should allow them to come back online much more
quickly, equivalent to rpm service restarts.
|
|
Scheduler var fix
|
|
node_dnsmasq - restart dnsmasq if it's not currently running
|
|
Fixes Bug 1401425
Fixes BZ1401425
|
|
Conditionalize master config update for admission_plugin_config.
|
|
|
|
upgrade_control_plane.yml: systemd_units.yaml needs the master facts
|
|
openshift-master/restart : use openshift.common.hostname instead of inventory_hostname
|
|
|
|
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
|
|
- Introduce additional variables for current scheduler config and default
values to better determine if the values we are getting are user-defined,
coming from config or are the default values.
|
|
|
|
openshift_node_dnsmasq - Remove strict-order option from dnsmasq
|
|
strict-order forces dnsmasq to iterate through nameservers in order. If one of
the nameservers is down this will slow things down while dnsmasq waits for a
timeout. Also, this option prevents dnsmasq from querying other nameservers if
the first one returns a negative result. While I think it's odd to have a
nameserver that returns negative results for a query that another returns
positive results for this does seem to fix the issue in testing.
Fixes Bug 1399577
|
|
Explictly set etcd vars for byo scaleup
|
|
Fixes #2738
|
|
Cleanup ovs file and restart docker on every upgrade.
|
|
Sync latest image stream and templates for v1.3 and v1.4
|
|
In 3.3 one of our services lays down a systemd drop-in for configuring
Docker networking to use lbr0. In 3.4, this has been changed but the
file must be cleaned up manually by us.
However, after removing the file docker requires a restart. This had big
implications particularly in containerized environments where upgrade is
a very fragile series of upgrading and service restarts.
To avoid double docker restarts, and thus double service restarts in
containerized environments, this change does the following:
- Skip restart during docker upgrade, if it is required. We will restart
on our own later.
- Skip containerized service restarts when we upgrade the services
themselves.
- Clean shutdown of all containerized services.
- Restart Docker. (always, previously this only happened if it needed an
upgrade)
- Ensure all containerized services are restarted.
- Restart rpm node services. (always)
- Mark node schedulable again.
At the end of this process, docker0 should be back on the system.
|
|
|
|
allow 'latest' origin_image_tag
|
|
xpaas v1.3.5
|
|
Update scheduler defaults
|
|
Ansible version check update
|
|
|
|
We require ansible >= 2.2.0 now. Updating version checking playbook to
reflect this change.
|
|
Remove duplicate when key
|
|
|
|
|
|
Fix rare failure to deploy new registry/router after upgrade.
|
|
Set nameservers on DHCPv6 event
|
|
fix selinux issues with etcd container
|
|
|
|
|
|
|
|
|
|
Refactored to use Ansible systemd module
|
|
Gracefully handle OpenSSL module absence
|
|
etcd upgrade playbook is not currently applicable to embedded etcd in…
|
|
Make it so that we don't relabel /etc/etcd/ (via `:z`) on every run.
Doing this causes systemd to fail accessing /etc/etcd/etcd.conf when
trying to run the systemd unit file on the next run. Convert it from
`:z` to `:ro` since we only need read-only access to the files.
Fixes #2811
|
|
Fixes Bug 1395945
|
|
Fix invalid embedded etcd fact in etcd upgrade playbook.
|
|
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1398549
Was getting a different failure here complaining that openshift was not
in the facts, as we had not loaded facts for the first master during
playbook run. However this check was used recently in
upgrade_control_plane and should be more reliable.
|
|
Should fix #2869
|
|
lhuard1A/fix_list_after_create_on_libvirt_and_openstack
Fix the list done after cluster creation on libvirt and OpenStack
|
|
* Ansible systemd module used in place of service module
* Refactored command tasks which are no longer necessary
* Applying rules from openshift-ansible Best Practices Guide
|
|
Updating docs for Ansible 2.2 requirements
|
|
Verify the presence of dbus python binding
|
|
Merge admission plugin configs
|
|
|