Bug #2778

SOGo data disappeared after packages update

Added by Nicola Rauso about 7 years ago. Updated over 6 years ago.

Status:CLOSEDStart date:
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:nethserver-sogo
Target version:v6.6
Security class: Resolution:
Affected version:v6.5 NEEDINFO:Yes

Description

After the update of the packages:

nethserver-mail-server-1.7.0-1.ns6.noarch
nethserver-samba-1.4.3-1.ns6.noarch
nethserver-sogo-1.4.0-1.ns6.noarch

all users data (calendars and contacts) disappeared.


Related issues

Related to NethServer 6 - Feature #2748: Upgrade SOGO to 2.2.15 CLOSED

Associated revisions

Revision c16783de
Added by Stefano Fancello almost 7 years ago

added an action that fix #2778 if it is needed

Revision dc7365b2
Added by Stefano Fancello almost 7 years ago

nethserver-sogo-update event: invoke nethserver-sogo-fix-2778 action. Refs #2778

History

#1 Updated by Nicola Rauso about 7 years ago

NethServer is bound to an AD and uses its users

#2 Updated by Davide Principi about 7 years ago

  • Status changed from NEW to TRIAGED
  • Target version set to v6.5
  • % Done changed from 0 to 20
  • Affected version set to v6.5

The problem affects upgrades to SOGo installations with user accounts from AD environments.

The problem originated from nethserver-sogo-1.4.0-1.ns6.noarch.rpm, in the change of the ID attributes.

It could be fixed with sogo-tool rename-user command, by cycling on every AD user account: the old user id (UIDFieldName) was userPrincipalName, now is sAMAccountName.

#3 Updated by Giacomo Sanchietti almost 7 years ago

#4 Updated by Giacomo Sanchietti almost 7 years ago

  • NEEDINFO changed from No to Yes

I don't understand if we need to develop a migration fragment or something like this. Or we can solve this with some documentation?

The bug is still present?

#5 Updated by Davide Principi almost 7 years ago

Giacomo Sanchietti wrote:

I don't understand if we need to develop a migration fragment or something like this. Or we can solve this with some documentation?

The bug is still present?

Only nethserver-sogo before 1.4.0-1 are affected when update to the latest version. There should not be so many out there, using accounts from Active Directory.

If it's not too expansive, I think is better to implement an action in nethserver-sogo-update event that fixes the problem automatically.

Otherwise it could be documented here and closed as WONTFIX.

#6 Updated by Stefano Fancello almost 7 years ago

  • Status changed from TRIAGED to ON_DEV
  • Assignee set to Stefano Fancello
  • % Done changed from 20 to 30

#7 Updated by Stefano Fancello almost 7 years ago

  • Status changed from ON_DEV to TRIAGED
  • % Done changed from 30 to 20

#8 Updated by Stefano Fancello almost 7 years ago

  • Status changed from TRIAGED to ON_DEV
  • % Done changed from 20 to 30

#9 Updated by Stefano Fancello almost 7 years ago

  • Status changed from ON_DEV to MODIFIED
  • Assignee deleted (Stefano Fancello)
  • % Done changed from 30 to 60
commit c16783dee7ccb47509184fd78106207e4cb64a82

#11 Updated by Stefano Fancello almost 7 years ago

  • Status changed from MODIFIED to ON_QA
  • % Done changed from 60 to 70

#12 Updated by Nicola Rauso almost 7 years ago

  • Assignee set to Nicola Rauso

#13 Updated by Nicola Rauso almost 7 years ago

  • Status changed from ON_QA to VERIFIED
  • Assignee deleted (Nicola Rauso)
  • % Done changed from 70 to 90

Tested: OK

#14 Updated by Giacomo Sanchietti over 6 years ago

  • Target version changed from v6.5 to v6.6-rc1

#15 Updated by Giacomo Sanchietti over 6 years ago

  • Target version changed from v6.6-rc1 to v6.6

#16 Updated by Giacomo Sanchietti over 6 years ago

  • Status changed from VERIFIED to CLOSED
  • % Done changed from 90 to 100
Released in nethserver-base:
  • nethserver-sogo-1.5.0-1.ns6.noarch.rpm

Also available in: Atom PDF