Description of problem: If user edits option in apache virtual host, after clicking save button the embedded-agent.log shows an error Version-Release number of selected component (if applicable): 1.4.0-SNAPSHOT How reproducible: Steps to Reproduce: Login to imanage UI Select the apache httpd resource Click on 'Inventory' tab. Create a virtual host (Add option say All while creating new virtual host) Navigate to the 'Configuration' tab of virtual host created. Click on 'Edit' button. Click on 'Edit' button for option. Change the option from 'All' to anything else say 'FollowSymLinks' by selecting from the 'Option' dropdown. Click 'OK' button. Click on 'Save' button. Actual results: The status display failure and the log displays error which is attached. Expected results: User should be able to edit the option in virtual hosts and those should be reflected. Additional info: The embedded-agent.log shows following error: 19:03:07,414 ERROR [ConfigurationManager.threadpool-1] (rhq.core.pc.configuration.UpdateResourceConfigurationRunner)- Plugin Error: Exception thrown while updating Resource configuration for Apache Virtual Host Resource with id [10741]. org.rhq.core.pc.inventory.TimeoutException: Call to [org.rhq.plugins.apache.ApacheVirtualHostServiceComponent.updateResourceConfiguration()] with args [[org.rhq.core.pluginapi.configuration.ConfigurationUpdateReport@eda22e]] timed out. Invocation thread will be interrupted at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invokeInNewThreadWithLock(ResourceContainer.java:465) at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invoke(ResourceContainer.java:434) at $Proxy6036.updateResourceConfiguration(Unknown Source) at org.rhq.core.pc.configuration.LegacyConfigManagement.executeUpdate(LegacyConfigManagement.java:87) at org.rhq.core.pc.configuration.UpdateResourceConfigurationRunner.call(UpdateResourceConfigurationRunner.java:121) at org.rhq.core.pc.configuration.UpdateResourceConfigurationRunner.run(UpdateResourceConfigurationRunner.java:109) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619)
*** Bug 560583 has been marked as a duplicate of this bug. ***
*** Bug 559903 has been marked as a duplicate of this bug. ***
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
The above exception no longer occurs but there is a different problem. The mode of the option doesn't get persisted on update and is always set to "set" after commiting the configuration updates.
This bug 576148 might be related.
commit f3aca43b79d01ee27555d9426ec31f7a1631f8db
Was this discovered with embedded agent? Does the same occur with regular agent?
QA Verified - This seems to work now.
Mass-closure of verified bugs against JON.