Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: I had earlier installed aeolus-all-0.8.12-1.el6_2.noarch and then I upgraded to aeolus-all-0.8.13-1.el6_2.noarch.rpm using yum upgrade aeolus-all. Upgrade was successful.navigated through the applications..however rails.log was not getting updated. Actual results: All the aeolus-conductor logs were not getting updated. # ls -lhtr total 0 -rw-r--r--. 1 aeolus aeolus 0 Apr 20 12:27 thin.log -rw-r--r--. 1 aeolus aeolus 0 Apr 20 12:27 rails.log -rw-r--r--. 1 aeolus aeolus 0 Apr 20 12:27 dbomatic.log Expected results: logs must get updated. Additional info: rpm -qa | grep aeolus aeolus-configure-2.5.3-1.el6.noarch aeolus-conductor-daemons-0.8.13-1.el6_2.noarch aeolus-conductor-doc-0.8.13-1.el6_2.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-all-0.8.13-1.el6_2.noarch aeolus-conductor-0.8.13-1.el6_2.noarch rubygem-aeolus-cli-0.3.1-1.el6.noarch
when i restarted the aeolus-conductor.. logs were getting updated. Should restart be part of rpm upgrade or not?
So we are going to close this out as a restart of conductor services will be part of the upgrade process. We need to make sure we get a test case open for this.