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.
the same behaviour is seen as said in https://bugzilla.redhat.com/show_bug.cgi?id=886909#c17
Per coment 17, the fix should be to not log the 409 to stdout, since that is a valid use case: 2013-10-30T12:27:21-0400: [Worker(delayed_job host:sam13 pid:1635)] Provider#queue_import_manifest failed with RestClient::Conflict: Resources::Candlepin::Owner: 409 Conflict {"displayMessage":"Import is the same as existing data","requestUuid":"17f3fb96-525f-4c3c-8d43-721578bcd05e","conflicts":["MANIFEST_SAME"]} (POST /candlepin/owners/ACME_Corporation/imports) - 0 failed attempts 2013-10-30T12:27:21-0400: [Worker(delayed_job host:sam13 pid:1635)] PERMANENTLY removing Provider#queue_import_manifest because of 1 consecutive failures. Resources::Candlepin::Owner: 409 Conflict {"displayMessage":"Import is the same as existing data","requestUuid":"17f3fb96-525f-4c3c-8d43-721578bcd05e","conflicts":["MANIFEST_SAME"]} (POST /candlepin/owners/ACME_Corporation/imports)
removing the blockers since it is now a logging issue.
This is no longer occuring in the latest builds. Please re-open if it starts to happen again.