Another Bugzilla import issue...
Thanks to Anna, I was able to get around one of the issues I encountered while importing our existing BZ database to YouTrack. However now I'm getting the following error on a different Project I'm importing:
Attaching custom fields to project [ 10 ] finished
Importing issues to project [ 10 ]
Traceback (most recent call last):
File "bugzilla2youtrack.py", line 330, in <module>
main()
File "bugzilla2youtrack.py", line 27, in main
bugzilla2youtrack(target_url, target_login, target_pass, bz_db, bz_host, bz_port, bz_login, bz_pass, bz_product_names)
File "bugzilla2youtrack.py", line 273, in bugzilla2youtrack
issues = client.get_issues(product_id)
File "/home/sqa/Downloads/youtrack_python_client_library/bugzilla/bzClient.py", line 240, in get_issues
issue.attachments = self.get_attachments_by_id(row[id_row])
File "/home/sqa/Downloads/youtrack_python_client_library/bugzilla/bzClient.py", line 340, in get_attachments_by_id
attach.content = file_cursor.fetchone()[data_row]
TypeError: 'NoneType' object is not subscriptable
It looks like the failure occurs when grabbing the attachments. No issues are actually showing up in YouTrack. Any thoughts? Thanks!
Please sign in to leave a comment.
Could this error happen due to attachment size? I realized that our current BZ config doesn't have an attachment size limit (some of our log files are gigs in size). Is there a way to set the attachment size limit in YouTrack?
I figured out how to increase the YouTrack attachment limit but unfortunately that didn't help. Still get the error above.
I was able to get around it by just commenting out the Attachment import in the script. This is fine for now as we're evaluating but when/if we do the actual change over, we'd like to keep our attachments intact.
Did all the issues imported fine? When you do a change over I think I will be able to provide you a script that'll just import missing attachments.
Thanks, Anna. It did error out at some point but I was able to get the majoriy of our issues imported -- enough to start the evaluation. I will definitely look you up when we do the actual cutover.
Did you save stacktrace of the error, you've got?