| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
From now on, all master configurations use the api / controller split,
regardless of HA mode or previous configuration. This will be our only
supported configuration starting in 3.7 or 3.8.
|
|\
| |
| |
| |
| | |
ingvagabund/allow-to-specify-docker-registry-for-system-containers
Allow to specify docker registry for system containers
|
| | |
|
|\ \
| | |
| | | |
Merged by openshift-bot
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|/ / |
|
|\ \
| | |
| | | |
Fix log dumping on service failure
|
| |/
| |
| |
| | |
Also, add log dumping to master service startup too
|
|/
|
|
| |
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1466783
|
| |
|
| |
|
| |
|
|\
| |
| | |
Merged by openshift-bot
|
| |
| |
| |
| |
| | |
We cannot assume that 3.5 to 3.6 upgrades were signed with the correct
certs
|
|/
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
Fixes "Could not find the requested service atomic-openshift-master:
cannot enable" error during reinstall.
https://bugzilla.redhat.com/show_bug.cgi?id=1451693
|
| |
|
|
|
|
|
|
|
| |
Adds service file templates for both maste and node. These will lay down
in /etc/system/systemd to override what may already be present from a
package. These instances take into account the name of the container
daemon (docker or container-engine).
|
|
|
|
|
|
|
| |
Using lineinfile and with_items, the items end up logged and in this
case include AWS credentials.
Simple us of no_log to hide them.
|
| |
|
| |
|
|
|
|
| |
https://github.com/openshift/openshift-ansible/pull/2707)
|
|
|
|
| |
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
|
|
|
| |
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
|
|
|
| |
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
|
|
|
|
|
|
|
| |
Upstream version has "atomic containers update ..." but the RHEL
version is still using "atomic update --container" so stick with this
for now.
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use use_system_containers=true in the inventory file
alternatively you can select each component as:
use_openvswitch_system_container=true
use_node_system_container=true
use_master_system_container=true
system_images_registry holds the registry from where to fetch system
containers.
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
|
|
|
|
| |
* Added checks to make ci for yaml linting
* Modified y(a)ml files to pass lint checks
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
* 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
|
|
|
|
|
| |
The Ansible package module will call the correct package manager for the
underlying OS.
|
| |
|
|
|
|
|
|
|
|
| |
Found bug syncing binaries to containerized hosts where if a symlink was
pre-existing, but pointing to the wrong destination, it would not be
corrected.
Switched to using oc adm instead of oadm.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Master startup can fail when ec2 transparently reallocates the block
storage, causing etcd writes to temporarily fail. Retry failures blindly
just
once to allow time for this transient condition to to resolve and for
systemd
to restart the master (which will eventually succeed).
https://github.com/coreos/etcd/issues/3864
https://github.com/openshift/origin/issues/6065
https://github.com/openshift/origin/issues/6447
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
These could exist from 3.1 releases or manual edits, and were getting
wiped out in all variants of the master sysconfig files as we template
these.
This change uses the established pattern of grepping them out if they're
there, then reapplying them if the user has not configured the
cloudprovider framework already.
|
| |
|
|\
| |
| | |
1.3 / 3.3 Upgrades
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Refactored the 3.2 upgrade common files out to a path that does not
indicate they are strictly for 3.2.
3.3 upgrade then becomes a relatively small copy of the byo entry point,
all calling the same code as 3.2 upgrade.
Thus far there are no known 3.3 specific upgrade tasks. In future we
will likely want to allow hooks out to version specific pre/upgrade/post
tasks.
Also fixes a bug where the handlers were not restarting
nodes/openvswitch containers doing upgrades, due to a change in Ansible
2+.
|
| |
| |
| |
| | |
openshift ca bundle.
|
| | |
|
|\ \
| |/
|/| |
Refactor openshift certificates roles.
|
| | |
|
|/ |
|
|
|
|
|
| |
Allows the use of arbitrary tags, precise control over containers and
rpms, and likely mixed environments.
|
|\ |
|