Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Syncing repo with typo in URL creates lock.


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


How reproducible:
always


Steps to Reproduce:
1. Create new product in webUI:
   Content -> Products -> [+ New Product]
     Name: ISEProduct
2. Create new repository in the product:
   Content -> Products -> ISEProduct -> [Create Repository]
     Name: ISERepository
     Type: yum
     URL: http://www.redhat.com/notExistingRepo
3. Sync it (using Content -> Sync Status ... do not trigger this, just fails,
   but I do not see the lock - strange (!))
   Content -> Products -> ISEProduct -> ISERepository -> [Sync Now]
   Also you can initialize sync using hammer.


Actual results:
Looks like some locks are left around.


Expected results:
Should fail without locks around or something.


Additional info:
To clean this, you have to release the lock:
  Monitor -> Tasks -> <your_failed_task> -> [Force Stop] -> [Force Stop]

I'm working on better handling of the error states in Dynflow as part of https://bugzilla.redhat.com/show_bug.cgi?id=1093124 so that at the end, it should finish the task with warnings instead of pausing in this case

Created redmine issue http://projects.theforeman.org/issues/6072 from this bug

Note for release nanny: depends on dynflow-0.7.0 and foreman-tasks-0.6.0

The changed in Katello were made in https://github.com/Katello/katello/pull/4219

created repository with wrong URL and synchronization task finished -> Verified.

Satellite-6.0.3-RHEL-6-20140612.1

This was delivered with 6.0.3, which is the Satellite 6 Beta.