Bug 1219558

Summary: publishing content view after I have made repository available through HTTPS only fails: PLP0000: Failed to copy metadata.
Product: Red Hat Satellite Reporter: Jan Hutař <jhutar>
Component: Content ViewsAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: UnspecifiedCC: bbuckingham
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-14 18:47:36 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:

Description Jan Hutař 2015-05-07 15:18:05 UTC
Description of problem:
When I publish content view and then you publish another version after I have made contained repository available through HTTPS only, it fails

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a product with a repository in it (published via HTTP - it is
   by default)
2. Create content view with that repository
3. Publish version of the content view
4. Make the repository available via HTTPS only (set "Publish via HTTP"
   to "no")
5. Attempt to publish another version of the content view

Actual results:
It fails

Expected results:
Should work

Comment 4 RHEL Program Management 2015-05-07 15:32:51 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 6 Bryan Kearney 2016-07-08 20:24:15 UTC
Per 6.3 planning, moving out non acked bugs to the backlog

Comment 8 Brad Buckingham 2016-08-24 12:52:14 UTC
Created redmine issue http://projects.theforeman.org/issues/16266 from this bug

Comment 9 Brad Buckingham 2016-09-14 18:47:36 UTC

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