Got a problem with Fedora 33 about perl TimeZone module

Greetings,

I had installed RT 5.0 (not using RPM) on Fedora 33.
The perl-DateTime-TimeZone module is used from the system RPM.
It provided 2020b version of the timezone.

Just now Fedora 33 provide an updated version of the RPM for perl-DateTime-TimeZone, it provides 2020d version of the timezone.

Now for the RT, I cannot browse the settings of an individual user as root.
When the user info page is clicked, it had error on the browser.

Here’s the related log in RT:

[13412] [Thu Oct 29 12:01:30 2020] [error]: Error during compilation of /var/www/rt5/share/html/Elements/SelectTimezone:
Loaded DateTime::TimeZone::Africa::Abidjan, which is from a different version (2020d) of the Olson database than this installation of DateTime::TimeZone (2020b).
Loaded DateTime::TimeZone::Africa::Accra, which is from a different version (2020d) of the Olson database than this installation of DateTime::TimeZone (2020b).
Loaded DateTime::TimeZone::Africa::Algiers, which is from a different version (2020d) of the Olson database than this installation of DateTime::TimeZone (2020b).
.... Too many timezones, I removed lots of them ....
Loaded DateTime::TimeZone::WET, which is from a different version (2020d) of the Olson database than this installation of DateTime::TimeZone (2020b).


Stack:
  [/usr/share/perl5/vendor_perl/HTML/Mason/Interp.pm:450]
  [/usr/share/perl5/vendor_perl/HTML/Mason/Request.pm:1127]
  [/usr/share/perl5/vendor_perl/HTML/Mason/Request.pm:1060]
  [/usr/share/perl5/vendor_perl/HTML/Mason/Request.pm:1239]
  [/var/www/rt5/share/html/Admin/Users/Modify.html:123]
  [/var/www/rt5/share/html/Widgets/TitleBox:61]
  [/var/www/rt5/share/html/Admin/Users/Modify.html:137]
  [/var/www/rt5/share/html/Admin/autohandler:49]
  [/var/www/rt5/sbin/../lib/RT/Interface/Web.pm:710]
  [/var/www/rt5/sbin/../lib/RT/Interface/Web.pm:389]

I reverted back the perl-DateTime-TimeZone RPM and it’s fine now.
How to prevent or fix this problem? Thanks.

Try flushing the Mason cache and then restarting the webserver. You might have a cached copy of the old timezone stuff which is clashing with the new one.

Yes, it worked. Thanks for the help.