search

juanluisbaptiste / docker-otrs

The unofficial Znuny/OTRS Ticketing System docker image
https://www.juanbaptiste.tech/category/otrs
GNU Lesser General Public License v3.0
173 stars 101 forks source link

Migrating to Znuny #104

Open fajfer opened 3 years ago

fajfer commented 3 years ago

Due to OTRS community edition no longer available, Znuny has made a statement to support OTRS 6 with newer versions under the new name.

Source: https://forums.otterhub.org/viewtopic.php?f=53&t=42228 https://www.znuny.org/why https://github.com/znuny/znuny

Any comment on this? Are there any plans of migrating to znuny instead of staying with the now-dead OTRS 6?

juanluisbaptiste commented 3 years ago

Hi @sjal ,

Well this was something that I saw coming for some time now, OTRS AG has not been very transparent with that would happen with the future of the community edition, after OTRS 8 was released and there wasn't a community edition ver 7 I supposed that version had come to an end and we would have to wait for the official announcement, that has now happened.

So yes, I will support znuny too, as soon as I can.

fajfer commented 3 years ago

Cool, great :)

OTRS 7 was supposed to be open sourced November 2020 - which obviously never happened. Glad to hear you're planning to support Znuny

juanluisbaptiste commented 3 years ago

Hi @fajfer I have pushed on juanluisbaptiste/znuny:latest a first version using the znuny release for testing.

I'm still unsure if I should update juanluisbaptiste/otrs to the znuny branch so current users also get the updated versions as currently znuny is an LTS release of OTRS community edition, so there will not be any breaking changes. Or stop maintaining the otrs branch and switch development to the znuny branch.

The issue with the first option is that branding has been changed from ((OTRS)) Community Edition to ZNuny LTS so it could confuse users, but is just a cosmetic change. The other option is to maintain both for some time and then when the znuny repo is better known as the alternative stop maintaining the otrs repo and stick with znuny only.

WDTY ?

rkaldung commented 3 years ago

@juanluisbaptiste Without reading all of your detailed documentation, it is important to make sure the System Configuration is rebuild properly and the update script is always executed:

fajfer commented 3 years ago

I think we should let everyone who doesn't follow these stuff that OTRS they were using is now deprecated. We could keep znuny as separate branch to try to stabilize it (I can help out with the tests, I'm almost done struggling with my thesis but I'm a daily OTRS user). I leave the choice entirely to yourself, obviously, as you're the owner of the repo. What I would do, is implement deprecation warnings, keep master for a while with warnings on the deprecation until our version of the Znuny image is stable (while allowing others to test it) and then after you're happy with it just make it the new master. I wouldn't really then bother with implementing new features to the deprecated branch at all

juanluisbaptiste commented 3 years ago

@juanluisbaptiste Without reading all of your detailed documentation, it is important to make sure the System Configuration is rebuild properly and the update script is always executed:

* `bin/otrs.Console.pl Maint::Config::Rebuild --cleanup` - remove old, deprecated settings which are not present in any of the install files in Kernel/Config/Files/XML/, see also [znuny/Znuny#12](https://github.com/znuny/Znuny/issues/12) as an example

I was not aware of this command, I don't remember seeing it on the official docs but I can add it.

* `scripts/DBUpdate-to-6.pl` should take care of all other tasks which need to be performed even after a patch level upgrade

This script is run both when doing minor or major upgrades when doing the database upgrade.

juanluisbaptiste commented 3 years ago

Hey,

* `bin/otrs.Console.pl Maint::Config::Rebuild --cleanup` - remove old, deprecated settings which are not present in any of the install files in Kernel/Config/Files/XML/, see also [znuny/Znuny#12](https://github.com/znuny/Znuny/issues/12) as an example

Added. I also have been testing the upgrade from OTRS and everything is going fine! the only thing I noticed is that ftp.otrs.org is down, so the Package Manager is not working and takes a lot of time to load while it times out with this error on the log output:

Message: Can't perform GET on https://ftp.otrs.org/pub/otrs/misc/packages/repository.xml: 500 Can't connect to ftp.otrs.org:443
otrs_1     | 
otrs_1     |  RemoteAddress: 172.19.0.1
otrs_1     |  RequestURI: /otrs/index.pl?Action=AdminPackageManager
otrs_1     | 
otrs_1     |  Traceback (94): 
otrs_1     |    Module: Kernel::System::WebUserAgent::Request Line: 221
otrs_1     |    Module: Kernel::System::Package::_Download Line: 3583
otrs_1     |    Module: Kernel::System::Package::PackageOnlineRepositories Line: 1341
otrs_1     |    Module: Kernel::Modules::AdminPackageManager::Run Line: 1526
otrs_1     |    Module: Kernel::System::Web::InterfaceAgent::Run Line: 1135
otrs_1     |    Module: ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler Line: 38
otrs_1     |    Module: (eval) (v1.99) Line: 207
otrs_1     |    Module: ModPerl::RegistryCooker::run (v1.99) Line: 207
otrs_1     |    Module: ModPerl::RegistryCooker::default_handler (v1.99) Line: 173
otrs_1     |    Module: ModPerl::Registry::handler (v1.99) Line: 32

@rkaldung I don't know if it is temporal or not but really I think they just removed it so it needs to be updated with Znuny FTP address.

Apart from that the upgrade went fine ! Tomorrow I will start working on updating the README file with information about the switch.

juanluisbaptiste commented 3 years ago

@fajfer did you test the znuny beta image?

rkaldung commented 3 years ago

@juanluisbaptiste The latest release contains the fixed URL pointing to download.znuny.org

juanluisbaptiste commented 3 years ago

@kordianbruck excellent, I will update the beta image.

juanluisbaptiste commented 3 years ago

@kordianbruck excellent, I will update the beta image.

Updated and new images being built.

fajfer commented 3 years ago

@fajfer did you test the znuny beta image?

Hey, yes I have in the testing environment. I've used the newest image also but generally have no problems whatsoever - they seem to work flawlessly but since Znuny is (for now) mostly security updates it was kinda expected

I'm planning to update my company's OTRS to Znuny this weekend, haven't tested this on fresh install but I'm going to do it this weekend as well

juanluisbaptiste commented 3 years ago

@fajfer Excellent !

juanluisbaptiste commented 3 years ago

@fajfer how went your migratoin ? I have migrated other of my customers with no issues.

I'm sorry I have not finished the switch but I will work on this over these weekend.

fajfer commented 3 years ago

Hey, I forgot I did the migration actually, which might be a good sign.

No hurry whatsoever about the switch, wishing you a blessed and holy Easter!

juanluisbaptiste commented 3 years ago

Ok I added a notice to the README file letting now that we now use the znuny release and pushed new images using it.

juanluisbaptiste commented 3 years ago

Hi @rkaldung and @fajfer , I noticed that now Znuny started releasing a new version with new features since 6.1.x. I updated the image to the LTS release (v6.0.36), but I plan to support both. The master branch will use the new 6.1.x release and znuny_6_0_x branch will be used for the LTS version.

I'll let you know when this is ready, probably for next week.

rdxmb commented 3 years ago

Hallo,

I am still running juanluisbaptiste/otrs:6.0.28

Thanks for your great work!

juanluisbaptiste commented 3 years ago

@rdxmb yes, you can use it without issues, but I still only support the LTS release, the latest release is 6.0.36.

I haven't had time to work with the new Znuny versions yet (6.1.x), which have new features.

rdxmb commented 3 years ago

@juanluisbaptiste ok, thanks

rkaldung commented 3 years ago

@rdxmb yes, you can use it with issues, but I still only support the LTS release, the latest release is 6.0.36.

@juanluisbaptiste What are the issue? Maybe I can help.

juanluisbaptiste commented 3 years ago

@rkaldung with the LTS version none, with the new releases, lack of time to work on it :disappointed:

juanluisbaptiste commented 3 years ago

Oops now I get what you meant, it should have been without issues, I just updated my answer.

rdxmb commented 2 years ago

Hello @juanluisbaptiste , I see that https://hub.docker.com/layers/juanluisbaptiste/otrs has tags like 6.0.36 and 6.0.37 , while https://hub.docker.com/r/juanluisbaptiste/znuny/tags has only older images

I'm still unsure if I should update juanluisbaptiste/otrs to the znuny branch

So you decided to push the znuny-Images to https://hub.docker.com/layers/juanluisbaptiste/otrs ?

Kind regards and thanks again for your great work with this project.

juanluisbaptiste commented 2 years ago

As the tagging process of versioned images is a manual process I'm only tagging the images from juanluisbaptiste/otrs, and znuny only has an auto-build of the master branch. I have deleted the 6.0.32 and 0.33 tags on juanluisbaptiste/znuny for now to avoid confusions.

juanluisbaptiste commented 2 years ago

As the tagging process of versioned images is a manual process I'm only tagging the images from juanluisbaptiste/otrs, and znuny only has an auto-build of the master branch. I have deleted the 6.0.32 and 0.33 tags on juanluisbaptiste/znuny for now to avoid confusions.

At some point I will have to do it the other way around or work on automating those tagged builds for both repos.

juanluisbaptiste commented 2 years ago

I also started to work on supporting the new znuny versions, today I sync'ed the znuny_6_0_x branch with master, and built the latest 6.0.38 release from there, that way master now can be used for the new releases and znuny_6_0_x will be used for LTS releases only. I also did a rebuild of master with znuny 6.2.1 and it seems to work fine with no modifications to the image, so I will be pushing that release shortly, but first I need to update the documentation too.

The main issue now is that I do not have many time to work on this, since I switched jobs some months ago I'm not using this images any more so I have less time to work on them, any help would be appreciated.

rdxmb commented 2 years ago

Thanks for your answer and the transparent information. I will check if I can support this project.

Mickaelh51 commented 2 years ago

Hi, I started to upgrade Znuny image to last version. I will push with PR, but I don't know when, I have no time too ;)

++

Le mar. 9 nov. 2021 à 10:06, Marc Bihlmaier @.***> a écrit :

Thanks for your answer and the transparent information. I will check if I can support this project.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/juanluisbaptiste/docker-otrs/issues/104#issuecomment-963949686, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACLNNXEYFBB5L7KLVYLKYW3ULDQCPANCNFSM4WHJH3IQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

juanluisbaptiste commented 2 years ago

Hi @Mickaelh51 , PR for what ?

Mickaelh51 commented 2 years ago

Hi Upgrade image to last lts version.

Le mar. 9 nov. 2021 à 23:48, Juan Luis Baptiste @.***> a écrit :

Hi @Mickaelh51 https://github.com/Mickaelh51 , PR for what ?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/juanluisbaptiste/docker-otrs/issues/104#issuecomment-964616075, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACLNNXGNYIJ5H44T62EKEPDULGQNPANCNFSM4WHJH3IQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

juanluisbaptiste commented 2 years ago

That was done already this week.

Mickaelh51 commented 2 years ago

lol sorry, I didn't see that ;)

rdxmb commented 2 years ago

Is there a plan for renaming the env variables (OTRS_*)? Is there any plan for that - or will you keep the otrs-naming?

rkaldung commented 2 years ago

My guess he's waiting for Znuny to have settings etc. renamed. It's on the list of open issues but this is a huge change because existing values needs to be renamed to. Just think about templates, auto replies, notifications, etcl.

rdxmb commented 2 years ago

this is a huge change

Yes, this is the reason of my question

juanluisbaptiste commented 2 years ago

Is there a plan for renaming the env variables (OTRS_*)? Is there any plan for that - or will you keep the otrs-naming?

@rkaldung currently I do not have plans on renaming variables, it is a huge work and I do not see the benefit from doing so, it is more of a cosmetic change and I do not have the time to spend on that. There are more important things to work on, like supporting the latest 6.x versions, which I have been working on for many weeks but haven't had the time to finish testing the upgrade procedures.

rdxmb commented 2 years ago

I've just upgraded from 6.0.28 to 6.0.40. Seems there are some jquery problems, so login is not possible.

From https://community.znuny.org/viewtopic.php?t=43031 I've tried to cleanup the caches

bin/otrs.Console.pl Maint::Loader::CacheCleanup
bin/otrs.Console.pl Maint::Loader::CacheGenerate

But it did not help. After that I added 

$Self->{"Loader::Enabled::JS"} = 0;

to 

/opt/otrs/Kernel/Config.pm

and the error changed to

Namespace Core.UI.Dialog could not be initialized, because jQuery UI draggable could not be found.

Changing several files manually seems not to be a solution for me - so please let me ask if upgrade 6.0.28 to 6.0.40 is supported and if I missed any manual migration steps? (If you want me to create a new issue for that, please let me know)

Thanks and kind regards!

rkaldung commented 2 years ago

From Znuny this is supported, as long as the migration script is executed. Between 6.0.28 and 6.0.40 the version of Jquery changed. Since the version number is used in the path sometimes it is required to check the system configuration. I recommend exporting the system configuration (only changed settings are exported) and search in the file for jquery related changes and check the path.

rdxmb commented 2 years ago

Thanks for your quick answer! @rkaldung

Since the version number is used in the path sometimes it is required to check the system configuration. I recommend exporting the system configuration (only changed settings are exported) and search in the file for jquery related changes and check the path.

I have exported the system settings. There is no jquery within that file.

However, I can reproduce that with a "fresh" container: https://github.com/juanluisbaptiste/docker-otrs/issues/123

juanluisbaptiste commented 2 years ago

Probably the same issue #118

enricoandreoli commented 1 year ago

I'm on OTRS 6.0.22. Is there an easy way to migrate to latest release of znuny?

DevFontes commented 1 year ago

We are migrating from 6.0.24 to 6.0.45

I made a backup using the /otrs/scripts/backup.pl script and restored it from a deploy of the most current image available on github following the backup and restore documentation. Our deployment was done on a Kubernetes cluster.

Some problems arose and were circumvented with the scripts

/opt/otrs/bin/otrs.Console.pl Admin::package::ReinstallAll -s /bin/bash otrs

/opt/otrs/bin/otrs.Console.pl Maint::Cache::Delete -s /bin/bash otrs

/opt/scripts/scripts/DBUpdate-to-6.pl

Now when clicking on any existing ticket we get the error:

Message: Can't locate Kernel/Output/HTML/TicketMenu/TeaserAttachmentView.pm in @INC (@INC contains: /opt/otrs/Custom /opt/otrs/Kernel/cpan-lib /opt/otrs/ /usr/local /lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 . /etc/httpd) at /opt/ otrs//Kernel/System/Main.pm line 86.

On that page I saw that the script below would be a possible solution but I still couldn't make it work

$ /opt/otrs/bin/otrs.Console.pl Maint::Config::Rebuild --cleanup
Rebuilding the system configuration...
ERROR: OTRS-otrs.Console.pl-Maint::Config::Rebuild-10 Perl: 5.16.3 OS: linux Time: Mon May 15 18:30:10 2023

 Message: Setting Fetchmail::Bin Effective value is not correct: /usr/bin/fetchmail not exists!

 Traceback (1301): 
   Module: Kernel::System::SysConfig::ConfigurationDeploy Line: 3486
   Module: Kernel::System::Console::Command::Maint::Config::Rebuild::Run Line: 138
   Module: (eval) Line: 461
   Module: Kernel::System::Console::BaseCommand::Execute Line: 455
   Module: Kernel::System::Console::InterfaceConsole::Run Line: 81
   Module: /opt/otrs/bin/otrs.Console.pl Line: 37

Error: There was a problem writing ZZZAAuto.pm.