Skip to content
This repository has been archived by the owner on Aug 28, 2023. It is now read-only.

"No schema supplied" when trying to create a ticket #95

Closed
danielgagnon-logient opened this issue Jun 1, 2016 · 8 comments
Closed

"No schema supplied" when trying to create a ticket #95

danielgagnon-logient opened this issue Jun 1, 2016 · 8 comments

Comments

@danielgagnon-logient
Copy link

I configured sentry-jira with a project and it connected to Jira just fine. However when I tried to create a jira ticket from a stacktrace, I got the following error:

Error in request to jira.alogient.com/rest/api/2/priority: Invalid URL 'jira.alogient.com/rest/api/2/priority': No schema supplied. Perhaps you meant http://jira.alogient.com/rest/api/2/priority?

Why would the https:// part be stripped when making that request?

Sentry version: 8.4.1
sentry-jira version: 0.9.0

@dcramer
Copy link
Member

dcramer commented Jun 2, 2016

Did you enter the instance URL with the schema included? I don't know what else would cause this.

@dcramer dcramer closed this as completed Jun 2, 2016
@danielgagnon-logient
Copy link
Author

Yes, https.

And as mentioned in the first line, the initial connection with JIRA works fine, I can see my JIRA project and pick the one I want from the dropbox just fine.

The schema is somehow stripped when I can to create a ticket.

@dcramer
Copy link
Member

dcramer commented Jun 6, 2016

I am unfortunately unable to find any way for this to be possible unless its not entered in with HTTPS

@danielgagnon-logient
Copy link
Author

Any way I can provide some logs that would help shed light on this?

@dcramer
Copy link
Member

dcramer commented Jun 6, 2016

Could you dump the relevant rows from sentry_projectoption? Make sure to only grab instance_url, as password is unencrypted (we really should get away from this auth model).

@danielgagnon-logient
Copy link
Author

id project_id key value
44 5 jira:enabled gAKILg==
51 1 jira:enabled gAKILg==
45 4 jira:username [removed]
46 4 jira:password [removed]
47 4 jira:instance_url gAJYGQAAAGh0dHBzOi8vamlyYS5hbG9naWVudC5jb21xAS4=
48 4 jira:ignored_fields gAJYAAAAAC4=

What kind of encoding is this in?!

@dcramer
Copy link
Member

dcramer commented Jun 6, 2016

@danielgagnon-logient its pickled (Python's native serializer) and encoded via base64. I'll try to find more time to dig into this, but I'm stumped at the moment as the values look fine.

@danielgagnon-logient
Copy link
Author

It also works fine in the config screen. Connects fine, lets me pick the project.

It's only when trying to actually creating the ticket that somethings happens.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants