Description of problem: When check help info of asbd, the output has some error 'ERROR: Failed to validate input'. and helpinfo duplicate Version-Release number of selected component (if applicable): asbd version: 0.9.6 imageid: 04d97e16eb82 How reproducible: Always Steps to Reproduce: 1. Check the help info of asbd [root@host-8-174-71 ~]# docker images|grep service-broker registry.access.stage.redhat.com/openshift3/ansible-service-broker latest 04d97e16eb82 3 days ago 589.8 MB [root@host-8-174-71 ~]# docker run -it --entrypoint=/bin/sh registry.access.stage.redhat.com/openshift3/ansible-service-broker:latest sh-4.2$ ls bin boot dev etc home lib lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var sh-4.2$ asbd --version 0.9.6 sh-4.2$ asbd --help Usage: asbd [OPTIONS] Application Options: -c, --config= Config File (default: /etc/ansible-service-broker/config.yaml) -v, --version Print version information Help Options: -h, --help Show this help message ERROR: Failed to validate input Usage: asbd [OPTIONS] Application Options: -c, --config= Config File (default: /etc/ansible-service-broker/config.yaml) -v, --version Print version information Help Options: -h, --help Show this help message USAGE: To be implemented... Actual results: Expected results: Additional info:
patch upstream: https://github.com/openshift/ansible-service-broker/pull/264
https://github.com/openshift/ansible-service-broker/pull/264
[root@host-8-241-2 ~]# docker run -it --entrypoint=/bin/sh xxxx/openshift3/ansible-service-broker sh-4.2$ asbd --help Usage: asbd [OPTIONS] Application Options: -c, --config= Config File (default: /etc/ansible-service-broker/config.yaml) -v, --version Print version information Help Options: -h, --help Show this help message sh-4.2$ asbd -v 0.9.9
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