Version-Release number of selected component (if applicable): JON 3.2.ER5 How reproducible: always Steps to Reproduce: 1. create bundleGroup 2. assign it to any role 3. delete budnleGroup Actual results: it fails, ConstraintViolationException Expected results: Bundle group should be deleted. Same scenario works for resource groups. Additional info:
It's even worse. Checked on 3.2.0.GA deleting a bundleGroup does fail on ConstraintViolationException only if assigned role is assigned by some user. When this role has no users assigned it actually deletes the role as well.
I discussed this with Libor and I think he has found the root cause. He will be fixing and adding the necessary regression unit test.
in master commit a85776d3191076f851cbbcd45f2b6b01fc58d75d Author: Libor Zoubek <lzoubek> Date: Mon Feb 10 17:08:11 2014 +0100
release/jon3.2.x commit 90e0068993c5e0ce667f127f8f0c11e2d8bba7d4 Cherry-Pick master a85776d3191076f851cbbcd45f2b6b01fc58d75d Signed-off-by: Jay Shaughnessy <jshaughn>
Moving to ON_QA as available for testing in the following brew build: https://brewweb.devel.redhat.com//buildinfo?buildID=336752 Note: the installed version is still JON 3.2.0.GA by design and this represents part of the payload for JON 3.2.1 also known as cumulative patch 1 for 3.2.0.GA. How this will be delivered to customers is still being discussed.
verified bundle group is removed (from role as well), role without assigned user and with assigned is not removed during the bundle group remove.
re-verified in jon 3.2 + Cp1
JON 3.2.1 released week of 5/5/2014