Loading...

XML

Word

Printable

Fuse Progress Bar:

% %
Target Release:

fuse-7.5-GA
Steps to Reproduce:

Hide

1. create integration for instance webhook -> log
2. notice the token - the access route should be created by default
3. there are options for exposing using 3scale and not exposing using 3scale, but no route to run webhook

Show
1. create integration for instance webhook -> log 2. notice the token - the access route should be created by default 3. there are options for exposing using 3scale and not exposing using 3scale, but no route to run webhook

When creating integration which uses webhook - the route is not created.

Marked as a blocker because this is a regression.

Edit: this is also applicable to the API-provider based integrations

Edit2: this issue also seems to cause after several attempts to create API-provider based integration unhealthy Syndesis server-pod status with following the server pod restart.
This causes the QE tests to fail, as the server pod is not available:
https://fuse-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/syndesis-qe/view/Syndesis/job/syndesis-tests-chrome/257/Cucumber_20report_20-_20chrome/