New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Binding errors are no longer displayed #941
Labels
3.11 | release-1.3
Kubernetes 1.11 | Openshift 3.11 | Broker release-1.3
Comments
|
Using the following bind playbook, I was able to see the failure in the UI: - name: Create a user, password, and database
hosts: localhost
gather_facts: false
connection: local
roles:
- role: ansible.kubernetes-modules
install_python_requirements: no
- role: ansibleplaybookbundle.asb-modules
- role: bind-rhscl-postgresql-apb-openshift
playbook_debug: false
pre_tasks:
- fail:
msg: "bind that always fails"The log snippet shows the binding starting, running, and finally failed. This is using OpenShift 3.10 with a release-1.2 broker: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Bug:
Binding errors are no longer displayed in the
Create bindingdialog.What happened:
In the
release-1.1tag when a binding failed (by usingfailin the ansible role) an error was shown in the dialog and the binding was marked withError:That does no longer seem to be the case in more recent versions (tested with the
canaryandsprint-147.2tags). The binding appears to be successful even though the pod running the ansible role shows a failure:This is how the dialog looked like in that case:
What you expected to happen:
The binding dialog should show an error when the pod running the ansible role fails.
How to reproduce it:
Use the
sprint-147.2tag of the ASB and create a bind role that will error (by usingfailin ansible). Trigger that binding.The text was updated successfully, but these errors were encountered: