Missing action parameter after upgrade

[j.stutterheim@…]

I was installing the latest updates (including zentyal-core 2.2.1), then it suddenly restarted and gave me this error.

Error

Missing action parameter

Trace

Missing action parameter at /usr/share/perl5/EBox/CGI/Software/InstallPkgs.pm line 63
	EBox::CGI::Software::InstallPkgs::_process('EBox::CGI::Software::InstallPkgs=HASH(0x7f244360e620)') called at /usr/share/perl5/EBox/CGI/Base.pm line 275
	EBox::CGI::Base::run('EBox::CGI::Software::InstallPkgs=HASH(0x7f244360e620)') called at /usr/share/perl5/EBox/CGI/Run.pm line 129
	EBox::CGI::Run::run('EBox::CGI::Run', 'Software/InstallPkgs', 'EBox') called at /usr/share/zentyal/cgi/ebox.cgi line 34
	ModPerl::ROOT::ModPerl::Registry::usr_share_zentyal_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0x7f2441882e30)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
	eval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
	ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0x7f24454281c8)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
	ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x7f24454281c8)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
	ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0x7f2441882e30)') called at -e line 0
	eval {...} called at -e line 0

[anonymous]

zentyal.log

[anonymous]

software.log

[jacalvo@…]

It is due to a change in the cookie name in 2.2.1 to avoid problems with some browsers. When apache is restarted at the end of the installation, you lose the session and gets redirected to login, and you get the error because the login tries to get back to the previous page (the InstallPkgs? CGI which is no longer valid are there are parameters missing).

We'll see if we can do this better on 2.2.2, but don't worry at all, because the error is completely harmless, you will be able to keep using Zentyal and installing or updating packages without problems with the new cookie.

[jacalvo@…]

In 2.2.2 we have finally opted by revert the change due to the high number of reports like this. People you were already upgraded to 2.2.1 will probably experience this again (just one time) when upgrading to 2.2, but that's all. As I said in the previous comment, this is completely harmless for the server functioning.