Bug 1092588
Summary: | DEPLOYING and UNDEPLOYING statuses are in opposite for REST API deployment unit operations | ||
---|---|---|---|
Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Ivo Bek <ibek> |
Component: | Business Central | Assignee: | Shelly McGowan <smcgowan> |
Status: | CLOSED EOL | QA Contact: | Ivo Bek <ibek> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.0.2 | CC: | ibek, kverlaen |
Target Milestone: | DR2 | ||
Target Release: | 6.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-03-27 19:47:56 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ivo Bek
2014-04-29 14:05:10 UTC
Could you add a test that reproduces this problem? Thanks! I just realized that there might be a problem with BZ 1050894 if you work with the last changes. Fixed with this commit: https://github.com/droolsjbpm/droolsjbpm-integration/commit/1509b17022b4141e303dd7eef396d8ebcdb27184 (Among other changes, here: https://github.com/droolsjbpm/droolsjbpm-integration/commit/1509b17022b4141e303dd7eef396d8ebcdb27184#diff-e7fb6939eaedec362d0e943f20d7b449R48 ) However, the deployment operations were somewhat refactored, so there are a couple of other changes that helped fix this as well. Verified in BPMS 6.1.0.DR2 The current behavior is following: ACCEPTED -> UNDEPLOYING -> UNDEPLOYED ACCEPTED -> DEPLOYING -> DEPLOYED Additionally, I filed BZ 1139745 - After undeployment of a deployment unit which was previously deployed via REST API, status of the deployment unit remains DEPLOYED instead of NONEXISTENT. |