Description of problem: When doing two (or more) concurrent deployments, all of them are syncing content as a first step of the installation. This presents a problem, because the first one to take the lock is blocking the others, which causes the sync subtasks and subsequently the Deploy task to fail. User needs to wait until the first sync is complete, then resume the failing task to do the second sync. Version-Release number of selected component (if applicable): rc4 - RHCI-6.0-RHEL-7-20150829.0-RHCI-x86_64-dvd1.iso How reproducible: Always Steps to Reproduce: 1. Start first deployment, then start second deployment 2. First deployment locks resources while syncing content 3. Second deployment is unable to sync and the Deploy task pauses with error Actual results: Both deployments trying to sync content at the same time, locking the resources and causing some of the subtask to fail Expected results: Content sync successfully ran, all deployments continue and finish Additional info: Possible solution to this is abstract the content sync from the installer, and make the installer call out for status.
For GA the solution to this might be light weight, perhaps we just disable the deployment button if another deployment in this organization is syncing content.