Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Imported integration with extension does not import the extension #4981

Closed
mmuzikar opened this issue Mar 20, 2019 · 9 comments
Closed

Imported integration with extension does not import the extension #4981

mmuzikar opened this issue Mar 20, 2019 · 9 comments
Assignees
Labels
cat/bug A bug which needs fixing closed/verified Used by QE to indicate that verified the issue prio/p0 The priority of a bug. p0 means blocking source/qe Raised by QE

Comments

@mmuzikar
Copy link
Contributor

This is a...


[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Documentation issue or request

Description

I created a simple integration
Timer -> OpenAPI connector -> Script Extension -> Log
Exported it, manually deleted all connections, OpenAPI specifications and extensions. The OpenAPI connector gets imported while importing the integration, but the integration gets imported with empty step instead of the Script extension, although the .jar file is present in the exported file ZIP.

@mmuzikar mmuzikar added cat/bug A bug which needs fixing prio/p0 The priority of a bug. p0 means blocking source/qe Raised by QE labels Mar 20, 2019
@pure-bot pure-bot bot added the notif/triage The issue needs triage. Applied automatically to all new issues. label Mar 20, 2019
@heiko-braun
Copy link
Collaborator

@gaughan Do you think this classifies for p0?

@gaughan
Copy link

gaughan commented Mar 20, 2019

yes

@heiko-braun heiko-braun added this to the Sprint 43 (4/4) milestone Mar 20, 2019
@heiko-braun heiko-braun removed the notif/triage The issue needs triage. Applied automatically to all new issues. label Mar 20, 2019
@dhirajsb dhirajsb self-assigned this Mar 20, 2019
@dhirajsb
Copy link
Contributor

dhirajsb commented Mar 20, 2019

@mmuzikar can you attach the test export zip you created? It will help to easily recreate this issue.

@mmuzikar
Copy link
Contributor Author

Sure, here you are 😄

todo-test-export.zip

@dhirajsb
Copy link
Contributor

I tried importing it the first time and it imported the script correctly:
image

@dhirajsb
Copy link
Contributor

When I tried re-importing the same integration after deleting the integration, connection, API spec and extension, I am able to reproduce the missing step issue:
image

dhirajsb added a commit to dhirajsb/syndesis that referenced this issue Mar 21, 2019
dhirajsb added a commit to dhirajsb/syndesis that referenced this issue Mar 21, 2019
@dhirajsb
Copy link
Contributor

@mmuzikar PR #5012 should fix this issue. You can test it off the PR branch if you like.
@heiko-braun I've added the backport 1.6.x label as well.

@dhirajsb
Copy link
Contributor

dhirajsb commented Apr 1, 2019

@mmuzikar please close this issue after verifying.

dhirajsb added a commit to dhirajsb/syndesis that referenced this issue Apr 3, 2019
@mmuzikar mmuzikar added the closed/verified Used by QE to indicate that verified the issue label Apr 3, 2019
@mmuzikar
Copy link
Contributor Author

mmuzikar commented Apr 3, 2019

Extension are now imported, thanks @dhirajsb

@mmuzikar mmuzikar closed this as completed Apr 3, 2019
@pure-bot pure-bot bot locked as resolved and limited conversation to collaborators Apr 3, 2019
@pure-bot pure-bot bot reopened this Apr 3, 2019
@pure-bot pure-bot bot unlocked this conversation Apr 3, 2019
@mmuzikar mmuzikar closed this as completed Apr 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cat/bug A bug which needs fixing closed/verified Used by QE to indicate that verified the issue prio/p0 The priority of a bug. p0 means blocking source/qe Raised by QE
Projects
None yet
Development

No branches or pull requests

4 participants