Bug 1601334 - when update apb, retry time should be larger at task 'Wait for deployment to become available'
Summary: when update apb, retry time should be larger at task 'Wait for deployment to ...
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: Jason Montleon
QA Contact: Zihan Tang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-16 06:38 UTC by Zihan Tang
Modified: 2018-10-11 07:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2018-10-11 07:21:41 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:22:03 UTC

Description Zihan Tang 2018-07-16 06:38:15 UTC
Description of problem:
when update apb instance, after 13 retry times,  it failed at ' Wait for deployment to become available', but after less than 1min, the new apb pod is ready. the retry time should be larger.

Version-Release number of selected component (if applicable):
asb: 1.2.17
apb: v3.10.18

How reproducible:
random: 10%

Steps to Reproduce:
1. provision postgresql-apb in dev plan
2. update plan to 'prod' by editing serviceinstance
3. check sandbox and serviceinstance.

Actual results:
in step3.
the update pod in sandbox failed.
# oc get pod 
NAME                                       READY     STATUS    RESTARTS   AGE
apb-9bbbcbbf-39cc-4282-99da-18175e008029   0/1       Error     0          30m

TASK [postgresql-apb : Set postgresql objects state=present] *******************
ok: [localhost] => (item={u'state': u'present', u'name': u'service.yaml'})
changed: [localhost] => (item={u'state': u'present', u'name': u'pvc.yaml'})
changed: [localhost] => (item={u'state': u'present', u'name': u'deployment.yaml'})

TASK [postgresql-apb : Update last operation] **********************************
changed: [localhost]

TASK [postgresql-apb : Wait for deployment to become available] ****************
FAILED - RETRYING: Wait for deployment to become available (12 retries left).Result was: {
    "attempts": 1, 
    "changed": false, 
    "msg": "Deployment available status: False", 
    "retries": 13
}
.......
FAILED - RETRYING: Wait for deployment to become available (1 retries left).Result was: {
    "attempts": 12, 
    "changed": false, 
    "msg": "Deployment available status: False", 
    "retries": 13
}
fatal: [localhost]: FAILED! => {
    "msg": "Deployment available status: False"
}

PLAY RECAP *********************************************************************
localhost                  : ok=9    changed=8    unreachable=0    failed=1   

but after less than 1 min, and apb pod is ready 
# oc get pod -n postsql1
NAME                                                      READY     STATUS    RESTARTS   AGE
postgresql-cf359aed-88b9-11e8-81f9-0a580a0204ce-1-sght5   1/1       Running   0          30m

Expected results:
update succeed.

Additional info:

Comment 2 David Zager 2018-08-01 22:32:52 UTC
https://errata.devel.redhat.com/advisory/33505 updated

openshift-enterprise-mariadb-apb-v3.11.0-0.10.0.3
openshift-enterprise-mediawiki-apb-v3.11.0-0.10.0.3
openshift-enterprise-postgresql-apb-v3.11.0-0.10.0.3
openshift-enterprise-mysql-apb-v3.11.0-0.10.0.3
openshift-enterprise-mediawiki-container-v3.11.0-0.10.0.0
openshift-enterprise-asb-container-v3.11.0-0.10.0.1
openshift-enterprise-apb-base-container-v3.11.0-0.10.0.3

Comment 3 Zihan Tang 2018-08-09 03:17:05 UTC
Verified.

Comment 5 errata-xmlrpc 2018-10-11 07:21:41 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.