[PATCH conductor] Fix aeolus user home directory on upgrade

Scott Seago sseago at redhat.com
Wed Jul 11 13:42:22 UTC 2012


On 07/11/2012 09:00 AM, Justin Clift wrote:
> On 11/07/2012, at 9:34 PM, Imre Farkas wrote:
> <snip>
>> After building the rpms on F17 tried to install them but with this patch in master I got the following error message:
>> usermod: user aeolus is currently logged in
>>
>> With this patch reverted I was able to install the rpms.
>>
>> Did I forget something or a new issue was introduced with this patch?
> This one's a bit tricky... from conversation in IRC yesterday,
> it turns out Aeolus can't be running these rpm's are
> installed.  i.e. if it's an upgrade, you'll need to stop the services
>
> Personally, no idea how that requirement should be enforced by the
> rpms.  Idea's probably welcome. :)
>
> + Justin
Yes, I hit this yesterday. I had to shut down aeolus-conductor, 
conductor-dbomatic, and conductor-delayed_job to install this. The issue 
is this line in the %pre section:
     test ~aeolus == /usr/share/aeolus-conductor || usermod --home 
/usr/share/aeolus-conductor aeolus

Previously the aeolus homedir was /var/aeolus, and it needed to be 
changed. The first time you upgrade an RPM after this change takes 
effect, you can't install it with any aeolus processes running or the 
usermod will fail. Subsequent RPM upgrades no longer require services 
stopped. The root cause here is that usermod will not allow this change 
while the user has any active processes.

Scott




More information about the aeolus-devel mailing list