Red Hat Bugzilla – Bug 702748
reverting a deployment fails if the deployment was more than the second one
Last modified: 2013-09-02 03:27:38 EDT
Reverting a deployment is failing if trying to revert a #3 or higher deployment.
1) Deploy a bundle (deployment #1)
2) Deploy another version of the bundle to the same destination (#2)
3) Deploy a third version of the bundle to the same destination (#3)
4) Revert the last deployment (going from #3 -> #2). This succeeds
5) Revert again (going from #2 to #1).
This fails and the error message and on screen wizard information is screwed up. The wizard's "previous deployment" information is pointing to data from a completely differerent destination (as if the IDs got mismatched). The error message says there was no previous deployment (which we know there was)
commit 310d34c - makes sure we assign the proper "replacedBundle" ID when reverting so we can revert back multiple times.
turns out the fix for this that was committed to master required the fix for bug #702390 because it sets the value which was a BundleDeployment but is now an Integer
cherry picked over to release-4.0.0 branch - f905896
Verified on rhq401 build#25 (Version: 4.0.1-SNAPSHOT Build Number: 2267ccb)
Deployed a bundle with three versions to the same destination. The revert from #3 -> #2 and the revert from #2 to #1 is successful.
The revert wizard's "previous deployment" information is pointing to data from the correct destination when reverting from #2 to #1.
Marking as verified.
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.