wrong plugin ID error

Description

Issue reported by customer c478 using CFY version 4.4.

The issue happens when a blueprint is uploaded, then a required plugin is removed and needs to be reinstalled. When creating the deployment the plugin id registered is not the same and deployment create fails:

2019-03-11 21:34:42.052 CFY <dcae_dtiapi_03_11_2019_001_dyh1b_01> 'create_deployment_environment' workflow execution failed: RuntimeError: Workflow failed: Task failed 'cloudify_agent.operations.install_plugins' -> Managed plugin installation found but its ID does not match the ID of the plugin currently on the manager. [existing: 08306439-17f0-437a-8fcd-5011884fc561, new: c749a3d4-eec3-455a-8979-6868706ecbcf]

Activity

Show:
Mohammed Abuaisha
March 10, 2020, 7:44 AM

Usually this should not happened and it could be that the plugin deleted from DB but not from the filesystem which cause the issue. I tried to re-produce it but without luck. Also I’m not sure how the managed plugin get installed during the deployment creation since it get installed when call cfy plugin upload and the only way to install plugin during deployment creation is when the plugin associated with blueprint is built form source.

If or can provided more information with exact steps the customer did so that I can try again that would be helpful to figure out how this exactly happened.

Ofer Yarom
March 10, 2020, 7:50 AM

Thanks. Would the workaround in this specific situation be to delete the items from the file system and re-upload?

Mohammed Abuaisha
March 10, 2020, 8:07 AM

In order to answer you question I need to know what the customer did exactly because during the deployment creation there is a try to install a managed plugin and I’m not sure if this is should happened or not because the managed plugin should be installed when running cfy plugin upload based on my knowledge.

Moreover, I did a quick testing which is:

  1. Upload the plugin to manager

  2. Upload Blueprint to manager

  3. Delete a plugin from the manager using cfy plugin delete and at the same time I simulated a test to delete plugin from the DB but not from the filesystem

  4. Then Upload the plugin again to the manager and got the same error which is make sense since there is a mismatch between the new uploaded plugin and the what have on the filesystem

  5. I never succeed to re-produce the same error on deployment creation

 

Jonathan Abramsohn
March 10, 2020, 10:21 AM

I couldn’t repro it either.

Please close the Jira.

Ofer Yarom
March 10, 2020, 11:01 AM

For ease of fix tracking I am setting this as done rather than Closed. I expect this one was resolved in between 4.4 and 5.0.5.

Assignee

Mohammed Abuaisha

Reporter

Eve Land

Labels

Target Version

5.1

QA Owner

Mohammed Abuaisha

Premium Only

no

Documentation Required

Yes

Why Blocked?

None

Release Notes

yes

Priority

None

Epic Link

Sprint

None

Priority

Unprioritized
Configure