Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1601334 - when update apb, retry time should be larger at task 'Wait for deployment to become available'
when update apb, retry time should be larger at task 'Wait for deployment to ...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker (Show other bugs)
3.10.0
Unspecified Unspecified
medium Severity medium
: ---
: 3.11.0
Assigned To: Jason Montleon
Zihan Tang
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-07-16 02:38 EDT by Zihan Tang
Modified: 2018-10-11 03:22 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-10-11 03:21:41 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 None None None 2018-10-11 03:22 EDT

  None (edit)
Description Zihan Tang 2018-07-16 02:38:15 EDT
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 18:32:52 EDT
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-08 23:17:05 EDT
Verified.
Comment 5 errata-xmlrpc 2018-10-11 03:21:41 EDT
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.