Bug 1085247

Summary: promoting content view version which is being published fails: required lock
Product: Red Hat Satellite Reporter: Jan Hutař <jhutar>
Component: WebUIAssignee: Brad Buckingham <bbuckingham>
WebUI sub component: Katello QA Contact: Katello QA List <katello-qa-list>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: unspecified CC: bbuckingham, cwelton, mmccune
Version: NightlyKeywords: Triaged
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-16 21:20:55 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 Jan Hutař 2014-04-08 08:11:28 UTC
Description of problem:
When you attempt to promote content view version which is being published, it fails. If this is not supposed to work, it should not be allowed on webUI. If it is, it should work.


Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140404.0


How reproducible:
always


Steps to Reproduce:
1. Create Dev environment
2. Sync RHEL6 RPMs and Kickstarts
3. Create content view with them
4. Create new version of the content view
5. While it is being published (I had a green progress bar in about 20%)
   click to "Promote" button, select your "Dev" environment and press
   the button


Actual results:
It fails with this error in webUI:

required lock: #<ForemanTasks::Lock:0x007f001480bf68> conflicts wiht [#<ForemanTasks::Lock id: 174, task_id: "3c3641fb-03ba-4853-89dd-e8d9d0d654bb", name: "read", resource_type: "Katello::ContentView", resource_id: 3, exclusive: true>] 


Expected results:
If this is not supposed to work, it should not be allowed on webUI. If it is, it should work.

Comment 1 RHEL Program Management 2014-04-08 08:24:57 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Brad Buckingham 2014-07-16 21:20:55 UTC

*** This bug has been marked as a duplicate of bug 1104104 ***