| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
Automatic merge from submit-queue.
Verify that requested services have schedulable nodes matching the selectors
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1538445
Not sure if I should keep one task per failure or should group them by service (e.g. all logging check in one tasks)
|
| |
| |
| |
| | |
Signed-off-by: Vadim Rutkovsky <vrutkovs@redhat.com>
|
| |
| |
| |
| | |
Signed-off-by: Vadim Rutkovsky <vrutkovs@redhat.com>
|
|\ \
| | |
| | | |
additional mounts: specify 'type' in container_runtime_crio_additional_mounts
|
| |/ |
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| | |
Automatic merge from submit-queue.
Removing prefix, replacing with cidr, pool_start and pool_end vars
The heat template was hardcoded with a /24 cidr and that limited customers to 251 ip addresses in the OpenStack subnet. This allows the user to configure the cidr and the allocation pool start and end.
Addresses issue #6829 that I created last week.
@tomassedovic please take a look
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Automatic merge from submit-queue.
Normalize the time we wait for pods to 5s * 60 retries
A few people have run into situations where it takes longer than 120seconds for the webconsole to start up so lets be a bit more foregiving and allow for up to 5 minutes in scenarios where we're waiting for pods.
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Automatic merge from submit-queue.
Limit host scope during plays
Many plays only target a select subset of hosts,
especially oo_first_master for components such
as logging and registry.
This commit limits the scope of most plays to
eliminate unnecessary task execution on node
groups. This will result in great time
savings for large deployments.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1516526
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Many plays only target a select subset of hosts,
especially oo_first_master for components such
as logging and registry.
This commit limits the scope of most plays to
eliminate unnecessary task execution on node
groups. This will result in great time
savings for large deployments.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1516526
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Automatic merge from submit-queue.
Pause for console rollout
/assign @sdodson
|
| | | | | |
|
|\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Automatic merge from submit-queue.
Fix upgrade-control plane post_control_plane.yml
An entry-point playbook was imported by mistake.
This caused common init code to run again, which
is undesireable.
This commit changes the import to use the corresponding
'private' play which does not call the init code.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1542855
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
An entry-point playbook was imported by mistake.
This caused common init code to run again, which
is undesireable.
This commit changes the import to use the corresponding
'private' play which does not call the init code.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1542855
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
Created by command:
/usr/bin/tito tag --debug --accept-auto-changelog --keep-version --debug
|
|\ \ \ \
| |/ / /
|/| | | |
Adding ability to provide additional mounts to crio system container.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Automatic merge from submit-queue.
Set default image to openshift_release
Previously `v3.7` was hardcoded as a default value, instead `openshift_release` should be used.
A new var is introduced - `openshift_template_service_broker_image_tag`, similar to vars for other services.
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1530183
TODO:
* [x] Make sure all images have a variable for image prefix
* [x] Figure out if `latest` is a good default for origin images
* [ ] Set correct `openshift_image_tag` in CI inventory for tests to pass
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Vadim Rutkovsky <vrutkovs@redhat.com>
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Automatic merge from submit-queue.
Only try to yaml.load a file if it ends in .yml or .yaml in logging facts
Addresses error seen in https://bugzilla.redhat.com/show_bug.cgi?id=1543625
Also prevents us from seeing this when rerunning a deployment for es5.x branch.
When we are trying to load a configmap file to parse it for facts based on the values, we should only parse if it is a yaml or yml file.
Note: if someone created a configmap entry with key that matched that, but wasn't a yaml file, it would still fail... not sure if that can be helped.
|
| |/ / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Automatic merge from submit-queue.
Redeploy router certificates during upgrade only when secure.
Wrap the upgrade logic for redeploying certificates into another block so that insecure registries do not perform any certificate tasks.
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Automatic merge from submit-queue.
GlusterFS: Fix block StorageClass heketi route
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1542861
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Update xPaaS content to v1.4.8
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | |_|_|_|/ /
| |/| | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Determine which host is the etcd CA host
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
first host in the etcd host group.
|
| | | | | | | | |
|
| | | | | | | | |
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
changed oc to {{ openshift_client_binary }}
|
| | | | | | | | | |
|
|\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Automatic merge from submit-queue.
Fix master and node system container variables
This commit corrects service names and adds
DOCKER_SERVICE variable to openshift_master
system container creation.
This will ensure services will restart correctly
and in the proper order.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1542324
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
This commit corrects service names and adds
DOCKER_SERVICE variable to openshift_master
system container creation.
This will ensure services will restart correctly
and in the proper order.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1542324
|
|\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Automatic merge from submit-queue.
Changing the check for the number of etcd nodes
This playbook is called (via std_include.yml) when the scale up playbook for either master or etcd is called. In the scenario where you are scaling up the number of masters/etcd nodes it is feasible, if not likely, that the number of etcd nodes is not 1, 3 or 5 and this check therefore causes a scale up to fail.
The two example scenarios that are driving this change are:
You have a cluster with 3 master nodes (each running etcd) and one of those masters fail. The master node is removed from both the OpenShift cluster and the etcd cluster and the inventory updated to reflect the state of the cluster minus the failed master node. You would then run the scale up playbook to add a new master / etcd master into the cluster using an inventory containing and etcd group of just 2 nodes.
As above but the cluster has 5 master nodes. If you lose a master node and update the inventory to reflect that then the inventory will contain an etcd group with 4 nodes.
@sdodson
Previously submitted as https://github.com/openshift/openshift-ansible/pull/6979
|
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
In making the initial change I introduce some spaces at the beginning of the line. Removing them.
|
| | | | | | | | | | | |
|
|\ \ \ \ \ \ \ \ \ \ \
| | | | | | | | | | | |
| | | | | | | | | | | | |
Bug 1524805- CFME example now works disconnected
|
|/ / / / / / / / / / / |
|
|\ \ \ \ \ \ \ \ \ \ \
| |_|_|_|_|/ / / / / /
|/| | | | | | | | | | |
Bug 1541625- properly cast provided ip address to unicode
|
| | | | | | | | | | | |
|
|\ \ \ \ \ \ \ \ \ \ \
| |_|_|_|_|_|_|_|/ / /
|/| | | | | | | | | | |
Use wait_for_connection to validate ssh transport is alive
|
| | | | | | | | | | | |
|