https://pulp.plan.io/https://pulp.plan.io/favicon.ico2016-09-12T15:52:44ZPulpRPM Support - Issue #2248: metadata file copy results in error 'Content import of FILENAME failed - must be an existing file'https://pulp.plan.io/issues/2248?journal_id=144052016-09-12T15:52:44Zjsherril@redhat.comjsherril@redhat.com
<ul></ul><p>The only current way to resolve the issue is to run:</p>
<p>pulp-admin rpm repo remove metafile --repo-id=REPO_ID --match='repo_id=.*'</p>
<p>where REPO_ID is the repo you are copying from, resync the repo, and try the copy again.</p> RPM Support - Issue #2248: metadata file copy results in error 'Content import of FILENAME failed - must be an existing file'https://pulp.plan.io/issues/2248?journal_id=144312016-09-13T14:24:09Zipanova@redhat.comipanova@redhat.com
<ul></ul><p>How to reproduce that:</p>
<p>1. create repo1 and sync it ( with <a class="issue tracker-1 status-11 priority-7 priority-high2 closed" title="Issue: YumMetadataFile copy does not save its new storage_path (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/1944">#1944</a> present)<br>
2. create repo2<br>
3. copy yum_metadata_file from repo1 to repo2( there will in db 2 units of yum_metadata_file that will reference same storage_path due to <a class="issue tracker-1 status-11 priority-7 priority-high2 closed" title="Issue: YumMetadataFile copy does not save its new storage_path (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/1944">#1944</a>)<br>
4. Remove repo2<br>
5. Notice 1 yum_metadata_file among orphans<br>
6. Clean orphans( since in db 2 units of yum_metadata_file reference same storage_path, remaining unit after orphan clean will reference to non-existing storage path)<br>
7. Upgrade to 2.8.6, run migration( it will calculate correct storage path) + <a class="issue tracker-1 status-11 priority-7 priority-high2 closed" title="Issue: YumMetadataFile copy does not save its new storage_path (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/1944">#1944</a> will be fixed at this point.<br>
8. create repo3<br>
9. copy from repo1 to repo3<br>
10. observe traceback.</p>
<p>I am not sure if that can be fixed, that is just concatenation of circumstances where if you did all the steps listed above in same order you have no other choice than just re-sync repo. And if it is a repo without feed...then you're in very unpleasant non recoverable state.</p> RPM Support - Issue #2248: metadata file copy results in error 'Content import of FILENAME failed - must be an existing file'https://pulp.plan.io/issues/2248?journal_id=145672016-09-16T14:47:09Zamacdona@redhat.comaustin@redhat.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li><li><strong>Severity</strong> changed from <i>3. High</i> to <i>2. Medium</i></li><li><strong>Triaged</strong> changed from <i>No</i> to <i>Yes</i></li></ul><p>Priority is set high to investigate this. If it cannot be fixed, then the issue should be changed to making the recovery more accessible in a release note or troubleshooting doc.</p> RPM Support - Issue #2248: metadata file copy results in error 'Content import of FILENAME failed - must be an existing file'https://pulp.plan.io/issues/2248?journal_id=186992017-03-23T12:07:13Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-11 priority-7 priority-high2 closed" href="/issues/1944">Issue #1944</a>: YumMetadataFile copy does not save its new storage_path</i> added</li></ul> RPM Support - Issue #2248: metadata file copy results in error 'Content import of FILENAME failed - must be an existing file'https://pulp.plan.io/issues/2248?journal_id=374382019-04-12T20:18:08Zbmbouterbmbouter@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>CLOSED - WONTFIX</i></li></ul><p>Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" class="external">developer mailing list</a>.</p> RPM Support - Issue #2248: metadata file copy results in error 'Content import of FILENAME failed - must be an existing file'https://pulp.plan.io/issues/2248?journal_id=386432019-04-15T20:25:02Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> <i>Pulp 2</i> added</li></ul>