Segmentation fault in zentyal-services.postinst when upgrading Zentyal

[richard-oss@…]

I am on Ubuntu Precise and upgrade 2.3. I get the following output:

Setting up zentyal-services (2.3.7) ...
Use of uninitialized value $eValue in string eq at /usr/share/perl5/EBox/Model/DataTable.pm line 3281.
Use of uninitialized value $eValue in string eq at /usr/share/perl5/EBox/Model/DataTable.pm line 3281.
Use of uninitialized value $eValue in string eq at /usr/share/perl5/EBox/Model/DataTable.pm line 3281.
Use of uninitialized value $eValue in string eq at /usr/share/perl5/EBox/Model/DataTable.pm line 3281.
Use of uninitialized value $eValue in string eq at /usr/share/perl5/EBox/Model/DataTable.pm line 3281.
Use of uninitialized value $eValue in string eq at /usr/share/perl5/EBox/Model/DataTable.pm line 3281.
Use of uninitialized value $eValue in string eq at /usr/share/perl5/EBox/Model/DataTable.pm line 3281.
Use of uninitialized value $eValue in string eq at /usr/share/perl5/EBox/Model/DataTable.pm line 3281.
Use of uninitialized value $eValue in string eq at /usr/share/perl5/EBox/Model/DataTable.pm line 3281.
Use of uninitialized value $eValue in string eq at /usr/share/perl5/EBox/Model/DataTable.pm line 3281.
Use of uninitialized value $eValue in string eq at /usr/share/perl5/EBox/Model/DataTable.pm line 3281.
Use of uninitialized value $eValue in string eq at /usr/share/perl5/EBox/Model/DataTable.pm line 3281.
/var/lib/dpkg/info/zentyal-services.postinst: line 7: 24461 Segmentation fault      /usr/share/zentyal/initial-setup services $2
dpkg: error processing zentyal-services (--configure):
 subprocess installed post-installation script returned error exit status 139

The $2 parameter to zentyal-services.postinst contains the value 2.3.6 even though I'm installing 2.3.7. I wonder if that is the problem.

[richard-oss@…]

I purged the modules that were causing trouble, and then they installed cleanly. But Zentyal ended up in a really weird state that required a configuration restore. I think I am functional again now.

[jacalvo@…]

This should be fixed with the last published versions of the packages, thanks for reporting!