[rudder-dev] rules and directives gone after upgrade to nightly

[Nicolas Perron]

> On Wednesday 12 Sep 2012 14:36:43 Nicolas Perron wrote:
>> Can you give us the output of these command, please ?:
>>
>> /cd /var/rudder/configuration-repository/ && git log/
>> /
> The only commits since before starting the upgrade to nightly are:
>
>
> commit 7896312c9677198b952f83b1e1afa85de2cc56e3
> Author: root <root at centostest.(none)>
> Date:   Wed Sep 12 10:45:48 2012 +0100
>
>     Propagate deletion of system Techniques - from rudder-
> techniques at c164347663460ea2fa0e9d7db1dd43f421ceb996
>
> commit 834d50918591adfcd4acc76192bc2a0eab50408e
> Author: root <root at centostest.(none)>
> Date:   Tue Sep 11 22:58:19 2012 +0100
>
>     Upgrade system Techniques - automatically done by rudder-upgrade script
>
>
> Where commit 7896312c9677198b952f83b1e1afa85de2cc56e3 was actually me 
> deleting techniques/system/distributePolicy/1.0/logrotate.st as it was causing 
> upgrade to fail.
>
> As far as I can see there were no renames in the other commit, only changes to 
> do with disable_agent.
>
>> //find /var/rudder/configuration-repository/ -name "category.xml"/
> (did a cd and find . for shorter paths)
>
> ./techniques/fileConfiguration/fileSecurity/category.xml
> ./techniques/fileConfiguration/category.xml
> ./techniques/system/category.xml
> ./techniques/systemSettings/networking/category.xml
> ./techniques/systemSettings/process/category.xml
> ./techniques/systemSettings/security/category.xml
> ./techniques/systemSettings/category.xml
> ./techniques/systemSettings/misc/category.xml
> ./techniques/systemSettings/userManagement/category.xml
> ./techniques/systemSettings/remoteAccess/category.xml
> ./techniques/systemSettings/systemManagement/category.xml
> ./techniques/category.xml
> ./techniques/fileDistribution/category.xml
> ./techniques/applications/category.xml
> ./techniques/jobScheduling/category.xml
> ./directives/fileConfiguration/fileSecurity/category.xml
> ./directives/fileConfiguration/category.xml
> ./directives/systemSettings/networking/category.xml
> ./directives/systemSettings/process/category.xml
> ./directives/systemSettings/security/category.xml
> ./directives/systemSettings/category.xml
> ./directives/systemSettings/misc/category.xml
> ./directives/systemSettings/userManagement/category.xml
> ./directives/systemSettings/remoteAccess/category.xml
> ./directives/systemSettings/systemManagement/category.xml
> ./directives/category.xml
> ./directives/fileDistribution/category.xml
> ./directives/applications/category.xml
> ./directives/jobScheduling/category.xml
> ./groups/category.xml
>
>
>> It could be due to the latest modifications in packaging which involve
>> the renaming of a folder in //var/rudder/configuration-repository/ .
>>
>> /Thanks/
> Many thanks for helping out Nicolas!  Let me know what else to check.
>
Ok, then it could be due to LDAP which fail during migration. Do you
have the output from the migration and if so could you send it to us ?

I've tried to reproduce your problem without success.
Could it be possible to have a dump of your LDAP base with
/opt/rudder/sbin/slapcat , please ?

-- 
==========================================
Nicolas PERRON
------------------------------------------
Normation
87 rue de Turbigo, 75003 Paris, France
------------------------------------------
Telephone:  +33 (0)1 83 62 56 79
Mobile:     +33 (0)6 24 79 31 79
------------------------------------------
Web:        http://www.normation.com/
==========================================