Bug 1217254

Summary: [GSS] (6.1.z) migration tool makes the disabled rule available again
Product: [Retired] JBoss BRMS Platform 6 Reporter: Andrea Hoffer <ahoffer>
Component: Migration ToolAssignee: Jan <jschatte>
Status: CLOSED EOL QA Contact: Tibor Zimanyi <tzimanyi>
Severity: high Docs Contact:
Priority: high    
Version: 6.1.0CC: ahoffer, ghu, jschatte, kverlaen, mbaluch, tzimanyi
Target Milestone: CR1   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1217113 Environment:
Last Closed: 2020-03-27 18:35:25 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:
Bug Depends On: 1217113    
Bug Blocks: 1220521, 1220522    

Comment 2 Andrea Hoffer 2015-04-30 19:29:59 UTC
Description:

When running the migration tool shipped by BPMS 6.1 against repository generated by BRMS 5.2, the guided rule that is disabled from 5.2 UI is again available after the migration.

Comment 3 Jan 2015-05-05 10:13:39 UTC
Fixed in master: http://github.com/droolsjbpm/drools-wb/commit/a82b649b4
Cherry-picked into 6.2.x: http://github.com/droolsjbpm/drools-wb/commit/442caaeb6

Dsibaled repository artifacts are no longer migrated, a warning is issued in the console output log.

Comment 4 Tibor Zimanyi 2015-05-19 11:39:14 UTC
Verified running migration on repositories from parent BZ. There is no rule gov.hhs.cms.ffe.rules.ee.eligibilitydetermination.aptceligibility - BTW100And400FPL_ESCOrNonESI in migrated git repo. Also verified on another project (migration tool integration tests).