Bug 809230
Summary: | App destroy doesn't always remove things in the right order | ||
---|---|---|---|
Product: | OKD | Reporter: | Thomas Wiest <twiest> |
Component: | Pod | Assignee: | Rajat Chopra <rchopra> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.x | CC: | adietish, jialiu, mpatel |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-04-13 18:31:03 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Thomas Wiest
2012-04-02 19:14:33 UTC
No bug with configure order. The way we store it in mongo has changed. The new code, if run with the old configure order creates this problem. We need to run a migration script to port the old apps to new way of storing the configure_order. Migration script checked in with rev#c158bc7d7e1f1d41addff7ef687c8fc3058bd7b7 Verified this bug with migrate-mongo-2.0.8a, and PASS. Reproduce step: 1. Launch a sprint7 release instance (devenv-150) 2. Create an app, and embed mysql to it. 3. According to devel's ticket, run migrate steps. 4. Try to destroy this app, but failed as above. Verified steps: 1. Launch a sprint7 release instance (devenv-150) 2. Create an app, and embed mysql to it. 3. According to devel's ticket, run migrate steps 4. Run migrate-mongo-2.0.8a 5. Destroy this app successfully. |