Actions
Bug #16266
closedpublishing content view after I have made repository available through HTTPS only fails: PLP0000: Failed to copy metadata.
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1219558
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
How reproducible:
always
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
Updated by Brad Buckingham over 8 years ago
- Subject changed from publishing content view after I have made repository available through HTTPS only fails: PLP0000: Failed to copy metadata. to publishing content view after I have made repository available through HTTPS only fails: PLP0000: Failed to copy metadata.
- Status changed from New to Duplicate
Duplicate of http://projects.theforeman.org/issues/15649
Updated by Brad Buckingham over 8 years ago
- Is duplicate of Bug #15649: conflict with dangling repo symlink and yum_clone_distributor added
Updated by Eric Helms about 8 years ago
- Translation missing: en.field_release set to 166
Actions