Bug 1532942

Summary: [APB] Run the Mediawiki failed via the `apb run` command
Product: OpenShift Container Platform Reporter: Jian Zhang <jiazha>
Component: Service BrokerAssignee: David Zager <dzager>
Status: CLOSED ERRATA QA Contact: Jian Zhang <jiazha>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.9.0CC: aos-bugs, chezhang, dzager
Target Milestone: ---   
Target Release: 3.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
 Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-28 14:18:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jian Zhang 2018-01-10 03:31:36 UTC 
Description of problem:
The input dialog always exists.

Version-Release number of selected component (if applicable):
apb version: apb-1.1.2-1.20171221180811.fc25.noarch

How reproducible:
Always

Steps to Reproduce:

1, Install the apb tool:

su -c 'wget https://copr.fedorainfracloud.org/coprs/g/ansible-service-broker/ansible-service-broker-latest/repo/epel-7/group_ansible-service-broker-ansible-service-broker-latest-epel-7.repo -O /etc/yum.repos.d/ansible-service-broker.repo'
sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
sudo yum -y install apb

2, Enable docker daemon

3, Clone the Mediawiki project from https://github.com/ansibleplaybookbundle/mediawiki-apb.

4, Login a cluster.

5, Provision the Mediawiki via the `apb run` command.

Actual results:
[root@localhost mediawiki-apb]# apb run --project jian --tag registry.access.redhat.com/openshift3/mediawiki-123:latest --dockerfile Dockerfile-latest
Finished writing dockerfile.
Building APB using tag: [registry.access.redhat.com/openshift3/mediawiki-123:latest]
Successfully built APB image: registry.access.redhat.com/openshift3/mediawiki-123:latest
mediawiki_db_schema(required)[default: mediawiki]: 
mediawiki_site_name(required)[default: MediaWiki]: 
mediawiki_site_lang(required)[default: en]: 
mediawiki_admin_user(required)[default: admin]: 
mediawiki_admin_pass(required): test
mediawiki_admin_pass(required): test
mediawiki_admin_pass(required): test
mediawiki_admin_pass(required): test
mediawiki_admin_pass(required): 

Expected results:
Should run the next step after input the password.

Additional info:
Comment 1 David Zager 2018-01-16 17:52:19 UTC 
https://github.com/ansibleplaybookbundle/ansible-playbook-bundle/pull/200
Comment 3 Jian Zhang 2018-01-25 06:49:01 UTC 
I used the apb-1.1.5 version to test this.
[root@localhost mediawiki-apb]# rpm -qa | grep apb
apb-1.1.5-1.20180117190645.el7.centos.noarch

Followed the above steps 1-5,
[root@localhost mediawiki-apb]# apb run --project jian --tag registry.access.redhat.com/openshift3/mediawiki-123:latest --dockerfile Dockerfile-latest
Finished writing dockerfile.
Building APB using tag: [registry.access.redhat.com/openshift3/mediawiki-123:latest]
Successfully built APB image: registry.access.redhat.com/openshift3/mediawiki-123:latest
mediawiki_db_schema(required)[default: mediawiki]: db
mediawiki_site_name(required)[default: MediaWiki]: 
mediawiki_site_lang(required)[default: en]: 
mediawiki_admin_user(required)[default: admin]: 
mediawiki_admin_pass(required): test
Creating project jian
Created project
Creating service account in jian
Created service account
Creating role binding for apb-run-mediawiki-apb in jian
Created Role Binding
Creating pod with image registry.access.redhat.com/openshift3/mediawiki-123:latest in jian
Created Pod
APB run started

So, we can see the thread into the next step after input the password. LGTM.
Comment 6 errata-xmlrpc 2018-03-28 14:18:26 UTC 
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/RHBA-2018:0489