Imported extension fails when building integration #5097
Comments
mmuzikar
added
cat/bug
pure-bot
bot
added
the
notif/triage
heiko-braun
removed
the
notif/triage
|
@mmuzikar This looks to me as if the spme of the prod artefacts cannot resolved from central, which is expected I think: |
|
Or is |
|
I am on the 1.6.X branch if that helps, but I think this was also happening on master on Friday |
|
@dhirajsb Can you try to reproduce it on 1.6.x? |
|
I will take a look at this today. |
|
The |
|
@zregvart yeah, that seems like a likely possibility. |
|
@heiko-braun i have found a potential bug in the way extensions are being imported when part of an integration. I am working on a fix that I will finish tomorrow. |
|
@mmuzikar Can you redo the test? We suspect that between exporting and importing the dev build artefacts have been purged (they have a short lifespan) |
|
Thanks @dhirajsb , so we don't need to redo the test for now? |
heiko-braun
added
prio/p1
|
Changing to |
…rect id, which was causing project generation to fail
|
I tested importing the integrations again. The same error happens when I use the exported integration I provided (which is from an older instance of Syndesis) but exporting and then importing in the same version works correctly. |
Fixes #5097, fixed extension import to write files with correct id, which was causing project generation to fail
|
With #5126 merged to |
|
I think Dhiraj created a separate PR to backport this |
|
Its here #5127 |
|
@mmuzikar I tested the zip you provided in a 1.7.x instance and it worked with no issues. I did not see the same issue in 1.6.x either. But I was having some other trouble late last night with missing 1.6-SNAPSHOT artifacts in S2I build for some reason, which should be in the 1.6.x S2I image already. I am planning on testing it again today on a fresh build. Also, the issue I fixed would actually show up if you exported and imported into a brand new instance. Or you could reinstall and try importing the same zip again. I discovered it while I was messing around with the DB and I deleted the old extension records. We apparently need to test more import use cases. |
mmuzikar
added
the
closed/verified
This is a...
Description
relates to #4981
If you import an exported integration which used extension then that extension is imported as well, but for some reason the imported integration can't be built if you use the imported extension.
I tried to build the same integration with importing everything manually (not from the integration zip) and the integration builds and works.
Attaching log from the build phase
And also the exported integration todo-test-export.zip
The text was updated successfully, but these errors were encountered: