mdm
April 6, 2019, 11:02am
1
Infos:
Used Zammad version:
Used Zammad installation source: docker-composer
Operating system: ubuntu 18.01
Browser + version: chrome
Expected behavior:
Zendesk migration to proceeed
Actual behavior:
Migration stops with error at the Organization Import step. The reported error refers to a custom field that is defined in zendesk as “multiline text”
Steps to reproduce the behavior:
You need to have a running zendesk with a custom field of multiline text type defined.
zammad-scheduler_1 | I, [2019-04-06T10:56:07.310944 #1-47255222044820] INFO -- : execute Channel.fetch (try_count 0)...
zammad-scheduler_1 | -- add_column("organizations", "go_live", :date, {:default=>nil, :null=>true})
zammad-scheduler_1 | -> 0.0033s
zammad-scheduler_1 | -- add_column("organizations", "status", :string, {:limit=>255, :null=>true})
zammad-scheduler_1 | -> 0.0019s
zammad-scheduler_1 | -- add_column("organizations", "product_type", :string, {:limit=>255, :null=>true})
zammad-scheduler_1 | -> 0.0031s
zammad-scheduler_1 | -- add_column("organizations", "platform_version", :string, {:limit=>255, :null=>true})
zammad-scheduler_1 | -> 0.0022s
zammad-scheduler_1 | E, [2019-04-06T10:56:11.060975 #1-47255269680860] ERROR -- : ImportJob 'Import::Zendesk' failed: Problem with ObjectManager Attribute 'website_url': Validation failed: Data option must have one of text/password/tel/fax/email/url for :type
zammad-scheduler_1 | E, [2019-04-06T10:56:11.061037 #1-47255269680860] ERROR -- : Problem with ObjectManager Attribute 'website_url': Validation failed: Data option must have one of text/password/tel/fax/email/url for :type (ActiveRecord::RecordInvalid)
zammad-scheduler_1 | /usr/local/bundle/gems/activerecord-5.1.6.2/lib/active_record/validations.rb:78:in `raise_validation_error'
zammad-scheduler_1 | /usr/local/bundle/gems/activerecord-5.1.6.2/lib/active_record/validations.rb:50:in `save!'
zammad-scheduler_1 | /usr/local/bundle/gems/activerecord-5.1.6.2/lib/active_record/attribute_methods/dirty.rb:43:in `save!'
zammad-scheduler_1 | /usr/local/bundle/gems/activerecord-5.1.6.2/lib/active_record/transactions.rb:313:in `block in save!'
zammad-scheduler_1 | /usr/local/bundle/gems/activerecord-5.1.6.2/lib/active_record/transactions.rb:384:in `block in with_transaction_returning_status'
zammad-scheduler_1 | /usr/local/bundle/gems/activerecord-5.1.6.2/lib/active_record/connection_adapters/abstract/database_statements.rb:235:in `block in transaction'
zammad-scheduler_1 | /usr/local/bundle/gems/activerecord-5.1.6.2/lib/active_record/connection_adapters/abstract/transaction.rb:194:in `block in within_new_transaction'
zammad-scheduler_1 | /usr/local/lib/ruby/2.4.0/monitor.rb:214:in `mon_synchronize'
zammad-scheduler_1 | /usr/local/bundle/gems/activerecord-5.1.6.2/lib/active_record/connection_adapters/abstract/transaction.rb:191:in `within_new_transaction'
zammad-scheduler_1 | /usr/local/bundle/gems/activerecord-5.1.6.2/lib/active_record/connection_adapters/abstract/database_statements.rb:235:in `transaction'
zammad-scheduler_1 | /usr/local/bundle/gems/activerecord-5.1.6.2/lib/active_record/transactions.rb:210:in `transaction'
zammad-scheduler_1 | /usr/local/bundle/gems/activerecord-5.1.6.2/lib/active_record/transactions.rb:381:in `with_transaction_returning_status'
zammad-scheduler_1 | /usr/local/bundle/gems/activerecord-5.1.6.2/lib/active_record/transactions.rb:313:in `save!'
zammad-scheduler_1 | /usr/local/bundle/gems/activerecord-5.1.6.2/lib/active_record/suppressor.rb:46:in `save!'
zammad-scheduler_1 | /opt/zammad/app/models/object_manager/attribute.rb:370:in `add'
zammad-scheduler_1 | /opt/zammad/lib/import/zendesk/object_attribute/base.rb:19:in `add'
zammad-scheduler_1 | /opt/zammad/lib/import/zendesk/object_attribute/base.rb:11:in `initialize'
zammad-scheduler_1 | /opt/zammad/lib/sequencer/unit/import/zendesk/object_attribute/add.rb:13:in `new'
zammad-scheduler_1 | /opt/zammad/lib/sequencer/unit/import/zendesk/object_attribute/add.rb:13:in `block in process'
Hi @mdm - looks like you found a bug. Please get in touch with us via support@zammad.com and refer to this topic and me. I’ll provide you with a debug script which will help us to resolve this issue. Looking forward to hear from you
Hi @mdm - thanks for reaching out! I was able to reproduce the error and found its cause. It’s actually an issue. So could you please migrate this thread over to GitHub with all the valuable information you already provided? Thanks! I’ll then add my findings so that my colleagues can pick it up and provide a solution.
system
Closed
August 9, 2019, 12:17pm
4
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.