Send Cancel Task Operation Failed With KeyError for Rabbitmq UserName

Description

There is an issue happened on 5.0.5 when execute kill-cancel workflow, the kill cancel never send the cancel task to the host agent so that to start canceling the desired process. It failed with the following error

When it tries to get the tenant information from the workflow context https://github.com/cloudify-cosmo/cloudify-manager/blob/master/mgmtworker/mgmtworker/worker.py#L152

This is working fine in 5.0.0

Steps to Reproduce

Environment:
OS (CLI), HA cluster, cloud provider
------------------------------------

Steps to reproduce:
------------------
1. Run Install workflow
2. While the install workflow is running, execute kill-cancel workflow
3. The status of the workflow will stuck in kill-canceling status
4. Check the logs of the mgmtworker.logs, there will be the error added to this jira

Expected result:
---------------

Actual result:
-------------

Why Propose Close?

None

Activity

Show:
Barak Azulay
December 29, 2019, 12:39 PM

just for clarifications,

I assume that 5.0 was tested on All-In-One , for 5.0.5 what deployment type was it (cluster? all-in-one)?

 

Mohammed Abuaisha
December 29, 2019, 12:47 PM

for 5.0.5 I was testing using ALL-IN-ON

Łukasz Maksymczuk
December 30, 2019, 2:58 PM

After CY-1043, tenant credentials are exposed via api, behind the tenants endpoint

Instead of accessing tenant rabbitmq credentials on the ctx, where they are not necessarily available, the cancel mechanism needs to use that api endpoint as well.

Without fixing this issue, kill-cancelling doesn't actually cancel agent tasks, it only cancels mgmtworker tasks

Mohammed Abuaisha
December 31, 2019, 7:30 AM

Is this now releases as part of the GA ?, can we test it ?

Mohammed Abuaisha
January 5, 2020, 8:30 AM

The issue is no longer appeared

Assignee

Łukasz Maksymczuk

Reporter

Mohammed Abuaisha

Labels

None

Severity

Critical

Target Version

5.0.5

Premium Only

no

Found In Version

5.0

QA Owner

None

Bug Type

legacy bug

Customer Encountered

No

Customer Name

None

Release Notes

yes

Priority

None

Epic Link

Priority

Blocker
Configure