Bug 1595153 - Regression: [APB] In cluster, apb test fails to retrieve test results
Summary: Regression: [APB] In cluster, apb test fails to retrieve test results
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.11.0
Assignee: Dylan Murray
QA Contact: Zihan Tang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-26 08:54 UTC by sunzhaohua
Modified: 2018-10-11 07:21 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2018-10-11 07:20:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 0 None None None 2018-10-11 07:21:18 UTC

Description sunzhaohua 2018-06-26 08:54:48 UTC
Description of problem:
In cluster, `apb test` is failing to retrieve test results. 

How reproducible: 
Always


Steps to Reproduce:
1. create an apb test (or `git clone git:cfchase/test-apb.git`) 
2. cd into test apb directory
3. run `apb test`

Actual results:
[root@qe-zhsun-stack-000master-etcd-1 test-apb]# apb test
Found registry IP at: 172.30.220.107:5000
Finished writing dockerfile.
Building APB using tag: [172.30.220.107:5000/openshift/test-apb]
Successfully built APB image: 172.30.220.107:5000/openshift/test-apb
Pushing the image, this could take a minute...
Successfully pushed image: 172.30.220.107:5000/openshift/test-apb
Creating project apb-test-test-apb-14bn5
Created project
Creating service account in apb-test-test-apb-14bn5
Created service account
Creating role binding for apb-test-test-apb-14bn5 in apb-test-test-apb-14bn5
Created Role Binding
Creating pod with image 172.30.220.107:5000/openshift/test-apb in apb-test-test-apb-14bn5
Created Pod
Unable to retrieve test result.
Deleting project apb-test-test-apb-14bn5
Project deleted


Expected results:
Test successfully passed

Additional info:

Comment 1 Zhang Cheng 2018-06-26 09:15:56 UTC
We set target release to 3.11, please correct me if anybody have different thinking. Thanks.

Comment 2 sunzhaohua 2018-06-26 09:23:56 UTC
In previous it is work in cluster.

[root@host-172-16-120-16 test-apb]# apb test
Found registry IP at: 172.30.20.140:5000
Finished writing dockerfile.
Building APB using tag: [172.30.20.140:5000/openshift/test-apb]
Successfully built APB image: 172.30.20.140:5000/openshift/test-apb
Found image: docker-registry.default.svc:5000/openshift/test-apb
Warning: Tagged image registry prefix doesn't match. Deleting anyway. Given: 172.30.20.140:5000; Found: docker-registry.default.svc:5000
Successfully deleted sha256:a38336cd1452dd936a878c487127b55509878bae17ab50f3af4c1f7419b177d3
Pushing the image, this could take a minute...
Successfully pushed image: 172.30.20.140:5000/openshift/test-apb
Creating project apb-test-test-apb-afyuo
Created project
Creating service account in apb-test-test-apb-afyuo
Created service account
Creating role binding for apb-test-test-apb-afyuo in apb-test-test-apb-afyuo
Created Role Binding
Creating pod with image 172.30.20.140:5000/openshift/test-apb in apb-test-test-apb-afyuo
Created Pod
Test successfully passed
Deleting project apb-test-test-apb-afyuo
Project deleted

Comment 3 Dylan Murray 2018-08-08 17:06:29 UTC
https://github.com/automationbroker/apb/pull/109

Comment 4 Dylan Murray 2018-08-22 14:48:15 UTC
New builds added to advisory:
openshift-enterprise-asb-container-v3.11.0-0.20.0.0
openshift-enterprise-apb-tools-container-v3.11.0-0.20.0.0

Comment 5 Zihan Tang 2018-08-29 08:12:27 UTC
verify passed
apb: 1.9.3

step : 
1. add registry
# apb registry add docker --org ansibleplaybookbundle --type dockerhub --whitelist  '.*apb$'
2. run apb test
# apb bundle test postgresql-apb -r docker 
Found APB [postgresql-apb] in registry [docker]
List of available plans:
name: dev
name: prod
Enter name of plan to execute: dev
Plan: dev
Enter value for parameter [postgresql_database], default: [admin]: 
Enter value for parameter [postgresql_user], default: [admin]: 
Enter value for parameter [postgresql_password], default: [<nil>]: 
Enter value for parameter [postgresql_version], default: [9.6]: 
INFO OpenShift version: v3.11.0-0.24.0            
INFO Creating RoleBinding bundle-de951cc1-1c89-4b73-876f-e0820fc44568 
INFO Successfully created apb sandbox: [ bundle-de951cc1-1c89-4b73-876f-e0820fc44568 ], with edit permissions in namespace [ post ] 
Successfully created pod [bundle-de951cc1-1c89-4b73-876f-e0820fc44568] to test [postgresql-apb] in namespace [post]
INFO Monitoring test pod [bundle-de951cc1-1c89-4b73-876f-e0820fc44568] for status every 5 seconds... 
INFO Test pod [bundle-de951cc1-1c89-4b73-876f-e0820fc44568] status: Pending 
INFO Test pod [bundle-de951cc1-1c89-4b73-876f-e0820fc44568] status: Running 
INFO Test pod [bundle-de951cc1-1c89-4b73-876f-e0820fc44568] status: Succeeded 
Test succeeded for bundle [postgresql-apb]

check pod log: 

[root@qe-zitang-r4-master-etcd-1 ~]# oc logs -f bundle-de951cc1-1c89-4b73-876f-e0820fc44568 -n post
DEPRECATED: APB playbooks should be stored at /opt/apb/project
PLAY [Test postgresql-apb] *****************************************************
TASK [ansibleplaybookbundle.asb-modules : debug] *******************************
skipping: [localhost]
TASK [include_role : postgresql-apb] *******************************************
....
TASK [postgresql-apb : Update last operation] **********************************
skipping: [localhost]

PLAY RECAP *********************************************************************
localhost                  : ok=4    changed=2    unreachable=0    failed=0 

3. user build apb(created by ansible-galaxy) also succeed with the command

Comment 7 errata-xmlrpc 2018-10-11 07:20:54 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:2652


Note You need to log in before you can comment on or make changes to this bug.