Red Hat Bugzilla – Bug 1503233
Warning statements from `oc status` because ASB deploymentconfig has no readiness & liveness checks
Last modified: 2017-11-28 17:17:38 EST
Description of problem: We currently do not have readiness and liveness checks configured for the brokers deploymentconfig. This produces warnings in `oc status -v`. Version-Release number of selected component (if applicable): 3.7.0 How reproducible: 100% Steps to Reproduce: 1. Deploy Ansible Service Broker from template 2. Type `oc status -v` in the broker project Actual results: Info: * dc/asb has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful. try: oc set probe dc/asb --readiness ... * dc/asb has no liveness probe to verify pods are still running. try: oc set probe dc/asb --liveness ... Expected results: We get no informational events related to readiness and liveness checks
https://github.com/openshift/ansible-service-broker/pull/500
Commits pushed to master at https://github.com/openshift/openshift-ansible https://github.com/openshift/openshift-ansible/commit/6acf9bbff6df939b26699da591dab14eaba3d6e0 Bug 1503233 - Add liveness and readiness probe checks to ASB deploymentconfig https://github.com/openshift/openshift-ansible/commit/bdf4c4de4fa7a533a7d555c3d21bc112ffa58efd Merge pull request #5783 from dymurray/readiness Bug 1503233 - Add liveness and readiness probe checks to ASB deployme…
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=611233 ansible-service-broker-1.0.11-1.el7
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:3188