Red Hat Bugzilla – Bug 790079
cleaning a re-deployment with a edited file fails
Last modified: 2015-02-01 18:27:43 EST
+++ This bug was initially created as a clone of Bug #785268 +++
1) deploy a bundle that has a file in it - foo.txt.
2) edit foo.txt after its laid down on the destination directory
3) re-deploy the same bundle you did in step 1 BUT make it a "clean deployment" (check the clean option in the bundle deploy wizard).
What should happen is foo.txt should be reverted back to what it looks like in the bundle. However, what happens is foo.txt gets outright deleted and missing after the second deployment completes.
--- Additional comment from email@example.com on 2012-01-27 16:56:57 EST ---
git commit to master: 657f2f2
this includes the fix and some unit tests to show it working
--- Additional comment from firstname.lastname@example.org on 2012-01-31 09:39:25 EST ---
the use-case here was the drift remediation demo that jay s produced and a feature that ian/lukas promoted earlier.
The concept is that you deploy a bundle, and someone changes a file that was laid down. Drift gets detected due to that change and that drift triggers an alert which then invokes an alert CLI script which turns around and does a clean deployment of the same bundle.
When that sequence of events happens, this bug is hit.
per triage 2/13/2012 (asantos, crouch, foley, loleary)
cherry picked to release/jon3.0.x branch - commit: 69cd904c42b383eaa93abb244347df45cf716e3e
Moving to ON_QA for testing with JON 3.0.1.GA RC5 or better:
Created attachment 564760 [details]
test bundle distribution file
try to test with the attached small-v1.jar bundle distribution file. This can be uploaded as a bundle to the RHQ server and then deployed. It will deploy a single .properties file.
Bulk closing of old issues in VERIFIED state.