Bug 826998
Summary: | Problem when an old bundle version is deleted | |||
---|---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | bkramer <bkramer> | |
Component: | Provisioning | Assignee: | RHQ Project Maintainer <rhq-maint> | |
Status: | CLOSED DUPLICATE | QA Contact: | Mike Foley <mfoley> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 4.2 | CC: | hrupp, loleary | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | All | |||
OS: | All | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 826995 (view as bug list) | Environment: | ||
Last Closed: | 2012-06-05 19:00:38 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 826995, 828905, 916380 |
Description
bkramer
2012-05-31 11:52:57 UTC
No help make this issue clear and better define, 'deploy' and 'deployed' as mentioned in comment #0 refers to the actual creation of the bundle and its versions. i.e. uploading a bundle ZIP containing version 1, then uploading a bundle ZIP that contains version 2, deleting bundle version 1, then uploading a bundle ZIP that contains version 3. Additionally, it appears that the upload and creation of bundle version 3 is successful but nothing is displayed in the UI due to the duplicate rows as described in comment #0. This means version 3 can not be deployed to a destination because the bundle is no longer available from the UI. However, if you create bundle version 4, the versions become visible again in the UI and the UI error goes away. Once version 4 has been created the rhq_bundle_version table looks like: Results for statement 1 of 1: SELECT name, version, version_order FROM rhq_bundle_version WHERE name = 'base_jee_test' name version version_order base_jee_test 1.0.1-SNAPSHOT 1 base_jee_test 1.0.2-SNAPSHOT 1 base_jee_test 1.0.3-SNAPSHOT 2 name version version_order Query Time=1 To provide even further details and correct a statement from comment #1: > ...This means version 3 can not be deployed to a destination because the bundle is no longer available from the UI.... You actually can still deploy the version to a destination. You just don't see the bundle listed on the Bundles (http://localhost:7080/coregui/#Bundles) page and you see mentioned error message in the UI. However, the navigation tree does not seem to be affected. You can still expand and select Destinations from the navigation tree and deploy the bundle via the destination page. Not sure what other issues these duplicate version_order rows will cause. Perhaps reverting to a previous version will be broken? Looks like another bug got created this morning to track the upstream work instead of using this one... because the work was already captured in the duplicate Bug 828905, I am marking this one as the dupe and closing. *** This bug has been marked as a duplicate of bug 828905 *** |