Red Hat Bugzilla – Bug 825354
Deconfigure and destroy aren't always cleaning up httpd proxy config
Last modified: 2015-05-14 18:54:38 EDT
Created attachment 586926 [details]
Description of problem:
Attached is the log from a failed libra check. You can see that create failed for 6aa261ac328c4c4eafa3f0bc4a0403c0. Then deconfigure didn't find anything to delete and gave up. I think we need to make deconfigure still attempt to clean up the httpd proxy even if the app dir isn't there.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Reproduce steps on devenv_1809:
1. Create app
2. Go to /var/lib/stickshift, remove the app dir.
3. Destroy app.
deconfigure script exits at setup_deconfigure function.
so it does not remove http proxy config file (/var/lib/stickshift/.httpd.d/).
The fix patch does not integerated into devenv_1809, so keep this bug in "ON_QA" status, once latest ami come out, will verify this bug soon.
The fix was in 1809. Did you see an issue still?
FYI: I think we have confirmed at this point there was an issue with 1809 like you said.
Verified this bug with devenv-stage_198, and PASS.