Bug 1570603
Summary: | Should not launch multi depr sandboxes while provision failed | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Zhang Cheng <chezhang> |
Component: | Service Broker | Assignee: | David Zager <dzager> |
Status: | CLOSED ERRATA | QA Contact: | Zhang Cheng <chezhang> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3.10.0 | CC: | aos-bugs, dzager, jesusr, jiazha, pmorie, zhsun, zitang |
Target Milestone: | --- | ||
Target Release: | 3.10.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-07-30 19:13:42 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
Zhang Cheng
2018-04-23 10:20:11 UTC
I am seeing this behavior in service catalog 0.1.13 but not in 0.1.11. @pmorie Do you know which behavior is correct for 3.10? Clearing needinfo Plan for this BZ is to update the mediawiki APB so it's deprovision playbook is idempotent. That is the first issue here, the deprovision should be able to run multiple times and ensure it has cleaned up the artifacts, if they do not exist it should _not_ treat that as an error. For longer term, we will investigate and determine how we want to handle failure cases and a possible rate limiter so we will control how often we attempt a deprovision. Trello for longer term approach here (post 3.10): https://trello.com/c/hSGqK7wm Summary: For 3.10, we will update the deprovision playbook in mediawiki so it is idempotent https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=696144 https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=696139 https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=696141 https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=696142 There are all the PRs associated with making our main 4 APBs idempotent: https://github.com/ansibleplaybookbundle/mediawiki-apb/pull/31 https://github.com/ansibleplaybookbundle/postgresql-apb/pull/45 https://github.com/ansibleplaybookbundle/mariadb-apb/pull/31 https://github.com/ansibleplaybookbundle/mysql-apb/pull/31 https://errata.devel.redhat.com/advisory/33505 moved to QE openshift-enterprise-asb-container-v3.10.0-0.51.0.1 openshift-enterprise-mediawiki-apb-v3.10.0-0.51.0.1 openshift-enterprise-postgresql-apb-v3.10.0-0.51.0.1 openshift-enterprise-mysql-apb-v3.10.0-0.51.0.1 openshift-enterprise-mariadb-apb-v3.10.0-0.51.0.1 openshift-enterprise-apb-tools-v3.10.0-0.32.0.2 I want to know what is our expected in currently. I tried with openshift-enterprise-mediawiki-apb-v3.10.0-0.51.0.1 and latest asb:1.2.14, but still get similar result. 1. Will automatic launch depr sandbox if mediawiki provision failed 2. Still launch multi depr sandboxes while provision failed, but not frequently. rh-mediawiki-apb-depr-4w8c6 Active 33m rh-mediawiki-apb-depr-kpdwq Active 40m rh-mediawiki-apb-depr-kxjtd Active 1h rh-mediawiki-apb-depr-mnsqr Active 29m rh-mediawiki-apb-prov-fnjl5 Active 1h From jmatthews: Plan for this BZ is to update the mediawiki APB so it's deprovision playbook is idempotent. You should expect to see the multiple sandboxes, however they should now be idempotent. That is OK. Verified in here. 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:1816 |