Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

join service deployment failure #25

Open
danmelamed opened this issue Jul 5, 2016 · 6 comments
Open

join service deployment failure #25

danmelamed opened this issue Jul 5, 2016 · 6 comments
Labels
Milestone

Comments

@danmelamed
Copy link
Contributor

In dmdp7, the eval query failed with the message

"code": "Conflict",
"message": "{\r\n "code": "Conflict",\r\n "message": "The Stream Analytics job is not in a valid state to perform this operation.",\r\n "details": {\r\n "code": "409",\r\n "message": "The Stream Analytics job is not in a valid state to perform this operation.",\r\n "correlationId": "55c5746d-0a39-415d-b110-0b8527883cda",\r\n "requestId": "911a11d3-66f2-4d4c-a738-6ae18efe7e04"\r\n }\r\n}"

@danmelamed danmelamed added the bug label Jul 5, 2016
@danmelamed danmelamed added this to the R0 milestone Jul 5, 2016
@sidsen
Copy link
Contributor

sidsen commented Jul 6, 2016

Are you able to reproduce this error? If so (or even if not), can you describe the steps you did to arrive at that result?

@eisber
Copy link
Collaborator

eisber commented Jul 6, 2016

Multiple errors in this deployment.

  1. Classic cloud service is not supported in Japan for this subscription.
  2. ASA query is actually in state running. Following up with ASA team.

@eisber
Copy link
Collaborator

eisber commented Jul 6, 2016

@sidsen I think deploying in Japan seems to be the cause of the problem

@lhoang29
Copy link
Contributor

lhoang29 commented Jul 6, 2016

FYI (1) is related to #13.

@sidsen
Copy link
Contributor

sidsen commented Jul 7, 2016

What's the verdict on this, is this a bug we can fix? If not, can we move it out beyond R0?

@eisber
Copy link
Collaborator

eisber commented Jul 7, 2016

We can't fix. Waiting for the team to investigate.

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

No branches or pull requests

4 participants