Fix incorrect vsp version id in upgrade

During the upgrade of a VF through a VSP, the VSP version id passed to
the backend is always the current VF version id, not the one to
upgrade.
Even passing the correct VSP version id, the backend was not
persisting the latest version id in the metadata, keeping always the
previous one.

Change-Id: Ife2b92789d47a63ba5358c6ed8db8279db94ed46
Issue-ID: SDC-3790
Signed-off-by: andre.schmid <andre.schmid@est.tech>
Signed-off-by: krupa.nagabhushan <krupa.nagabhushan@est.tech>

1 files changed, 0 insertions, 3 deletions

diff --git a/catalog-be/src/main/java/org/openecomp/sdc/be/components/impl/ResourceBusinessLogic.java b/catalog-be/src/main/java/org/openecomp/sdc/be/components/impl/ResourceBusinessLogic.java
index f7beca6200..666529986c 100644
--- a/catalog-be/src/main/java/org/openecomp/sdc/be/components/impl/ResourceBusinessLogic.java
+++ b/catalog-be/src/main/java/org/openecomp/sdc/be/components/impl/ResourceBusinessLogic.java
@@ -3640,9 +3640,6 @@ public class ResourceBusinessLogic extends ComponentBusinessLogic {
             if (oldResource.getCsarUUID() != null) {
                 newResource.setCsarUUID(oldResource.getCsarUUID());
             }
-            if (oldResource.getCsarVersionId() != null) {
-                newResource.setCsarVersionId(oldResource.getCsarVersionId());
-            }
             if (oldResource.getImportedToscaChecksum() != null) {
                 newResource.setImportedToscaChecksum(oldResource.getImportedToscaChecksum());
             }