Upgrade 6.2 to 6.3 error with success termination?

[disciple]

I am using my night to prepare some migrations

I am about migrating from 6.2 to 6.3 and I am getting this error:

Code: Select all

    Step 18 of 27: Rebuild configuration ...
ERROR: OTRS-otrs.Console.pl-Dev::Code::CPANAudit-10 Perl: 5.30.0 OS: linux Time: Tue Aug 2 00:50:28 2022

 Message: Its not an array!

[b] Traceback (3971): 
   Module: Kernel::System::SysConfig::ConfigurationXML2DB Line: 2690
   Module: scripts::Migration::Base::RebuildConfig Line: 82
   Module: scripts::Migration::Base::RebuildConfig::Run Line: 29
   Module: scripts::MigrateToZnuny6_3::_ExecuteComponent Line: 155
   Module: scripts::MigrateToZnuny6_3::Run Line: 67
   Module: ./scripts/MigrateToZnuny6_3.pl Line: 82[/b]

    Step 19 of 27: Remove Generic Agent system commands ...
    Step 20 of 27: Uninstall merged packages ...
    Step 21 of 27: Initialize default cron jobs ...
    Copying /opt/otrs/var/cron/aaa_base.dist to /opt/otrs/var/cron/aaa_base...
    done.
    Copying /opt/otrs/var/cron/otrs_daemon.dist to /opt/otrs/var/cron/otrs_daemon...
    done.
    Step 22 of 27: Clean up the cache ...
    Step 23 of 27: Rebuild configuration another time ...
    Step 24 of 27: Deploy ACLs ...
    Step 25 of 27: Deploy processes ...
    Step 26 of 27: Check invalid settings ...
    Step 27 of 27: ITSM upgrade check ...



 Migration completed! 

I am confused. Here I see a traceback but migration seems to be completed?

[shawnbeasley]

Migration complete is the important part. Have fun and enjoy your updated system.

[disciple]

Migration complete is the important part. Have fun and enjoy your updated system.

Thank you for your feedback, but a traceback is IMHO a unexpected issue.
I tried to understand the corresponding source code at the given lines to see if I can find the root cause. But I am too far away from perl and Znuny

Since I am afraid of loosing configs - or - my new building is built on a broken basement, I want to ensure to have clean migrated environment.
Can you let me know why you are sure the migration was done properly?

[root]

Hi,

Could your check in your SysConfig (Kernel/Config/Files/ZZZAAuto.pm) of the 6.2 if there is a setting for Package::RepositoryList? If yes keep that in mind. The reason for your traceback is that the data structure for this setting changed in 6.3.2. If you had repositories configured you can configure them after the migration to 6.3 again.

- Roy

[disciple]

Thank you for clarification.

I have manually removed from ZZZAAuto the entry (below). And it was only Znuny listed there. But not sure if this is the right approach?

Code: Select all

$Self->{'Package::RepositoryList'} =  {
  'https://addons.znuny.com/api/addon_repos/public' => 'Addons - Znuny4OTRS / Public'
};

after having removed this code block

Code: Select all

ERROR: OTRS-otrs.Console.pl-Dev::Code::CPANAudit-10 Perl: 5.30.0 OS: linux Time: Tue Aug 2 19:57:27 2022

 Message: Its not an array!

 Traceback (4475): 
   Module: Kernel::System::SysConfig::ConfigurationXML2DB Line: 2690
   Module: scripts::Migration::Base::RebuildConfig Line: 82
   Module: scripts::Migration::Base::RebuildConfig::Run Line: 29
   Module: scripts::MigrateToZnuny6_3::_ExecuteComponent Line: 155
   Module: scripts::MigrateToZnuny6_3::Run Line: 67
   Module: ./scripts/MigrateToZnuny6_3.pl Line: 82

So the error is still exactly the same

tried to uninstall pre-upgrade a custom add-on as of my understanding from viewtopic.php?f=34&t=43154&p=175018&hil ... DB#p175018
but sadly also no success.

Sadly the error message is also useless, so that I have no clue what I shall change.

Also wondering if this issue will be the same for the users later switching from 6.0 LTS to 6.x LTS?
Will they require to step through the intermediate upgrades 6.0->6.1->6.2->6.3->6.4->6.5 ...?
In this case the error will probably be faced by more persons?

[root]

Hi,

You should read more carefully, I've never told you to remove the code. I just explained what the root cause is. Besides that this code is in the file there are other places with the data structure e.g. in the database.

- Roy

[disciple]

okay, sorry misunderstood.
I appreciate that you wanted to explain the root cause, but I haven't understood it in my specific case.
Especially it is unclear since the traceback is not really helpful as meta information are missing to the user.

Can I somehow increase log level during upgrading?

For me it is unclear if I have to do something or not.
The traceback implies it is a non expected issue from coding side.

From my side I am afraid to move ahead without knowing what the root cause of the reported issue. And if I can move ahead without fetching a later unwished issue due to the fact the migration somehow failed. Hope i could explain my issue here better?

[hkais]

no hints in this case?

having faced the same issue here too

after fiddling around found this (german) post, which looks to me related.
viewtopic.php?f=35&t=43180

What format did change, and is there a push/commit to review to understand this issue better?