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

Repeated API calls orchestration results in error response #76

Open
joseph-v opened this issue Jun 14, 2019 · 4 comments
Open

Repeated API calls orchestration results in error response #76

joseph-v opened this issue Jun 14, 2019 · 4 comments
Assignees
Labels
backlog Backlog items - consider for next planning always

Comments

@joseph-v
Copy link
Contributor

Calling API endpoint immediately after first call results in SQLAlchemy session error response

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug

What happened:
Error response

What you expected to happen:
We should be able to call API endpoint immediately

@skdwriting
Copy link
Contributor

@kumarashit and @joseph-v can we close this?

@kumarashit
Copy link
Collaborator

Issue analysis:
This issue is very limited to Service definition being creation. In the call to create service definition, we are updating table out of session scope. The sessionmaker for DB has autocommit=false. So there need to be explicit commit. There is another call to add service_definition and commit which will eventually commit. So we may land into this issue.
Ideal fix will be to use all update/add in session scope.
As this call is done by installer only as of now and the changes are involved too. So IMO, these changes can be done later.
@skdwriting @joseph-v @wisererik please suggest

@skdwriting
Copy link
Contributor

  1. Please mark this as a known issue and also provide the workaround for custom service definition through scripts
  2. This needs to be handled later. Moving to backlog.

@skdwriting
Copy link
Contributor

No impact on the current service definition and testing from dashboard

@skdwriting skdwriting added backlog Backlog items - consider for next planning always and removed CAPRI Handle for CAPRI 18th June 2019 labels Jun 15, 2019
@skdwriting skdwriting added this to the Daito SODA v1.0 milestone Oct 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Backlog items - consider for next planning always
Projects
None yet
Development

No branches or pull requests

3 participants