[PATCH conductor] Fix aeolus user home directory on upgrade

John Eckersberg jeckersb at redhat.com
Wed Jul 11 13:37:06 UTC 2012


On Wed, 11 Jul 2012 23:00:36 +1000, Justin Clift <jclift at redhat.com> 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
> 
> --
> Aeolus Community Manager
> http://www.aeolusproject.org
> 

I guess in the specific edge case that we:

1) Are upgrading

2) Already have an aeolus user, with home directory /var/aeolus

3) Already have a new enough version of aeolus-configure installed so
   that the `aeolus-services` script is available to stop/start all
   services (as opposed to aeolus-restart-services which is useless in
   this situation).  Looks like this is only in aeolus-configure >= 2.6.0-1.

In this case, we can stop services, change the home directory with
usermod, and start the services.

Alternatively, we could probably do something nasty like sed
/etc/passwd.  I have no idea how badly that may screw things up though.
I'll go look into that a bit right now...



More information about the aeolus-devel mailing list