Red Hat Bugzilla – Bug 816228
aeolus-conductor logs fails to update after an upgrade
Last modified: 2012-10-25 09:40:30 EDT
Description of problem:
Version-Release number of selected component (if applicable):
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.
All the aeolus-conductor logs were not getting updated.
# ls -lhtr
-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
logs must get updated.
rpm -qa | grep aeolus
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.