Upgrading from likewise-open5 changes home directory locations

[David Leon]

Binary package hint: likewise-open

On a machine correctly joined to a domain with likewise-open5:

The homedir template variable in /etc/likewise-open5/lsassd.conf was set to its default:
[auth provider:lsa-activedirectory-provider]
...
    homedir-template = %H/%D/%U

After upgrading to likewise-open on Mon 2010-04-12, package likewise-open 5.4.0.42111-2

/etc/likewise-open/lsassd.conf.reg
[HKEY_THIS_MACHINE\Services\lsass\Parameters\Providers\ActiveDirectory]
...
"HomeDirTemplate"="%H/%D/%U"
...
[HKEY_THIS_MACHINE\Services\lsass\Parameters\Providers\Local]
...
"HomeDirTemplate"="%H/%U"

/etc/likewise-open/lsassd.reg
[HKEY_THIS_MACHINE\Services\lsass\Parameters\Providers\ActiveDirectory]
...
"HomeDirTemplate"="%H/likewise-open/%D/%U"
...
[HKEY_THIS_MACHINE\Services\lsass\Parameters\Providers\Local]
...
"HomeDirTemplate"="%H/likewise-open/%D/%U"
...
[HKEY_THIS_MACHINE\Services\lsass\Parameters\RPCServers\samr]
...
"HomeDirTemplate"="%H/likewise-open/%D/%U"

lw-edit-reg showed the same configuration as lsassd.reg

The change didn't become apparent right away after the upgrade. I could login normally and get all my files, but a few days later, when I logged in, I got a new home directory in the new location, looking like all my files were lost.

etckeeper recorded a single change, during the upgrade after the apt run. The files didn't exist previously.

After a few tries editing the configuration files, changing the configuration with lw-edit-reg, clearing the ad cache and rebooting I could finally login and get the old home directory back.

[Scott Salley (ssalley)]

I could not reproduce this problem upgrading from Ubuntu 9.10 Desktop amd64.

On Ubuntu 9.10 Desktop amd64, I installed likewise-open5 and joined a domain. I verified the home directory template settings in the configuration (lassd.conf) and logged in as a domain user -- the home directory corresponded to %H/%D/%U.

I then upgraded using the alternate CD (ubuntu-10.04-rc-alternate-amd64.iso). At the end of installation and subsequent reboot, I was still able to log in as a domain user to the proper home directory (%H/%D/%U). I checked the registry with lwregshell and lw-edit-reg and they reported %H/%D/%U for the HomeDirTemplate.

[Vide (vide80)]

This happens here as well. Updated from 9.10 to 10.04 beta2 (now on rc, tomorrow on final :) via update-manager, I had to create a symlink for /home/likewise-open pointing to /home.
This is a showstopper for me upgrading all the workstation I manage from 9.10 to 10.04

[Thierry Carrez (ttx)]

Scott, could you try reproducing by using "update-manager -d" on a Karmic+likewise-open5 setup and upgrade to Lucid from there ?

[Gerald Carter (coffeedude.jerry)]

Theirry, what does "update-manager -d" dlo that is different from "apt-get dist-upgrade" or just the normal distro upgrade process started from the update-manager gui? Thanks

[Thierry Carrez (ttx)]

I'm trying to see why we have two reporters of this bug and you can't reproduce it. One difference is that they ran the recommended way to upgrade (update-manager -> upgrade to the new version of the distribution), which runs extra scripts to make sure the upgrade runs correctly. Scott seems to have used a different path, which may or may not explain the difference...

"update-manager -d" is the same as "update-manager" except that it enables the possibility to upgrade to the release in development. Normal users won't have that option until Lucid is released.

[Gerald Carter (coffeedude.jerry)]

Thanks. That;s what I needed to know. I'll try to get a repro today.

[Scott Salley (ssalley)]

I could not reproduce this problem with 'update-manager -d':

On Ubuntu 9.10 Desktop amd64, I installed likewise-open5 and joined a domain. I verified the home directory template settings in the configuration (lassd.conf) and logged in as a domain user -- the home directory corresponded to %H/%D/%U.

I then upgraded using 'update-manager -d'. At the end of installation and subsequent reboot, I was still able to log in as a domain user to the proper home directory (%H/%D/%U). I checked the registry with lwregshell it reported %H/%D/%U for the HomeDirTemplate.

[Pasi Sjöholm (pasi-sjoholm)]

I've been able to reproduce this with Ubuntu 9.10 i386 and I used "update-manager"-cmd.

[David Leon (fongsled)]

Scott:

When I upgraded I could login correctly at first. It took a few days before I was redirected to the new home directory. There was also a package update in the meantime.

Could you check if the configuration files in /etc/likewise-open/ point to %H/%D/%U after the upgrade too? Could it confuse a subsequent update if they don't match the registry?.

[Scott Salley (ssalley)]

I think the package update would explain things. The update overwrote all the existing settings that were present in the registry, ignoring the upgrade. I'll see about fixing that.

> -----Original Message-----
> From: <email address hidden> [mailto:<email address hidden>] On Behalf Of
> David Leon
> Sent: Monday, May 03, 2010 2:28 PM
> To: <email address hidden>
> Subject: [Bug 568422] Re: Upgrading from likewise-open5 changes home
> directorylocations
>
> Scott:
>
> When I upgraded I could login correctly at first. It took a few days
> before I was redirected to the new home directory. There was also a
> package update in the meantime.
>
> Could you check if the configuration files in /etc/likewise-open/ point
> to %H/%D/%U after the upgrade too? Could it confuse a subsequent update
> if they don't match the registry?.
>
> --
> Upgrading from likewise-open5 changes home directory locations
> https://bugs.launchpad.net/bugs/568422
> You received this bug notification because you are a member of Likewise
> Open Developers, which is subscribed to likewise-open in ubuntu.
>
> Status in “likewise-open” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: likewise-open
>
> On a machine correctly joined to a domain with likewise-open5:
>
> The homedir template variable in /etc/likewise-open5/lsassd.conf was
> set to its default:
> [auth provider:lsa-activedirectory-provider]
> ...
> homedir-template = %H/%D/%U
>
> After upgrading to likewise-open on Mon 2010-04-12, package likewise-
> open 5.4.0.42111-2
>
> /etc/likewise-open/lsassd.conf.reg
> [HKEY_THIS_MACHINE\Services\lsass\Parameters\Providers\ActiveDirectory]
> ...
> "HomeDirTemplate"="%H/%D/%U"
> ...
> [HKEY_THIS_MACHINE\Services\lsass\Parameters\Providers\Local]
> ...
> "HomeDirTemplate"="%H/%U"
>
> /etc/likewise-open/lsassd.reg
> [HKEY_THIS_MACHINE\Services\lsass\Parameters\Providers\ActiveDirectory]
> ...
> "HomeDirTemplate"="%H/likewise-open/%D/%U"
> ...
> [HKEY_THIS_MACHINE\Services\lsass\Parameters\Providers\Local]
> ...
> "HomeDirTemplate"="%H/likewise-open/%D/%U"
> ...
> [HKEY_THIS_MACHINE\Services\lsass\Parameters\RPCServers\samr]
> ...
> "HomeDirTemplate"="%H/likewise-open/%D/%U"
>
> lw-edit-reg showed the same configuration as lsassd.reg
>
> The change didn't become apparent right away after the upgrade. I could
> login normally and get all my files, but a few days later, when I
> logged in, I got a new home directory in the new location, looking like
> all my files were lost.
>
> etckeeper recorded a single change, during the upgrade after the apt
> run. The files didn't exist previously.
>
> After a few tries editing the configuration files, changing the
> configuration with lw-edit-reg, clearing the ad cache and rebooting I
> could finally login and get the old home directory back.
>

[Gerald Carter (coffeedude.jerry)]

We have a fix in testing. I will generate new packages for the likewise open PPA in the next 24 hours hopefully and let you know.

[Gerald Carter (coffeedude.jerry)]

Fix committed to the 5.4.0.42111-3~ppa4~lucid package in the "likewise-open-ppa". The root cause was using "lwregshell import" rather than "lwregshell upgrade".

[Etienne Goyer (etienne-goyer-outlands)]

Yuri, I am not sure why you marked this bug as Fix Released - it's not.

Targeting it for 10.04.1, although I am not entirely sure it is relevant considering the likewise-open 5 package is not on the ISO.

[Nico Stöckigt (nico-stoeckigt)]

it's definetly NOT fixed. as far as I found out the *new* registry is not working properly! values are saved and maybe loaded but not applied! this happens to several settings such as home-directory-template, default-domain, cache-times...

[Martin Pitt (pitti)]

Removing 10.04.1 milestone. This is not on the images, and thus we do not need to block on this. Also, presumably this needs to be fixed in maverick as well?

[Jerome Charaoui (jcharaoui)]

I hit this bug when upgrading from 9.10 to 10.04.1. Changing the HomeDirTemplate values did not work, though I tried multiple ways to do it : lw-edit-reg, re-importing *.reg files, purging the confirguration and reinstalling. Packages from the likewise-open PPA did not help either.

I fixed this by removing all Ubuntu likewise-open packages and installing the likewise-open.com "official" package.

[Jerome Charaoui (jcharaoui)]

And I forgot to mention that I also tried the same steps on Ubuntu 10.10, with the same results (ie. original home directory not being used)