search

syndesisio / syndesis-ui

The front end application or UI for Syndesis - a flexible, customizable, cloud-hosted platform that provides core integration capabilities as a service. It leverages Red Hat's existing product architecture using OpenShift Online/Dedicated and Fuse Integration Services.
https://syndesis.io/
14 stars 28 forks source link

Create integration fails silently #328

Closed jludvice closed 7 years ago

jludvice commented 7 years ago

After creating integration in ipaas-ui and clicking on publish, I'm redirected on Integration list page, but my integration is not present and I didn't see any error message.

Inspecting Chrome -> Network tab, I can see HTTP 400 - bad request with response to url https://ipaas-staging.b6ff.rh-idev.openshiftapps.com/api/v1/integrations with response

Unrecognized field "statusType" (class com.redhat.ipaas.model.integration.Integration$Builder), not marked as ignorable

screenshot_20170328_140135

jludvice commented 7 years ago

CC @gashcrumb @kahboom @dsimansk

gashcrumb commented 7 years ago

Yep, probably need to update the model looks like. You'll also notice there's a TODO in the code on error handling at the moment :-)

jludvice commented 7 years ago

Status update - now i see some error (master branch on commit 28e8950fb2a93468cb99aa7b323ab50ba3b2b970) integration-error

gashcrumb commented 7 years ago

Yup, that's it not failing silently :-) But we get a timeout error from the backend which we can't do much about in the frontend, so I think this particular issue is all set from the UI perspective.

@sjcox-rh Do we have an 'error saving' design? I stuck in this quick alert as a stopgap so we at least don't lose the user's work on the frontend side...

KurtStam commented 7 years ago

@gashcrumb @jludvice Can you list any server exception that reaches the UI here: https://github.com/redhat-ipaas/ipaas-rest/issues/247? I can't really see what exception is thrown above exactly since it is a screenshot. We are attempting to handle them all, but it looks like some are slipping through. So if you list them I can go after them. Note that this won't fix the gateway timing out exception. That needs to be address in the whatever the gateway is on OpenShift OnLine.

gashcrumb commented 7 years ago

So that's from the gateway timeout, I think we've some code client-side that's seeing that null response and throwing that error possibly.

kahboom commented 7 years ago

Was this resolved?

gashcrumb commented 7 years ago

As far as the UI is concerned, yes...

On Mar 30, 2017 7:16 AM, "Rachel Yordán" notifications@github.com wrote:

Was this resolved?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/redhat-ipaas/ipaas-ui/issues/328#issuecomment-290380713, or mute the thread https://github.com/notifications/unsubscribe-auth/AAVdrHYGO22_XQ4w4hzlgcB-1y-CWSzwks5rq475gaJpZM4MrfIm .

kahboom commented 7 years ago

Okay, closing this for now then.