Bugzilla Import "Issue Not Found" problem


I've just attempted to import my Bugzilla database into my freshly made YouTrack server, it managed to upload only 2 issues before this error popped up.

Processing tag [ Morph ]
Traceback (most recent call last):
  File "bugzilla2youtrack.py", line 348, in <module>
  File "bugzilla2youtrack.py", line 29, in main
    bz_product_names, lambda issue: True)
  File "bugzilla2youtrack.py", line 311, in bugzilla2youtrack
    "tag " + t.encode('utf8'))
  File "C:\Users\buildbot\Downloads\youtrack-rest-python-library-master\youtrack-rest-python-library-master\python\youtrack\connection.py", line 620, in execute
    urllib.urlencode(params), body='')
  File "C:\Users\buildbot\Downloads\youtrack-rest-python-library-master\youtrack-rest-python-library-master\python\youtrack\connection.py", line 47, in _req
 raise youtrack.YouTrackException(url, response, content)
youtrack.YouTrackException: Error for http://forum.jetbrains.com/issue/68-22037/execute?command=tag+Morph: 404: Not Found: Issue not found.

'Morph' is a tag in our database used for Morph Target issues, I added the tag manually into YouTrack in an attempt to resolve this, but I still see the error.

Any clues?
Ah, my mistake, the tag wasn't added to the issue, because the issue wasn't even created.

Here's the actual error:
Importing issues to project [ 68 ]
Failed to import issue [ 68-22037 ].Reason :
<item id="22037" imported="false">
<error fieldName="watcherName" value="name@company.com">user login is expected</error>
</item>Request was :  <issue>
ok, we've figured this out, we're only evaluating and have the 10 user trial, looks like we've hit our 10 user limit.
We've recently upgraded our evaluation to have a few more users, to allow me to test our current Bugzilla database within YouTrack, and have ran into another 'Issue not found' import error.

Running the Bugzilla2Youtrack python script I get the attached output.

All I can see from this output is that it's attempting to tag issue 27-46883 with the 'runtime' tag, but can't run the command because the issue hasn't been created.

I notice that the line "can't parse response" is present, suggesting something failed, but I'm cluel
CantParseResponse_Bugzilla2YouTrack.txt (9.3KB)
Hello Jim,
Please attach full import log.
And also it would be great to know what YouTrack and BugZilla versions do you use?
I've checked the logging folder, and can only see 'stdout_20130304.log', a load of 'youtrack.log's and 'catalina.2013-03-04.log'.
None of them appear to contain the actual import output though. I also can't see anything within the python folder of the 'youtrack-rest-python-library-master' directory, maybe I'm missing something?
I've provided any modified files from the YouTrack logs dir, in case that's what you were referring to.

We're evaluating YouTrack 4.1.3, and are importing from Bugzilla version 3.4.6.

I meant log from import script. For example, you can use this command to write log to file: python bugzilla2youtrack.py ... >/import.log
I thought you would have meant that, and initially attempted the method you suggested, I've attached this as stdout.txt (you'll notice that it doesn't actually contain the output from the Python subprocesses, and just displays attempted tag processing)

I modified the bugzilla2YouTrack.py file to add the following.
f = open("stdout2.txt", "w") original_stderr = sys.stderr sys.stderr = f

This creates something a bit more helpful (see stdout2.txt)

Although I'm still no clearer myself, I hope this helps.
stdout.zip (710KB)

EDIT: I'm guessing it's the use of the escape character in the text for comment #4 of issue '46883' that's causing the issue?
Jim, as I can see you have not removed previously imported project.
So, there are a lot of errors about not unique issue ids in logs. Please, delete the project and rerun import.
N.B. To join stdout and stderr use this command: python bugzilla2youtrack.py ... >/import.log 2>&1
OK, following your instruction, I've deleted the project, and re-imported following your command example.
import.log (83KB)
OK, we've sorted this here.
As suggested in my comment above, comment #4 in the bug contained an escape character, which doesn't appear to being handled within the python import script.

The text in question is '[0m□[33m'

We've modified our Bugzilla comments, and managed to import our Framework project error-free.

Thanks for your assistance, but it sounds like a small bug needs creating to handle that character correctly, as it's standard output from Wii execution output.
Yep, it's because of escape sequences in comments. And of course, it's a bug.
Thank you too to help us find this bug!

Please sign in to leave a comment.